Genesis Implement

---
name: "Implement"
description: Implement one micro spec — one commit, one PR. The micro spec is the complete instruction set; write only the files in its File Operations table, verify against its acceptance criteria, commit.
argument-hint: "<spec-id> [feature-name]"
---

# Implement — One Spec, One Commit, One PR

Implement **exactly one micro spec** per invocation. The micro spec is the complete instruction set — no task selection, no group management. Write the code/content for the files in its File Operations table, verify against its acceptance criteria, then commit.

**Gate:** the active group's micro specs are written and the prior phase is accepted. Followed by the A1–A5 audits once the group's specs are all implemented.

## Inputs

- The single target micro spec at `.genesis/features/<feature>/micro-specs/{spec-id}.md` (the complete instruction set).
- `.genesis/project-state.md` (mode), the constitution, `northstar.md`.
- `approvals/master.json` / `approvals/group-<N>.json` for position.
- The files listed in the spec's `reads` interface.

## Process

1. **Pre-flight:** confirm the feature/group/spec and that the prior phase is accepted; read the target spec in full.
2. **Implement (mode-branched):**
   - **Greenfield:** implement the files in the File Operations table; satisfy every FR/AC; write tests per the constitution.
   - **Brownfield:** stay strictly within the spec's File Operations table (scope discipline); preserve existing behavior; classify any touched code inherited vs introduced via git blame; ensure no regressions.
   - **Lowfield:** produce the stage's artifacts per the declared artifact schema; verify the schema validates.
3. **Verify:** run the project's `build` / `test` / `lint` commands as declared in the constitution, and confirm the spec's acceptance criteria pass. **Do not write outside the spec's File Operations table.**
4. **Finalize:** one commit scoped to the spec (`implement: {spec-id} — {title}`), then open one PR. Log any failed approaches to `tried.json` so they are not retried.

## Anti-laziness

What you write runs. No stubs, no TODO, no "simplified version," no narrowing the spec to dodge it. A change is not done at the first file — sweep the blast radius named in the File Operations table (callers, types, tests, configs). If the spec cannot be satisfied as written, stop and surface why — do not ship a partial.

## Output

- The source files / content artifacts named in the spec's File Operations table.
- One commit + one PR.
- (Optional) a `tried.json` entry recording failed approaches.

## Next step

Implement the next spec, or — when the group's specs are all done — run `/genesis-a1`.

## Natural language triggers

```
- "implement spec 1.3"
- "build this micro spec"
- "implement the next spec"
```