feature-planner

Phase-based feature planning breaks work into 3-7 structured stages with defined goals and tests. Quality gates enforce validation checks at each phase boundary, requiring user approval before proceeding to ensure stakeholder alignment and incremental delivery.

Create a phased roadmap by drafting 3-7 phases where each delivers runnable functionality within 1-4 hours. Define goals, tests, and quality gates for every phase, then output a reviewable plan document with markdown checkboxes to track progress.

Feature planning supports incremental delivery by requiring explicit user sign-off before any implementation begins. Each phase produces runnable functionality within strict timeboxing, ensuring stakeholders review and approve measurable quality gates at every stage.

Track feature planning progress using markdown checkboxes embedded in the plan document. This approach reflects phase completion visually, aligns with quality gates, and provides a clear incremental delivery status for stakeholder review and approval.

Yes, phase planning operates without external dependencies or components. It generates a structured plan document from scratch, guiding teams through 3-7 phases with defined goals, tests, and quality gates for immediate review and approval.

Avoid phased feature plans when deliverables cannot be broken into 3-7 phases or when runnable functionality cannot be achieved within 1-4 hours per phase. Quality gates require explicit validation, making it unsuitable for continuous, unstructured workflows.