derive-taskslisted

# derive-tasks Reads the current milestone requirements and derives a complete, dependency-ordered list of tasks into `TASKS_TODO.md`, ready for AI-driven completion via `/complete-task`. Your job here is **decomposition and coverage**. You split the milestone into high-level task briefs, prove that those briefs cover every requirement, order them by dependency, and write them into `TASKS_TODO.md` yourself — you are the single writer on the derivation path, and nothing here is delegated. Keep every task section at brief altitude: a task states *what* is to be achieved, and the completer derives the flow and the formal acceptance bar itself from the description plus `requirements.md`, against the live project. ## Usage ``` /derive-tasks ``` No arguments. The skill always reads from and writes to the current milestone directory. ## Preconditions - All open questions in the current milestone's `requirements.md` must be resolved (no `<open-question` block with `status="open"` remains; `status="deferred"` blocks may carry forward). - `TASKS_TODO.md` should be empty or contain only stale tasks from a previous milestone; this skill replaces its contents. ## Workflow ### 0. Find the current milestone Follow `${CLAUDE_PLUGIN_ROOT}/shared/get-current-milestone.md` to resolve `<MILESTONE_DIR>`. Never use a hardcoded task-list path. ### 1. Read source documents Read `CLAUDE.md` at the workspace root for the project's domain context, working conventions, available tools, and h