The idea is that the Project Spec should be accessible to the user and should be used to make changes.
• The Spec is initially written by an Agent based on User prompt.
• It should be accessible to the user as SPECIFICATION.md
• User should be able to change/update it.
• User should be able to direct an Agent to change/update it.
• There should be a function to "notify" the Agents about changes, and integrate those changes into ongoing project development.
Examples:
If I could say e.g. "I have updated 4.2 in the Spec to address this issue."
Or "I have added feature 4.3"
Or "Please redraft feature 3 in the Spec, to use flexbox."
This would give absolute clarity and confidence. This would solve several related issues, which I will link in this issue.
blarvin
commented
4 months ago
Version
VisualStudio Code extension
Suggestion
The idea is that the Project Spec should be accessible to the user and should be used to make changes.
• The Spec is initially written by an Agent based on User prompt. • It should be accessible to the user as SPECIFICATION.md • User should be able to change/update it. • User should be able to direct an Agent to change/update it. • There should be a function to "notify" the Agents about changes, and integrate those changes into ongoing project development.
Examples: If I could say e.g. "I have updated 4.2 in the Spec to address this issue." Or "I have added feature 4.3" Or "Please redraft feature 3 in the Spec, to use flexbox."
This would give absolute clarity and confidence. This would solve several related issues, which I will link in this issue.
I have a thread about this in the Discord https://discord.com/channels/1145718759550615582/1232264068077719562 , and several people are making constructive comments and ideas along these lines.