Momento/.agent/skills/wds-2-trigger-mapping/steps-c/step-00b-business-goals-extract.md

---
name: 'step-00b-business-goals-extract'
description: 'Extract and validate business goals from existing documentation'

# File References
nextStepFile: './step-00c-target-groups-extract.md'
activityWorkflowFile: '../workflow.md'
---

# Step 2: Business Goals Extraction

## STEP GOAL:

Extract, validate, and refine business goals (vision statement and strategic objectives) from the user's existing documentation through collaborative dialogue.

## 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 the Analyst - facilitating strategic clarity from existing documentation
- ✅ 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 facilitation and pattern recognition, user brings business knowledge and user insight
- ✅ Work together as equals in a partnership, not a client-vendor relationship

### Step-Specific Rules:

- 🎯 Focus on extracting and validating vision and objectives from documentation
- 🚫 FORBIDDEN to invent business goals not supported by documentation or user input
- 💬 Approach: Frame as validation - "Your material suggests X, is this correct?"
- 📋 Fill gaps through conversation if documentation is incomplete
- 📋 Help transform vague goals into SMART objectives

## EXECUTION PROTOCOLS:

- 🎯 Analyze documentation for vision statements and objectives
- 💾 Store validated vision_statement and objectives
- 📖 Present extracted goals for user validation
- 🚫 Do not proceed until vision and objectives are confirmed

## CONTEXT BOUNDARIES:

- Available context: User's documentation from step-00a analysis
- Focus: Vision statement and strategic objectives extraction/validation
- Limits: Only extract what exists or fill gaps through dialogue - do not fabricate
- Dependencies: Requires completed step-00a documentation analysis

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

### 1. Extract Vision Statement

Analyze documentation for vision and objectives.

**If clear vision found:**
Present: "Your documentation suggests this vision:
> {{extracted_vision}}
Is this the aspirational goal you're working toward?"

Ask: "Does this capture your vision, or should we refine it?"

**If vague vision found:**
Present: "I found some aspirational language in your documentation. It seems like your vision is:
> {{interpreted_vision}}
But this isn't explicitly stated. Is this accurate?"

Ask: "Should we use this, or define a clearer vision statement?"

**If no vision found:**
Present: "I don't see an explicit vision statement in your documentation. However, based on your objectives and plans, the implied vision seems to be:
> {{inferred_vision}}
This is reverse-engineered from what you're trying to achieve."

Ask: "Does this capture your aspirational goal? Or should we define it differently?"

Refine based on feedback and store vision_statement.

### 2. Extract Strategic Objectives

**If SMART objectives found:**
Present the extracted measurable objectives with their metrics, targets, and timelines. Note they look SMART. Ask for confirmation or adjustments.

**If vague goals found:**
Present the original vague goals alongside suggested SMART versions. Ask if the SMART versions capture what needs to be measured. Refine based on feedback.

**If no objectives found:**
Ask: "What metrics would prove you're achieving your vision? Think about user metrics, business metrics, and quality metrics."

Create objectives through conversation using SMART method.

Store objectives.

### 3. Present Workshop 1 Summary

Output:
"**Workshop 1 Complete!**

**Vision:**
{{vision_statement}}

**Strategic Objectives:**
{{#each objectives}}
{{@index + 1}}. {{this.statement}}
{{/each}}

Next, we'll identify who can help you achieve these goals."

### 4. Present MENU OPTIONS

Display: "**Select an Option:** [C] Continue to Target Groups Extraction | [M] Return to Activity Menu"

#### Menu Handling Logic:
- IF C: Load and execute {nextStepFile}
- IF M: Return to {activityWorkflowFile}
- 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 selects [C] will you load the next step file. Vision and objectives must be confirmed before proceeding to target group extraction.

---

## 🚨 SYSTEM SUCCESS/FAILURE METRICS

### ✅ SUCCESS:
- Vision statement extracted or created through dialogue
- Strategic objectives validated as SMART (Specific, Measurable, Achievable, Relevant, Time-bound)
- Vague goals transformed into measurable objectives
- User confirmed both vision and objectives
- Gaps filled through collaborative conversation
- Results stored for subsequent steps

### ❌ SYSTEM FAILURE:
- Inventing business goals not supported by documentation
- Skipping vision statement
- Accepting vague goals without making them SMART
- Not getting user confirmation on extracted goals
- Proceeding without stored vision_statement and objectives
- Pure extraction without validation dialogue

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