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={})` for diagnostics. `check_gate` is an EXIT gate: it requires `user_mode_choice` and `plan_file_exists` — both produced by HANDOFF itself, i.e. evidence to *advance*, not to *enter*. On first entry neither exists yet, so a `gate_passed: false` here is EXPECTED — the state machine's legal transitions already guarantee only legal entry. - **First entry** (no evidence yet): note the result and continue with the Procedure. - **Re-entry**: if the gate reports violations, report them and stop — it protects against re-running a completed phase or skipping ahead from GENERATE. 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 displaye...