feature-dev

Multi-file feature development is planned using a seven-phase workflow that enforces design-first execution, mapping required files and modules before implementation. This structured process ensures architecture-driven changes are carefully staged.

A design-first approach mandates exploration and questions before any code is written. It requires mapping a blueprint of required files and decisions in earlier phases to prevent bad architecture and rework.

You need a structured workflow when implementing a new feature that requires multiple files and careful planning. It is applicable for multi-module features and teams seeking rigorous planning and clear handoffs.

Mandatory exploration and questions phases are required because understanding the codebase prevents bad architecture, and verifying assumptions avoids rework. Skipping these phases leads to poor design decisions.

Skipping the review phase limits your ability to catch issues early, as self-review catches 80% of problems. You also lose the structured handoffs required for completion if scope grows beyond the original request.

No, you must never write code before Phase 5 because the workflow enforces a design-first execution. Code is only implemented after mapping required files, modules, and architectural decisions.