-
Officially Documented WorkflowAccording to the official documentation, the workflow for using SpecKit is: constitution → spec → plan → tasks → implement There are also optional steps:
References: Commands and Guide details My UnderstandingFrom my experience using it, during the analyze step, SpecKit provides suggestions such as modifying the tasks, plan, or even the spec. When it suggests modifying tasks:I prefer not to manually edit the file. Instead, I would rather modify the plan and regenerate the tasks. This is because the tasks file contains many implicit SpecKit conventions (e.g., Phase, checkpoints, [P], [US], [T00X], etc.), which are auto-generated. I’m not familiar with these conventions, and even if I try to imitate them, the internal references become difficult to manage. When it suggests modifying the plan:The plan also has its own structure and syntax, which differs from the original description I provided when using the When it suggests modifying the spec:The spec also follows its own structure and syntax, which differs from the original My Questions
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
You have 4 options when it comes to modifying what Spec Kit produces:
There is no hard and set rule for when to use which and how many times. |
Beta Was this translation helpful? Give feedback.
You have 4 options when it comes to modifying what Spec Kit produces:
There is no hard and set rule for when to use which and how many times.