skill
Atomic TDD build skill. Takes a context packet (shaped ticket) and produces code + tests on a feature branch. Red → Green → Refactor. Does not shape, review, QA, or ship — single concern: spec to green tests. Use when: "implement this spec", "build this", "TDD this", "code this up", "write the code for this ticket", after /shape has produced a context packet. Trigger: /implement, /build (alias).
/implement
Source: skills/implement/SKILL.md
Atomic TDD build skill. Takes a context packet (shaped ticket) and produces code + tests on a feature branch. Red → Green → Refactor. Does not shape, review, QA, or ship — single concern: spec to green tests. Use when: "implement this spec", "build this", "TDD this", "code this up", "write the code for this ticket", after /shape has produced a context packet. Trigger: /implement, /build (alias).
Build primitive in the Harness Kit operating loop.
This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.
Spec in, green tests out. One packet, one feature branch, one concern.
## Invariants
- Trust the context packet. Do not reshape. Do not re-plan.
- If the packet is incomplete, **fail loudly** — do not invent the spec.
## Delegation Floor
Delegation floor applies: probe the roster first; dispatch two or more
providers for substantive work; direct solo only for mechanical, emergency,
user-forbidden, or fewer-than-two-providers cases. See
`harnesses/shared/AGENTS.md` (Roster).
Local lane guidance: Use one bounded builder lane and one adversarial validator/refactor lane; give them the context packet, oracle, boundaries, repo anchors, and what would embarrass us if green tests missed it.
## Completion Evidence
Completion evidence core applies: use `harnesses/shared/AGENTS.md`
(Completion Evidence) as the universal evidence shape, then fill the local
fields required by the implementation final message.
## Contract
**Input.** A context packet: goal, non-goals, constraints, repo anchors,
oracle (executable preferred), implementation sequence. Resolution order:
1. Explicit path argument (`/implement backlog.d/033-foo.md`)
2. Backlog item ID (`/implement 033`) → resolves via `backlog.d/<id>-*.md`
3. Last `/shape` output in the current session
4. **No packet found → stop.** Do not guess the spec from a title.
Required packet fields (hard gate — missing any = stop):
- `goal` (one sentence, testable outcome with a well-defined exit condition)
- `oracle` (how we know it's done, ideally executable commands)
- `implementation sequence` (ordered steps, or explicit "single chunk")
If the packet contains `Formal Spec Required: yes`, also require a `Formal
Spec` block with: informal spec, formal examples, acceptance oracle, hardening
budget, and waiver path. Missing or vague formal-spec fields are packet
...