Right way to change Spec after /implement

[pvgueiros]

What is the best way to make changes in specification & implementation after you've already run /implement? Changing files manually is very time-consuming. You need to find the right places, search multiple files, etc. And there's always the risk of missing something. I tried using /specify again, followed by the change request, but it created a new branch and all new files and added my request as a new feature. 🥺

Is there some way to achieve this in the same branch, by requiring the LLM to modify the original files? I've been telling the AI "review all spec docs and change where it says X to Y". But it would be nice to have commands for this, that reviewed and changed all relevant docs, added new tasks, and became ready for re-implementation with something like "/update-spec" "/update-plan" "/update-tasks" and then "/implement tasks H through L", considering H through L are the new tasks.

This would preserve the "living" nature of the specification files.

[MRiabov]

oh yes. And after working for 2 months on a project, when your projects have 90 tasks - (which is the case for me), reintegrating changes for 50th time again and again becomes pointless to the point of slowing you down.

OpenSpec does it better with changes/ feature.