-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Description
Hi, I have a few questions about how to correctly use the Spec Kit workflow. I want to make sure I’m following the intended best practices.
- When should I use the specify command?
Should it only be used at the beginning of a new feature? I noticed that running specify automatically checks out a new branch. Also, for the plan stage: if the technical implementation feels straightforward and there’s nothing special to describe, is it acceptable to leave the technical details empty and just rely on the existing architecture?
2.During implement, there are many test-related tasks.
Are all of these mandatory? Or is it acceptable to skip certain testing tasks depending on the context?
3.If I encounter issues or realize the implementation direction needs adjustment while running implement, how should I report that?
Is there a recommended Spec Kit command for feeding back the error or updating the workflow? Or should I manually communicate the issue and wait for updated instructions?
4.If I discover additional small requirements either during implement or after finishing plan, what is the recommended way to add them into the workflow?
Should I use a specific Spec Kit command to append or modify the specification?
5.After implement is completed, I remain on the auto-created feature branch.
Is there a Spec Kit command that can merge the feature branch back into main? Or is it expected that I manually create a pull request / merge the branch myself? What is the recommended workflow?
6.If I skip some tasks during the implement phase and then move on to another feature, how can I later return to the previous workflow state and let Spec Kit continue the unfinished tasks?
Is there a recommended command or workflow for resuming an incomplete implement session, or should I manually check out the feature branch and rerun a specific Spec Kit command?
Thanks in advance for your guidance.