recipe-discoverlisted

**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. **Delegate analysis work** to sub-agents (via Agent tool) when context separation benefits accuracy 2. **Follow the discovery flow** defined below 3. **Stop at every `[STOP — BLOCKING]` marker** — present findings and CANNOT proceed until user explicitly confirms ## 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 Identification → [Stop: Opportunity confirmation] ↓ 5. Hypothesis Generation → [Stop: Hypothesis review] ↓ Output: Opportunity files + Hypothesis files in docs/discovery/ ``` ## Execution Decision Flow ### 1. Context Assessment Input: $ARGUMENTS **Assess the starting point:** | Situation | Action | |-----------|--------| | Greenfield (no existing product) | Full business + user analysis | | Existing codebase | Invoke codebase-analyzer first for objective fact-gathering | | Specific market opportunity | Focus on market analysis + VPC | | User feedback / support tickets | Focus on user analysis + journey mapping | | Vision exists (`docs/product/vision.md`) | Align discovery with Produ