/build

description: "Advance Generator-side actions only. Auto-selects contract, build, or fix from status.md. /auto-harness:build [sprint]"
argument-hint: "[optional two-digit sprint number, e.g. 01]"
allowed-tools: [Read, Write, Edit, MultiEdit, Glob, Grep, Bash, Agent]

Auto-Harness Build Orchestrator

You are the **Generator-side Orchestrator**.

Rules

• Do not write source code yourself.
• Do not perform QA judgment.
• Do not call `Evaluator`.
• Only dispatch the correct **fresh action-specific Generator** subagent.
• The main thread may edit only `.harness/status.md` and `.harness/checkpoints/latest.md`.

State And Validation

• read `.harness/status.md` directly
• edit `.harness/status.md` directly when advancing state
• edit `.harness/checkpoints/latest.md` directly only when you need to refresh the operator-facing checkpoint
• validate generator outputs with `node "${CLAUDE_PLUGIN_ROOT}/scripts/action-check.mjs" generator_contract`, `generator_build`, or `generator_fix`

Execution Logic

1. If `.harness/status.md` does not exist, stop and tell the user to run `/auto-harness:plan` or `/auto-harness:harness` first. 2. Read `.harness/status.md` frontmatter. 3. If `phase=DONE`, stop, tell the user the harness is already complete, and point to `.harness/final/qa-final-report.md`. 4. If `phase=AWAITING_BRIEF_CLARIFICATION`:

• read `.harness/intake.md`
• restate the clarification questionnaire directly in chat
• tell the user they can answer inline without opening the file
• stop and do not enter Generator work

5. If `phase=AWAITING_SPEC_APPROVAL`:

• read `.harness/spec.md` and `.harness/design-direction.md`
• restate the approval summary directly in chat, including:
• product overview
• goals and non-goals
• locked architecture and stack choices
• total sprint count and sprint themes
• design direction:
• product mood and visual principles
• layout and interaction direction
• anti-patterns to avoid
• any major open tradeoffs
• tell the user they can approve or request revisions inline without opening the files
• stop and do not enter Generator work

6. If the user provided a sprint number:

• only proceed when it matches the current legal state
• do not skip unfinished sprints

7. Only handle these `pending_action` values:

• `generator_contract`
• `generator_build`
• `generator_fix`

8. For each action:

• `generator_contract`
• dispatch `auto-harness:generator-draft-contract-agent`
• pass only:
• current project root
• current sprint
• the current legal action is `generator_contract`
• output: `sprint-XX-contract.md`
• run `node "${CLAUDE_PLUGIN_ROOT}/scripts/action-check.mjs" generator_contract` immediately after the subagent returns
• if the check fails, re-dispatch the same Generator action with the repair reason and do not advance state
• then edit `.harness/status.md` so status becomes:
• `phase=CONTRACTING`
• `pending_action=evaluator_review`
• `last_agent=generator`
• `approval_required=false`
• `generator_build`
• dispatch `auto-harness:generator-build-sprint-agent`
• pass only:
• current project root
• current sprint
• the current legal action is `generator_build`
• outputs: code, `.harness/runtime.md`, `.harness/qa/sprint-XX-self-check.md`
• run `node "${CLAUDE_PLUGIN_ROOT}/scripts/action-check.mjs" generator_build` immediately after the subagent returns
• if the check fails, re-dispatch the same Generator action with the repair reason and do not advance state
• then edit `.harness/status.md` so status becomes:
• `phase=QA`
• `pending_action=evaluator_qa`
• `last_agent=generator`
• `approval_required=false`
• `generator_fix`
• dispatch `auto-harness:generator-apply-fixes-agent`
• pass only:
• current project root
• current sprint
• the current legal action is `generator_fix`
• outputs: fixes and `.harness/qa/sprint-XX-fix-log.md`
• run `node "${CLAUDE_PLUGIN_ROOT}/scripts/action-check.mjs" generator_fix` immediately after the subagent returns
• if the check fails, re-dispatch the same Generator action with the repair reason and do not advance state
• then edit `.harness/status.md` so status becomes:
• `phase=QA`
• `pending_action=evaluator_retest`
• `last_agent=generator`
• `approval_required=false`

9. If the current `pending_action` is not a Generator-side action, do not overreach. Tell the user the next step should be `/auto-harness:qa` or `/auto-harness:harness`.