Build Auto

# Build: Auto (Full Feature Implementation)

**AUTOMATED FULL-STACK IMPLEMENTATION**

Fully automates planning, development, review, and deployment of: **$ARGUMENTS**

---

## ⚠️ WARNING: UNATTENDED EXECUTION

This command runs for HOURS and makes autonomous decisions. Use only when:
- ✅ All specs are complete and validated
- ✅ You trust the automation to implement without supervision
- ✅ You're prepared for the agent to make implementation choices
- ✅ You can review the commits later

**This is NOT a toy command. It will write real code and commit it.**

---

## What This Does

Orchestrates the ENTIRE implementation workflow autonomously:

┌─────────────────────────────────────────────────────────────┐ │ AUTOMATED WORKFLOW │ └─────────────────────────────────────────────────────────────┘

Phase 0: Pre-Flight Checks → Validate all specs exist → Run /spec-validate (abort if BLOCKERS) → Check git status (abort if dirty) → Estimate total duration → Ask for final confirmation

Phase 1-8: Implementation Loop (AUTOMATED) FOR EACH PHASE: 1. Planning → If Phase 1: Run /build-plan (auto-select strategy) → If Phase 2+: Run /build-plan-next (rolling wave)

2. Implementation
   → Run /build-phase <feature> <N>
   → Developer agent implements ALL tasks in phase
   → Reviewer agent reviews each task
   → Fix any rejections automatically

3. Validation
   → Run /validate (architecture, build, tests, analytics)
   → If validation fails: Attempt auto-fix (1 retry)
   → If still fails: STOP and report

4. QA Verification Gate (NEW)
   → Invoke android-qa agent for phase verification
   → Verify FR-XXX requirements are actually implemented
   → Check traceability matrix accuracy
   → If missing implementations: Return to step 2

5. Commit
   → git add all changed files
   → git commit with detailed phase summary
   → Log progress to build-log.md

6. Status Update
   → Update progress file
   → Estimate remaining time
   → Continue to next phase

Phase 9: Finalization → Run final /validate on entire feature → Run FULL QA verification (android-qa agent) → Verify ALL requirements across ALL phases → Generate implementation summary → List all commits made → Provide next steps (manual testing, PR creation)

---

## Usage

```bash
/build-auto <feature>

Example:

/build-auto notification-rules

---

Prerequisites (CRITICAL - Checked Automatically)

1. Specifications Complete

internal-documentation/temp/prd/<feature>/
├── requirements.md (FINAL status)
├── acceptance-criteria.md
└── traceability-matrix.md

internal-documentation/temp/design/<feature>/
├── design-spec.md (FINAL status)
└── user-flows.md

internal-documentation/temp/analytics/<feature>/
├── event-spec.md (FINAL status)
└── dashboard-spec.md

Auto-check: Files exist and have "FINAL" status (not DRAFT)

---

2. Specs Validated

/spec-validate <feature>

Auto-check: No BLOCKERS (warnings are OK)

---

3. Clean Git State

git status

Auto-check: Working tree is clean (no uncommitted changes)

---

4. No Existing Plan

Auto-check: Plan directory doesn't exist (will be created fresh)

---

Pre-Flight Confirmation

Before starting automation, system will ask:

═══════════════════════════════════════════════════════════════
              AUTOMATED BUILD: notification-rules
═══════════════════════════════════════════════════════════════

Pre-Flight Checks:
✅ Specs exist and are FINAL
✅ Spec validation: 0 BLOCKERS, 2 WARNINGS
✅ Git working tree: Clean
✅ No existing plan (will create fresh)

Estimated Duration: 6-8 hours
  Phase 1 (Data Layer): ~60 min
  Phase 2 (Repository): ~60 min
  Phase 3 (Domain): ~45 min
  Phase 4 (Feature Setup): ~30 min
  Phase 5 (ViewModel): ~90 min
  Phase 6 (UI): ~120 min
  Phase 7 (Navigation): ~45 min
  Phase 8 (Polish): ~60 min

Strategy: Layer-Based (auto-selected based on complexity)

What will happen:
1. Create implementation plan (8 phases)
2. Implement each phase with developer agent
3. Review each task with reviewer agent
4. Validate and commit after each phase
5. Continue until all phases complete

Commits: ~8 commits will be created (one per phase)

═══════════════════════════════════════════════════════════════

⚠️  This will run UNATTENDED for ~6-8 hours.

Type 'START' to begin automated build, or 'CANCEL' to abort:

User must type 'START' (all caps) to proceed.

---

Automation Workflow (Detailed)

Step 1: Initialize

# Create progress tracking
mkdir -p internal-documentation/temp/build-progress/<feature>
touch internal-documentation/temp/build-progress/<feature>/build-log.md

# Initialize log
echo "# Automated Build Log: <feature>" >> build-log.md
echo "Started: $(date)" >> build-log.md

---

Step 2: Planning (Phase 0)

Invoke Plan agent:

Create phased implementation plan for: <feature>

## Context
This is an AUTOMATED build. The plan will be executed immediately without human review.

## Requirements
- Read all specs from internal-documentation/temp/
- Create detailed, actionable tasks
- Include precise file paths and line numbers
- Specify exact requirements for each task
- Make tasks small and independent (easier to debug)

## Strategy Selection (Auto)
Analyzing specs to determine strategy...

Screens: <count from design-spec.md>
Requirements: <count from requirements.md>

Auto-selected: [LAYER-BASED | VERTICAL-SLICE]
Reason: <justification>

Create plan using selected strategy.

Output: 8 phase files in internal-documentation/temp/plan/<feature>/

Log to build-log.md:

## Phase 0: Planning
- Status: ✅ Complete
- Duration: 3 minutes
- Strategy: Layer-Based
- Phases: 8

---

Step 3: Phase Loop (Phases 1-8)

FOR EACH phase_number IN 1..8:

3.1 Invoke Developer Agent