feature-dev

A phased feature development workflow coordinates end-to-end implementation across multiple modules using structured stages like discovery, codebase exploration, architecture design, implementation, and quality review to reduce ambiguity and misalignment.

To implement a feature across multiple modules, follow a structured workflow: discover scope, explore the codebase with multi-agent strategies, clarify questions, design architecture, implement code, and review quality with explicit gating approvals.

Codebase exploration uses multi-agent strategies to map existing architecture and dependencies during the discovery phase, ensuring the subsequent architecture design aligns with the current codebase before any implementation begins.

Yes, this phased workflow supports agile feature development by requiring explicit gate decisions, stakeholder communication, and structured design reviews before moving from discovery and exploration into active implementation and quality review.

The best way to ensure alignment during feature development is to use clear gating questions, clarifying questions, and approval steps before implementation, combined with thorough documentation and stakeholder communication throughout the workflow.

Yes, explicit gate decisions are required after architecture design and codebase exploration to ensure stakeholder alignment and maintainable architecture before proceeding to the implementation and quality review phases.