build

/build - Implementation Orchestrator

Chains /challenge → /checkout → /research → /think → /code → quality → /commit → /pr, running end-to-end from premise GO verification through committing test-verified implementation to PR creation. Covers not just new features but refactoring and migrations. Every phase is mandatory (no early exit).

Input

Take the implementation task from $ARGUMENTS (optional). If empty, ask the user what to implement via AskUserQuestion.

Phase 1: PREFLIGHT

1. Context-scan CLAUDE.md, package.json, Cargo.toml, etc.
2. Run PREFLIGHT
3. Resolve inferences and unknowns
4. Track with TaskCreate (Phase 2-9)

Phase 2: challenge

Run Skill("challenge", $ARGUMENTS) to verify the implementation premise as GO / NO-GO.

• NO-GO → present the refuting evidence and stop. Designing or implementing on a dead premise is wasted effort
• GO → pass Verdict / decisions / trade-offs / Actionable items into Phase 5 (think). Feeding the premise that challenge settled into think's design as a starting point turns the double critic-design attack (challenge and think) into a relationship where the premise GO/NO-GO feeds the design approach

Phase 3: Branch

Run Skill("checkout", $ARGUMENTS) to create the working branch. Creating it after challenge GO avoids branching for a NO-GO proposal. The subsequent research / think / code artifacts and the final commit all land on this branch, keeping main clean. At the start the diff is empty, so naming leans mainly on $ARGUMENTS. Skip if already off the default branch.

Phase 4: research

Run Skill("research", $ARGUMENTS).

Output goes to .claude/workspace/research/YYYY-MM-DD-<slug>.md. Phase 5 detects it as prior research.

Phase 5: Design

Run Skill("think", $ARGUMENTS). Generate SOW + Spec from the Phase 2 challenge output (verdict / decisions / trade-offs) and the Phase 4 research results as input.

Output is .claude/workspace/planning/YYYY-MM-DD-[feature]/sow.md + spec.md.

Phase 6: Implementation

Run Skill("code", $ARGUMENTS). /code auto-detects the SOW from the Phase 5 output.

Phase 7: Quality

Get changed files with git diff main...HEAD --name-only. Phase 6 (/code) passes the mechanical baseline of lint / type / test / readability / coverage, so Phase 7 stacks two layers, internal audit and external polish. Audit runs a multi-dimensional review of security / resilience / causation / encapsulation under adversarial challenge with severity. Polish stacks external Codex (a non-Claude lens that counters Self-Enhancement bias) plus simplify / enhancer-code cleanup. Present any remaining issues to the user for a decision.

Step	Action	Exit condition
1	Run Skill("audit") against the diff (assigns severity, adversarial challenge)	0 critical/high → go to Step 3
2	Fix each snapshot critical/high finding ID with Skill("fix", "<ID>"), then re-audit; this is one round	0 critical/high or 3 rounds reached → go to Step 3
3	Run Skill("polish") against the uncommitted diff (external Codex + cleanup, fixes directly)	Codex not installed → continue with cleanup only
4	Confirm tests pass	Test failure → fix (max 2). Still failing → present remaining issues

If a polish fix breaks tests, polish stashes it internally. Surface any remaining issues before the Phase 8 commit.

Phase 8: commit

After the quality layer and all tests pass, run Skill("commit", ...) to commit the changes in Conventional Commits format. Planning artifacts and implementation land in one commit. If issues remain unresolved, present them to the user before committing.

Phase 9: PR

Run Skill("pr", $ARGUMENTS) to create a PR from the committed changes. pr previews the body and confirms creation via AskUserQuestion, so build adds no extra gate.

Error handling

Error	Action
/challenge returns NO-GO	Present refuting evidence and stop
/checkout finds branch exists	Propose an alternate name or continue on it
/research or /think cancelled/failed	Save context and exit
/code failed	Present the error and ask the user
Quality loop exhausted (3 rounds)	Present remainder, user decides
/code quality gate shows AC unmet	Propose re-entry to Phase 6 or 7
/commit failed	Present the error and ask the user
/pr failed/cancelled	Present the error and ask the user

Validation

End only when every check holds. Present the reason to the user for any check that cannot be met.

• challenge GO verdict
• Working branch created
• PREFLIGHT passed
• SOW + Spec generated
• All tests pass
• /code AC coverage
• Polish passed (Codex review + cleanup)
• Committed
• PR created