spec-writer

To create execution-ready specifications for large repository changes, convert rough ideas into a structured spec folder containing requirements.md, plan.md, and tasks.md to define scope, constraints, and ordered task lists.

Breaking down a major software refactor into actionable tasks requires generating a numbered spec folder with a tasks.md file, ensuring explicit assumptions and acceptance criteria align with live repository conventions.

You need formal specification documents instead of ad hoc notes for a migration when the scope is too large, requiring clear requirements, implementation plans, and a validation checklist checked against the live repository.

To ensure implementation plans align with existing repo conventions, generate a spec package that forces explicit assumptions and re-checks the plan against the live repo conventions rather than applying generic templates.

Yes, you can use a structured spec package for feature work, refactors, migrations, cleanups, and workflow changes, producing targeted requirements, plans, and task lists to remove ambiguity from non-trivial repository modifications.