Cleanup after implementation

[masawik]

There is a feeling that the plan, tasks, research and quickstart files are temporary files that must be deleted after launch/implementation and the implementation details are consolidated into some kind of cumulative file.
Because now, if you decide to go back to the branch and change some implementation detail, then these files are being overwritten and the change is already described in them, not the original feature. Such files become completely useless token eaters.

How is it supposed to work with such changes after/implement in this SDD paradigm?

my case:

• /specify -> /clarify -> /plan -> /tasks -> /implement
• Merge into master
• Awareness that the feature needs to be redone
• Return to the feature branch
• /clarify -> /plan - and at this point the plan begins to overwrite

[mnriem]

The answer as always is it depends on your own requirements. Some folks like the specifications to be living documents that must stay in sync with the codebase (more like an epic). Which is why there are extensions that address that. Others see them as artifacts that merely directed the flow of one unit of work (more like a work item).

Whichever way you decide to work. If you treat them more as work item it is a continued flow of /specify -> /implement. If you decide to treat them as Epic see the extensions at https://github.com/github/spec-kit/tree/main/extensions#available-community-extensions and use whichever one serves your use case.