spec-authoringlisted

# Spec authoring — closed-loop AC → Scenario → Test The brief is in prose. Tests are in code. The gap between them is where regression hides. The **executable spec** (Gherkin) is the bridge — every brief AC becomes one Scenario, every Scenario must have at least one test. `devteam spec verify` catches drift; the stage-03b gate records the mapping. ## When to use You're authoring stage-03b. The orchestrator has just finished clarification and your task is to translate the brief's `AC-N` lines into Gherkin scenarios in `pipeline/spec.feature`. Tracks: `full`, `quick`. ## Phase 1 — Load context Read in order: 1. `pipeline/brief.md` — extract every `AC-N` line. These are your inputs. 2. `pipeline/clarification-log.md` (if present) — answers may have refined ACs. 3. `pipeline/design-spec.md` (if present) — design hints the Given/When/Then. Confirm the brief has at least one `AC-N` line. If it doesn't, stop — go back to PM and tighten the brief first. Don't try to invent ACs from prose. ## Phase 2 — Scaffold ``` devteam spec generate ``` This writes `pipeline/spec.feature` with one `@AC-N` + `Scenario:` block per AC found in brief.md. The Given/When/Then lines are TODO placeholders. The scaffold makes it harder to forget an AC than to remember it. If the file already exists, the command refuses to overwrite. Edit by hand or pass `--force` (rare — usually you've drifted and want `verify` to tell you exactly what's off). ## Phase 3 — Fill in steps For each scenario: - **