---
description: "Build it — auto-plan, delegate to sub-agents with TDD, and verify. The main execution engine."
---

# /go — Build It

**CRITICAL**: Run `HARNESS_DIR=$(epic-harness path)` first. NEVER use `.harness/` in the project directory.

You are starting the **Go** phase — the core execution engine of epic-harness.

## Process

### Step 0: Preflight
- Check if a spec exists (`$HARNESS_DIR/specs/` or recent conversation). If not, run a quick inline spec conversation first.
- Check if `$HARNESS_DIR/team/` exists — if yes, use project-specific agents.

### Step 1: Plan
Break the work into ordered tasks:
```
Task 1: [description] — depends on: none
Task 2: [description] — depends on: Task 1
Task 3: [description] — depends on: none (parallel with 1)
```
Show the plan. Get user confirmation (or auto-proceed if user said "just do it").

### Step 2: Execute
For each task, launch a Codex sub-agent with:
- The task description
- Instruction to follow TDD: write test first → implement → green
- Instruction to invoke `debug` skill if tests fail
- Instruction to invoke `verify` skill before reporting done
- For independent tasks: launch in parallel using Codex's parallel task execution

### Step 3: Integrate
After all tasks complete:
- Run the full test suite
- Check for integration issues between tasks
- If anything fails, dispatch a sub-agent to fix it

### Step 4: Report
Summarize what was built, what tests pass, and any remaining issues.

## Skills Auto-Triggered
- **tdd**: Every sub-agent follows red-green-refactor
- **debug**: On any test failure or error
- **verify**: Before marking any task complete
- **simplify**: If any file exceeds 200 lines

## Red Flags
- Implementing without a plan
- Skipping tests "to save time"
- Not verifying the full suite after integration
- Implementing everything in a single file
