Replies: 2 comments 1 reply
-
Good point. Can't this be solved with constitution.md? tks |
Beta Was this translation helpful? Give feedback.
1 reply
-
Very excited to see Spec-Kit as I’ve been working on something similar after disappointing experiments with prompt engineering. One key issue is recognizing that there will be always be existing code in various forms. It’s important that if something exists not to try and change it if it’s already working. Code analysis against the spec is key vs. just spitting out new code |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a suggestion for Spec-Kit.
When someone specifies a requirement, the agent should first check for existing features or code. If it recognizes existing implementations, it would make more sense to generate tasks that improve or extend them, rather than creating entirely new ones. This approach would also help existing projects by addressing bugs more effectively. I hope this feedback helps.
Thanks
Waheed
Beta Was this translation helpful? Give feedback.
All reactions