/build

Stop planning. Start shipping.

Role

Senior engineer. Codex is your software engineer.

Objective

Implement Issue #$ARGUMENTS . Ship working, tested, committed code on a feature branch.

Latitude

• Delegate ALL work to Codex by default (investigation AND implementation)

• Keep only trivial one-liners where delegation overhead > benefit

• If Codex goes off-rails, re-delegate with better direction

Startup

gh issue view $1 --comments gh issue edit $1 --remove-label "status/ready" --add-label "status/in-progress" --add-assignee phrazzld

If on master /main , branch: feature/issue-$1 or fix/issue-$1 .

TDD Baseline

If the issue lacks test coverage, invoke /test-driven-development for the first logical chunk. Establishes a failing test before Codex writes implementation — prevents shipping untested code.

Execution Loop

For each logical chunk:

• Delegate — Codex with clear spec + pattern reference + verify command

• Review — git diff --stat && pnpm typecheck && pnpm lint && pnpm test

• Commit — feat: description (#$1) if tests pass

• Repeat until complete

Final commit: feat: complete feature (closes #$1)

Multi-Module Mode (Agent Teams)

When the issue spans 3+ distinct modules (e.g., API + UI + tests):

• Create team with one teammate per module

• Shared task list tracks dependencies (API must land before UI integration)

• Each teammate runs its own Codex delegation loop on its module

• Lead coordinates commit sequencing

Use when: cross-layer features, 3+ modules, clear boundaries. Don't use when: single module, sequential dependencies dominate.

Post-Implementation

• code-simplifier:code-simplifier agent for clarity

• ousterhout agent for module depth review

• Commit simplifications separately

Visual QA (Frontend Changes)

If the diff touches app/ , components/ , or *.css files:

• Run /visual-qa --fix with affected routes

• Fix P0/P1 issues, commit separately (fix: visual QA — [description] )

• Note any P2 findings for the PR body

Skip if: pure backend, pure config, no user-facing changes.

Issue Comments

Leave breadcrumbs: starting work, decision points, scope creep, completion. Concise, high-context, useful, human.

Output

Commits made, files changed, verification status.

Visual Deliverable

After completing the core workflow, generate a visual HTML summary:

• Read ~/.claude/skills/visualize/prompts/build-progress.md

• Read the template(s) referenced in the prompt

• Read ~/.claude/skills/visualize/references/css-patterns.md

• Generate self-contained HTML capturing this session's output

• Write to ~/.agent/diagrams/build-{issue}-{date}.html

• Open in browser: open ~/.agent/diagrams/build-{issue}-{date}.html

• Tell the user the file path

Skip visual output if:

• The session was trivial (single finding, quick fix)

• The user explicitly opts out (--no-visual )

• No browser available (SSH session)