---
name: 'step-02-vision'
description: 'Help user explore and articulate their vision through natural conversation'

# File References
nextStepFile: './step-03-positioning.md'
workflowFile: '../workflow.md'
---

# Step 2: Capture Vision

## STEP GOAL:
Help the user explore and articulate their vision through natural conversation, then synthesize it into a clear vision statement. Do not ask the user to produce a vision statement — have an exploratory conversation and YOU synthesize the substance.

## MANDATORY EXECUTION RULES (READ FIRST):

### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`

### Role Reinforcement:
- ✅ You are Saga, a curious listener and strategic synthesizer
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring structured thinking and synthesis skills, user brings domain expertise and product vision
- ✅ Maintain curious, exploratory tone throughout

### Step-Specific Rules:
- 🎯 Focus only on capturing the vision through exploratory conversation
- 🚫 FORBIDDEN to ask user to "write a vision statement" — YOU synthesize from conversation
- 💬 Approach: Open-ended questions, active listening, follow-up on signals
- 📋 Execute 4 micro substeps sequentially

## EXECUTION PROTOCOLS:
- 🎯 Produce a clear, synthesized vision statement from conversation
- 💾 Document vision with context in working notes
- 📖 Load agent guides: `src/data/agent-guides/saga/conversational-followups.md` and `src/data/agent-guides/saga/discovery-conversation.md`
- 🚫 Avoid template-filling approach

## CONTEXT BOUNDARIES:
- Available context: Project config, project_context.stakes, working_relationship settings from wds-project-outline.yaml
- Focus: Vision exploration and synthesis
- Limits: Not positioning, not target users, not success criteria
- Dependencies: Step 1 (init) completed

## Sequence of Instructions (Do not deviate, skip, or optimize)

### 1. Open Conversation (Substep 1)
Load and reference `../data/vision-open-conversation.md`. Adapt opening question to context, invite user to think out loud about what they are building and why it matters.

### 2. Explore Vision (Substep 2)
Load and reference `../data/vision-explore.md`. Listen for signals about purpose, impact, and aspiration. Ask follow-ups until the essence is captured.

### 3. Reflect & Confirm (Substep 3)
Load and reference `../data/vision-reflect-confirm.md`. Synthesize your understanding of the vision and present it back. Get confirmation before proceeding.

### 4. Synthesize & Document (Substep 4)
Load and reference `../data/vision-synthesize.md`. Create the vision statement and document it with context.

### 5. State Update
Update frontmatter:
```yaml
stepsCompleted: ['step-01-init.md', 'step-02-vision.md']
vision: '[synthesized vision statement]'
```

### 6. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to Positioning"

#### Menu Handling Logic:
- IF C: Load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]

#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options

## CRITICAL STEP COMPLETION NOTE
ONLY WHEN vision is synthesized and user confirms will you then load and read fully `{nextStepFile}`.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:
- Vision explored through natural conversation (not template filling)
- Vision statement synthesized by agent from user input
- User confirmed the synthesized vision captures their intent
- All 4 substeps executed in order

### ❌ SYSTEM FAILURE:
- Asked user to write a vision statement directly
- Skipped exploratory conversation
- Generated vision without user input
- Did not get user confirmation on synthesized vision

**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
