Handling Modifications in the Spec Kit Workflow

[XKonstX]

Modifications to implemented features are an inevitable part of the development lifecycle, necessary for improvements or corrections.

The key question is: What's the right approach for applying modifications to features developed using the spec kit workflow?

My current thinking: If a complete feature has been implemented and is considered "done," but an improvement or fix is later required, treating the modification as a brand-new feature seems wrong. The original feature needs modification.

I believe an impact analysis based on the proposed modifications is the best path forward, but I'm unsure if a structured approach for this exists within the current spec kit tooling or methodology.

[wilsonneto-swe]

The usual way I am solving it is asking the agent to check my last updates and fix/apply any needed update in the spec and adding a follow-ups section in the plan with the changes. If I am planning to change I also ask the agent the same but also to add the new tasks.

So that way the spec will still be updated, for docs purpose the plan will show how the things really went, the plan execution + some follow up fixes.

But yes, a more structured way or a command to do that would be great.