setup

# Phase 0: Setup Declarative phase skill. Invoked by the prd-taskmaster orchestrator when `current_phase` is null or `SETUP`. Never called directly by a user. ## Entry gate 1. Call `mcp__plugin_prd_go__check_gate(phase="SETUP", 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. **Known issue (Mum dogfood feedback [4]):** check_gate semantics are structurally an EXIT gate (verifies evidence sufficient to advance) but wired here as an ENTRY gate. On first entry, evidence=`{}` will fail the SETUP gate's `validate_setup.ready=true` requirement (which Step 4 below produces). State machine LEGAL_TRANSITIONS (`None: ["SETUP"]`) already prevents illegal entry — proceed past this gate on first entry and rely on the exit gate for evidence verification. Semantic fix in flight (see morning brief). ## Procedure (5 steps, abort on hard failure) ### Step 1: Backend detection Run backend detection: ```bash python3 script.py backend-detect ``` If TaskMaster is unavailable, report one compact info line: ``` TaskMaster is optional. Installing task-master-ai unlocks the TaskMaster backend: npm install -g task-master-ai Proceeding with the resolved backend. ``` Do NOT auto-install and do NOT stop for installation. Continue with the resolved backend. ### Step 2: Project init Check whether the current project has a `.ta...