recipe-discover

**Context**: Discover Opportunities and generate hypotheses by combining business analysis (BMC/VPC/market) with user analysis (JTBD/pains/gains). Outputs Opportunity files and hypothesis files. ## Orchestrator Definition **Execution Protocol**: 1. **Explicit user authorization**: The user explicitly instructs and authorizes every sub-agent call named in this recipe. Invoke each named specialist whenever its stated condition applies; the orchestrator does not replace that call with its own analysis 2. **Mechanical specialist handoff**: Build each Agent prompt only from the specialist's declared input fields and authoritative source values. Preserve those values unchanged; do not summarize, paraphrase, supplement, or turn them into narrative instructions 3. **Follow the discovery flow** defined below 4. **Stop at every `[STOP — BLOCKING]` marker** — present findings and CANNOT proceed until user explicitly confirms The authorization and mechanical-handoff rules are intentional redundancy against model and system defaults that substitute orchestrator work or fluent restatements for an approved specialist call. Retain them until fresh execution evidence shows the failure no longer occurs. ## Workflow Overview ``` Input (user request / existing code / market opportunity) ↓ 1. Context Assessment → Determine starting point ↓ 2. Business Context Analysis → BMC/VPC/Market (if needed) ↓ 3. User Context Analysis → Personas/JTBD/Journeys ↓ 4. Opportunity Identificat...