feature-builder

Systematic feature development mandates Phase 0 architecture documentation before coding begins, requiring explicit user approval at strict quality gates to ensure architectural integrity and prevent context loss.

Feature development state is managed across sessions by tracking progress and decisions in a dedicated markdown progress tracker, enabling seamless session recovery without losing architectural context or workflow status.

Paired programming integrates into feature development through a collaborative 'two-in-the-box' approach, facilitating shared understanding and meeting quality gates via specialized agents for code review and documentation checks.

Yes, the 8-phase workflow guides feature implementation from initial architecture documentation through coding, thorough testing, and final validation, enforcing quality gates and documentation updates throughout the entire lifecycle.

Explicit user approvals are required at critical junctures during feature development, specifically after Phase 0 architecture documentation and before proceeding through subsequent quality gates and validation phases.