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={})` for diagnostics. `check_gate` is an EXIT gate: it verifies the evidence to *advance*, not to *enter*. On first DISCOVER entry you have no evidence yet (the User Approval / Self-Approval Gate below produces `user_approved=true` OR `auto_classification=CLEAR with assumptions_documented`), 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 SETUP. 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 (d...