feature-planner

Phase-based planning structures features into 3-7 phases with defined outcomes, 1-4 hour estimates, and quality gates that prevent progression until validation criteria are met and user approval is obtained. This approach organizes work systematically and ensures quality checkpoints throughout delivery.

A feature plan document includes objectives, phased breakdown with success criteria, checklists, risk assessment, rollback strategies, and progress tracking. The Skill generates this from plan-template.md and produces docs/plans/PLAN_<feature-name>.md as a reusable reference.

Test-first planning applies Red-Green-Refactor cycles within each phase, ensuring quality discipline from the start. This prevents rework and aligns development with acceptance criteria before implementation begins.

Yes. Phase-based planning with explicit approval gates ensures team alignment by breaking features into clear milestones, defining success criteria, and requiring stakeholder sign-off at each gate before advancing to the next phase.

Phase-based planning adds structure with quality gates, incremental delivery windows (1-4 hours per phase), risk assessment, and rollback strategies. Task lists lack this gating discipline and risk mitigation, making them less suitable for complex feature coordination.

Feature planning typically spans 1-4 hours per phase depending on complexity. A complete plan for a multi-phase feature like an onboarding flow takes several hours but reduces downstream rework and team misalignment significantly.