writing-plans

To generate a step-by-step implementation plan, provide a feature name to produce a comprehensive, task-focused roadmap. The output covers files touched, testing, and documentation, saved as a date-stamped markdown file under docs/plans.

Documenting an implementation roadmap for zero-context developers requires detailing every file to touch, code to write, and test to run. Bite-sized tasks ensure explicit upfront planning, verification, and frequent commit practices are clearly defined.

Structure task analysis and design plans by breaking down multi-step engineering tasks into bite-sized actions. Each task details specific files, tests, documentation checks, and success criteria to guide implementation and support frequent commits.

Yes, you can create a feature roadmap without external dependencies. The skill operates standalone to generate detailed plans, requiring only a feature name to output a date-stamped markdown file with task granularity and verification steps.

A limitation when generating detailed implementation plans is that it assumes execution in a dedicated worktree and strictly saves outputs to docs/plans. It focuses on explicit upfront planning rather than dynamic runtime edge case handling.