add-featurelisted
Install: claude install-skill kvdm-co-pilot/create-cmp-showcase
# 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`.
## 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).
If the configured exemplar has grown files beyond the canonical 11-file shape (an extra
ViewModel, a helper, a second use case named for its entity), the stamper clones **only the
canonical set** and prints a `WARNING:` listing exactly what it skipped — never silently.
When you see that warning, tell the human: the extras are part of the exemplar's pattern in
spirit but