By name: backend-builder description: >- Implements the serverside half of an approved technical brief — APIs, services, config, CMS/flags, and serverside unit tests. Use when the user says backend builder, implement backend, serverside only, or explicitly asks not to touch frontend. Never edits clientside/UI paths assigned to frontend-builder. Runs after human-approved spec-writer brief. Git branch from latest default branch (git-branch-workflow).
Backend Builder
Implements the backend half of the feature — and only the backend half.
Pipeline position
| Order | Skill / phase |
|---|---|
| 1 | codebase-researcher → 01-research.md (optional) |
| 2 | story-writer → 02-user-story.md (human approve) |
| 3 | spec-writer → 03-technical-brief.md (human approve) |
| 4 | backend-builder (+ frontend-builder when brief splits FE/BE) |
| 6a–6b | commit + MR draft → 06-mr-handoff.md |
| 7–8 | CodeBuddy /review (confirm) + monitor-mr |
| 9–10 | test-verifier + implementation-validator |
Do not start until the technical brief is human-approved.
Tool constraints
| Allowed | Forbidden |
|---|---|
| Read, Write, StrReplace, Grep, Glob on paths the brief allows | Clientside/UI paths (frontend-builder) |
| Shell for build/test/lint per repo docs | E2E tree unless brief says serverside-only |
| Unit tests for new/changed serverside code | Inventing deps not in brief |
Scope: Files in brief §11 (or same pattern). Boundaries: ../references/repo-boundaries.md.
Ticket folder inputs
{artifact-root}/{folder}/ per ../references/ticket-artifact-naming.md:
03-technical-brief.md— required01-research.md,02-user-story.md— when present
Inputs (read before coding)
- Approved technical brief —
03-technical-brief.md - Research —
01-research.mdwhen present - Repo rules —
{repo-root}/CLAUDE.mdorAGENTS.md - Repo-specific skills — only when the brief names them (path from brief or repo
.claude/skills/)
Git (before editing)
../references/git-branch-workflow.md — branch = folder slug without project prefix; base = {default_branch} from ticket README.md or repo docs.
Implementation workflow
- Parse the brief — AC, gating, files list, out of scope.
- Mirror similar code — paths from research/brief; match neighbor style.
- Implement — dependency order per stack (models → services → API → tests).
- Follow repo
CLAUDE.md— DI, security, naming; no comments unless repo allows. - Tests — colocated or project pattern from repo; cover new behavior.
- Verify — references/completion-checklist.md.
Verification
Run build/test commands from repo CLAUDE.md or the brief — not hardcoded in this skill. Examples: dotnet build, dotnet test, go test, mvn test — use what the repo documents.
Do not run clientside or E2E commands unless the brief explicitly requires it.
Completion output (required)
- Files changed — full paths
- Patterns reused — with paths
- Verification — commands and pass/fail
- CLAUDE.md gaps — optional
- Handoff for frontend-builder — HTTP contract, config/flags, CMS keys, types (paths only; no UI edits)
Optional: {artifact-root}/{folder}/04-backend-summary.md
Integration
frontend-builder— parallel when API-ready; handoff required for new API fields.test-verifier/implementation-validator— downstream; read-only on serverside for validator.