feature-planner

A phase-based feature plan breaks work into 3-7 phases, each delivering complete runnable functionality with Red-Green-Refactor cycles. The plan enforces quality gates between phases and generates a markdown document requiring user approval before proceeding.

A quality gate in project management is a validation checkpoint enforced before transitioning between phases. In phase-based planning, quality gates ensure incremental delivery and early validation of each work item before subsequent phases begin.

Structure a roadmap by generating a phase-based plan that includes defined dependencies, risk assessment, rollback strategies, and a success criteria checklist. Each phase delivers runnable functionality and tracks progress using markdown checklists.

Phase-based planning suits features requiring 3-7 phases. It scales from small features needing structured validation to larger projects requiring dependency mapping, risk assessment, and rollback strategies with incremental runnable delivery.

Track phase completion progress using markdown checklists within the generated plan document. The planning workflow monitors completion of each phase's defined quality gates, dependencies, and success criteria checklist items.

Avoid phase-based planning workflows for tasks requiring fewer than three phases or when work cannot be structured into incremental runnable deliverables. The approach requires distinct phases with quality gates and user approval steps.