ai-spec-draftlisted

# Spec Brief Researches the problem, surveys the existing surface, and lands a 14-section brief at `.ai-engineering/specs/drafts/<topic>-brief.md` for handoff to `/ai-brainstorm`. The brief is the human-readable contract between the idea phase and the spec phase: every claim cites `file:line` evidence; no machine paths leak into the rendered output; emojis are banned by team convention. ``` /ai-spec-draft "skills-and-agents-excellence-v2" /ai-spec-draft "installer-windows-support" ``` ## Quick Start 1. Invoke the skill with a kebab-case topic slug. Topic words drive the filename and the brief title. 2. The skill dispatches `/ai-explore` and `/ai-research` in parallel to gather codebase evidence and external references. Each runs in its own fresh context. 3. The skill drafts the 14 canonical sections using the captured evidence. Every architectural claim cites at least one `file:line` location. 4. Output lands at `.ai-engineering/specs/drafts/<topic>-brief.md`. The operator reviews, edits, and hands off to `/ai-brainstorm` for spec promotion. ## Workflow Principles applied: §10.6 SDD (every brief precedes a spec — the spec phase consumes the brief as the canonical problem statement); §10.5 TDD (structural test enforces the 14-section shape so brief drift is impossible without a visible test failure); §10.1 KISS (one file, one location, one handoff token — no parallel surfaces). 1. **Interview owner intent.** Ask up to three clarifying questions: (a) the problem statemen