design-doclisted

# /design-doc — architecture + task map Step 3 of the AI-DLC pipeline. Turns an approved `story.md` into `design-doc.md`: the single source of **structure** (architecture, decisions, dependencies, and a task map). Per-task detail — the API surface each unit exposes — lives in the task files produced by `/tasks`. Neither the design doc nor the task files hold full implementations; those are written in the building phase, after inception. ## Input The story slug, e.g. `/design-doc weather-tool`. Reads `.local/user-stories/<slug>/story.md`. ## Steps 1. **Read** the story. If it still has unresolved `⏳ open:` items, STOP and recommend `/story-refine <slug>` first — a design on shifting requirements is wasted work. 2. **Read the template** in `references/design-template.md` (bundled). Match its section order. 3. **Draft the design doc.** For each section: - **Goal & non-goals** — lift from the story's Scope; make non-goals explicit. - **Architecture** — the layering/module split and *why*. An ASCII diagram + a package/file layout tree when it's a Python package or React/TS app. Keep each layer independently testable. - **Key dependencies** — a table of load-bearing choices with a one-line justification each. Verify versions/features against real sources; note the date verified. Do not assert versions from memory. - **Task map** — a numbered table (T1…Tn) with Task / Depends-on / File columns, plus a recommended order. Each task must end green (