Wds 2 Trigger Mapping

Follow the instructions in ./workflow.md.

Business Goals Document Template

Complete template structure for 01-Business-Goals.md

---

1. Header

# Business Goals & Objectives

> Strategic goals and measurable objectives for [Project Name]

**Document:** Trigger Map - Business Goals
**Created:** [Date]
**Status:** COMPLETE

---

2. Vision Statement

## Vision

**[Insert vision statement from workshop]**

[Should be 1-2 sentences describing the ultimate goal/transformation]

---

3. Business Objectives (3 Priority Tiers)

## Business Objectives

### ⭐ PRIMARY GOAL: [Title] (THE ENGINE)
- **Statement:** [What we're building]
- **Metric:** [How we measure it]
- **Target:** [Specific number]
- **Timeline:** [X months]
- **Impact:** This drives ALL other objectives - this is the key to expansion

---

### 🚀 [SECONDARY GOALS CATEGORY] (Driven by [Primary Goal])

**Objective 1: [Title]**
- **Statement:** [What we're achieving]
- **Metric:** [How we measure]
- **Target:** [Number]
- **Timeline:** [X months from launch]

[Repeat for all secondary objectives: 2, 3, 4...]

---

### 🌟 [TERTIARY GOALS CATEGORY] (Real-World Benefits for Members)

**Note:** These are opportunities [Product] creates FOR the community members - [benefit description].

**Objective X: [Title]**
- **Statement:** [What members get]
- **Metric:** [How we measure member success]
- **Target:** [Number]
- **Timeline:** [X months]
- **Benefit to Members:** [Career/personal growth impact]

[Repeat for all tertiary objectives]

---

4. The Flywheel Section

## The Flywheel: How Goals Connect

**THE ENGINE (Priority #1):**
- [Primary goal number] [primary goal description]
- Timeline: [X] months
- These [users] [action that drives everything]
- They create the flywheel that drives ALL other objectives

**[Secondary Category] (Priority #2):**
- Driven BY the [primary goal achievers]
- [List key targets with numbers]
- Timeline: [X] months
- Focus: [What this tier achieves]

**[Tertiary Category] (Priority #3):**
- Real-world benefits FOR community members
- [List key opportunities]
- Timeline: [X] months
- **Key benefit**: [How members' lives improve]

---

5. Success Metrics Alignment

## Success Metrics Alignment

### How Trigger Map Connects to Objectives (Properly Prioritized):

**⭐ PRIMARY: Creating Awesome [Users] Who Become [Champions] → Achieves:**
- ✅ **[Number] [champions]** (THE ENGINE - [Persona] becomes one of them naturally)
- ✅ [Action 1]
- ✅ [Action 2]
- ✅ [Natural outcome]
- **Timeline: [X] months**
- **This drives ALL other objectives**

**🚀 SECONDARY: [Champions] Drive [Product] Adoption → Achieves:**
- ✅ [Objective 1] ([champions] spread the word)
- ✅ [Objective 2] ([champions] demonstrate value)
- ✅ [Objective 3] ([champions] create engagement)
- **Timeline: [X] months**

**🌟 TERTIARY: [Product] Success Creates Opportunities for Community → Achieves:**
- ✅ [Opportunity 1] (members [benefit])
- ✅ [Opportunity 2] (members [benefit])
- ✅ [Opportunity 3] (members [benefit])
- **Timeline: [X] months**
- **Benefit: [Impact on members' lives/careers]**

**The Trigger Map IS the Strategic Foundation - And Prioritization Matters**

The page must empower [Primary Persona] → make [them] awesome → [they] naturally become [champions] → [champions] drive adoption → adoption creates opportunities for all members.

---

6. Related Documents Footer

## Related Documents

- **[00-trigger-map.md](00-trigger-map.md)** - Visual overview and navigation
- **[02-[Primary].md](02-[Primary].md)** - Primary persona
- **[03-[Secondary].md](03-[Secondary].md)** - Secondary persona
- **[04-[Tertiary].md](04-[Tertiary].md)** - Tertiary persona [if exists]
- **[05-Key-Insights.md](05-Key-Insights.md)** - Strategic implications

---

_Back to [Trigger Map](00-trigger-map.md)_

Key Insights Document Structure Guide

Complete template for generating 05-Key-Insights.md

---

1. Header

# Key Insights & Strategic Implications

> How the Trigger Map informs design and development decisions

**Document:** Trigger Map - Key Insights
**Created:** [Date]
**Status:** COMPLETE

---

2. The Flywheel Section

## The Flywheel: [X] [Champions] Drive Everything

**THE ENGINE (Priority #1):**
- [X] [champions] are THE PRIMARY GOAL
- Timeline: [X] months
- These [description of what makes them champions]
- They create the flywheel that drives ALL other objectives

**[Product] Adoption (Priority #2):**
- Driven BY the [X] [champions] spreading the word
- [List key adoption targets with numbers]
- Timeline: [X] months
- Focus: [What this tier achieves]

**Community Opportunities (Priority #3):**
- Real-world benefits FOR community members
- [List key opportunities]
- Timeline: [X] months
- **Key benefit**: [How members' lives/careers improve]

---

3. Primary Development Focus

## Primary Development Focus

1. **Create Awesome [Users] Who Become [Champions]** - [Primary persona] is the profile who becomes one of the [X]
2. **[Key Transformation Need]** - Address [primary persona]'s core need to move from [before] to [after]
3. **[Core Capability Building]** - [Specific approach to building confidence/skill]
4. **[Validation Need]** - Show [secondary persona] how [product] delivers [value]
5. **[Support Need]** - Prove to [tertiary persona] that [benefit] reduces [pain]

---

4. Critical Success Factors

## Critical Success Factors

- **[Factor 1]**: [Description] (the [key element] in action)
- **[Factor 2]**: [Clear steps description]
- **[Factor 3]**: [Proof element] ([specific example])
- **[Factor 4]**: [Access description]
- **[Factor 5]**: [Scope description] (not just [limitation])

---

5. Design Implications

## Design Implications

### Content Priorities Based on Triggers:

**[Section 1] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

**[Section 2] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

**[Section 3] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

**[Section 4] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

**[Section 5] Must:**
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

---

6. Emotional Transformation Goals

## Emotional Transformation Goals

- **[Goal 1]**: "[First-person statement of transformation]"
- **[Goal 2]**: "[First-person statement about capability]"
- **[Goal 3]**: "[First-person statement about confidence]"
- **[Goal 4]**: "[First-person statement about impact]"
- **[Goal 5]**: "[First-person statement about identity]"

---

7. Design Focus Statement

## Design Focus Statement

**The [Product] [Page/Experience] transforms [target users] from [before state] into [after state] who [key transformation] as a [metaphor], not a [negative metaphor].**

**Primary Design Target:** [Primary Persona Name] ([Role])

**Must Address (Critical for Conversion):**
1. [Fear 1] → [Solution approach]
2. [Fear 2] → [Solution approach]
3. [Fear 3] → [Solution approach]
4. [Want 1] → [Delivery approach]
5. [Want 2] → [Delivery approach]

**Should Address (Supporting Conversion):**
1. [Secondary persona] needs [thing] → [Approach]
2. [Tertiary persona] needs [thing] → [Approach]
3. [Community proof element] → [Approach]
4. [Learning curve concern] → [Approach]
5. [Integration concern] → [Approach]

---

8. Development Phases

## Development Phases

### **First Deliverable: [Product Name] [Initial Release]**
Focus on empowering [primary persona] from [before] to awesome [after] who naturally becomes [champion]:
- **[Section 1]** - [Key message/approach]
- **[Section 2]** - [Key message/approach]
- **[Section 3]** - [Key message/approach]
- **[Section 4]** - [Key message/approach]
- **[Section 5]** - [Key message/approach]
- **[Section 6]** - [Key message/approach]
- **[Section 7]** - [Key message/approach]

### **Future Phases: Additional Content**
- **Phase 2**: [Next priority]
- **Phase 3**: [Next priority]
- **Phase 4**: [Next priority]
- **Phase 5**: [Next priority]

---

9. Related Documents Footer

## Related Documents

- **[00-trigger-map.md](00-trigger-map.md)** - Visual overview and navigation
- **[01-Business-Goals.md](01-Business-Goals.md)** - Objectives and metrics
- **[02-[Primary].md](02-[Primary].md)** - Primary persona
- **[03-[Secondary].md](03-[Secondary].md)** - Secondary persona
- **[04-[Tertiary].md](04-[Tertiary].md)** - Tertiary persona [if exists]
- **[06-Design-Implications.md](06-Design-Implications.md)** - Detailed design requirements [if exists]

---

_Back to [Trigger Map](00-trigger-map.md)_

---

Template Guidelines

Tone:

• Actionable and specific
• "Create awesome" language throughout
• Links back to workshop outputs

Focus:

• PRIMARY persona gets most attention in "Must Address"
• Secondary and tertiary get "Should Address"
• Transformation is central theme

Design Implications:

• Organized by page/experience sections
• Each section has clear "must do" items
• Tied to specific fears/wants from personas

Emotional Goals:

• First-person statements
• Show identity shift
• Positive and empowering

Expected Length:

• ~145-150 lines for complete document
• Use specific examples from trigger map
• Keep actionable and scannable

---

_Complete structure guide for Step 04: Generate Key Insights_

Micro Instructions: Generate Mermaid Trigger Map Diagram

Purpose: Create visually appealing, professional Mermaid flowchart diagrams for trigger maps

---

Format Requirements

1. Mermaid Configuration

%%{init: {'theme':'base', 'themeVariables': { 'fontFamily':'Inter, system-ui, sans-serif', 'fontSize':'14px'}}}%%

• Always use Inter/system-ui font
• Set fontSize to 14px
• Use base theme

2. Flowchart Direction

flowchart LR

• Always use left-to-right (LR) direction
• Business goals on left → Platform center → Target groups → Driving forces on right

3. Node Content Formatting

Every node must:

• Start with <br/> for top padding
• End with <br/><br/> for bottom padding
• Use <br/> for line breaks (not multiple spaces)
• Include emoji at the start of the title

Example node structure:

NodeID["<br/>🎯 TITLE<br/><br/>Line 1<br/>Line 2<br/>Line 3<br/><br/>"]

4. Business Goals Nodes (Left Column)

Structure:

BG1["<br/>🌟 WDS VISION<br/><br/>Point 1<br/>Point 2<br/>Point 3<br/><br/>"]
BG2["<br/>📊 CORE OBJECTIVES<br/><br/>Point 1<br/>Point 2<br/>Point 3<br/><br/>"]

Rules:

• Use BG0, BG1, BG2, etc. as node IDs
• Include relevant emoji (🌟 for vision, 📊 for objectives, 🚀 for growth, etc.)
• List 3-5 key points per goal
• Keep titles in ALL CAPS

5. Platform Node (Center)

Structure:

PLATFORM["<br/>🎨 PLATFORM NAME<br/><br/>Tagline or category<br/><br/>Transformation statement<br/>that spans multiple lines<br/>describing the core change<br/><br/>"]

Rules:

• Single node ID: PLATFORM
• Include platform emoji
• Show tagline/category
• Include transformation/value statement
• Break long text into multiple lines

6. Target Group Nodes

Structure:

TG1["<br/>🎯 PERSONA NAME<br/>PRIORITY LEVEL<br/><br/>Trait 1<br/>Trait 2<br/>Trait 3<br/><br/>"]

Rules:

• Use TG0, TG1, TG2, etc. as node IDs
• Include persona-specific emoji
• Show priority (PRIMARY TARGET, SECONDARY TARGET, etc.)
• List 3-4 key profile traits
• Keep persona name in ALL CAPS

7. Driving Forces Nodes

Structure:

DF1["<br/>🎯 PERSONA'S DRIVERS<br/><br/>WANTS<br/>✅ Positive driver 1<br/>✅ Positive driver 2<br/>✅ Positive driver 3<br/><br/>FEARS<br/>❌ Negative driver 1<br/>❌ Negative driver 2<br/>❌ Negative driver 3<br/><br/>"]

Rules:

• Use DF0, DF1, DF2, etc. matching TG IDs
• Use same emoji as corresponding persona
• Add "PERSONA'S DRIVERS" in ALL CAPS
• Section headers: "WANTS" and "FEARS" (no emojis on headers)
• ✅ emoji before each positive driver
• ❌ emoji before each negative driver
• Exactly 3 drivers per category (top 3 only)
• Blank line between sections

8. Connections

Required connections:

%% Business Goals to Platform
BG0 --> PLATFORM
BG1 --> PLATFORM
BG2 --> PLATFORM

%% Platform to Target Groups
PLATFORM --> TG0
PLATFORM --> TG1
PLATFORM --> TG2

%% Target Groups to Driving Forces
TG0 --> DF0
TG1 --> DF1
TG2 --> DF2

Rules:

• All business goals connect to platform
• Platform connects to all target groups
• Each target group connects to its driving forces
• Use simple arrows (-->), no fancy styling

9. Styling Classes

Required classes:

classDef businessGoal fill:#f3f4f6,color:#1f2937,stroke:#d1d5db,stroke-width:2px
classDef platform fill:#e5e7eb,color:#111827,stroke:#9ca3af,stroke-width:3px
classDef targetGroup fill:#f9fafb,color:#1f2937,stroke:#d1d5db,stroke-width:2px
classDef drivingForces fill:#f3f4f6,color:#1f2937,stroke:#d1d5db,stroke-width:2px

Application:

class BG0,BG1,BG2 businessGoal
class PLATFORM platform
class TG0,TG1,TG2 targetGroup
class DF0,DF1,DF2 drivingForces

Rules:

• Always use these exact colors (light grays with dark text)
• Business goals: lightest gray (#f3f4f6)
• Platform: medium gray (#e5e7eb) with thicker border (3px)
• Target groups: near white (#f9fafb)
• Driving forces: light gray (#f3f4f6)
• Text color: dark gray (#1f2937 or #111827)
• Borders: light gray (#d1d5db or #9ca3af)

---

Complete Example Template

%%{init: {'theme':'base', 'themeVariables': { 'fontFamily':'Inter, system-ui, sans-serif', 'fontSize':'14px'}}}%%
flowchart LR
    %% Business Goals
    BG0["<br/>🌟 VISION<br/><br/>Vision statement line 1<br/>Vision statement line 2<br/>Vision statement line 3<br/><br/>"]
    BG1["<br/>📊 OBJECTIVES<br/><br/>Objective 1<br/>Objective 2<br/>Objective 3<br/><br/>"]
    
    %% Platform
    PLATFORM["<br/>🎨 PRODUCT NAME<br/><br/>Product category or tagline<br/><br/>Transformation statement<br/>describing the change<br/><br/>"]
    
    %% Target Groups
    TG0["<br/>🎯 PERSONA ONE<br/>PRIMARY TARGET<br/><br/>Profile trait 1<br/>Profile trait 2<br/>Profile trait 3<br/><br/>"]
    TG1["<br/>💼 PERSONA TWO<br/>SECONDARY TARGET<br/><br/>Profile trait 1<br/>Profile trait 2<br/>Profile trait 3<br/><br/>"]
    
    %% Driving Forces
    DF0["<br/>🎯 PERSONA ONE'S DRIVERS<br/><br/>WANTS<br/>✅ Positive driver 1<br/>✅ Positive driver 2<br/>✅ Positive driver 3<br/><br/>FEARS<br/>❌ Negative driver 1<br/>❌ Negative driver 2<br/>❌ Negative driver 3<br/><br/>"]
    
    DF1["<br/>💼 PERSONA TWO'S DRIVERS<br/><br/>WANTS<br/>✅ Positive driver 1<br/>✅ Positive driver 2<br/>✅ Positive driver 3<br/><br/>FEARS<br/>❌ Negative driver 1<br/>❌ Negative driver 2<br/>❌ Negative driver 3<br/><br/>"]
    
    %% Connections
    BG0 --> PLATFORM
    BG1 --> PLATFORM
    PLATFORM --> TG0
    PLATFORM --> TG1
    TG0 --> DF0
    TG1 --> DF1

    %% Styling
    classDef businessGoal fill:#f3f4f6,color:#1f2937,stroke:#d1d5db,stroke-width:2px
    classDef platform fill:#e5e7eb,color:#111827,stroke:#9ca3af,stroke-width:3px
    classDef targetGroup fill:#f9fafb,color:#1f2937,stroke:#d1d5db,stroke-width:2px
    classDef drivingForces fill:#f3f4f6,color:#1f2937,stroke:#d1d5db,stroke-width:2px
    
    class BG0,BG1 businessGoal
    class PLATFORM platform
    class TG0,TG1 targetGroup
    class DF0,DF1 drivingForces

---

Emoji Selection Guide

Business Goals

• 🌟 Vision
• 📊 Objectives/Metrics
• 🚀 Growth/Expansion
• 💰 Revenue/Business
• 🤝 Partnerships/Community
• 🎯 Goals/Targets

Personas

• 🎯 Strategic/Primary personas
• 💼 Business/Leadership personas
• 💻 Technical/Developer personas
• 👥 Team/Group personas
• 🎨 Creative/Designer personas
• 📱 User/Customer personas

Platform

• 🎨 Design/Creative products
• 💻 Software/Tech products
• 📱 Mobile/App products
• 🛠️ Tools/Utilities
• 📊 Analytics/Data products
• 🤖 AI/Automation products

---

Quality Checklist

Before finalizing diagram, verify:

• [ ] Mermaid config includes custom font and fontSize
• [ ] All nodes start with <br/> and end with <br/><br/>
• [ ] All titles are in ALL CAPS
• [ ] Each persona has matching emoji in both TG and DF nodes
• [ ] Exactly 3 positive drivers per persona (with ✅)
• [ ] Exactly 3 negative drivers per persona (with ❌)
• [ ] "WANTS" and "FEARS" headers have no emojis
• [ ] All connections are present (goals→platform→groups→forces)
• [ ] Light gray styling with dark text applied
• [ ] Platform has thicker border (3px)
• [ ] No syntax errors or missing brackets

---

Common Mistakes to Avoid

❌ Don't:

• Use multiple spaces for alignment (use <br/> only)
• Mix HTML tags (bold, italic) - keep plain text
• Forget padding (<br/>) at top and bottom
• Use colors other than light grays
• Add emojis to "WANTS" and "FEARS" headers
• Include more than 3 drivers per category
• Use lowercase in titles

✅ Do:

• Use <br/> for all line breaks
• Keep consistent spacing (blank lines between sections)
• Match emojis between personas and their drivers
• Use exactly 3 drivers per category
• Apply consistent styling to all nodes
• Test diagram renders correctly

---

This format creates professional, scannable trigger maps that clearly communicate strategic insights at a glance.

Quality Check & Verification Checklist

Complete checklist for verifying trigger map documentation quality

---

1. File Structure Check

• [ ] 00-trigger-map.md exists
• [ ] 01-Business-Goals.md exists
• [ ] 02-[Primary Persona].md exists
• [ ] 03-[Secondary Persona].md exists
• [ ] 04-[Tertiary Persona].md exists (if applicable)
• [ ] 05-Key-Insights.md exists
• [ ] 06-Feature-Impact.md exists (if Feature Impact workshop was completed)
• [ ] All files use consistent naming pattern

---

2. Mermaid Diagram Quality

In `00-trigger-map.md`:

• [ ] Diagram renders without errors
• [ ] BG0 (PRIMARY GOAL) has gold highlighting (primaryGoal class)
• [ ] All nodes have proper padding (<br/> at start and end)
• [ ] Emojis present: ✅ for wants, ❌ for fears
• [ ] Exactly 3 drivers per persona
• [ ] Connections flow correctly: BG→PLATFORM→TG→DF
• [ ] Styling section includes all 5 classes (primaryGoal, businessGoal, platform, targetGroup, drivingForces)
• [ ] Font family set to Inter or system-ui

---

3. Content Consistency

Across ALL documents:

• [ ] PRIMARY GOAL consistently labeled as "THE ENGINE"
• [ ] Transformation journey clearly described
• [ ] Timeline numbers match across documents
• [ ] Target numbers (50 champions, 5000 users, etc.) are consistent
• [ ] Persona names spelled consistently
• [ ] Product name consistent throughout

---

4. Language Check

Verify empowering language:

• [ ] "Create awesome [users]" NOT "convert users"
• [ ] "Naturally become [champions]" NOT "make them champions"
• [ ] "Community Opportunities" emphasize benefits FOR members
• [ ] No pushy or transactional language
• [ ] Transformation language is positive and organic

---

5. Cross-Reference Verification

Check links in each document:

00-trigger-map.md:

• [ ] Links to 01-Business-Goals.md
• [ ] Links to all persona docs (02, 03, 04...)
• [ ] Links to 05-Key-Insights.md
• [ ] All links use correct file names

01-Business-Goals.md:

• [ ] Links back to 00-trigger-map.md
• [ ] Links to all persona docs
• [ ] Links to 05-Key-Insights.md

Persona documents (02, 03, 04...):

• [ ] Each links back to 00-trigger-map.md
• [ ] Each links to OTHER persona docs
• [ ] Each links to 05-Key-Insights.md

05-Key-Insights.md:

• [ ] Links back to 00-trigger-map.md
• [ ] Links to 01-Business-Goals.md
• [ ] Links to all persona docs

06-Feature-Impact.md (if exists):

• [ ] Links back to 00-trigger-map.md
• [ ] Links to 01-Business-Goals.md
• [ ] Links to all persona docs
• [ ] Links to 05-Key-Insights.md

---

6. Persona Document Completeness

For EACH persona document, verify:

• [ ] Has all 13 sections (header through related docs)
• [ ] Profile summary is compelling (1-2 paragraphs)
• [ ] Background section tells their story
• [ ] Current situation shows challenges
• [ ] Psychological profile reveals motivations
• [ ] 6 driving forces (3 wants + 3 fears) each with Product Promise/Answer
• [ ] Transformation journey (especially PRIMARY)
• [ ] Strategic triangle diagram present
• [ ] Role clearly explained
• [ ] Impact on business goals shown
• [ ] Related documents footer complete

---

7. Hub Document (00) On-Page Content

Verify hub has on-page summaries for:

• [ ] Transformation clearly stated
• [ ] Flywheel explained (3 tiers)
• [ ] Business Strategy section with key points
• [ ] Each persona with profile + drivers visible
• [ ] Strategic Implications with key focus areas
• [ ] "How to Read" explanation present
• [ ] Total length ~220-250 lines

---

8. Business Goals Document (01) Completeness

• [ ] Vision statement present
• [ ] PRIMARY GOAL clearly marked as THE ENGINE
• [ ] SECONDARY goals grouped and explained
• [ ] TERTIARY goals emphasize member benefits
• [ ] Each objective has: Statement, Metric, Target, Timeline, Impact/Benefit
• [ ] Flywheel section explains priorities
• [ ] Success metrics show persona connections
• [ ] Total length ~150-160 lines

---

9. Key Insights Document (05) Completeness

• [ ] Flywheel priorities explained
• [ ] Primary Development Focus lists 5 areas
• [ ] Critical Success Factors (3-5 items)
• [ ] Design Implications by section (5+ sections)
• [ ] Emotional Transformation Goals in first person
• [ ] Design Focus Statement present
• [ ] Development Phases outlined
• [ ] Total length ~145-155 lines

---

10. Feature Impact Document (06) Completeness (If Exists)

• [ ] Scoring system clearly explained
• [ ] Primary persona weighted higher (5/3/1 vs 3/1/0)
• [ ] Feature table with scores for all personas
• [ ] Must Have / Consider / Defer categories
• [ ] Strategic rationale explains prioritization
• [ ] Connection to business goals shown
• [ ] Development phases aligned with flywheel
• [ ] Each feature ties to specific persona drivers

---

11. Priority Tier Consistency

Verify throughout all documents:

• [ ] ⭐ PRIMARY GOAL always uses star emoji + gold in diagram
• [ ] 🚀 SECONDARY uses rocket emoji
• [ ] 🌟 TERTIARY uses sparkle emoji
• [ ] PRIMARY always described as "THE ENGINE"
• [ ] SECONDARY always "driven by" PRIMARY
• [ ] TERTIARY always "benefits FOR members"

---

12. Driving Forces Quality

For each persona's 6 driving forces:

• [ ] Each want has [Product] Promise:
• [ ] Each fear has [Product] Answer:
• [ ] Promises/Answers are specific (not generic)
• [ ] They show HOW product addresses the driver
• [ ] Language is empowering and actionable

---

13. Formatting Check

• [ ] Markdown renders correctly
• [ ] Headers use proper hierarchy (# ## ###)
• [ ] Code blocks use correct syntax
• [ ] Emojis display properly
• [ ] Lists are formatted consistently
• [ ] Links are properly formatted [text](file.md)
• [ ] Horizontal rules (---) used appropriately

---

Error Correction Process

If any checklist item fails:

1. Identify which document(s) need fixing 2. Re-read the specific step instructions 3. Make corrections 4. Re-verify the corrected sections

---

_Complete quality checklist for Step 05: Quality Check & Verification_

Step 1: Documentation Synthesis

STEP GOAL:

Receive and analyze existing documentation from the user, identify what is covered and what gaps exist, and prepare for structured extraction through the documentation synthesis workshops.

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 receiving documentation and creating a mental map of coverage
• 🚫 FORBIDDEN to skip documentation analysis or assume content without reading
• 💬 Approach: Frame questions as "Your material suggests X, is this correct?" not as pure extraction
• 📋 Documentation may only answer PART of the Trigger Map questions - identify gaps explicitly
• 📋 Create a clear picture of what is present, vague, or missing before proceeding

EXECUTION PROTOCOLS:

• 🎯 Analyze documentation thoroughly before presenting findings
• 💾 Create mental map of what is covered vs. gaps
• 📖 Present clear summary of documentation strengths and gaps
• 🚫 Do not proceed to extraction until documentation is analyzed

CONTEXT BOUNDARIES:

• Available context: User's existing documentation (provided in conversation)
• Focus: Documentation analysis, coverage mapping, gap identification
• Limits: Do not generate Trigger Map content yet - only analyze what exists
• Dependencies: Requires user to provide their documentation

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

1. Present Documentation Synthesis Workshop Introduction

Output: Documentation Synthesis Workshop

"I'll help you transform your existing documentation into an actionable Trigger Map.

Here's how this works:

• I'll analyze your documentation
• We'll go through the same workshops as building from scratch
• But I'll frame questions based on what your material suggests
• Where documentation is incomplete, we'll fill gaps through conversation

This creates a single-slide strategic reference from your extensive documentation.

Let's begin!"

2. Receive and Analyze Documentation

Ask user to provide their documentation.

Read through all provided documentation carefully.

Create mental map of what is covered:

• Vision/strategy statements (present/absent/vague?)
• Business goals or objectives (SMART/vague/missing?)
• User research findings (deep/shallow/none?)
• Target group descriptions (behavioral/demographic/missing?)
• User pain points, needs, desires (explicit/implied/absent?)
• Project plans or feature lists (detailed/high-level/none?)
• Psychological insights about users (present/absent?)

3. Present Analysis Summary

Output:

"Documentation analyzed.

I can see you have: {{what_is_present}}

{{#if gaps_identified}} I notice some areas are less covered: {{what_is_missing_or_vague}} {{/if}}

We'll work through the same workshops as building a Trigger Map from scratch, but I'll use your documentation to inform the questions. Where your docs are clear, I'll validate. Where they're incomplete, we'll fill gaps together.

Ready to start with Business Goals?"

Wait for user confirmation before proceeding.

4. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Business Goals 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. Do NOT auto-proceed. Documentation analysis must be confirmed by the user before moving to extraction workshops.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Documentation received and thoroughly analyzed
• Coverage map created identifying present, vague, and missing areas
• Clear summary presented to user with strengths and gaps
• User confirmed understanding before proceeding
• Framed as validation ("your material suggests...") not extraction
• Mental model of documentation quality established for subsequent steps

❌ SYSTEM FAILURE:

• Skipping documentation analysis
• Not identifying gaps in documentation
• Generating Trigger Map content before analysis
• Not presenting coverage summary to user
• Proceeding without user confirmation
• Treating documentation as complete when it has gaps
• Not reading provided documentation thoroughly

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

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.

Step 3: Target Groups Extraction

STEP GOAL:

Extract, validate, and deepen target group definitions and personas from the user's existing documentation, transforming demographic descriptions into behavioral profiles with psychological depth.

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 - building empathy through understanding 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 deepening target group definitions from documentation
• 🚫 FORBIDDEN to accept demographic-only descriptions without adding behavioral depth
• 💬 Approach: Frame as validation - "Your material suggests X, is this correct?"
• 📋 Documentation may have demographics but need behavioral depth - probe for it
• 📋 Help prioritize to 3-4 groups maximum

EXECUTION PROTOCOLS:

• 🎯 Analyze documentation for target groups and user research
• 💾 Store validated target_groups and personas
• 📖 Transform demographic descriptions into behavioral profiles
• 🚫 Do not proceed until personas have psychological depth

CONTEXT BOUNDARIES:

• Available context: User's documentation, validated vision and objectives from step-00b
• Focus: Target group identification, persona creation with behavioral/psychological depth
• Limits: Maximum 3-4 target groups - help prioritize if more exist
• Dependencies: Requires completed step-00b with confirmed vision and objectives

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

1. Extract Target Groups

Analyze documentation for target groups and user research.

If target groups found: Present extracted groups with their characteristics. Ask if these are the right groups and suggest focusing on top 3-4 most critical for objectives. Help prioritize.

If demographic-only groups found: Present the demographic descriptions but explain that for Trigger Mapping, behavioral profiles are needed. Ask about each group's context and situation when using the product, and what they are trying to accomplish.

Transform demographic descriptions into behavioral profiles through conversation.

If no target groups found: Present inferred groups based on context and objectives. Ask: "Who are the 3-4 key user groups whose product usage will drive your objectives? Remember the core question: WHO out there in the world will make sure, with their use of the product, that you achieve your goals?"

Define target groups through conversation.

Store target_groups.

2. Create Detailed Personas

For each target group, check documentation for:

• Context and situation
• Goals and aspirations
• Frustrations and fears
• Behavioral patterns
• User quotes or interview insights

If deep personas found: Present personas with context, goals, frustrations, and any research quotes. Ask if they capture the psychological depth needed and request refinements.

If shallow personas found: Present basic descriptions and explain more psychological depth is needed. Ask for each persona: context when using product, what they are trying to accomplish (usage goals), what frustrates them, and what they fear or want to avoid.

Build psychological depth through conversation.

If interview quotes available: Incorporate quotes to enrich persona descriptions.

Store personas.

3. Present Workshop 2 Summary

Output: "Workshop 2 Complete!

Target Groups (Prioritized): {{#each prioritized_groups}} {{@index + 1}}. {{this.name}} {{/each}}

Next, we'll map what drives each group psychologically."

4. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Driving Forces 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. Target groups and personas must have behavioral and psychological depth before proceeding.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Target groups extracted or identified through dialogue
• Groups prioritized to 3-4 maximum
• Personas created with behavioral profiles (not just demographics)
• Psychological depth added: context, goals, frustrations, fears
• User quotes incorporated where available
• User confirmed target groups and personas
• Results stored for subsequent steps

❌ SYSTEM FAILURE:

• Accepting demographic-only descriptions without behavioral depth
• Having more than 4 target groups without prioritizing
• Not validating extracted groups with user
• Missing psychological depth in personas
• Proceeding without confirmed target_groups and personas
• Not asking about context, goals, frustrations, and fears

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

Step 4: Driving Forces Extraction

STEP GOAL:

Extract and validate both positive and negative driving forces for each persona from the user's existing documentation, ensuring psychological depth and usage-context specificity.

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 - uncovering motivation psychology 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 BOTH positive and negative driving forces per persona
• 🚫 FORBIDDEN to skip negative drivers - they are often more powerful (loss aversion)
• 💬 Approach: Frame as validation - "Your material suggests X, is this correct?"
• 📋 Documentation often focuses on positive wants - actively probe for negative drivers
• 📋 Ensure drivers are specific to the usage context, not general life goals

EXECUTION PROTOCOLS:

• 🎯 Analyze documentation for psychological drivers per persona
• 💾 Store validated driving_forces_positive and driving_forces_negative for each persona
• 📖 Transform pain points into psychological negative drivers
• 🚫 Do not proceed until both positive and negative forces are mapped for all personas

CONTEXT BOUNDARIES:

• Available context: User's documentation, validated vision/objectives from step-00b, personas from step-00c
• Focus: Positive and negative driving forces per persona
• Limits: Must have both positive AND negative forces for each persona
• Dependencies: Requires completed step-00c with confirmed personas

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

1. Introduce Driving Forces Framework

Output: "Mapping Psychological Drivers

For each persona, we need to understand BOTH sides of motivation:

• Positive drivers (what they want to achieve)
• Negative drivers (what they fear or want to avoid)

Remember: Negative drivers are often more powerful (loss aversion principle)."

2. For Each Persona, Extract Driving Forces

For each persona, analyze documentation for psychological drivers:

Positive Drivers:

If found: Present extracted positive drivers and ask for validation and additions.

If vague: Present general needs and help make them specific to the usage context. Ask: "When {{persona.name}} uses your product, what specific outcomes do they want? Not general life goals, but what they want to accomplish in this usage context."

If not found: Ask what positive outcomes the persona seeks when using the product.

Negative Drivers:

If found: Present extracted fears and frustrations, ask for validation.

If pain points exist but not framed as drivers: Transform pain points into psychological drivers. Ask: "Based on these pain points, what does {{persona.name}} fear? Think about fear of embarrassment, wasting time/money, making wrong decisions, frustration with current solutions, anxiety about outcomes."

If not found: Explain that documentation focuses on what users want but doesn't mention fears. Note negative drivers are often MORE powerful. Ask about fears as the flip side of positive wants.

Define negative drivers through conversation.

Store driving forces for each persona.

3. Present Workshop 3 Summary

Output: "Workshop 3 Complete!

Driving Forces Mapped: {{#each personas}}

• {{this.name}}: {{this.positive_count}} positive drivers, {{this.negative_count}} negative drivers

{{/each}}

Next, we'll prioritize which groups and drivers matter most."

4. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Prioritization 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. Both positive and negative driving forces must be mapped for ALL personas before proceeding.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Both positive AND negative driving forces extracted for every persona
• Drivers are specific to usage context (not general life goals)
• Pain points transformed into psychological negative drivers
• Negative drivers actively probed (not just accepted as "none found")
• User confirmed driving forces for each persona
• Forces have clear link to product usage and design opportunities
• Results stored for subsequent steps

❌ SYSTEM FAILURE:

• Skipping negative drivers for any persona
• Accepting vague or general driving forces
• Not probing for negative drivers when documentation lacks them
• Proceeding without confirmed forces for all personas
• Pain points not transformed into psychological drivers
• Drivers not specific to usage context

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

Step 5: Prioritization Extraction

STEP GOAL:

Extract or establish strategic prioritization of target groups and driving forces from the user's existing documentation, creating clear priority rankings with rationale.

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 - challenging assumptions and seeking clarity from 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 establishing clear priority rankings for groups and drivers
• 🚫 FORBIDDEN to accept prioritization without rationale
• 💬 Approach: Use documentation signals (budget, depth of research, frequency of mention) to suggest priorities
• 📋 Documentation rarely includes explicit prioritization - establish through conversation
• 📋 Create impact x feasibility assessment for each group

EXECUTION PROTOCOLS:

• 🎯 Check documentation for priority signals before asking
• 💾 Store validated prioritized_groups, prioritized_drivers, and focus_statement
• 📖 Help user assess impact and feasibility for each group
• 🚫 Do not proceed until focus statement is confirmed

CONTEXT BOUNDARIES:

• Available context: User's documentation, validated vision/objectives, personas, driving forces
• Focus: Priority ranking of groups and drivers, design focus statement
• Limits: Must have clear rationale for each priority decision
• Dependencies: Requires completed step-00d with confirmed driving forces

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

1. Introduce Prioritization

Output: "Prioritizing Strategic Elements

Your documentation gives us the pieces. Now we need to prioritize:

• Which target groups have highest impact on your objectives?
• Which groups are most feasible to reach?
• Which driving forces are most frequent and intense?"

2. Check for Priority Signals

Analyze documentation for prioritization signals:

• Explicit priority statements
• Resource allocation (budget, team focus)
• Timeline emphasis (what's first)
• Frequency of mention
• Depth of research on certain groups

If signals found: Present them and their implications. If no signals: Note documentation doesn't explicitly prioritize and proceed to collaborative prioritization.

3. Prioritize Target Groups

Present all target groups. For each group, assess:

• Impact on objectives: If this group succeeds with your product, how much does it drive your objectives? (High/Medium/Low)
• Feasibility: How easy is it to reach and serve this group? (High/Medium/Low)

Calculate priority score (Impact x Feasibility). Rank groups.

Present priority ranking with reasoning. Ask if prioritization aligns with strategic thinking.

Store prioritized_groups.

4. Prioritize Driving Forces

Analyze driving forces for frequency, intensity, and alignment with top-priority groups.

Present top driving forces ranked. Ask if these feel like the most critical drivers to address.

Store prioritized_drivers.

5. Create Design Focus Statement

Synthesize into focus statement combining top priority group, top 3-5 drivers, and connection to objectives.

Present focus statement. Ask if it captures where design efforts should focus.

Store focus_statement.

6. Present Workshop 4 Summary

Output: "Workshop 4 Complete!

Strategic Priorities Set:

• Top group: {{top_group.name}}
• Top drivers: {{top_driver_count}} identified
• Focus statement: Defined

Next, we'll run a gap analysis and validate strategic alignment."

7. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Gap Analysis | [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. Priority rankings and focus statement must be confirmed before proceeding to gap analysis.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Target groups prioritized with impact and feasibility assessment
• Driving forces prioritized by frequency, intensity, and alignment
• Each priority decision has documented rationale
• Design focus statement created and confirmed
• Documentation priority signals identified and used where available
• User confirmed all priority rankings
• Results stored for subsequent steps

❌ SYSTEM FAILURE:

• Accepting prioritization without rationale
• Not checking documentation for priority signals first
• Skipping impact/feasibility assessment
• No design focus statement created
• Proceeding without confirmed priorities
• Prioritizing without considering driving forces
• Not challenging assumptions about priority

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

Step 6: Gap Analysis & Validation

STEP GOAL:

Analyze what was strong vs. weak in the documentation, validate strategic alignment between documentation and plans, and prepare a comprehensive summary of what has been built from the existing documentation.

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 - validating strategic alignment and identifying gaps
• ✅ 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 identifying strengths, gaps, and strategic alignment
• 🚫 FORBIDDEN to skip alignment validation or ignore contradictions
• 💬 Approach: Honest assessment of documentation quality with constructive recommendations
• 📋 Identify what was strong vs. weak in documentation
• 📋 Validate strategic alignment between stated vision and actual plans

EXECUTION PROTOCOLS:

• 🎯 Compare original documentation to synthesized Trigger Map
• 💾 Store gap_analysis and alignment_check results
• 📖 Present clear summary of strengths, gaps, and alignment
• 🚫 Do not proceed until user decides how to handle gaps

CONTEXT BOUNDARIES:

• Available context: Original documentation, all synthesized outputs (vision, objectives, personas, forces, priorities)
• Focus: Gap analysis, strategic alignment validation, summary
• Limits: Be honest about gaps - do not gloss over weaknesses
• Dependencies: Requires all previous extraction steps completed

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

1. Analyze Documentation Strengths

Compare original documentation to synthesized Trigger Map. Identify what was clear and strong.

Present documentation strengths.

2. Identify Gaps

Determine what was vague or missing, what was filled through conversation, and any contradictions or misalignments.

Present gaps identified with their impact and how they were filled.

3. Handle Critical Gaps (If Any)

If critical gaps exist, present them and ask: "These gaps could affect your strategy. Would you like to: a. Address now - Fill these gaps through focused conversation b. Note for later - Document as areas for future research c. Accept as-is - Work with what we have"

If address now: Run targeted mini-workshops for critical gaps. If note for later: Document gaps in handover notes.

4. Strategic Alignment Check

Reverse engineer alignment: Does the plan match the vision?

• Compare stated vision to implied vision from plans
• Check if objectives align with vision
• Verify target groups serve objectives
• Validate features address drivers

If alignment good: Confirm strong alignment and explain how objectives, groups, and forces connect to support the vision.

If alignment issues: Present potential misalignments with what documentation says vs. what plan implies. Ask if these should be addressed before finalizing.

Discuss and resolve misalignments if needed.

5. Present Accomplishment Summary

Output what was accomplished:

• Clear Vision (statement)
• Strategic Objectives (count and SMART status)
• Prioritized Target Groups (count with behavioral profiles)
• Driving Forces (count, both positive and negative)
• Strategic Focus (statement)
• Gap Analysis (areas identified for future research)

Explain what they now have (single-slide reference instead of extensive docs) and what they can do with it (reference in design work, share in AI chats, team alignment, feature prioritization, design decisions).

Ask: "Ready to proceed to documentation generation and handover?"

Store gap_analysis and alignment_check.

6. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Overview | [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. Gap analysis and alignment check must be complete and user must confirm readiness to proceed.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Documentation strengths clearly identified
• Gaps identified with impact assessment
• Critical gaps addressed or documented for later
• Strategic alignment validated (vision vs. plan vs. groups vs. forces)
• Misalignments surfaced and discussed
• Comprehensive summary presented
• User confirmed readiness to proceed
• gap_analysis and alignment_check stored

❌ SYSTEM FAILURE:

• Skipping gap analysis
• Not checking strategic alignment
• Glossing over contradictions in documentation
• Not giving user choice on how to handle gaps
• Missing critical gaps that could affect strategy
• Not presenting accomplishment summary
• Proceeding without user confirmation

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

Step 7: Trigger Mapping Overview

STEP GOAL:

Present Phase 2: Trigger Mapping overview, offer engagement mode selection (Workshop, Suggest, Dream), and route to the appropriate workshop path based on user choice.

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 - facilitator of strategic clarity
• ✅ 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 presenting mode options and routing to correct path
• 🚫 FORBIDDEN to skip mode selection or auto-choose for user
• 💬 Approach: Clear presentation of three modes with time estimates
• 📋 Workshop mode proceeds through step-by-step facilitation
• 📋 Suggest and Dream modes use the dream-up-approach with design log tracking

EXECUTION PROTOCOLS:

• 🎯 Present overview and mode options clearly
• 💾 Store selected mode for subsequent steps
• 📖 Route to correct path based on selection
• 🚫 Do not proceed without explicit mode selection

CONTEXT BOUNDARIES:

• Available context: Configuration loaded, Product Brief available
• Focus: Mode selection and routing
• Limits: Must get explicit user choice before proceeding
• Dependencies: Requires Phase 1 Product Brief completed

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

1. Present Phase 2 Overview

Output: "Phase 2: Trigger Mapping

Connect business goals to user psychology. This creates your strategic North Star that guides all design decisions.

We'll create: Business Goals -> Target Groups -> Driving Forces -> Prioritization"

2. Offer Engagement Mode

Ask: "How do you want to create it?

[W] Workshop - I facilitate, you provide insights (45-60 min) [S] Suggest - I suggest, you review after each step (20-35 min) [D] Dream - I create all steps autonomously, you review final result (15-25 min)"

Wait for user selection.

3. Route Based on Selection

If Workshop (W): Ask: "Run all 4 workshops now, or one at a time? [A] All now (45-60 min) [O] One at a time"

If All: Proceed through all workshops sequentially. If One at a time: Run Workshop 1, then offer to save and continue later.

If Suggest (S) or Dream (D): Output: "{{mode}} selected. I'll generate the Trigger Map using WDS methodology + Product Brief + domain research."

Inform user: "I'm creating a design log to track my learning, research, generation, and self-review process."

Create session log at {output_folder}/_progress/agent-experiences/{date}-trigger-map-{{mode}}.md

Execute Layer 1: Learn WDS Form (Static - loaded once)

• Read docs/method/phase-wds-2-trigger-mapping-guide.md
• Read docs/quick-start/0wds-2-trigger-mapping.md
• Read src/data/agent-guides/saga/trigger-mapping.md
• Read docs/models/impact-effect-mapping.md
• Read docs/method/dream-up-rubric-phase-2.md
• Internalize: Structure, quality criteria, common mistakes, best practices
• Document in design log "Layer 1: WDS Form Learned" section

Execute Layer 2: Project Context (Initial load, grows with each step)

• Read {output_folder}/A-Product-Brief/product-brief.md
• Read {output_folder}/A-Product-Brief/content-language.md
• Read {output_folder}/A-Product-Brief/platform-requirements.md
• Read {output_folder}/A-Product-Brief/visual-direction.md
• Extract: business context, user archetypes, constraints, strategic direction
• Document in design log "Layer 2: Project Context (Initial)" section
• NOTE: Layer 2 grows cumulatively - add Business Goals, Target Groups, Driving Forces, Prioritization as created

For EACH step (Business Goals, Target Groups, Driving Forces, Prioritization):

Execute Layer 3: Domain Research (per step)

• WebSearch relevant to current step
• Look for industry insights, user reviews, behavioral patterns
• Document findings in design log

Execute Layer 4: Generate

• Apply WDS Form (Layer 1) with ALL Project Context (Layer 2 cumulative)
• Enhanced by Domain Research (Layer 3)
• Create this step's artifact

Execute Layer 5: Self-Review

• Check against rubric (completeness, quality, mistakes, practices)
• Calculate quality score, identify gaps
• Document in design log

If gaps exist: Create refinement plan, regenerate (max 5 iterations per step)

If mode == S (Suggest): Show user what was created, learning/research applied, self-review results. Wait for approval/feedback. If mode == D (Dream): Show progress update, continue autonomously.

When step threshold met: Add to Layer 2, proceed to next step. If 5 iterations without threshold: Offer to switch to Workshop Mode for this step.

When all steps complete:

• Assemble complete trigger-map.md at {output_folder}/B-Trigger-Map/trigger-map.md
• Create persona documents if needed
• Create mermaid diagram if generated
• Present final output to user
• Update design log with final output section

Skip to handover after generation complete.

4. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Business Goals Workshop | [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. Mode must be selected and routed appropriately before continuing.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Overview presented clearly with value proposition
• All three engagement modes offered with time estimates
• User explicitly selected a mode
• Correct path activated based on selection
• Workshop sub-choice (All/One) offered if Workshop mode selected
• Suggest/Dream modes properly initialize design log and layered approach
• User confirmed and ready to proceed

❌ SYSTEM FAILURE:

• Auto-selecting a mode without user input
• Not presenting all three mode options
• Not explaining what each mode involves
• Proceeding without explicit user selection
• Not initializing design log for Suggest/Dream modes
• Skipping the layered approach for autonomous modes

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

Step 8: Workshop 1 - Business Goals

STEP GOAL:

Facilitate Workshop 1 to define the user's business vision and transform it into SMART strategic objectives that will guide all design decisions.

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
• ✅ 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 capturing vision and creating SMART objectives
• 🚫 FORBIDDEN to define vision or objectives without user input
• 💬 Approach: Start with the dream, then make it measurable
• 📋 Aim for 3-5 clear objectives
• 📋 Help transform vague metrics into SMART format

EXECUTION PROTOCOLS:

• 🎯 Facilitate vision capture through aspirational questions
• 💾 Store vision_statement and objectives
• 📖 Help refine each objective to SMART format
• 🚫 Do not proceed until objectives are confirmed

CONTEXT BOUNDARIES:

• Available context: Product Brief, configuration
• Focus: Vision statement and SMART objectives
• Limits: User must provide the vision - do not invent it
• Dependencies: Requires Phase 1 Product Brief

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

1. Introduce Workshop

Output: "Workshop 1: Business Goals

We'll define what success looks like at two levels:

• Vision - The inspiring, aspirational goal (not easily quantified)
• Objectives - SMART metrics that indicate progress

Let's start with the dream, then make it measurable."

2. Capture the Vision

Ask: "Where do you want to be?

Think big. If everything goes perfectly, what position do you want to hold?

Examples:

• 'Be the most trusted platform for dog owners in Sweden'
• 'The go-to tool for indie designers'
• 'Make project management actually enjoyable'"

Listen for aspirational, motivating language. Help refine into a clear, inspiring vision statement.

Output: "Your Vision: {{vision_statement}}"

Store vision_statement.

3. Break Down into Objectives

Output: "Now let's make this measurable. What would indicate you're achieving that vision?"

Ask: "How would you measure progress toward this vision?

Think about:

• User metrics (adoption, engagement, retention)
• Business metrics (revenue, growth, market share)
• Quality metrics (satisfaction, referrals, reviews)

What numbers would make you confident you're on track?"

For each metric mentioned, help make it SMART:

• Specific - What exactly?
• Measurable - What number?
• Achievable - Is this realistic?
• Relevant - Does this connect to the vision?
• Time-bound - By when?

Aim for 3-5 clear objectives.

4. Refine Objectives

Output: "Let me help sharpen these into SMART objectives."

Walk through each objective with example transformation:

• Vague: "Get influential users"
• SMART: "Onboard 10 verified dog trainers with 1000+ followers by Q4 2026"

Present each refined objective for confirmation.

Ask for any adjustments.

Store objectives.

5. Present Workshop Summary

Output: "Workshop 1 Complete!

Vision: {{vision_statement}}

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

This gives us clear targets to work toward. Next, we'll identify who can help you achieve these goals."

Store vision_statement and objectives for next workshop.

6. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Target Groups Workshop | [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.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Vision statement captured from user input (not generated)
• 3-5 SMART objectives defined and confirmed
• Each objective is Specific, Measurable, Achievable, Relevant, Time-bound
• Vague metrics transformed into measurable goals
• User confirmed both vision and objectives
• Results stored for subsequent workshops

❌ SYSTEM FAILURE:

• Generating vision without user input
• Accepting vague, unmeasurable objectives
• Having fewer than 3 or more than 5 objectives without discussion
• Not applying SMART framework to each objective
• Proceeding without user confirmation
• Not storing results for next workshop

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

Step 9: Workshop 2 - Target Groups

STEP GOAL:

Facilitate Workshop 2 to identify the most critical user groups, narrow to 2-4 focus groups, and build rich narrative personas with psychological depth for each.

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 - building empathy through understanding
• ✅ 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 identifying user groups and building narrative personas
• 🚫 FORBIDDEN to create personas without user input or skip persona depth
• 💬 Approach: Help user think about WHO will drive their objectives through product usage
• 📋 Narrow to 2-4 primary target groups
• 📋 Build narrative personas, not just bullet points - give them names, make them feel real

EXECUTION PROTOCOLS:

• 🎯 Link target groups back to objectives
• 💾 Store target_groups and personas
• 📖 Help distinguish similar groups and build psychological depth
• 🚫 Do not proceed until personas feel real and complete

CONTEXT BOUNDARIES:

• Available context: Vision, objectives from Workshop 1
• Focus: User group identification and persona creation
• Limits: Maximum 2-4 groups - help prioritize if more identified
• Dependencies: Requires completed Workshop 1 with confirmed objectives

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

1. Introduce Workshop

Output: "Workshop 2: Target Groups

Now we identify the people who matter most to achieving your goals.

We'll create:

• A list of user groups
• Rich descriptions (personas)
• Understanding of their context"

2. Identify User Groups

Present objectives as context.

Ask: "Who needs to use your product for you to achieve these goals?

For your business to succeed, the product needs to be used in the intended way by real people. Think about:

• Who out there in the world, by using your product, will make these business goals happen?
• Primary users - Who uses it directly and regularly?
• Influencers - Who affects whether others adopt it?
• Decision makers - Who chooses to buy/use it?

List the types of people that come to mind."

Capture each group mentioned. Ask clarifying questions to distinguish similar groups.

Store target_groups_raw.

3. Select Focus Groups

Present all mentioned groups.

Ask: "Which 2-4 groups are most critical to your success?

Consider:

• Who has the most influence on your objectives?
• Who, if delighted, would drive the others?
• Where is the biggest opportunity?"

Help narrow to 2-4 primary target groups.

Store target_groups.

4. Build Personas

Output: "Let's bring each group to life. We'll create a persona for each."

For each target group, ask: "Let's explore: {{current_group}}

1. Who are they? (role, demographics, situation) 2. What's their day like? (context, responsibilities) 3. What are they trying to achieve? (goals) 4. What frustrates them? (pain points) 5. How do they solve this problem today? (current behavior)"

Build a narrative persona, not just bullet points. Give them a name and make them feel real.

Present each persona and ask: "Does this feel like a real person you'd design for? Any adjustments?"

Repeat for each target group.

Store personas.

5. Present Workshop Summary

Output: "Workshop 2 Complete!

Your Target Groups: {{#each personas}}

• {{this.name}} - {{this.summary}}

{{/each}}

These are the people we're designing for. Next, we'll explore what drives them - both toward and away from solutions."

Store target_groups and personas for next workshop.

6. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Driving Forces Workshop | [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. Personas must feel real and complete before proceeding.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• User groups identified from user input
• Narrowed to 2-4 focus groups with reasoning
• Narrative personas created for each group (not just bullet points)
• Personas have names and feel like real people
• Psychological depth: context, goals, frustrations, current behavior
• User confirmed each persona feels real
• Results stored for subsequent workshops

❌ SYSTEM FAILURE:

• Creating personas without user input
• Having more than 4 groups without narrowing
• Bullet-point personas without narrative depth
• Missing context, goals, or frustrations
• Personas that feel generic or template-like
• Proceeding without user confirmation on personas

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

Step 10: Workshop 3 - Driving Forces

STEP GOAL:

Facilitate Workshop 3 to identify both positive and negative driving forces for each persona, uncover cross-group patterns, and build the psychological foundation for design decisions.

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 - uncovering motivation psychology
• ✅ 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 identifying BOTH positive and negative driving forces per persona
• 🚫 FORBIDDEN to skip negative drivers - they reveal strongest design opportunities
• 💬 Approach: Explore both sides of motivation systematically per persona
• 📋 Capture 3-5 drivers per category (positive and negative) per persona
• 📋 Identify cross-group patterns after all personas mapped

EXECUTION PROTOCOLS:

• 🎯 Facilitate exploration of both toward and away-from motivation
• 💾 Store driving_forces and driver_patterns
• 📖 Emphasize loss aversion principle - negative drivers often more powerful
• 🚫 Do not proceed until both types mapped for all personas

CONTEXT BOUNDARIES:

• Available context: Vision, objectives, personas from previous workshops
• Focus: Positive and negative driving forces per persona
• Limits: Must have both positive AND negative forces for each persona
• Dependencies: Requires completed Workshop 2 with confirmed personas

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

1. Introduce Workshop

Output: "Workshop 3: Driving Forces

Now we dig into psychology. For each target group, we'll identify:

• Positive Drivers - What they want to achieve, gain, or experience
• Negative Drivers - What they want to avoid, escape, or prevent

Understanding both is crucial. Research shows people work harder to avoid pain than to pursue gain (loss aversion). Negative drivers often reveal the strongest design opportunities."

2. Explain the Framework

Output: "For each persona, we'll explore:

Positive Drivers (toward motivation):

• Aspirations and dreams
• Desired outcomes
• Experiences they seek
• Status or recognition goals

Negative Drivers (away-from motivation):

• Fears and anxieties
• Problems they want gone
• Frustrations they're tired of
• Risks they want to avoid

The magic happens when your design addresses both."

3. Explore Driving Forces Per Group

For each persona:

Output: "Let's explore what drives {{persona.name}}"

Ask about positive drivers: "Positive Drivers: What does {{persona.name}} want to achieve or experience?

Think about:

• What would make their day better?
• What would they brag about to colleagues?
• What would make them feel successful?"

Capture 3-5 positive drivers.

Ask about negative drivers: "Negative Drivers: What does {{persona.name}} want to avoid or escape?

Think about:

• What keeps them up at night?
• What frustrations are they tired of?
• What risks worry them?
• What embarrassments do they want to avoid?"

Capture 3-5 negative drivers.

Present summary for each persona and ask for confirmation.

Repeat for each persona.

Store driving_forces.

4. Identify Patterns

Output: "Looking across all personas, I notice some patterns..."

Analyze for:

• Common drivers across groups
• Unique drivers per group
• Potential conflicts between groups

Present cross-group patterns (shared drivers, unique drivers, potential tensions).

Store driver_patterns.

5. Present Workshop Summary

Output: "Workshop 3 Complete!

We've mapped the psychological landscape:

{{#each personas}} {{this.name}}:

• Wants: {{this.top_positive_driver}}
• Avoids: {{this.top_negative_driver}}

{{/each}}

This is powerful insight. Next, we'll prioritize which groups and drivers to focus on."

Store driving_forces and patterns for next workshop.

6. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Prioritization Workshop | [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. Both positive and negative forces must be mapped for all personas before proceeding.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• 3-5 positive drivers identified per persona from user input
• 3-5 negative drivers identified per persona from user input
• Loss aversion principle explained
• Cross-group patterns identified (shared, unique, tensions)
• User confirmed driving forces for each persona
• Results stored for subsequent workshops

❌ SYSTEM FAILURE:

• Skipping negative drivers for any persona
• Having fewer than 3 drivers per category
• Generating driving forces without user input
• Not identifying cross-group patterns
• Proceeding without confirmed forces for all personas
• Not emphasizing importance of negative drivers

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

Step 11: Workshop 4 - Prioritization

STEP GOAL:

Facilitate Workshop 4 to prioritize business goals, objectives, target groups, and driving forces through challenged reasoning, creating a clear design focus statement.

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 - challenging assumptions, seeking clarity
• ✅ 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 making hard choices with clear reasoning
• 🚫 FORBIDDEN to accept prioritization without challenging the reasoning
• 💬 Approach: For each choice, ask "Why is X more important than Y?"
• 📋 Push for clear reasoning to prevent "gut feel" prioritization
• 📋 Create MoSCoW-style focus statement (Must/Should/Could address)

EXECUTION PROTOCOLS:

• 🎯 Challenge every priority decision with "why" questions
• 💾 Store prioritized_visions, prioritized_objectives, prioritized_groups, prioritized_drivers, focus_statement
• 📖 Capture reasoning alongside rankings
• 🚫 Do not accept rankings without documented rationale

CONTEXT BOUNDARIES:

• Available context: Vision, objectives, personas, driving forces from previous workshops
• Focus: Priority ranking with reasoning for all elements
• Limits: Every ranking must have documented reasoning
• Dependencies: Requires completed Workshop 3 with confirmed driving forces

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

1. Introduce Workshop

Output: "Workshop 4: Prioritization

Now we make the hard choices. We'll prioritize: 1. Business goals (visions) 2. Objectives under each goal 3. Target groups 4. Driving forces

For each decision, I'll challenge you to explain why - because clear reasoning leads to better decisions."

2. Prioritize Business Goals

If multiple visions exist, present them and ask which is most critical right now. Challenge the choice: "Why is {{chosen_vision}} more important than {{other_vision}}?"

Capture reasoning. Build ranked list. Store prioritized_visions.

3. Prioritize Objectives

Present objectives under top goal. Ask which is most important to achieve first - which one would have the biggest impact or unlock the others.

Challenge the choice with "why" questions. Continue ranking with reasoning.

Store prioritized_objectives.

4. Prioritize Target Groups

Present target groups with reference to top objective.

Ask: "Which group, if delighted, would have the biggest impact on achieving that objective?"

Challenge: "Why is {{chosen_group}} more important than {{other_group}} for this objective?"

Push for clear reasoning. Build ranked list.

Ask: "The top group gets most design attention. Does this ranking reflect your strategy?"

Store prioritized_groups.

5. Prioritize Drivers Per Group

For top 2-3 groups, present their positive and negative drivers.

Ask: "Rank the top 3-5 drivers this group cares most about. Remember: negative drivers often have more weight (loss aversion)."

Help rank drivers with reasoning.

Store prioritized_drivers.

6. Create Focus Statement

Synthesize into focus statement:

Output: "Your Design Focus:

Primary Group: {{top_group.name}} Secondary: {{second_group.name}}

Must Address: {{must_address_drivers}}

Should Address: {{should_address_drivers}}

Could Address (if time permits): {{could_address_drivers}}"

Ask: "Does this focus feel right? This guides all feature decisions."

Store focus_statement.

7. Present Workshop Summary

Output: "Workshop 4 Complete!

Your Strategic Focus:

• Design primarily for {{top_group.name}}
• Address: {{top_drivers_summary}}

This focus means saying 'not yet' to some things. That's the power of prioritization.

Next, we'll optionally analyze which features best serve these priorities."

Store all prioritized outputs.

8. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Feature Impact Workshop | [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. All priorities and focus statement must be confirmed before proceeding.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Business goals prioritized with reasoning
• Objectives ranked with reasoning
• Target groups prioritized with challenged reasoning
• Driving forces ranked per group with reasoning
• Focus statement created (Must/Should/Could)
• Every priority decision has documented "why"
• User confirmed all rankings and focus statement

❌ SYSTEM FAILURE:

• Accepting priorities without "why" reasoning
• Not challenging priority decisions
• Allowing "gut feel" prioritization without reasoning
• Missing focus statement
• Not capturing reasoning alongside rankings
• Proceeding without confirmed priorities

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

Step 12: Extract Features

STEP GOAL:

Silently read the project brief and extract all strategically relevant features, presenting them for user review and confirmation before impact assessment.

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 - extracting features systematically
• ✅ 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 strategically relevant features from documentation
• 🚫 FORBIDDEN to include basic authentication, standard profiles, or basic CRUD unless unique/strategic
• 💬 Approach: Present extracted list, let user edit before proceeding
• 📋 Extract core features, user interactions, content elements, key differentiators
• 📋 Skip infrastructure features unless strategically relevant

EXECUTION PROTOCOLS:

• 🎯 Read project brief silently and extract features
• 💾 Store confirmed feature list
• 📖 Present as numbered list for easy review
• 🚫 Do not proceed to assessment until user confirms list

CONTEXT BOUNDARIES:

• Available context: Project brief, all workshop outputs
• Focus: Feature extraction from documentation
• Limits: Only strategically relevant features - skip basic/standard ones
• Dependencies: Requires completed prioritization workshop

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

1. Read and Extract Features

Silently read the project brief and extract all features mentioned in the documentation.

What to Extract:

• Core product features
• User interactions and workflows
• Content/communication elements
• Key differentiators
• Infrastructure features (if mentioned and strategic)

What to SKIP:

• Basic authentication (login/logout)
• Standard user profiles
• Basic CRUD operations (unless unique/strategic)

2. Present Extracted Features

Output: "I've extracted the following features from your project documentation:

1. [Feature Name] - [Brief description] 2. [Feature Name] - [Brief description] 3. [Feature Name] - [Brief description] ... (continue for all features)

Please review this list:

• Are there features you'd like to add?
• Would you like to rename or clarify any features?
• Should any features be combined or split?

Feel free to edit this list. Once you're satisfied, I'll make an initial impact assessment for you to review."

3. Wait for User Confirmation

Wait for user to confirm or make changes to the feature list. If changes requested, update and re-present. Store confirmed feature list.

4. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Impact Assessment Confirmation | [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. Feature list must be confirmed before proceeding to assessment.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• All strategically relevant features extracted from documentation
• Basic/standard features appropriately excluded
• Features presented as clear numbered list with descriptions
• User given opportunity to add, rename, combine, or split features
• User confirmed final feature list
• Confirmed list stored for assessment step

❌ SYSTEM FAILURE:

• Including basic auth, standard profiles, or basic CRUD
• Not presenting features for user review
• Proceeding to assessment without user confirmation
• Missing strategically important features
• Not allowing user to edit the list

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

Step 13: Confirm Assessment Approach

STEP GOAL:

Confirm the user is ready for the initial impact assessment by explaining the scoring methodology and getting explicit approval to proceed.

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 - setting expectations clearly
• ✅ 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 explaining the assessment methodology clearly
• 🚫 FORBIDDEN to start assessment without user confirmation
• 💬 Approach: Set clear expectations about scoring and review process
• 📋 Explain that user will have opportunity to adjust scores after initial assessment

EXECUTION PROTOCOLS:

• 🎯 Present scoring methodology transparently
• 💾 Confirm user ready to proceed
• 📖 Explain review opportunity after assessment
• 🚫 Do not proceed until user explicitly confirms

CONTEXT BOUNDARIES:

• Available context: Confirmed feature list, personas with priorities
• Focus: Assessment methodology explanation and user confirmation
• Limits: Do not start assessing - only explain and confirm
• Dependencies: Requires confirmed feature list from step-06a

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

1. Explain Assessment Approach

Output: "Perfect! I now have your confirmed feature list.

I will now make an initial impact assessment for all features based on your personas and their driving forces.

Assessment approach:

For each feature, I'll evaluate:

• Impact on {{primary_persona.name}} (Primary) - High/Medium/Low
• Impact on {{secondary_persona.name}} (Secondary) - High/Medium/Low
• Impact on {{tertiary_persona.name}} (Tertiary) - High/Medium/Low (if applicable)

Scoring:

• Primary Persona: High = 5 pts | Medium = 3 pts | Low = 1 pt
• Other Personas: High = 3 pts | Medium = 1 pt | Low = 0 pts

I'll base my assessment on the driving forces (wants and fears) we identified for each persona.

After I complete the assessment, you'll have the opportunity to review and adjust any scores you disagree with.

Ready for me to proceed with the assessment?"

2. Wait for User Confirmation

Wait for user to confirm readiness.

3. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Run Assessment | [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. User must explicitly confirm readiness for assessment.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Assessment methodology explained clearly
• Scoring system presented (Primary weighted higher)
• User informed about review opportunity after assessment
• User explicitly confirmed readiness to proceed

❌ SYSTEM FAILURE:

• Starting assessment without explanation
• Not explaining scoring methodology
• Proceeding without user confirmation
• Not mentioning review opportunity

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

Step 14: Make Initial Assessment

STEP GOAL:

For each feature in the confirmed list, assess impact on each persona based on their driving forces, present ranked results in a table, and iterate based on user feedback.

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 - analyzing feature impact strategically
• ✅ 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 assessing each feature against each persona's driving forces
• 🚫 FORBIDDEN to finalize without user review and confirmation
• 💬 Approach: Present initial assessment, invite user to adjust any scores
• 📋 Use consistent scoring: Primary High=5, Med=3, Low=1; Others High=3, Med=1, Low=0
• 📋 Highlight top scoring features with strategic rationale

EXECUTION PROTOCOLS:

• 🎯 Assess each feature against each persona's wants and fears
• 💾 Store confirmed assessment with scores
• 📖 Present as ranked table with clear scoring
• 🚫 Do not proceed until user confirms assessment

CONTEXT BOUNDARIES:

• Available context: Confirmed feature list, personas with driving forces
• Focus: Feature-persona impact assessment
• Limits: Assessment based on documented driving forces, not assumptions
• Dependencies: Requires confirmed feature list and user confirmation from step-06b

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

1. Run Assessment

For each feature in the confirmed list:

Assessment Criteria:

HIGH Impact:

• Directly addresses a major WANT (positive driver)
• Directly mitigates a major FEAR (negative driver)
• Core to persona's transformation or success

MEDIUM Impact:

• Helpful but not critical
• Supports wants/fears indirectly
• Nice-to-have improvement

LOW Impact:

• Minimal relevance to this persona
• Doesn't address their specific drivers
• Background/infrastructure feature

Scoring Logic: 1. Consider Primary Persona's wants and fears 2. Consider Secondary Persona's wants and fears 3. Consider Tertiary Persona's wants and fears (if exists) 4. Assign High/Medium/Low for each 5. Calculate total score: Primary: High=5, Med=3, Low=1; Others: High=3, Med=1, Low=0

2. Present Results

Output: "Initial Assessment Complete!

Here's my assessment of all features based on your personas' driving forces:

... (continue for all features, ranked by score)

Top Scoring Features (Score 8+): [Brief list with strategic rationale]

Please review this assessment:

• Do you agree with the impact ratings?
• Should any features be scored differently?
• Do the top priorities align with your strategic thinking?

Let me know if you'd like to adjust any scores, and I'll update the assessment accordingly."

3. Iterate on Feedback

If user requests changes:

• Make the adjustments
• Recalculate scores
• Show updated table
• Ask for confirmation again

Repeat until user confirms assessment.

4. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Generate Document | [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. Assessment must be confirmed by user before generating document.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• All features assessed against all personas
• Consistent scoring methodology applied
• Results presented as ranked table
• Top features highlighted with strategic rationale
• User given opportunity to review and adjust
• Adjustments made and re-presented when requested
• User confirmed final assessment

❌ SYSTEM FAILURE:

• Not assessing all features against all personas
• Inconsistent scoring methodology
• Not presenting results for user review
• Finalizing without user confirmation
• Not iterating when user requests changes
• Missing strategic rationale for top features

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

Step 15: Generate Feature Impact Document

STEP GOAL:

Generate the complete Feature Impact Analysis document with the confirmed assessment, including prioritization tiers, detailed rationale, strategic implications, and questions for the designer.

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 - documenting strategic priorities
• ✅ 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 generating complete, well-structured document
• 🚫 FORBIDDEN to save without user review of summary
• 💬 Approach: Generate document, present summary, iterate if needed
• 📋 Use template from ../templates/feature-impact.template.md
• 📋 Include Must Have/Consider/Defer prioritization tiers

EXECUTION PROTOCOLS:

• 🎯 Generate document following template structure
• 💾 Save to {output_folder}/B-Trigger-Map/feature-impact-analysis.md
• 📖 Present summary to user for review
• 🚫 Do not proceed until user confirms document

CONTEXT BOUNDARIES:

• Available context: Confirmed assessment scores, personas, driving forces
• Focus: Document generation with proper structure and rationale
• Limits: Use confirmed scores only - do not change assessment
• Dependencies: Requires confirmed assessment from step-06c

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

1. Generate Document

Use the template: ../templates/feature-impact.template.md

Include: 1. Header with project name, date, and scoring legend 2. Prioritized Features Table with all scores 3. Feature Details & Rationale for each feature (especially top scorers) 4. Strategic Implications section 5. Questions for Designer section

Prioritization Logic:

Must Have MVP:

• Any feature where Primary Persona scored HIGH (5 pts)
• OR features with score >= (max_possible - 3)

Consider for MVP:

• Mid-range scores
• Strategic value but not critical

Defer:

• Low scores
• Minimal strategic value

2. Save Document

Save as: {output_folder}/B-Trigger-Map/feature-impact-analysis.md

3. Present Summary

Output: "Feature Impact Analysis Document Generated!

Saved to: B-Trigger-Map/feature-impact-analysis.md

Summary:

Must Have MVP Features ({{must_have_count}}): {{#each must_have}}

• {{this.name}} (Score: {{this.score}})

{{/each}}

Consider for MVP ({{consider_count}}): {{#each consider}}

• {{this.name}} (Score: {{this.score}})

{{/each}}

Key Insights:

• [Strategic insight 1]
• [Strategic insight 2]
• [Strategic insight 3]

This Feature Impact Analysis serves as your Design Brief - it guides:

• Phase 4: UX Design - Which scenarios to design first
• Phase 6: PRD/Development - Epic and story prioritization

The document includes detailed rationale for each feature's scoring.

Would you like to make any final adjustments, or are we good to proceed?"

4. Handle Feedback

If user requests changes: Update document, regenerate, show summary again.

5. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Workshop Wrap-Up | [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. Document must be generated and user must confirm before proceeding.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Document generated following template structure
• All sections included (header, table, rationale, implications, questions)
• Prioritization tiers applied correctly (Must Have/Consider/Defer)
• Document saved to correct location
• Summary presented to user
• User confirmed or adjustments made and re-confirmed

❌ SYSTEM FAILURE:

• Document missing required sections
• Incorrect prioritization tier assignment
• Not saving to correct location
• Not presenting summary for user review
• Proceeding without user confirmation

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

Step 16: Feature Workshop Wrap-Up

STEP GOAL:

Provide a completion summary of the Feature Impact Workshop, listing all deliverables created during trigger mapping, and guide toward next steps.

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 - celebrating completion and guiding next steps
• ✅ 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 summarizing what was accomplished and guiding next steps
• 🚫 FORBIDDEN to skip the summary or rush to next phase
• 💬 Approach: Celebrate the work done, explain the value created
• 📋 List all deliverables comprehensively
• 📋 Explain how Feature Impact guides Phase 4 UX Design

EXECUTION PROTOCOLS:

• 🎯 Present comprehensive summary of all deliverables
• 💾 No new artifacts to create - summary only
• 📖 Explain how the Feature Impact Analysis guides future work
• 🚫 Do not skip celebration of accomplishment

CONTEXT BOUNDARIES:

• Available context: All workshop outputs, Feature Impact document
• Focus: Summary, celebration, next steps guidance
• Limits: No new analysis needed - just summarize and guide
• Dependencies: Requires completed Feature Impact document

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

1. Present Completion Summary

Output: "Feature Impact Workshop Complete!

What You Now Have:

1. Confirmed Feature List - All product features identified and named 2. Impact Assessment - Each feature scored against all personas 3. Strategic Priorities - Must Have vs. Consider vs. Defer decisions 4. Design Brief - Clear guidance for UX design prioritization

Your Complete Trigger Mapping Deliverables:

• Business Goals (with prioritization)
• Target Personas (detailed profiles)
• Driving Forces (wants + fears)
• Key Insights (strategic implications)
• Feature Impact Analysis (NEW!)

All documents accessible from: 00-trigger-map.md (your navigation hub)

---

Ready for Phase 4: UX Design!

The Feature Impact Analysis will guide your design decisions:

• What to design first: Top-scoring features
• Where to focus detail: Features with HIGH primary impact
• Who to optimize for: Impact scores show which personas matter most per feature

Next Steps:

If you're ready to continue, you can: 1. Start Phase 4: UX Design (Scenario Design) 2. Review the Trigger Map one more time 3. Share the Feature Impact with your team for alignment

Would you like to proceed to document generation, or is there anything else you'd like to adjust?"

2. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Document Generation | [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. User must confirm readiness to proceed to document generation.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Complete summary of all deliverables presented
• Feature Impact Workshop acknowledged as complete
• Explanation of how deliverables guide future phases
• Next steps clearly presented
• User confirmed readiness to proceed

❌ SYSTEM FAILURE:

• Skipping summary
• Not listing all deliverables
• Not explaining value of Feature Impact for future work
• Rushing to next phase without acknowledgment
• Proceeding without user confirmation

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

Step 17: Generate Hub Document

STEP GOAL:

Create the main entry point document (00-trigger-map.md) with Mermaid diagram, on-page summaries, navigation menu, and strategic overview including the key transformation and flywheel.

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 - creating comprehensive trigger map 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 creating the hub document with all required sections
• 🚫 FORBIDDEN to skip Mermaid diagram or on-page summaries
• 💬 Approach: Generate structured document following template
• 📋 Include: Header, Mermaid diagram, Summary, Detailed Documentation menu, How to Read, Footer
• 📋 Target ~220-250 lines total

EXECUTION PROTOCOLS:

• 🎯 Generate Mermaid diagram by loading step-08a-mermaid-init-structure.md sequence
• 💾 Save as 00-trigger-map.md in trigger map folder
• 📖 Include on-page summaries for each section (visible without clicking)
• 🚫 Do not skip any required section

CONTEXT BOUNDARIES:

• Available context: All workshop outputs, personas, driving forces, priorities
• Focus: Hub document creation with diagram and navigation
• Limits: Follow template structure exactly
• Dependencies: Requires all workshop outputs available

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

0. Data Extraction (MANDATORY BEFORE GENERATION)

Before generating ANY content, extract structured data from all workshop outputs:

Read and extract from workshop data:

1. From Business Goals workshop:

• vision_statement = exact vision text (character-for-character)
• objectives[] = each SMART objective with metric, target, timeline

2. From Target Groups workshop:

• target_groups[] = each group with name, priority, persona summary
• positive_drivers[] per group (specific wants)
• negative_drivers[] per group (specific fears)

3. From Prioritization workshop:

• focus_statement = strategic focus
• top_group = primary design target
• must_address_drivers[] and should_address_drivers[]

Store these as variables. When filling the hub document, use EXACT values from these variables. Do NOT paraphrase or summarize workshop outputs.

Validation rule: Vision statement in the hub MUST be character-for-character identical to the vision from Business Goals workshop. If you cannot find the exact text, ask the user rather than inventing a paraphrase.

---

1. Generate Header Section

Create header with project name, date, author, and methodology credit.

2. Generate Mermaid Diagram

Load and execute the mermaid generation sequence starting with step-08a-mermaid-init-structure.md.

Requirements:

• Light gray professional styling (consistent for all business goals)
• All nodes have proper padding (<br/>)
• Emojis: checkmark for wants, X for fears
• Exactly 3 drivers per persona
• Proper connections: BG->PLATFORM->TG->DF

3. Generate Summary Section

Include:

• Primary Target with one-line transformation
• The Flywheel (numbered steps with priority emojis)
• Key Transformation statement

4. Generate Detailed Documentation Menu

For each section, provide:

• Link to document with description
• On-page content (key information visible without clicking)
• Proper formatting with bold, bullets, clear structure

Include sections for:

• Business Strategy (01-Business-Goals.md)
• Target Users (persona documents)
• Strategic Implications (05-Key-Insights.md)

5. Generate How to Read Section

Explain diagram reading: left-to-right flow, top-to-bottom priority, driving force symbols.

6. Generate Footer

Include WDS framework credit and Effect Mapping methodology credits.

6b. Cross-Validation Check

Before saving, verify data consistency:

• [ ] Vision in hub matches vision from Business Goals workshop exactly
• [ ] Persona names in hub match names used in individual persona documents
• [ ] Driver count in Mermaid diagram matches drivers in per-persona workshop outputs
• [ ] Priority ordering in hub matches prioritization workshop output

If any mismatch found: correct the hub document to match the source workshop data.

7. Save and Confirm

Store as: 00-trigger-map.md in trigger map folder.

Output: "Hub document created with diagram and navigation!"

8. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Business Goals Document | [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. Hub document must be generated before proceeding. Do NOT skip ahead.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Hub document created with all required sections
• Mermaid diagram generated with proper styling
• On-page summaries included for all sections
• Navigation links to all sub-documents
• Summary with transformation and flywheel
• How to Read section explaining diagram
• Footer with methodology credits
• Document saved to correct location
• ~220-250 lines total

❌ SYSTEM FAILURE:

• Missing Mermaid diagram
• Missing on-page summaries (requiring clicks to see content)
• Missing navigation links
• Missing transformation or flywheel in summary
• Not following template structure
• Document not saved

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

Step 18: Generate Business Goals Document

STEP GOAL:

Create the comprehensive 01-Business-Goals.md document with vision statement, SMART objectives across priority tiers, the flywheel explanation, and success metrics alignment.

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 - documenting 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 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 creating comprehensive business goals document
• 🚫 FORBIDDEN to use "convert users" language - use "create awesome" language
• 💬 Approach: Empowering, organic growth language throughout
• 📋 Use template from {businessGoalsTemplate}
• 📋 PRIMARY GOAL clearly marked as THE ENGINE; target ~150-160 lines

EXECUTION PROTOCOLS:

• 🎯 Generate document following template structure
• 💾 Save as 01-Business-Goals.md in trigger map folder
• 📖 Reference template for complete structure
• 🚫 Do not use "converting" language

CONTEXT BOUNDARIES:

• Available context: Vision, objectives, priorities from workshops
• Focus: Business goals document with flywheel
• Limits: Use empowering language, mark PRIMARY clearly as THE ENGINE
• Dependencies: Requires completed workshops and hub document

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

1. Reference Template

See {businessGoalsTemplate} for the complete template structure.

2. Generate Document Sections

Include: 1. Header - Project name, date, status 2. Vision Statement - 1-2 sentence transformation goal 3. Business Objectives - 3 priority tiers (Primary/Secondary/Tertiary) 4. The Flywheel - How goals connect causally 5. Success Metrics Alignment - Persona to objective connections 6. Related Documents Footer - Links to other trigger map docs

Language Requirements:

• "Create awesome [users]" NOT "convert users"
• "Naturally become [champions]" NOT "make them champions"
• Empowering, organic growth language

Priority Clarity:

• PRIMARY GOAL clearly marked as THE ENGINE
• SECONDARY driven by primary
• TERTIARY benefits FOR members (not company revenue)

SMART Objectives:

• Specific, Measurable, Achievable, Relevant, Time-bound

Flywheel Logic:

• Shows causal relationships
• Emphasizes natural emergence
• Makes primary goal's importance clear

3. Save and Confirm

Store as: 01-Business-Goals.md in trigger map folder.

Output: "Business goals document created with flywheel!"

4. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Primary Persona Document | [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. Document must be generated and saved before proceeding. Do NOT skip ahead.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• Document generated with all 6 sections
• Vision statement clear and inspiring
• 3 priority tiers with SMART objectives
• PRIMARY GOAL marked as THE ENGINE
• Flywheel showing causal relationships
• Empowering language throughout (no "convert" language)
• ~150-160 lines
• Document saved to correct location

❌ SYSTEM FAILURE:

• Missing required sections
• Using "convert users" or similar language
• PRIMARY GOAL not clearly marked
• Missing flywheel explanation
• Objectives not SMART
• Not saved to correct location

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

Feature Impact Analysis: {{project_name}}

Scoring

Primary Persona (⭐): High = 5 pts | Medium = 3 pts | Low = 1 pt Other Personas: High = 3 pts | Medium = 1 pt | Low = 0 pts

Max Possible Score: {{max_score}} (with {{persona_count}} personas) Must Have Threshold: {{must_have_threshold}}+ or Primary High (5)

---

Prioritized Features

{{#each sorted_features}} | {{this.rank}} | {{this.name}} | {{this.score}} | {{this.decision}} | {{/each}}

---

Decisions

Must Have MVP (Primary High OR Top Tier Score): {{#each must_have}}

• {{this.name}} ({{this.score}})

{{/each}}

Consider for MVP: {{#each consider}}

• {{this.name}} ({{this.score}})

{{/each}}

Defer (Nice-to-Have or Low Strategic Value): {{#each defer}}

• {{this.name}} ({{this.score}})

{{/each}}

---

_Generated with Whiteport Design Studio framework_ _Strategic input for Phase 4: UX Design and Phase 6: PRD/Development_

Validate Trigger Map

Goal: Systematically validate all Trigger Map documents against WDS quality standards and generate an actionable report.

Your Role: Validation specialist reviewing trigger map completeness, consistency, and strategic alignment.

---

INITIALIZATION

Design Log

Read {output_folder}/_progress/00-design-log.md. Check Current and Backlog for context.

Configuration Loading

Load and read full config from {project-root}/_bmad/wds/config.yaml and resolve:

• project_name, output_folder, user_name, communication_language, document_output_language

Load Trigger Map Data

Load all trigger map documents from {output_folder}/B-Trigger-Map/.

Route to Validation

Load, read completely, and execute {validateWorkflow} (steps-v/step-01-target-group-coverage.md)

Auto-proceed through all validation steps. Present final report at the end.

---

AFTER COMPLETION

1. Update design log 2. Suggest next action 3. Return to activity menu