writing-plans

To turn vague software specifications into actionable implementation plans, you decompose requirements into structured tasks, defined files, tests, and milestones. This ensures comprehensive task breakdown and clear ownership before any code is written, outputting a ready-to-save plan document.

The best way to break down feature development tasks for multiple teams is generating a detailed implementation plan with precise task decomposition. This enforces a consistent plan structure, scope checks, and measurable milestones for cross-cutting improvements.

You create a structured plan document with task granularity and milestones by applying consistent planning guidelines to your specification. The output is a documentation-ready file containing defined files, tasks, tests, and a clear plan header.

Yes, you can use this implementation plan generation process for cross-cutting software improvements. It applies directly to multi-team software projects and feature development where precise task decomposition and measurable milestones are required.

You should save generated implementation plan documents under the docs/superpowers/plans directory. The tool outputs a ready-to-save plan document using a date-based filename within this specific location.

Before generating a software implementation plan from a spec, you need a specification detailing the requested feature. The planning process then converts this input into a complete implementation plan with defined scope, tasks, tests, and milestones.