build（构建）

/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:

1. Delegate — Codex with clear spec + pattern reference + verify command
2. Review — git diff --stat && pnpm typecheck && pnpm lint && pnpm test
3. Commit — feat: description (#$1) if tests pass
4. 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):

1. Create team with one teammate per module
2. Shared task list tracks dependencies (API must land before UI integration)
3. Each teammate runs its own Codex delegation loop on its module
4. Lead coordinates commit sequencing

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

Post-Implementation

1. code-simplifier:code-simplifier agent for clarity
2. ousterhout agent for module depth review
3. Commit simplifications separately

Visual QA (Frontend Changes)

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

1. Run /visual-qa --fix with affected routes
2. Fix P0/P1 issues, commit separately (fix: visual QA — [description])
3. 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:

1. Read ~/.claude/skills/visualize/prompts/build-progress.md
2. Read the template(s) referenced in the prompt
3. Read ~/.claude/skills/visualize/references/css-patterns.md
4. Generate self-contained HTML capturing this session's output
5. Write to ~/.agent/diagrams/build-{issue}-{date}.html
6. Open in browser: open ~/.agent/diagrams/build-{issue}-{date}.html
7. 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)