writing-plans

To generate an implementation plan, provide a feature spec and the skill outputs a self-contained Markdown document with task decomposition, file maps, and testing steps. This plan details exactly which files to touch and what code to write before execution.

Task decomposition breaks complex software tasks into actionable steps and reviewer checkpoints. You need it during feature brainstorming to produce work breakdowns that assume an engineer has zero codebase context, ensuring minimal back-and-forth during execution.

Yes, you can use this to map out file and module responsibilities before coding. The generated plan includes clear file mapping with defined interfaces, ensuring engineers know exactly which files to touch and how to validate the changes.

The best way to structure an implementation plan is using a standardized frontmatter header, task sections, and reviewer checkpoints. This enforces a plan structure that includes end-to-end testing steps, documentation checks, and commit guidance.

Yes, implementation plan generation works without external dependencies. The skill operates independently to produce self-contained Markdown plan documents ready for execution, requiring only a feature spec as input to generate the comprehensive work breakdown.