Replies: 1 comment
-
|
See my idea: #1255 I don't know if this the answer you want but the kind of change you describe is more in the realm of "made a small CR" than a "new feature". Also because if you work with speckit and a coding agent a spec like a login form will have, 99% sure, the requirement to gracefully manage wrong credentials of forgotten passwords, if not in the specify phase for sure the clarify step. But the question remains, a spec change like "show also this field from the database" how it should be managed? I did a proposal... |
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'm not sure about the flow here.
I've run the
/speckit.specify
/speckit.clarify
/speckit.plan
/speckit.tasks
/speckit.analyze and
/speckit.implement commands.
Now here's the thing. Everything looks good, but I have a few things that I want to add to the spec. Let's say I have a login form. When the user enters wrong credentials the form just resets. I want to add a functional requirement that the user should be informed if wrong credentials are entered. I assume when adding that the plan.md and tasks.md must be updated accordingly.
What's the best way to do this? I do not want to create an entire new feature for this.
Beta Was this translation helpful? Give feedback.
All reactions