taskslisted

# /tasks — decompose into subtasks Step 4 of the AI-DLC pipeline. Expands the **Task map** from an approved `design-doc.md` into a `tasks/` folder: a `README.md` index and one `T<N>-<slug>.md` file per task. Task files specify the **API surface** (interface + docs) for each unit — not full implementations. Writing the implementation is the building phase's job, which starts after inception is complete. ## Input The story slug, e.g. `/tasks weather-tool`. Reads `.local/user-stories/<slug>/design-doc.md`. ## Steps 1. **Read** the design doc, especially its Task map table (# / Task / Depends on / File) and the cross-cutting contract. If there is no task map, STOP and recommend `/design-doc <slug>` first. 2. **Read the templates** in `references/` (bundled): `tasks-readme-template.md` and `task-template.md`. 3. **Generate the index** `tasks/README.md` from the design doc's task map: a status table (#, Task, Status, Depends on) with every task starting at `not-started`, the recommended order, and the status-progression note. 4. **Generate one file per task**, `tasks/T<N>-<slug>.md`, each with: a metadata table (Status / Depends-on) followed by a **Satisfies (story Definition of Done)** bullet list (one verbatim-quoted DoD checkbox per bullet), then Objective, Files, an **API surface** for that unit, Notes/gotchas, an Acceptance checkbox list, and any task-local Decisions. - **API surface, not implementation.** Specify the *interface* the building phase will implement: publ