feature-planner

Phase-based feature planning breaks work into 3-7 phases of 1-4 hours each, with quality gates between phases. This Skill automates that structure, generating roadmaps with Red-Green-Refactor cycles, test coverage targets, and explicit approval checkpoints before proceeding to the next phase.

A structured feature plan documents scope, deliverables, test-driven development cycles, quality gates, user approvals, and rollback strategies organized by phase. This Skill auto-generates these plans as docs/plans/PLAN_<feature-name>.md with measurable test coverage targets and risk assessment for each phase.

Yes. Phase-gated planning organizes large features into incremental, runnable phases with explicit scope and approval workflows. Each phase delivers testable functionality within 1-4 hours, making it ideal for task breakdown, roadmap creation, and development strategy structuring.

Test-first development integrates through Red-Green-Refactor cycles enforced at each quality gate. This Skill embeds test coverage targets and measurable quality checks into every phase, ensuring code meets standards before progressing and satisfying test-driven development requirements.

Before advancing phases, explicit user approval is required after quality gates are met. This includes verification of test coverage targets, Red-Green-Refactor completion, and any risk assessment or rollback strategy validation for that phase.