revise-plan

To revise an implementation plan without affecting in-progress tickets, update only todo items while enforcing hard rules to never modify in-progress, done, or merged tickets. Re-map dependencies and save the revised plan to docs/tickets/$FEATURE.md.

The best way to apply feedback and update project docs is to revise revisable tickets by altering descriptions, scope, and dependencies. The revised implementation sequence is then saved back to docs/tickets/$FEATURE.md to synchronize the project plan.

Ticket locking works by identifying in-progress, done, and merged-to-cp tickets, then enforcing hard rules to prevent changes to them. Feedback is applied to docs/tickets, docs/requirements, and docs/architecture files while preserving all locked tickets.

Yes, you can add or remove tickets from an existing plan without churn by revising only todo tickets. This approach locks in-flight work, re-maps dependencies for the remaining tickets, and updates the implementation sequence to reflect the new scope.