implementlisted

# Transmute Implement — Stage 5: Feature Implementation Orchestrator Orchestrate the implementation of a COMPLETE product using Claude Code Agent Teams. Read the PRD, identify ALL features, and systematically implement every one — including backend, frontend, and tests — with quality gates between features and a final full-product integration verification. Read the detailed guide at `${CLAUDE_SKILL_ROOT}/references/implementation-detailed-guide.md` for the complete teammate instructions, testing pitfalls, and coordination protocol. ## Critical Framing: Full-Build Approach Build the COMPLETE product. Every feature in the PRD is implemented in this run. There is no MVP gate, no "good enough for Phase 1" checkpoint. Features are implemented in dependency order (P0 -> P1 -> P2 -> P3), but ALL priority levels are built. P0-P3 determines the build ORDER, not the build SCOPE. If Stage 5B audit later identifies systemic gaps (6+ Category C issues, OR 6+ total unfixed issues, OR 3 consecutive FAIL-RETRY outcomes triggering a FAIL-ESCALATE gate), the lead must re-run Stage 5 for those specific features — but features are never skipped, only reworked. When you reach the end of the queue, the product is complete. ## Post-Implementation Quality Gate After this stage completes, Stage 5B (Implementation Completeness Audit) will scan ALL features for: - Stub components that were never filled with real logic - Duplicate inline implementations that bypass scaffold components - Missing t