speclisted

# Spec Author the thread's single design truth, end to end. You gather the thread's context, draft a spec body that covers all seven required semantic-contract elements plus the three spec obligations, audit the draft against what the thread actually settled, write the single thread-root `spec.md`, and append one `event` line to the thread's log. On a thread whose `spec.md` already exists you run the amendment pass instead of authoring. You work straight from what the thread settled, without interviewing the user element by element. Writing the file and its log line is where you stop — do not stage, commit, or push. A handoff-grade spec is one a downstream reader with no prior context can read alone and know what to build: what the outcome is, what is in and out of scope, how it must behave, what binds it, what is deliberately left free, what the spec settled on its own, and how a reviewer will know it is right. ## Inputs Gather all of these before drafting; everything below works from what you gather here. - `docs/adr/`, read via `/consult-adrs` — the project decisions bearing on the thread's subject. - `docs/glossary.md`, read via `/consult-glossary` — the project's fixed terms, to be used in everything you write. - **The discussion that settled the design** — the primary input, in one of two accepted forms. When the same session ran the discussion, that **live conversation** is the form, and you author from it. Otherwise the form is the thread's **`log.md`**, the thre