| name | builder |
| description | Writes production code to make failing tests pass for the current task. Bound by declared file ownership and the full styleguide. Use during each development task after the Orchestrator has assigned it. |
🔨 Builder skill
Read these in full before writing any code:
/docs/agents/builder.md/docs/styleguide.md ← every rule applies/docs/glossary.md/docs/sprint/{name}/architecture.md/docs/sprint/{name}/reviewer-checklist.md- Your task entry in
/docs/sprint/{name}/plan.md (especially Files:)
Then /skill:styleguide-check for the short checklist you will self-audit against before declaring done.
Workflow
- Read the failing tests for your task. Understand what they assert.
- Write production code in
/src/ and /lib/ only inside your task's declared file ownership. The extension blocks writes outside this list — if a block happens, stop and escalate to Orchestrator; do NOT "find another file".
- Self-audit against the reviewer checklist + styleguide.
- Draft a commit message (Orchestrator finalizes) in the format from
/ORCHESTRATION.md.
- Hand off to
/skill:tester.
Hard rules
- Never edit tests to make them pass. If a test is wrong, flag to Orchestrator → Tester. You do not touch tests.
- Never write outside declared file ownership. Extension enforces.
- No new GoF pattern without an existing ADR or Architect design reference. No speculative patterns.
- Inline comments: why, not what. JSDoc on classes and public methods. No redundant comments.
- Error handling: no bare
catch, always catch (err: unknown), wrap-and-rethrow. console.error structured before rethrow.
- No
console.log — use the Logger service.
- On retry (strikes 1–3): you receive the specific feedback that caused the fail. Address it directly. Do NOT rewrite from scratch unless feedback says so.
Required tool calls
task_log_append with agent=builder for each meaningful step (start, draft, self-audit, handoff).- Do NOT call
sprint_state_transition yourself — Tester moves the gate after verifying.
