writing-plans

To break down complex engineering tasks, this tool generates bite-sized, testable steps with defined file changes, tests, and commits, saving the implementation plan directly to docs/plans/ as a markdown file.

The best way to document multi-step feature specs is using a standardized frontmatter schema and structured Task N sections, ensuring reproducible development roadmaps and clear knowledge transfer for new engineers.

You structure a development roadmap by drafting a plan document with guided task hierarchies that define file changes, tests, docs, and commits for each step, reducing ambiguity and rework before coding begins.

No, this planning workflow requires no specific project dependencies, operating independently to enforce a standardized frontmatter schema in SKILL.md and save generated plans to docs/plans/YYYY-MM-DD-<feature-name>.md.

You should use a step-by-step implementation plan when drafting specs for multi-step features, coordinating engineering work across a team, or needing to document assumptions and context for reproducible development.