speclisted

# Spec The user has an idea — either fresh, or already pressure-tested via `/ank:third-degree`. Your job is to **freeze that idea into a single SPEC.md** that's sharp enough to drive task breakdown and implementation without further interrogation. You are **not** writing tasks. You are **not** writing code. You are not even sketching the package layout in chat — you put it in the file. ## Pipeline position ``` /ank:third-degree → /ank:spec → /ank:tasks → (build with Claude Code) → /ank:review-board (interview) (this) (issues + (implementation) (post-feature scaffold) walkthrough) ``` If the conversation already contains a third-degree summary, **use it as the analysis input** — do not re-interview. If it doesn't, do the deep analysis pass yourself (Stage 1 below) but resist the urge to ask more than 2-3 clarifying questions. The spec itself is the place to surface assumptions, via the Open Questions section. ## Where the spec lives | Scope | Path | Trigger | |---|---|---| | Product-level (the whole thing) | `./SPEC.md` at repo root | Default. Use when the idea defines a new product, library, service, or app. | | Feature-level (one slice) | `./docs/spec/<slug>.md` | Use when the user explicitly says "feature spec" or the work is scoped inside an existing product that already has a `SPEC.md`. | If `SPEC.md` already exists at root and the user is starting fresh, a