house2-builderlisted

The house v2 build session — implement ONE plan unit from a kickoff brief, self-review it, reconcile that unit's docs, and report back through the house records. Use when you have been handed a kickoff brief for a single unit in a repo the house kernel tracks (it has a `.house/` dir). Do NOT use to drive a whole slice (that is house2-orchestrator), to shape new work (house2-shaper), or for non-build chat.
argent-gnome/sdlc-skills · ★ 0 · AI & Automation · score 58

Install: claude install-skill argent-gnome/sdlc-skills

# house2-builder — one unit, over shared state You are spun up to implement **one plan unit**, then torn down. The orchestrator owns sequencing and the merge decision; you own building that unit well and reporting honestly. **Compose — do not reimplement.** **Doctrine — read on-demand, never preloaded:** `$HOME/.claude/skills/house2-orchestrator/references/doctrine.md`, covering the composition contract (§7) while you build, hygiene (§8) at teardown, and reconcile (§9). ## 1. Preflight — validate the brief, never guess Check the brief against `cli/schema/kickoff.yaml`: every `required` field present, in the right shape. Any field missing or unusable ⇒ stop and finalize `--result NEEDS_CONTEXT`, naming the offenders as `missing_inputs`. **Never guess a missing input** — a brief you had to interpret is a brief that will be interpreted differently at the merge gate. Then resolve the brief's `stack:` against `.house/gates.yml`. **An absent or unknown stack key is also `NEEDS_CONTEXT`** — name the missing key. Guessing a stack's gates is how a run silently applies the wrong lenses and still reports green; that fail-open is closed. **You build; you do not decide the slice.** The brief's `scope_guards` are binding: work you find outside them is reported, not done. ## 2. The loop, per task **TDD's iron law:** write the failing test first, watch it fail for the right reason, then the minimal code that passes. **The build stays green at every task boundary** — a shared signatur