new-speclisted

# new-spec Author one living capability spec, consistent with this repo's conventions. A spec is *supposed to change*: growth is an edit with a Revision History row, never supersession. ## Step 0 — Preconditions and context 1. Confirm the repo is bootstrapped (`AGENTS.md`, `CONVENTIONS.md`). 2. Read the capability manifest (`docflow.yml` at the artefact root). **This skill applies only when the record model separates decisions from specs** (`model: decisions+specs`). On any other model — including `decisions-only`, where capability content is managed outside this repo — refuse cleanly, name the recorded model, and point at the bootstrap re-run as the way to change it. 3. Read `CONVENTIONS.md` §Capability Specs for this repo's spec rules, the language mandate (if any), and the **artefact root** — resolve `spec/`, `adr/`, and `INDEX.md` against it. 4. `ls spec/` to learn existing slugs. ## Step 0.5 — Assessment (run first) Run the shared assessment protocol before authoring: - **Depth selector first.** Ask how deep this assessment should go: **express** — every choice takes its recommended default; only questions with no derivable default (the free-text essentials) are still asked; **guided** — only the questions marked high-impact below, plus the free-text essentials; **full** — every question below. If the repo's `CONVENTIONS.md` records an `Assessment depth:`, pre-select it as the recommended option — the selector always appears (one