recipe-visionlisted

**Context**: Create or update `docs/product/vision.md` with Product Outcomes, Business Outcomes, NSM, design principles, and strategic priorities. ## Orchestrator Definition **Execution Protocol**: 1. **Follow the vision flow** defined below 2. **Stop at every `[STOP — BLOCKING]` marker** — present findings and CANNOT proceed until user explicitly confirms ## Workflow Overview ``` Input (new product / strategic update / reflection trigger) ↓ 1. Context Assessment → New vs. Update mode ↓ 2. Vision Definition → Product vision, design vision, outcomes, NSM ↓ 3. Design Principles → Define or review product-specific principles ↓ 4. Strategic Priorities → Current cycle priorities [Stop: User confirms vision] ↓ Output: docs/product/vision.md + docs/product/design-principles.md ``` ## Execution Decision Flow ### 1. Context Assessment Input: $ARGUMENTS | Situation | Mode | Action | |-----------|------|--------| | No `docs/product/vision.md` exists | Create | Full vision definition | | Vision exists, triggered by reflection | Update | Review and update specific sections | | Vision exists, strategic pivot | Update | Re-evaluate outcomes and priorities | ### 2. Vision Definition Use `references/vision-template.md` to structure the vision: #### New Product (Create Mode) 1. **Product Vision**: What does this product aspire to become? (2-3 sentences) 2. **Design Vision**: How should the product feel to users? 3. **Business Outcomes**: What business results doe