phased-delivery-plan

To break down a roadmap step into branch-sized implementation plans, generate a single markdown file containing 2–4 units. Each unit must specify objectives, prerequisites, progressive tasks, exit criteria, evidence, and handoff outputs for predictable progressive delivery.

Progressive delivery planning splits large roadmap items into reproducible branch-sized units with explicit entry and exit gates. This enforces single-step scope and requires evidence validation before stage promotion to eliminate hidden dependencies.

Create a phased delivery plan by generating a docs/plans/*.md file for one roadmap step. Structure 2–4 branch-sized migration units with prerequisites, progressive tasks, exit criteria, and evidence to ensure safe incremental rollouts.

Phased delivery planning supports scaffolding new features, refactoring, and migrations by producing unit-level templates with clear gates. Each unit includes objective, prerequisites, references, tasks, exit criteria, evidence, and outputs for the next step.

The best way to enforce exit criteria and evidence is applying a final stage gate that consolidates validation across all units. Each branch-sized unit must independently satisfy its exit criteria and evidence requirements before stage promotion.

You should not use a single-step phased delivery plan when a task spans multiple roadmap steps or lacks clear scope boundaries. This approach strictly enforces one roadmap step per plan to maintain predictable ordering and avoid ambiguous scope.