recipe-blueprintlisted

**Context**: Create or update structural design artifacts in `docs/product/design/` that provide shared context for prototype generation and downstream UI specification. Blueprint bridges the gap between "what problems to solve" (discovery) and "what the product looks and works like" (prototypes). ## Orchestrator Definition **Execution Protocol**: 1. **Delegate analysis work** to sub-agents (via Agent tool) when context separation benefits accuracy 2. **Follow the blueprint flow** defined below 3. **Stop at every `[STOP — BLOCKING]` marker** — present findings and CANNOT proceed until user explicitly confirms ## Workflow Overview ``` Input (validated opportunities / discovery outputs / strategic update) ↓ 1. Context Assessment → Determine scope and mode (create vs. update) ↓ 2. MVP Scope Definition → Feature prioritization from validated hypotheses ↓ 3. Information Architecture → Page structure, navigation, multi-sided layout [Stop: User confirms IA] ↓ 4. Content Model → Entity types, relationships, states ↓ 5. Core User Flows → 5-10 primary flows across personas [Stop: User confirms structure] ↓ 6. Brand Direction → Visual tone, color/typography direction, reference products ↓ 7. AI Interaction Model → Interaction patterns, capability boundaries, guardrails (if applicable) [Stop: User confirms design direction] ↓ Output: docs/product/design/ artifacts ``` ## Execution Decision Flow ### 1. Context Assessment Input: $ARGUMENTS **Read pro