handoff

# Phase 3: Handoff Declarative phase skill. Invoked by the prd-taskmaster orchestrator when `current_phase` is `HANDOFF`. Never called directly by a user. The one rule: **detect what the user has, recommend ONE mode, give the user a structured choice, dispatch the chosen mode. Mode D executes only on tier=premium; otherwise it is a locked teaser.** ## Entry gate 1. Call `mcp__plugin_prd_go__check_gate(phase="HANDOFF", evidence={})`. If the call returns `{gate_passed: false, violations: [...]}`, report the violations and stop. The gate protects against re-entering a completed phase or skipping ahead from GENERATE. **Known issue (Mum dogfood feedback [4]/[10]):** check_gate(HANDOFF) requires `user_mode_choice` and `plan_file_exists` — both produced by HANDOFF itself. On first entry, evidence=`{}` will fail. State machine LEGAL_TRANSITIONS already prevents illegal entry — proceed past this gate on first entry. Semantic fix in flight (see morning brief). 2. Read the GENERATE outputs — `.taskmaster/docs/prd.md`, `.taskmaster/tasks/tasks.json`, `.taskmaster/reports/task-complexity-report.json`. If any are missing, report and stop. The gate should have caught this, but belt-and-braces. ## Handoff checklist Copy into your response before running the procedure: ``` HANDOFF CHECKLIST: - [ ] Capabilities detected (tier + per-capability flags) - [ ] Recommended mode: ___ (reason: ___) - [ ] Summary displayed (spec location, task count, capabilities) ...