feature-development

A structured feature development workflow systematically guides new feature creation through defined phases from discovery to summary. You need it to prevent rushing into implementation without proper codebase exploration, architecture design, and user validation.

You manage parallel development by utilizing parallel subagents for codebase exploration and architecture design. This approach enables comprehensive analysis of your software design before moving to the actual implementation phase.

You prevent rushing by implementing explicit approval gates between development workflow phases. These validation checkpoints ensure due diligence is completed during codebase exploration and architecture design before proceeding to implementation.

The best way to start a new feature development process is to begin with a Discovery phase to build context. This initiates a 7-phase workflow including clarifying questions, architecture design, implementation, code review, and summary.

No, this feature development workflow does not require specific external dependencies. It operates independently using scripts and references to manage the 7-phase process, parallel subagents, and approval gate validations.

Code review fits into the software design workflow as the sixth phase of the 7-phase feature development process. It follows implementation and ensures quality before the final summary phase completes the structured workflow.