writing-plans

To generate an implementation plan, provide a feature specification and the skill produces a comprehensive document mapping out files to touch, modifications, tests, and goals. It enforces a Plan Document Header and task structure, saving the plan to a date-stamped markdown path.

Task decomposition for multi-subsystem work breaks complex specifications into bite-sized tasks with clear boundaries. This process defines incremental work steps, files to modify, and validation checkpoints before coding begins, ensuring repeatable and auditable workflows.

To structure a plan document, the skill enforces a standardized Plan Document Header and a task-by-task breakdown. It maps out files touched, modifications, tests, and goals, saving the output to docs/superpowers/plans with a date and feature name for versioning.

Yes, a complete specification is required before creating an implementation plan. The skill generates an end-to-end plan from the given spec to guide engineers, ensuring all steps, files, tests, and handoffs are defined before touching code.

The best way to plan complex tasks is generating a detailed implementation plan that decomposes work into bite-sized tasks with clear boundaries. This approach defines files to touch, modifications, tests, and goals beforehand, enabling precise planning before coding begins.

Automated plan generation is not suitable for single-step or simple tasks that lack multi-subsystem complexity. The skill is designed for complex, multi-step work where clear decomposition into tasks, files to touch, and validation steps is essential for reproducible workflows.