build

name	build
description	Use when executing an implementation plan or building a scoped feature or fix - after scope is clear, before code gets written. Triggers on "implement the plan at PATH", "start slice SP-2b".

Build

Input

A plan doc path or slice id - or a small directly-scoped change. Non-trivial work with no plan? Write one first (plan).

Execution rules

1. When a plan exists, work slice by slice in its order and update checkboxes as tasks complete. The plan is durable state that survives context resets; "what's pending?" must be answerable from it alone.
2. Read before writing: the files to be touched, their tests, the module's conventions. Reuse before adding: if most of the need already exists, extend or refactor it. Roughly 80% is a recon heuristic, not a numeric gate.
3. Load references/engineering-standards.md (once per feature - its completion checklist gates every slice) and the matching domain skills - spring-api (endpoints), migrations (DDL), ledger (money movement), temporal (workflows), igaming-ui (betting/casino UI) - plus repo instructions from AGENTS.md and/or CLAUDE.md. Detect the toolchain from the repo (Java, Boot, and build-tool versions differ across workspaces) - never assume.
4. Tests target business behavior, written with (and where practical before) the code. No DTO/getter tests, no framework tests, no log-assertion tests, no snapshot abuse.
5. Scope discipline: implement the plan, nothing else. No drive-by refactors, no CI/settings changes, no new abstractions, flags, or config beyond the plan. If the plan turns out wrong mid-slice: classify the drift, flag it, and update the plan or approved source before continuing. Never improvise silently.
6. Delegated agents must earn their overhead and must be allowed by the user or repository policy:
   • Recon: one read-only agent per genuinely unknown area; never a worktree.
   • Parallel implementation: only independent slices that share no files. Use the runtime's isolation mechanism when concurrent agents would otherwise mutate the same checkout.
   • Non-blocking side work (docs, test backfill): run in the background only when supported.
   • Context diet: each agent gets its slice's plan excerpt and file paths, nothing more, and returns a compact summary (what changed, test output tail) - never a transcript. Don't redo delegated work inline.

Slice completion gate

• Plan checkbox updated when a plan exists; build + tests green - run them and show the output tail, no claims.
• Cleanup executed: every legacy item listed in the plan actually deleted; no leftover mocks, stale files, or commented-out code; no TODOs without a tracked follow-up.
• Engineering-standards completion checklist passes (no new duplication, no consumer-less abstractions, obsolete tests and stale docs gone).
• Diff reread once for accidental scope.

After implementation, use audit for significant changes and e2e when live proof is relevant. Use ship only when the user asks for delivery actions.