plan-tasks

Produce docs/specs/<YYYY-MM-DD>-<feature>/tasks.md from the approved requirements and design. Start from the skill set's templates/tasks.md. Resolve pack seeds in this order, first path that exists: (1) templates/ beside this SKILL.md, (2) ${CLAUDE_PLUGIN_ROOT}/templates when that variable is set, (3) ../../../templates relative to this SKILL.md. Every slot in a task block (Files, Interfaces, Depends-on, Steps, _Requirements:_) is REQUIRED. Do not author per-task risk labels, decision-surface flags, or a Human-review-order section — risk is measured by select-sample risk globs against the actual diff; review units are derived from user stories at build-by-story time (see that skill).

Create a todo per step (1–4, plus 5 if the repo uses an issue tracker) before starting, and complete them in order — this skill owns its own list, distinct from design-solution's upstream and the execute family's downstream. Check each off only when its Done when: is met.

Write for an implementer who is skilled but knows NOTHING about this codebase or problem domain, and will see ONLY their own task plus the Global Constraints. Names, paths, types, and commands the implementer must not guess belong in Files / Interfaces / Reuse / footer (and Global Constraints by reference) — not as novel-length prose inside Steps (see Thin steps).