handoff-pickuplisted

<purpose> Read the project's `handoff.xml` (always in project root) and start a session from cold context. Primary producer is `/handoff-update`; this skill is the consumer. Goal: understand current project state, resume interrupted work safely, and choose the right next action without redoing work or treating planning notes as approved tasks. </purpose> <clarity_first> If an active task, next task, backlog item, or user request is unclear, stop and ask for clarification before implementing. This is mandatory even when the handoff contains detailed notes. Detailed does not always mean unambiguous. If there are unresolved choices, contradictory instructions, vague acceptance criteria, missing file ownership, unclear priority, or a decision that could materially change the implementation, ask the user. Do not guess through ambiguity. Ask early, with the smallest concrete question that unblocks the work. </clarity_first> <source_of_truth> `handoff.xml` is the canonical planning and pickup file. Supporting markdown/design files may be referenced from it, but they are not competing sources of truth. Read supporting files only when the handoff points to them or the user asks. </source_of_truth> <authority_order> Read and act in this priority order: 1. `<active>` - interrupted work to resume, verify, or finish first 2. `<next>` - approved ready-to-start task packets 3. `<decide>` - questions that need the user 4. `<blocked>` - work that cannot proceed until a reason is cleared