feature-planner

To create a phase-based feature plan, you provide feature goals to generate a structured roadmap with 3-7 phases. Each phase includes quality gates and test-first criteria to validate readiness before proceeding to the next development cycle.

The best way to structure a roadmap for incremental delivery is by breaking features into phase-sized work units. This approach enforces a test-first workflow with clear quality gates, ensuring each phase delivers runnable functionality and aligns stakeholders.

You generate a feature plan document by triggering plan generation with your feature goals. The system outputs a PLAN_<feature-name>.md file in the docs/plans directory, containing clear objectives, dependency mapping, and rollback strategies for stakeholder alignment.

Yes, you can include risk assessment and rollback strategies in your feature roadmap. The planning process supports dependency mapping, risk evaluation, and rollback planning alongside progress tracking to ensure structured delivery across development cycles.

Phase-based planning works well for iterative feature development by enforcing gated approaches with phase-sized work units. It supports iterative planning cycles, ensuring each phase delivers runnable functionality validated by test-first quality gates.

You need quality gates in a feature planning roadmap when managing complex features requiring incremental delivery. Gates validate readiness before proceeding to subsequent phases, ensuring test-first criteria are met and stakeholder alignment is maintained throughout development.