spec-taskslisted

# spec-tasks Split a feature's `requirements.md` into independently-deliverable, chronologically-ordered task files. This is step 2 of the spec-driven workflow: `spec-ideate` → `spec-tasks` → `spec-build`. ## When to use Invoke when the user wants to break down / split / plan the tasks for an existing spec. Requires a `specs/NNN_feature_slug/requirements.md` to already exist (produced by `spec-ideate`). ## Procedure 1. **Read the requirements.** Open `specs/NNN_feature_slug/requirements.md`. If the target feature is ambiguous, ask which one. 2. **Decompose into vertical slices.** Each task must be **deliverable on its own**: committable, QA-able, and verifiable independently, mapping back to the acceptance criteria. Avoid tasks that only make sense together. 3. **Order by dependency.** Sequence tasks so each can be completed and verified before the next. Number them `01_`, `02_`, … (zero-padded two digits). 4. **Write one file per task** at `specs/NNN_feature_slug/tasks/NN_task_slug.md` using the canonical structure below. `task_slug` is snake_case. 5. **Maintain the checklist.** Create/update `specs/NNN_feature_slug/tasks/README.md` — an ordered checklist of the tasks (`- [ ] 01 — {title}`) that `spec-build` ticks off as it goes. 6. **Update the index.** Set the feature's row in `specs/README.md` to `Status: Planned`. 7. **Format.** Run `deno fmt` on the new/changed files, then report and suggest running `spec-build`. ## Canonical task file structure ``