discover

# Phase 1: Discover Declarative phase skill. Invoked by the prd-taskmaster orchestrator when `current_phase` is `DISCOVER`. Never called directly by a user. The one rule: **invoke `superpowers:brainstorming` for discovery, intercept before it chains to `writing-plans` — we control the exit, not the brainstorm skill.** ## Entry gate 1. Call `mcp__plugin_prd_go__check_gate(phase="DISCOVER", 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 SETUP. **Known issue (Mum dogfood feedback [4]):** check_gate is structurally an EXIT gate. On first DISCOVER entry, evidence=`{}` will fail the `user_approved=true OR auto_classification=CLEAR with assumptions_documented` requirement (which the User Approval Gate / Self-Approval Gate below produces). State machine LEGAL_TRANSITIONS already prevents illegal entry — proceed past this gate on first entry. Semantic fix in flight (see morning brief). 2. Detect execution context. If any of the following signals are present, switch to Autonomous Mode: - `.claude/ralph-loop.local.md` exists in the project root - An `auto-enter` / `auto-approve` daemon is running against this session - The skill was invoked with an explicit `--autonomous` flag - Parent orchestrator is a cron, `/pentest-wtf`, or `/ralph-loop` Otherwise proceed in Interactive Mode (default). ## D...