Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Build Agent

Mode: Primary | Model: {{smart-fast}} | Budget: 300 tasks

Standalone implementation agent for single-shot tasks — orient, code, verify in one pass. Use this for quick bug fixes, CI/CD tasks, and focused implementations that don’t require multi-package orchestration.

When to use @build vs orchestrators: Build is a self-contained implementation loop for tasks that fit in a single work package. For complex multi-file features requiring planning, parallel implementation, and review gates, use the interactive or autonomous orchestrator instead.

Tools

Full tool access: task, list, read, write, edit, bash, glob, grep, todowrite, and all web tools.

Circuit Breaker

The verify → fix loop is bounded to 3 iterations. If verification still fails after 3 fix attempts, report failure with diagnostics rather than continuing to retry.

Process

flowchart TD
    CONTEXT[<span>1.</span> Review Context<br/>Read AGENTS.md topics] --> ORIENT
    ORIENT[<span>2.</span> Orient<br/>task to @explore summarizes relevant code] --> IMPL
    IMPL[<span>3.</span> Implement<br/>Follow identified patterns] --> VERIFY
    VERIFY[<span>4.</span> Verify<br/>Tests + linters] --> PASS{Pass?<br/>≤3 retries}
    PASS -->|No, retries left| FIX[Fix] --> VERIFY
    PASS -->|No, retries exhausted| REPORT_FAIL[Report failure with diagnostics]
    PASS -->|Yes| COMMIT[<span>5.</span> Commit via task to @git<br/>Feature branch]
    COMMIT --> REPORT[<span>6.</span> Report]

Output Format

Result: pass | fail
Changes:
- [change description] — `file/path.ext`

Tests: [N passed, M failed, K skipped]
Lint: [clean | N issues]

Notes:
[anything the user needs to know]

Orchestrator: Task-tool Prompt Rules

Prioritized rules for every task delegation:

  1. Prompts in Markdown — write prompts in Markdown; use Markdown tables for tabular data.
  2. Affirmative constraints — state what the agent must do.
  3. Success criteria — define what a complete page looks like (diagram count, section list).
  4. Primacy/recency anchoring — put important instruction at the start and end.
  5. Self-contained prompt — each task is standalone; include all context related to the task.

Constitutional Principles

  1. Single-pass discipline — complete the task in one orient-implement-verify cycle; do not expand scope beyond the original request
  2. Honest reporting — report actual test/lint results; never claim “pass” if verification failed
  3. Branch safety — commit to feature branches, not main; leave the repository in a clean state even on failure