writing-plans

To turn specs into implementation plans, you provide your requirements to generate a comprehensive document with task decomposition, file-structure mapping, and acceptance criteria. This ensures reproducible work and reduces ambiguity before touching code.

Task decomposition is breaking down vague project requirements into concrete, auditable milestones and step-by-step guidance. It explicitly maps required files, tests, and review steps to guide fast, reliable feature delivery.

You generate a plan document by providing a project spec, which creates a structured markdown file saved to docs/superpowers/plans/. It enforces header templates and explicit file and test touch lists to guide implementation.

Yes, this planning approach works for projects with minimal context. When starting a feature, the generated plan outlines required files, tests, and review steps, enabling fast and reliable delivery even with sparse initial requirements.

The best way to ensure consistent implementation plans is using reusable plan templates and guardrails. This enforces a standardized plan-document structure and header templates, reducing rework by documenting tasks and acceptance criteria uniformly.