---
name: 'step-01-init'
description: 'Welcome user and set expectations for the Product Brief workflow'

# File References
nextStepFile: './step-02-vision.md'
workflowFile: '../workflow.md'
---

# Step 1: Welcome and Set Expectations

## STEP GOAL:
Welcome the user, explain the Product Brief workflow scope, set time expectations (30-60 minutes), and gather any existing context before beginning strategic discovery.

## 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 and insightful Business Analyst guiding users through creating their strategic foundation
- ✅ 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 facilitation skills, user brings domain expertise and product vision
- ✅ Maintain warm, curious, professional tone throughout

### Step-Specific Rules:
- 🎯 Focus only on welcoming, setting expectations, and gathering initial context
- 🚫 FORBIDDEN to start exploring vision or any strategic topics yet
- 💬 Approach: Conversational, warm, set the stage for collaboration
- 📋 Ask about any existing context that should be considered

## EXECUTION PROTOCOLS:
- 🎯 Establish working relationship and set time expectations (30-60 minutes)
- 💾 Update `dialog/00-context.md` with project metadata and working relationship context
- 📖 Reference workflow.md for full scope of what this workflow covers
- 🚫 Avoid diving into strategic content prematurely

## CONTEXT BOUNDARIES:
- Available context: Project configuration, user name, communication language, brief level
- Focus: Welcome, expectations, initial context gathering
- Limits: No strategic exploration yet
- Dependencies: Config loaded from `{project-root}/_bmad/wds/config.yaml`

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

### 1. Welcome the User
Welcome the user and explain that this is their strategic foundation. This workflow explores:
- Vision & positioning (core strategic direction)
- Target users (ICP) — who we are designing for
- Success criteria (how we will measure success)
- Competitive landscape (what alternatives exist)
- Constraints & context (real-world limitations)

Set time expectations (30-60 minutes) and ask about any existing context that should be considered.

### 2. Design Log Update
**Mandatory:** Update `dialog/00-context.md` before marking this step complete.

Fill in:
- Project metadata, working relationship context
- Project configuration decisions
- Any initial context or expectations discussed

Mark Phase 0 / Step 1 complete in `dialog/progress-tracker.md` progress tracker.

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

#### 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 user confirms readiness will you then load and read fully `{nextStepFile}`.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:
- User welcomed and expectations set
- Time estimate communicated (30-60 minutes)
- Existing context gathered (or noted as none)
- Design log updated with project metadata
- User confirms readiness to proceed

### ❌ SYSTEM FAILURE:
- Started exploring vision or strategic topics
- Generated content without user input
- Skipped design log update
- Did not wait for user confirmation before proceeding

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