plan-tasks
Produce docs/specs/<YYYY-MM-DD>-<feature>/tasks.md from the approved
requirements and design, from the skill set's templates/tasks.md (first path
that exists: templates/ beside this SKILL.md, ${CLAUDE_PLUGIN_ROOT}/templates,
else ../../../templates). Every task-block slot (Files, Interfaces,
Depends-on, Steps, _Requirements:_) is REQUIRED — no per-task risk
labels, decision-surface flags, or Human-review-order (see Step 3's gate table
for why). Write for a skilled implementer with NO context on this codebase,
seeing ONLY their task plus Global Constraints: names, paths, types,
commands they must not guess go in Files / Interfaces / Reuse / footer,
never as prose inside Steps (see Thin steps). Create a todo per step (1–4,
plus 5 if there's a tracker) — this skill's own list, separate from
design-solution's and the execute family's — checked off only when its
Done when: is met.