plan-decompose

To decompose work into serial milestones, you provide a defined project design summary to generate a reviewable delivery plan. This produces explicit milestone structures, including goals, scope, testing specs, and technical routes for traceability.

Milestone-based planning splits discovered work into serial phases to ensure controlled progress and traceability. You need it when a project has a defined design summary and requires reviewable delivery plans with clear validation and audit focus.

You generate a delivery plan by triggering the decomposition workflow with your project context. It outputs structured milestones featuring defined expected artifacts, research requirements, technical routes, risks, alternatives, and validation specifications.

Yes, milestone planning requires a defined design summary as input. The decomposition process relies on this existing project context to accurately split work and generate structured, reviewable milestone-level plan artifacts.

The best way to structure milestones for reviewability is to decompose work serially with explicit goals, scope, testing specs, and audit focus. This ensures each delivery phase provides structured outputs and safe defaults for cross-cycle traceability.

A key limitation is its reliance on a pre-existing design summary; without discovered work and defined context, serial milestone decomposition cannot produce reviewable delivery plans. It is specifically structured for explicit milestone planning and auditing.