add-feature

add-feature — stamp a conforming vertical slice

Spec-first, deterministic-stamp, gate-proven. The script (qa/scaffold-feature.mjs) does the mechanical work — copy the exemplar file set, whole-word identifier rename, anchor injection into the three shared files. You (the AI) only refine spec wording and adapt the feature to its real shape. You are not done until node qa/verify.mjs PASSes and the receipt is committed — see this project's CLAUDE.md.

Step 0 — name the lane, out loud, before anything else

Every post-genesis change enters through one of two lanes (CLAUDE.md §"After genesis"), and the human must be told which one this request is taking, in your first reply — one or two plain sentences before any tool runs: what you understood the change to be, which lane, and why. Never route silently; the human can overrule the triage in a word.

• Brief lane — the request carries decisions a future contributor could plausibly "simplify" away, or blast radius into other governed artifacts. Say so, e.g.: "This carries real decisions (day-boundary rules, scheduling semantics) — I'll draft a feature brief at docs/features/<name>.md with the open decisions for you to close and sign BEFORE I stamp anything." Only after the brief is signed does this skill's stamping start — and if the feature has a UI surface, the design gate comes next, before the spec: draft the screens on stub data, render them, and stop for the human's signature on feature-design:<name> (brief → design → spec → build). A human signs rendered screens, never a description of screens.
• Direct lane — an ordinary feature with no decisions worth recording. Say so, e.g.: "Straightforward slice, no decisions worth a brief — direct lane: spec clauses for your confirmation, then I stamp and prove." Then continue with Step 1 below.

The clone source is configurable

The stamper clones from the project's configured exemplar — qa/approvals.json's top-level "exemplarFeature" key (absent ⇒ home, the shipped exemplar). This is the same resolution the approvals registry uses for the governed exemplar-feature artifact, so what gets stamped is always exactly what the human signed off on. After the genesis walk retargets exemplarFeature to the user's own first feature, every stamp from then on clones their pattern in their domain language — do not assume home still exists as the exemplar; read the config (or just run the stamper: it resolves the source itself).