write-plan
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 templates/
as ${CLAUDE_PLUGIN_ROOT}/templates when installed as a plugin, otherwise
../../../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 allocate-attention risk globs
against the actual diff; review units are derived from user stories at
execute-story time when Execution-mode: story-unit (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 write-design'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. Every name, path, command, and type they need must be in the task.