spec-update

To automate spec updates, this Skill guides an agent through creating, implementing, and reviewing update documents. It preserves all in-place updates in the original feature directory, enforcing incremental update-xxx.md numbering to track changes over time without creating new folders.

Yes, existing plan.md and summary.md files are strict prerequisites to start the update workflow. The Skill requires these documents to exist in the same directory as the newly created update-001.md file to properly guide the end-to-end feature update cycle.

The best way to manage incremental versioning is through enforced update-xxx.md sequencing. This Skill automatically guides agents to create update-001, update-002, and subsequent files, preserving previous versions in place to maintain a clear historical track of specification changes.

You can use a single agent for standard execution or enable multi-role collaboration for larger updates. The Skill supports both workflows, allowing flexible management of the end-to-end update cycle depending on the complexity and scale of your feature changes.

To create an update document without losing original plans, generate an update-001.md file in the same directory as your plan.md. The Skill enforces in-place updates, ensuring original specifications are preserved while guiding the agent through implementing and reviewing the new changes.