spec-designlisted

# /spec-design — spec → design doc (AI-DLC bridge) Bridges a factory **spec** (`specs/<name>.yaml`) into the AI-DLC inception pipeline. A spec is not a rough idea — it is *already-refined requirements* (tools, inputs, outputs, errors, dependencies, deploy target all resolved). So this skill enters AI-DLC at **phase 3 (design)**, skipping `story-new` and `story-refine`, and produces a `design-doc.md` whose task map the existing `/tasks` skill then expands. Building is manual from those tasks. The spec is the **source of truth**: this skill is re-runnable, and the design doc points back at the spec (not a `story.md`) as its authority. When the spec changes, re-run this skill to regenerate the design doc, then `/tasks`. Pipeline position: **specs/\<name\>.yaml → /spec-design → design-doc.md → /tasks → tasks/ → (manual build) → /pr-draft**. ## Input The spec name, e.g. `/spec-design pubmed` — reads `specs/pubmed.yaml`. Optional slug for the output folder (defaults to the spec name). ## Steps 1. **Read the spec** `specs/<name>.yaml`. If it is missing, STOP and list the specs under `specs/`. Parse its five layers: `server`, `dependencies`, `types`, `tools`, and each tool's inputs/constraints/output/errors/behavior. Also read `specs/SCHEMA-NOTES.md` if present — it records how spec fields map to code (e.g. a reserved word like `abstract` → `abstract_text`, `clamp` in core logic vs. `reject` at the input boundary). 2. **Resolve the target folder** `.local/user-stories/<slug>/`