multi-phase-feature

Multi-phase feature development requires a disciplined, phase-driven workflow with strict phase-by-phase progress and guardrails to prevent scope creep. Breaking work into defined phases with explicit success criteria enables controlled delivery and reduces integration errors across complex product features.

The best way to plan a multi-file feature is using a discovery-first workflow that studies existing patterns before coding. Generating an implementation plan coordinates backend routes, frontend pages, and data migrations incrementally, ensuring alignment with project conventions.

A copy-first pattern works by copying proven implementations exactly, then tailoring them to the new feature. This approach accelerates delivery while preserving reliability, ensuring new code aligns with established project conventions before adaptation.

You need a phased implementation workflow when adding complex product features requiring frontend, backend, and documentation steps. Multi-phase workflows are essential for features spanning multiple files, APIs, and UI components where strict phase-level success criteria maintain traceability.

You track progress during multi-phase feature development using todo-tracking and phase-specific tests. The workflow produces documentation updates and phase-level success criteria to maintain traceability, ensuring each implementation phase is validated before progression.

A phase-based workflow for feature development is limited by its strict phase-by-phase guardrails, which may slow rapid prototyping. This approach is designed for complex, multi-file features requiring discovery and testing, not for simple, single-file changes.