docs: update all documentation and add AI tooling configs

- Rewrite README.md with current architecture, features and stack
- Update docs/API.md with all current endpoints (corporate, BI, client 360)
- Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL
- Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente)
- Add docs/INDEX.md documentation index
- Add PROJETO.md comprehensive project reference
- Add BI-CCC-Implementation-Guide.md
- Include AI agent configs (.claude, .agents, .gemini, _bmad)
- Add netbird VPN configuration
- Add status report

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

_bmad/wds/workflows/2-trigger-mapping/data/business-goals-template.md

@@ -0,0 +1,150 @@
+# Business Goals Document Template
+
+Complete template structure for 01-Business-Goals.md
+
+---
+
+## 1. Header
+
+```markdown
+# Business Goals & Objectives
+
+> Strategic goals and measurable objectives for [Project Name]
+
+**Document:** Trigger Map - Business Goals
+**Created:** [Date]
+**Status:** COMPLETE
+```
+
+---
+
+## 2. Vision Statement
+
+```markdown
+## Vision
+
+**[Insert vision statement from workshop]**
+
+[Should be 1-2 sentences describing the ultimate goal/transformation]
+```
+
+---
+
+## 3. Business Objectives (3 Priority Tiers)
+
+```markdown
+## 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
+
+```markdown
+## 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
+
+```markdown
+## 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
+
+```markdown
+## 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)_
+```

_bmad/wds/workflows/2-trigger-mapping/data/key-insights-structure.md

@@ -0,0 +1,222 @@
+# Key Insights Document Structure Guide
+
+**Complete template for generating 05-Key-Insights.md**
+
+---
+
+## 1. Header
+
+```markdown
+# 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
+
+```markdown
+## 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
+
+```markdown
+## 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
+
+```markdown
+## 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
+
+```markdown
+## 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
+
+```markdown
+## 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
+
+```markdown
+## 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
+
+```markdown
+## 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
+
+```markdown
+## 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_

_bmad/wds/workflows/2-trigger-mapping/data/mermaid-formatting-guide.md

@@ -0,0 +1,262 @@
+# 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:**
+```css
+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
+
+```mermaid
+%%{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.**
+

_bmad/wds/workflows/2-trigger-mapping/data/quality-checklist.md

@@ -0,0 +1,212 @@
+# 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_

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-00a-documentation-synthesis.md

@@ -0,0 +1,147 @@
+---
+name: 'step-00a-documentation-synthesis'
+description: 'Receive and analyze existing documentation to create a Trigger Map'
+
+# File References
+nextStepFile: './step-00b-business-goals-extract.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-00b-business-goals-extract.md

@@ -0,0 +1,152 @@
+---
+name: 'step-00b-business-goals-extract'
+description: 'Extract and validate business goals from existing documentation'
+
+# File References
+nextStepFile: './step-00c-target-groups-extract.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 2: Business Goals Extraction
+
+## STEP GOAL:
+
+Extract, validate, and refine business goals (vision statement and strategic objectives) from the user's existing documentation through collaborative dialogue.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are Saga the Analyst - facilitating strategic clarity from existing documentation
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured facilitation and pattern recognition, user brings business knowledge and user insight
+- ✅ Work together as equals in a partnership, not a client-vendor relationship
+
+### Step-Specific Rules:
+
+- 🎯 Focus on extracting and validating vision and objectives from documentation
+- 🚫 FORBIDDEN to invent business goals not supported by documentation or user input
+- 💬 Approach: Frame as validation - "Your material suggests X, is this correct?"
+- 📋 Fill gaps through conversation if documentation is incomplete
+- 📋 Help transform vague goals into SMART objectives
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Analyze documentation for vision statements and objectives
+- 💾 Store validated vision_statement and objectives
+- 📖 Present extracted goals for user validation
+- 🚫 Do not proceed until vision and objectives are confirmed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: User's documentation from step-00a analysis
+- Focus: Vision statement and strategic objectives extraction/validation
+- Limits: Only extract what exists or fill gaps through dialogue - do not fabricate
+- Dependencies: Requires completed step-00a documentation analysis
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Extract Vision Statement
+
+Analyze documentation for vision and objectives.
+
+**If clear vision found:**
+Present: "Your documentation suggests this vision:
+> {{extracted_vision}}
+Is this the aspirational goal you're working toward?"
+
+Ask: "Does this capture your vision, or should we refine it?"
+
+**If vague vision found:**
+Present: "I found some aspirational language in your documentation. It seems like your vision is:
+> {{interpreted_vision}}
+But this isn't explicitly stated. Is this accurate?"
+
+Ask: "Should we use this, or define a clearer vision statement?"
+
+**If no vision found:**
+Present: "I don't see an explicit vision statement in your documentation. However, based on your objectives and plans, the implied vision seems to be:
+> {{inferred_vision}}
+This is reverse-engineered from what you're trying to achieve."
+
+Ask: "Does this capture your aspirational goal? Or should we define it differently?"
+
+Refine based on feedback and store vision_statement.
+
+### 2. Extract Strategic Objectives
+
+**If SMART objectives found:**
+Present the extracted measurable objectives with their metrics, targets, and timelines. Note they look SMART. Ask for confirmation or adjustments.
+
+**If vague goals found:**
+Present the original vague goals alongside suggested SMART versions. Ask if the SMART versions capture what needs to be measured. Refine based on feedback.
+
+**If no objectives found:**
+Ask: "What metrics would prove you're achieving your vision? Think about user metrics, business metrics, and quality metrics."
+
+Create objectives through conversation using SMART method.
+
+Store objectives.
+
+### 3. Present Workshop 1 Summary
+
+Output:
+"**Workshop 1 Complete!**
+
+**Vision:**
+{{vision_statement}}
+
+**Strategic Objectives:**
+{{#each objectives}}
+{{@index + 1}}. {{this.statement}}
+{{/each}}
+
+Next, we'll identify who can help you achieve these goals."
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Target Groups Extraction | [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+- IF C: Load and execute {nextStepFile}
+- IF M: Return to {activityWorkflowFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- User can chat or ask questions - always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN user selects [C] will you load the next step file. Vision and objectives must be confirmed before proceeding to target group extraction.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Vision statement extracted or created through dialogue
+- Strategic objectives validated as SMART (Specific, Measurable, Achievable, Relevant, Time-bound)
+- Vague goals transformed into measurable objectives
+- User confirmed both vision and objectives
+- Gaps filled through collaborative conversation
+- Results stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+- Inventing business goals not supported by documentation
+- Skipping vision statement
+- Accepting vague goals without making them SMART
+- Not getting user confirmation on extracted goals
+- Proceeding without stored vision_statement and objectives
+- Pure extraction without validation dialogue
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-00c-target-groups-extract.md

@@ -0,0 +1,149 @@
+---
+name: 'step-00c-target-groups-extract'
+description: 'Extract and deepen target group definitions from existing documentation'
+
+# File References
+nextStepFile: './step-00d-driving-forces-extract.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-00d-driving-forces-extract.md

@@ -0,0 +1,143 @@
+---
+name: 'step-00d-driving-forces-extract'
+description: 'Extract and validate driving forces (positive and negative) from existing documentation'
+
+# File References
+nextStepFile: './step-00e-prioritization-extract.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-00e-prioritization-extract.md

@@ -0,0 +1,159 @@
+---
+name: 'step-00e-prioritization-extract'
+description: 'Extract and validate strategic prioritization from existing documentation'
+
+# File References
+nextStepFile: './step-00f-gap-analysis.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-00f-gap-analysis.md

@@ -0,0 +1,151 @@
+---
+name: 'step-00f-gap-analysis'
+description: 'Analyze gaps and validate strategic alignment of documentation synthesis'
+
+# File References
+nextStepFile: './step-01-overview.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-01-overview.md

@@ -0,0 +1,185 @@
+---
+name: 'step-01-overview'
+description: 'Present engagement mode options and route to appropriate workshop path'
+
+# File References
+nextStepFile: './step-02-business-goals.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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-2-trigger-mapping-guide.md
+- Read docs/quick-start/02-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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-02-business-goals.md

@@ -0,0 +1,180 @@
+---
+name: 'step-02-business-goals'
+description: 'Workshop 1: Define business vision and SMART objectives'
+
+# File References
+nextStepFile: './step-03-target-groups.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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:
+- **S**pecific - What exactly?
+- **M**easurable - What number?
+- **A**chievable - Is this realistic?
+- **R**elevant - Does this connect to the vision?
+- **T**ime-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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-03-target-groups.md

@@ -0,0 +1,180 @@
+---
+name: 'step-03-target-groups'
+description: 'Workshop 2: Identify target groups and build detailed personas'
+
+# File References
+nextStepFile: './step-04-driving-forces.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-04-driving-forces.md

@@ -0,0 +1,191 @@
+---
+name: 'step-04-driving-forces'
+description: 'Workshop 3: Map positive and negative driving forces per persona'
+
+# File References
+nextStepFile: './step-05-prioritization.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-05-prioritization.md

@@ -0,0 +1,185 @@
+---
+name: 'step-05-prioritization'
+description: 'Workshop 4: Prioritize business goals, target groups, and driving forces'
+
+# File References
+nextStepFile: './step-06a-extract-features.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-06a-extract-features.md

@@ -0,0 +1,131 @@
+---
+name: 'step-06a-extract-features'
+description: 'Extract features from project documentation for impact analysis'
+
+# File References
+nextStepFile: './step-06b-confirm-assessment.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-06b-confirm-assessment.md

@@ -0,0 +1,118 @@
+---
+name: 'step-06b-confirm-assessment'
+description: 'Confirm assessment approach before running feature impact analysis'
+
+# File References
+nextStepFile: './step-06c-make-assessment.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-06c-make-assessment.md

@@ -0,0 +1,156 @@
+---
+name: 'step-06c-make-assessment'
+description: 'Run initial feature impact assessment against persona driving forces'
+
+# File References
+nextStepFile: './step-06d-generate-document.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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:
+
+| Rank | Feature | {{primary}} | {{secondary}} | {{tertiary}} | **Score** |
+|------|---------|-------------|---------------|--------------|-----------|
+| 1 | [Feature] | HIGH (5) | HIGH (3) | HIGH (3) | **11** |
+... (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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-06d-generate-document.md

@@ -0,0 +1,159 @@
+---
+name: 'step-06d-generate-document'
+description: 'Generate the complete Feature Impact Analysis document'
+
+# File References
+nextStepFile: './step-06e-feature-wrap-up.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-06e-feature-wrap-up.md

@@ -0,0 +1,133 @@
+---
+name: 'step-06e-feature-wrap-up'
+description: 'Feature Impact Workshop wrap-up with completion summary and next steps'
+
+# File References
+nextStepFile: './step-07a-generate-hub.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-07a-generate-hub.md

@@ -0,0 +1,182 @@
+---
+name: 'step-07a-generate-hub'
+description: 'Generate the 00-trigger-map.md hub document with Mermaid diagram and navigation'
+
+# File References
+nextStepFile: './step-07b-generate-business-goals.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-07b-generate-business-goals.md

@@ -0,0 +1,138 @@
+---
+name: 'step-07b-generate-business-goals'
+description: 'Generate the 01-Business-Goals.md document with vision, objectives, and flywheel'
+
+# File References
+nextStepFile: './step-07c-generate-primary-persona.md'
+activityWorkflowFile: '../workflow.md'
+
+# Data References
+businessGoalsTemplate: '../data/business-goals-template.md'
+---
+
+# 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.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-07c-generate-primary-persona.md

@@ -0,0 +1,136 @@
+---
+name: 'step-07c-generate-primary-persona'
+description: 'Generate the primary persona document with full transformation journey'
+
+# File References
+nextStepFile: './step-07d-generate-secondary-persona.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 19: Generate Primary Persona
+
+## STEP GOAL:
+
+Create the PRIMARY persona document with full transformation journey, champion creation story, and detailed driving forces with Product Promises.
+
+## 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 rich, human persona 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 most detailed persona document (PRIMARY gets most detail)
+- 🚫 FORBIDDEN to use "converting" language - use "creating awesome" language
+- 💬 Approach: Rich, nuanced, human storytelling - not template-like
+- 📋 Use template from ../templates/persona-document.template.md
+- 📋 Each driving force MUST have a Product Promise; target ~250-375 lines
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Generate persona with all 13 required sections from template
+- 💾 Save as 02-[Name]-the-[Role].md in trigger map folder
+- 📖 Include full BEFORE/AFTER transformation section
+- 🚫 Do not skip Product Promises for any driving force
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Primary persona from workshops, driving forces, priorities
+- Focus: PRIMARY persona document with champion creation story
+- Limits: Use persona data from workshops - rich and human, not template-like
+- Dependencies: Requires completed workshops and hub/business goals documents
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Gather Input
+
+From trigger map data:
+- targetGroups.primary section
+- Name, role, type, roleInFlywheel
+- 6 drivingForces (3 wants, 3 fears)
+
+### 2. Generate Document
+
+Use the comprehensive persona document template: `../templates/persona-document.template.md`
+
+This template provides the complete structure for sections 1-13.
+
+**File Naming:** `02-[Name]-the-[Role].md` (e.g., 02-Sarah-the-Student.md)
+
+**Key Requirements:**
+
+**Length:** ~250-375 lines
+
+**Tone:** Rich, nuanced, human. Not "converting" but "creating awesome." Natural language, storytelling.
+
+**Driving Forces:** Each must have **[Product] Promise**. Show how product addresses each driver. Be specific and actionable.
+
+**Transformation:** PRIMARY persona gets full BEFORE/AFTER section. Show emotional journey, not just functional. Use emojis to show emotional states.
+
+**Primary-Specific Section:** Include "Role in Flywheel: Creating Awesome [Personas] Who Become [Champions]"
+
+Show:
+- The natural evolution from user to champion
+- What they need to see on product page
+- Focus on transformation and champion creation
+- How they naturally advocate after transformation
+
+### 3. Save and Confirm
+
+Store as: 02-[Name]-the-[Role].md in trigger map folder.
+
+Output: "Primary persona document created: 02-[Name]-the-[Role].md"
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Secondary Persona | [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. Primary persona document must be complete before proceeding. Do NOT skip ahead.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All 13 sections from template included
+- 6 driving forces with Product Promises (3 wants, 3 fears)
+- Full BEFORE/AFTER transformation section
+- Champion creation story included
+- Rich, nuanced, human tone throughout
+- "Creating awesome" language (not "converting")
+- ~250-375 lines
+- Saved with correct filename
+
+### ❌ SYSTEM FAILURE:
+- Missing required sections
+- Driving forces without Product Promises
+- Using "converting" language
+- Missing transformation section
+- Template-like, not human and rich
+- Wrong filename format
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-07d-generate-secondary-persona.md

@@ -0,0 +1,139 @@
+---
+name: 'step-07d-generate-secondary-persona'
+description: 'Generate the secondary persona document with validation strategy'
+
+# File References
+nextStepFile: './step-07e-generate-tertiary-persona.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 20: Generate Secondary Persona
+
+## STEP GOAL:
+
+Create the SECONDARY persona document with validation strategy, trust building focus, and evaluation journey, including detailed driving forces with Product Answers.
+
+## 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 rich, human persona 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 secondary persona with validation and trust focus
+- 🚫 FORBIDDEN to use "converting" language - use "creating awesome" language
+- 💬 Approach: Rich, nuanced, human storytelling - not template-like
+- 📋 Use template from ../templates/persona-document.template.md
+- 📋 Each driving force MUST have a Product Answer; target ~250-375 lines
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Generate persona with all 13 required sections from template
+- 💾 Save as 03-[Name]-the-[Role].md in trigger map folder
+- 📖 Include validation strategy section
+- 🚫 Do not skip Product Answers for any driving force
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Secondary persona from workshops, driving forces
+- Focus: SECONDARY persona document with trust and validation focus
+- Limits: Use persona data from workshops
+- Dependencies: Requires completed primary persona document
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Gather Input
+
+From trigger map data:
+- targetGroups.secondary section
+- Name, role, type, roleInFlywheel
+- 6 drivingForces (3 wants, 3 fears)
+
+### 2. Generate Document
+
+Use the comprehensive persona document template.
+
+**File Naming:** `03-[Name]-the-[Role].md` (e.g., 03-Marcus-the-Mentor.md)
+
+**Key Requirements:**
+
+**Length:** ~250-375 lines
+
+**Tone:** Rich, nuanced, human. Natural language, storytelling.
+
+**Driving Forces:** Each must have **[Product] Answer**. Show how product addresses each driver.
+
+**Validation:** Focus on what builds trust. Show the evaluation journey. Address skepticism and concerns.
+
+**Secondary-Specific Section:** Include "Validation Strategy"
+
+Show:
+- What they need to see about the product
+- Conversion path: Discovery -> Evaluation -> Adoption -> Advocacy
+- Focus on validation and trust building
+- How product proves its value to them
+
+### 3. Save and Confirm
+
+Store as: 03-[Name]-the-[Role].md in trigger map folder.
+
+Output: "Secondary persona document created: 03-[Name]-the-[Role].md"
+
+### 4. Route to Next Step
+
+**If Tertiary persona exists:**
+Present MENU: [C] Continue to Tertiary Persona | [M] Return to Activity Menu
+
+**If NO Tertiary persona:**
+Present MENU: [C] Continue to Key Insights Document | [M] Return to Activity Menu
+
+(If no tertiary, nextStepFile should be adjusted to step-07f-generate-key-insights.md)
+
+#### Menu Handling Logic:
+- IF C: Load and execute {nextStepFile} (or step-07f if no tertiary)
+- 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. Secondary persona document must be complete before proceeding. Do NOT skip ahead.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All 13 sections from template included
+- 6 driving forces with Product Answers (3 wants, 3 fears)
+- Validation strategy section included
+- Trust building and evaluation journey described
+- Rich, nuanced, human tone
+- ~250-375 lines
+- Correct routing based on tertiary persona existence
+
+### ❌ SYSTEM FAILURE:
+- Missing required sections
+- Driving forces without Product Answers
+- Missing validation strategy
+- Template-like tone
+- Wrong filename format
+- Not routing correctly for tertiary/no-tertiary cases
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-07e-generate-tertiary-persona.md

@@ -0,0 +1,134 @@
+---
+name: 'step-07e-generate-tertiary-persona'
+description: 'Generate the optional tertiary persona document with organic discovery focus'
+
+# File References
+nextStepFile: './step-07f-generate-key-insights.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 21: Generate Tertiary Persona (Optional)
+
+## STEP GOAL:
+
+Create the TERTIARY persona document with organic value discovery focus, benefits recognition journey, and word-of-mouth potential, including driving forces with Product Answers.
+
+## 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 rich, human persona 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 tertiary persona with organic discovery and benefits focus
+- 🚫 FORBIDDEN to use "converting" or "targeting" language
+- 💬 Approach: Rich, nuanced, human storytelling - emphasize organic value recognition
+- 📋 Use template from ../templates/persona-document.template.md
+- 📋 Each driving force MUST have a Product Answer; target ~250-375 lines
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Generate persona with all 13 required sections from template
+- 💾 Save as 04-[Name]-the-[Role].md in trigger map folder
+- 📖 Include organic discovery section
+- 🚫 Do not use "targeted" language - tertiary discovers value organically
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Tertiary persona from workshops, driving forces
+- Focus: TERTIARY persona document with organic discovery and word-of-mouth
+- Limits: This step is optional - only if tertiary persona exists
+- Dependencies: Requires completed secondary persona document
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Gather Input
+
+From trigger map data:
+- targetGroups.tertiary section (if exists)
+- Name, role, type, roleInFlywheel
+- 6 drivingForces (3 wants, 3 fears)
+
+### 2. Generate Document
+
+Use the comprehensive persona document template.
+
+**File Naming:** `04-[Name]-the-[Role].md` (e.g., 04-Emma-the-Enthusiast.md)
+
+**Key Requirements:**
+
+**Length:** ~250-375 lines
+
+**Tone:** Rich, nuanced, human. Natural language, storytelling.
+
+**Driving Forces:** Each must have **[Product] Answer**. Show how product addresses each driver.
+
+**Discovery:** Focus on organic value recognition. Show the appreciation journey. Emphasize benefits FOR members.
+
+**Tertiary-Specific Section:** Include "How [Persona Name] Discovers [Product] Value"
+
+Show:
+- The recognition path
+- Journey: Experience -> Recognition -> Appreciation -> Word of Mouth
+- Focus on benefits and organic discovery
+- How they become advocates without being "targeted"
+
+### 3. Save and Confirm
+
+Store as: 04-[Name]-the-[Role].md in trigger map folder.
+
+Output: "Tertiary persona document created: 04-[Name]-the-[Role].md"
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Key Insights 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. Tertiary persona document must be complete before proceeding. Do NOT skip ahead.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All 13 sections from template included
+- 6 driving forces with Product Answers (3 wants, 3 fears)
+- Organic discovery section included
+- Benefits and appreciation journey described
+- Word-of-mouth potential shown
+- No "targeted" or "converting" language
+- ~250-375 lines
+- Saved with correct filename
+
+### ❌ SYSTEM FAILURE:
+- Missing required sections
+- Driving forces without Product Answers
+- Missing organic discovery section
+- Using "targeted" or "converting" language
+- Template-like tone
+- Wrong filename format
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-07f-generate-key-insights.md

@@ -0,0 +1,133 @@
+---
+name: 'step-07f-generate-key-insights'
+description: 'Generate the 05-Key-Insights.md strategic implications document'
+
+# File References
+nextStepFile: './step-07g-quality-check.md'
+activityWorkflowFile: '../workflow.md'
+
+# Data References
+keyInsightsStructure: '../data/key-insights-structure.md'
+---
+
+# Step 22: Generate Key Insights Document
+
+## STEP GOAL:
+
+Create the 05-Key-Insights.md document synthesizing the trigger map into actionable insights for design and development, including flywheel explanation, focus areas, design implications, and emotional transformation goals.
+
+## 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 - synthesizing strategic implications
+- ✅ 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 synthesizing actionable insights from all trigger map data
+- 🚫 FORBIDDEN to generate generic advice - all insights must derive from actual data
+- 💬 Approach: Actionable, specific, "create awesome" language throughout
+- 📋 Use structure from {keyInsightsStructure}
+- 📋 PRIMARY persona gets most attention; target ~145-150 lines
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Synthesize all workshop data into actionable insights
+- 💾 Save as 05-Key-Insights.md in trigger map folder
+- 📖 Reference key insights structure for all 9 sections
+- 🚫 Do not generate generic design advice
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All workshop outputs, persona documents, business goals
+- Focus: Strategic implications for design and development
+- Limits: Insights must derive from actual trigger map data
+- Dependencies: Requires all persona documents and business goals completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Reference Structure
+
+See {keyInsightsStructure} for complete structure.
+
+### 2. Generate All 9 Sections
+
+1. **Header** - Document title, purpose, status
+2. **The Flywheel** - How champions drive everything (Priority 1 -> 2 -> 3)
+3. **Primary Development Focus** - 5 key focus areas for development
+4. **Critical Success Factors** - Essential elements for success
+5. **Design Implications** - Section-by-section "must do" requirements
+6. **Emotional Transformation Goals** - First-person transformation statements
+7. **Design Focus Statement** - Primary target, must-address vs should-address
+8. **Development Phases** - Initial deliverable + future phases
+9. **Related Documents Footer** - Links to all trigger map documents
+
+**Key Requirements:**
+
+**Tone:** Actionable and specific. "Create awesome" language throughout. Links back to workshop outputs.
+
+**Focus:** PRIMARY persona gets most attention. 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.
+
+### 3. Save and Confirm
+
+Store as: 05-Key-Insights.md in trigger map folder.
+
+Output: "Key insights document created!"
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Quality Check | [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. Key Insights document must be generated before proceeding. Do NOT skip ahead.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All 9 sections generated
+- Insights derive from actual trigger map data (not generic)
+- Flywheel explanation clear
+- Design implications tied to specific persona fears/wants
+- Emotional transformation goals in first-person
+- PRIMARY persona gets most attention
+- "Create awesome" language throughout
+- ~145-150 lines
+- Document saved
+
+### ❌ SYSTEM FAILURE:
+- Generic design advice not derived from data
+- Missing required sections
+- Not linking to specific persona data
+- Missing emotional transformation goals
+- Template-like or generic tone
+- Not saved to correct location
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-07g-quality-check.md

@@ -0,0 +1,149 @@
+---
+name: 'step-07g-quality-check'
+description: 'Verify all documents are complete, consistent, and properly cross-linked'
+
+# File References
+nextStepFile: './step-08a-mermaid-init-structure.md'
+activityWorkflowFile: '../workflow.md'
+
+# Data References
+qualityChecklist: '../data/quality-checklist.md'
+---
+
+# Step 23: Quality Check & Verification
+
+## STEP GOAL:
+
+Ensure all generated documents are complete, consistent, and properly cross-linked by running through a comprehensive 13-dimension quality checklist and fixing any issues found.
+
+## 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 - verifying completeness and quality
+- ✅ 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 systematic quality verification across all documents
+- 🚫 FORBIDDEN to skip any quality dimension or approve with known issues
+- 💬 Approach: Systematic checklist-driven verification
+- 📋 Fix any issues found before marking as complete
+- 📋 Reference {qualityChecklist} for complete checklist
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Verify all 13 quality dimensions
+- 💾 Fix any issues found during verification
+- 📖 Present verification results to user
+- 🚫 Do not approve with unresolved issues
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All generated documents
+- Focus: Quality verification across all dimensions
+- Limits: Must check ALL dimensions - no shortcuts
+- Dependencies: Requires all documents generated
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Run Quality Verification
+
+Verify all generated documents across 13 quality dimensions:
+
+1. **File Structure** - All required files exist with consistent naming
+2. **Mermaid Diagram** - Renders correctly, proper styling
+3. **Content Consistency** - Names, numbers, timelines match across docs
+4. **Language Quality** - Empowering, organic transformation language
+5. **Cross-References** - All links working between documents
+6. **Persona Completeness** - All 13 sections, 6 driving forces with Promises/Answers
+7. **Hub Document (00)** - On-page summaries, flywheel, ~220-250 lines
+8. **Business Goals (01)** - THE ENGINE marked, metrics complete, ~150-160 lines
+9. **Key Insights (05)** - Flywheel, focus areas, design implications, ~145-155 lines
+10. **Feature Impact (06)** - Scoring system, prioritization (if exists)
+11. **Priority Tiers** - Consistent emojis and language throughout
+12. **Driving Forces** - Each has specific Product Promise/Answer
+13. **Formatting** - Markdown, headers, links, emojis render correctly
+
+**If any check fails:** Identify document, re-read step instructions, make corrections, re-verify.
+
+### 2. Present Verification Results
+
+Output:
+"**Trigger Map Documentation Complete & Verified!**
+
+**Created Structure:**
+```
+B-Trigger-Map/
+ 00-trigger-map.md          ([X] lines) - Hub with diagram & navigation
+ 01-Business-Goals.md        ([X] lines) - Objectives & flywheel
+ 02-[Primary Name].md       ([X] lines) - Primary persona
+ 03-[Secondary Name].md     ([X] lines) - Secondary persona
+ 04-[Tertiary Name].md      ([X] lines) - Tertiary persona [if exists]
+ 05-Key-Insights.md         ([X] lines) - Strategic implications
+ 06-Feature-Impact.md       ([X] lines) - Feature prioritization [if completed]
+```
+
+**Quality Verified:**
+- All cross-links working
+- Mermaid diagram renders correctly
+- Language is empowering and organic
+- All 6 driving forces have Product Promises/Answers
+- Priority tiers consistent throughout
+- Transformation journey clearly described
+
+**Primary Target:** [Primary Persona Name]
+**THE ENGINE:** [PRIMARY GOAL statement]
+
+**Ready for Phase 3: Platform Requirements or Phase 4: UX Design!**"
+
+Mark workflow as complete and return to main trigger mapping flow.
+
+### 3. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Mermaid Diagram 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. All quality checks must pass before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All 13 quality dimensions verified
+- Any issues found were fixed and re-verified
+- All documents complete and consistent
+- Cross-references working
+- Verification results presented to user
+- Document structure summary shown
+
+### ❌ SYSTEM FAILURE:
+- Skipping quality dimensions
+- Approving with known issues
+- Not fixing found issues
+- Not re-verifying after corrections
+- Not presenting verification results
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-08a-mermaid-init-structure.md

@@ -0,0 +1,138 @@
+---
+name: 'step-08a-mermaid-init-structure'
+description: 'Initialize the Mermaid diagram structure with configuration and node IDs'
+
+# File References
+nextStepFile: './step-08b-mermaid-business-goals.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 24: Initialize Diagram Structure
+
+## STEP GOAL:
+
+Set up the basic Mermaid diagram structure with configuration, section comments, and determine all node IDs based on the trigger map data.
+
+## 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 professional visual diagrams
+- ✅ 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 setting up diagram configuration and structure
+- 🚫 FORBIDDEN to use any theme other than 'base' or any font other than Inter
+- 💬 Approach: Systematic setup of diagram foundation
+- 📋 Use flowchart LR direction, base theme, Inter font, 14px fontSize
+- 📋 Determine all node IDs based on actual data
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Set up Mermaid configuration exactly as specified
+- 💾 Store diagram_config, node_ids, and diagram_structure
+- 📖 Use consistent node ID patterns
+- 🚫 Do not deviate from specified configuration
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All trigger map data (business goals, personas, drivers)
+- Focus: Diagram initialization and structure
+- Limits: Follow exact Mermaid configuration
+- Dependencies: Requires all trigger map data available
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Start with Mermaid Configuration
+
+Always begin with:
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': { 'fontFamily':'Inter, system-ui, sans-serif', 'fontSize':'14px'}}}%%
+flowchart LR
+```
+
+**Rules:**
+- Use `base` theme
+- Set font to `Inter, system-ui, sans-serif`
+- Set fontSize to `14px`
+- Use `flowchart LR` (left-to-right direction)
+
+### 2. Add Section Comments
+
+Structure the diagram with comments:
+
+```
+    %% Business Goals (Left)
+
+    %% Central Platform
+
+    %% Target Groups (Right)
+
+    %% Driving Forces (Far Right)
+
+    %% Connections
+
+    %% Styling
+```
+
+### 3. Determine Node IDs
+
+Create node ID list based on data:
+
+- **Business Goals:** `BG0`, `BG1`, `BG2` (sequential)
+- **Platform:** `PLATFORM` (always singular)
+- **Target Groups:** `TG0`, `TG1`, `TG2` (sequential, matching persona count)
+- **Driving Forces:** `DF0`, `DF1`, `DF2` (sequential, matching target groups)
+
+Store diagram_config, node_ids, and diagram_structure.
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Format Business Goals | [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. Diagram structure must be initialized before formatting nodes.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Mermaid configuration uses base theme with Inter font at 14px
+- Flowchart direction is LR
+- Section comments properly structured
+- All node IDs determined from actual data
+- Node IDs follow consistent patterns (BG0, TG0, DF0, PLATFORM)
+- Configuration and structure stored
+
+### ❌ SYSTEM FAILURE:
+- Wrong theme or font configuration
+- Wrong flowchart direction
+- Missing section comments
+- Node IDs not matching actual data
+- Inconsistent node ID patterns
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-08b-mermaid-business-goals.md

@@ -0,0 +1,139 @@
+---
+name: 'step-08b-mermaid-business-goals'
+description: 'Format business goals nodes with emojis, titles, and key points'
+
+# File References
+nextStepFile: './step-08c-mermaid-platform.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 25: Format Business Goals Nodes
+
+## STEP GOAL:
+
+Create properly formatted business goals nodes with emojis, ALL CAPS titles, key points, and proper padding for the Mermaid diagram.
+
+## 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 professional diagram nodes
+- ✅ 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 formatting business goal nodes following exact template
+- 🚫 FORBIDDEN to use HTML tags (bold, italic) in nodes
+- 💬 Approach: Systematic node creation following template pattern
+- 📋 Each node: starts with `<br/>`, emoji + ALL CAPS title, 3-5 key points, ends with `<br/><br/>`
+- 📋 Priority indicated by vertical order (BG0 top), not special formatting
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Format each business goal as a properly structured node
+- 💾 Store business_goals_nodes and business_goals_count
+- 📖 Follow exact node structure template
+- 🚫 Do not use HTML formatting tags
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Business goals from workshops, diagram structure from step-08a
+- Focus: Formatting BG nodes for Mermaid diagram
+- Limits: Follow exact template pattern - no custom formatting
+- Dependencies: Requires diagram structure from step-08a
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Format Each Business Goal Node
+
+**Node Structure Template:**
+```
+BGX["<br/>EMOJI TITLE<br/><br/>Point 1<br/>Point 2<br/>Point 3<br/><br/>"]
+```
+
+**Required elements per node:**
+1. Start with `<br/>` (top padding)
+2. Emoji + Title in ALL CAPS
+3. Blank line (`<br/><br/>`)
+4. 3-5 key points (each on separate line with `<br/>`)
+5. End with `<br/><br/>` (bottom padding)
+
+### 2. Choose Appropriate Emoji
+
+Based on goal theme:
+- Revenue/Profitability: money bag
+- Customer Satisfaction: happy face
+- Efficiency/Speed: lightning bolt
+- Growth/Expansion: rocket
+- Community: star
+- Objectives/Metrics: chart
+- Partnerships: handshake
+- Goals/Targets: target
+
+All business goals use consistent styling. Priority is indicated by vertical order (BG0 first = top priority).
+
+### 3. Verify Rules Checklist
+
+- Node ID follows pattern BG0, BG1, BG2
+- Starts with `<br/>`
+- Emoji at beginning of title
+- Title in ALL CAPS
+- Blank line after title (`<br/><br/>`)
+- 3-5 key points
+- Each point ends with `<br/>`
+- Ends with `<br/><br/>`
+- No HTML tags (bold, italic)
+- Proper quote and bracket closure `"]`
+
+Store business_goals_nodes and business_goals_count.
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Format Platform Node | [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 business goal nodes must be formatted before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All business goal nodes formatted following template
+- Proper padding at top and bottom
+- Emoji + ALL CAPS titles
+- 3-5 key points per node
+- No HTML tags in any node
+- Priority indicated by order, not formatting
+- Nodes stored for assembly
+
+### ❌ SYSTEM FAILURE:
+- Missing padding
+- HTML tags in nodes
+- Titles not in ALL CAPS
+- Missing or too many key points
+- Improper node closure
+- Using special formatting for priority
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-08c-mermaid-platform.md

@@ -0,0 +1,135 @@
+---
+name: 'step-08c-mermaid-platform'
+description: 'Format the central platform node with product name and transformation statement'
+
+# File References
+nextStepFile: './step-08d-mermaid-target-groups.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 26: Format Platform Node
+
+## STEP GOAL:
+
+Create the central platform node with product name in ALL CAPS, category/tagline, and a multi-line transformation 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 - creating professional diagram nodes
+- ✅ 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 central platform node
+- 🚫 FORBIDDEN to use HTML tags or skip transformation statement
+- 💬 Approach: Emotionally compelling transformation statement spanning 3-5 lines
+- 📋 Node ID must be exactly PLATFORM
+- 📋 Include category/tagline and multi-line transformation
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Format platform node following exact template
+- 💾 Store platform_node and transformation_statement
+- 📖 Transformation statement should describe before->after change
+- 🚫 Do not skip any required element
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Product name, vision, transformation goals
+- Focus: Central platform node creation
+- Limits: Follow exact node structure template
+- Dependencies: Requires business goal nodes from step-08b
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Format Platform Node
+
+**Node Structure Template:**
+```
+PLATFORM["<br/>EMOJI PRODUCT NAME<br/><br/>Category or tagline<br/><br/>Transformation statement<br/>that spans multiple lines<br/>describing the change<br/><br/>"]
+```
+
+**Required elements:**
+1. Start with `<br/>` (top padding)
+2. Emoji + Product name in ALL CAPS
+3. Blank line (`<br/><br/>`)
+4. Category or tagline
+5. Blank line (`<br/><br/>`)
+6. Transformation/value statement - break across multiple lines (3-5 lines)
+7. End with `<br/><br/>` (bottom padding)
+
+### 2. Craft Transformation Statement
+
+The transformation statement should:
+- Describe the before -> after change
+- Be emotionally compelling
+- Be specific about the transformation
+- Span 3-5 lines for readability
+- Connect to the strategic vision and transformation goals
+
+### 3. Verify Rules Checklist
+
+- Node ID is exactly `PLATFORM`
+- Starts with `<br/>`
+- Emoji at beginning
+- Product name in ALL CAPS
+- Category/tagline included
+- Transformation statement spans multiple lines
+- Each line ends with `<br/>`
+- Ends with `<br/><br/>`
+- No HTML tags
+- Proper quote and bracket closure `"]`
+
+Store platform_node and transformation_statement.
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Format Target Groups | [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. Platform node must be formatted before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Platform node formatted with all required elements
+- Transformation statement emotionally compelling and multi-line
+- Product name in ALL CAPS with emoji
+- Category/tagline included
+- Proper padding and closure
+- No HTML tags
+
+### ❌ SYSTEM FAILURE:
+- Wrong node ID (not PLATFORM)
+- Missing transformation statement
+- Single-line transformation
+- HTML tags in node
+- Missing category/tagline
+- Improper closure
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-08d-mermaid-target-groups.md

@@ -0,0 +1,140 @@
+---
+name: 'step-08d-mermaid-target-groups'
+description: 'Format target group nodes with emojis, priority levels, and profile traits'
+
+# File References
+nextStepFile: './step-08e-mermaid-driving-forces.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 27: Format Target Group Nodes
+
+## STEP GOAL:
+
+Create persona nodes with emojis, ALL CAPS names, priority levels (PRIMARY/SECONDARY/TERTIARY TARGET), and 3-4 key profile traits.
+
+## 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 professional diagram nodes
+- ✅ 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 target group nodes with consistent structure
+- 🚫 FORBIDDEN to use different emojis for TG and its corresponding DF node
+- 💬 Approach: Consistent formatting with proper padding
+- 📋 Use same emoji for TG node and its corresponding DF node (critical!)
+- 📋 Priority levels in ALL CAPS: PRIMARY TARGET, SECONDARY TARGET, etc.
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Format each persona as a properly structured TG node
+- 💾 Store target_group_nodes, persona_emojis (for DF matching), persona_count
+- 📖 Record emoji assignments for use in DF nodes
+- 🚫 Do not forget to record persona emojis for DF matching
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Personas from workshops, platform node from step-08c
+- Focus: Formatting TG nodes for Mermaid diagram
+- Limits: Follow exact template pattern, record emojis for DF matching
+- Dependencies: Requires platform node from step-08c
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Format Each Target Group Node
+
+**Node Structure Template:**
+```
+TGX["<br/>EMOJI PERSONA NAME<br/>PRIORITY LEVEL<br/><br/>Profile trait 1<br/>Profile trait 2<br/>Profile trait 3<br/><br/>"]
+```
+
+**Required elements per node:**
+1. Start with `<br/>` (top padding)
+2. Emoji + Persona name in ALL CAPS
+3. Priority level (PRIMARY TARGET, SECONDARY TARGET, etc.) in ALL CAPS
+4. Blank line (`<br/><br/>`)
+5. 3-4 key profile traits (concise, one line each with `<br/>`)
+6. End with `<br/><br/>` (bottom padding)
+
+### 2. Choose and Record Persona Emojis
+
+**Important:** Use same emoji for both TG node and corresponding DF node.
+
+Common persona emojis:
+- Target/Strategic: target emoji
+- Business/Leadership: briefcase emoji
+- Technical/Developer: computer emoji
+- Team/Group: people emoji
+- Creative/Designer: art emoji
+- User/Customer: phone emoji
+
+Record emoji assignments: TG0 emoji -> DF0, TG1 emoji -> DF1, etc.
+
+### 3. Verify Rules Checklist
+
+- Node ID follows pattern TG0, TG1, TG2
+- Starts with `<br/>`
+- Emoji matches persona type
+- Persona name in ALL CAPS
+- Priority level in ALL CAPS
+- Blank line after priority (`<br/><br/>`)
+- 3-4 profile traits
+- Each trait ends with `<br/>`
+- Ends with `<br/><br/>`
+- No HTML tags
+- Proper quote and bracket closure `"]`
+
+Store target_group_nodes, persona_emojis, persona_count.
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Format Driving Forces | [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 TG nodes must be formatted and emojis recorded before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All persona nodes formatted following template
+- Emojis selected and RECORDED for DF matching
+- Priority levels in ALL CAPS
+- 3-4 profile traits per node
+- Proper padding and closure
+- No HTML tags
+
+### ❌ SYSTEM FAILURE:
+- Not recording emojis for DF matching
+- Missing priority levels
+- Traits not concise
+- HTML tags in nodes
+- Inconsistent formatting
+- Wrong node ID pattern
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-08e-mermaid-driving-forces.md

@@ -0,0 +1,154 @@
+---
+name: 'step-08e-mermaid-driving-forces'
+description: 'Format driving forces nodes with wants and fears for each persona'
+
+# File References
+nextStepFile: './step-08f-mermaid-connections.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 28: Format Driving Forces Nodes
+
+## STEP GOAL:
+
+Create driving forces nodes with WANTS (checkmark) and FEARS (X) sections for each persona, using the SAME emoji as the corresponding TG node and exactly 3 drivers per category.
+
+## 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 professional diagram nodes
+- ✅ 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 DF nodes with exactly 3 wants and 3 fears
+- 🚫 FORBIDDEN to use different emoji than corresponding TG node or add emojis to WANTS/FEARS headers
+- 💬 Approach: Systematic creation matching TG node emojis exactly
+- 📋 Exactly 3 positive drivers with checkmark, exactly 3 negative with X
+- 📋 WANTS and FEARS headers are plain text (no emojis, ALL CAPS)
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Format each DF node with matching TG emoji
+- 💾 Store driving_forces_nodes, verify emoji matching
+- 📖 Follow exact node structure with WANTS and FEARS sections
+- 🚫 Do not deviate from exactly 3 drivers per category
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Driving forces from workshops, persona_emojis from step-08d
+- Focus: Formatting DF nodes for Mermaid diagram
+- Limits: MUST use same emoji as corresponding TG node
+- Dependencies: Requires TG nodes and persona_emojis from step-08d
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Format Each Driving Forces Node
+
+**Node Structure Template:**
+```
+DFX["<br/>EMOJI PERSONA'S DRIVERS<br/><br/>WANTS<br/>checkmark Positive driver 1<br/>checkmark Positive driver 2<br/>checkmark Positive driver 3<br/><br/>FEARS<br/>X Negative driver 1<br/>X Negative driver 2<br/>X Negative driver 3<br/><br/>"]
+```
+
+**Required elements per node:**
+1. Start with `<br/>` (top padding)
+2. **Same emoji as corresponding TG node** + "PERSONA'S DRIVERS" in ALL CAPS
+3. Blank line (`<br/><br/>`)
+4. "WANTS" header (no emoji, ALL CAPS)
+5. Exactly 3 positive drivers with checkmark emoji
+6. Blank line (`<br/><br/>`)
+7. "FEARS" header (no emoji, ALL CAPS)
+8. Exactly 3 negative drivers with X emoji
+9. End with `<br/><br/>` (bottom padding)
+
+### 2. Critical Emoji Rules
+
+**Matching emoji:**
+- DF node MUST use same emoji as corresponding TG node
+- TG0 emoji -> DF0 (same emoji)
+- TG1 emoji -> DF1 (same emoji)
+- TG2 emoji -> DF2 (same emoji)
+
+**Driver emojis:**
+- Checkmark for all positive drivers
+- X for all negative drivers
+- NO emojis on "WANTS" and "FEARS" headers
+
+### 3. Driver Formatting
+
+Each driver:
+- Starts with emoji (checkmark or X)
+- One space after emoji
+- Concise text (keep under 40 characters if possible)
+- Ends with `<br/>`
+
+**Exactly 3 drivers per category** - no more, no less.
+
+### 4. Verify Rules Checklist
+
+- Node ID follows pattern DF0, DF1, DF2 (matching TG nodes)
+- Starts with `<br/>`
+- Emoji matches corresponding TG node emoji
+- "PERSONA'S DRIVERS" in ALL CAPS
+- Blank line after title
+- "WANTS" header (no emoji, ALL CAPS)
+- Exactly 3 positive drivers with checkmark
+- Blank line between sections
+- "FEARS" header (no emoji, ALL CAPS)
+- Exactly 3 negative drivers with X
+- Ends with `<br/><br/>`
+- No HTML tags
+- Proper quote and bracket closure `"]`
+
+Store driving_forces_nodes and verify emoji matching with TG nodes.
+
+### 5. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Create Connections | [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 DF nodes must be formatted with matching emojis before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All DF nodes formatted with matching TG emojis
+- Exactly 3 positive and 3 negative drivers per persona
+- WANTS and FEARS headers plain text (no emojis)
+- Drivers concise (under 40 chars)
+- Proper padding and spacing
+- Emoji matching verified
+
+### ❌ SYSTEM FAILURE:
+- Different emoji than corresponding TG node
+- More or fewer than 3 drivers per category
+- Emojis on WANTS/FEARS headers
+- Missing blank line between sections
+- Drivers too long
+- Emoji matching not verified
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-08f-mermaid-connections.md

@@ -0,0 +1,119 @@
+---
+name: 'step-08f-mermaid-connections'
+description: 'Create connections between all nodes in the proper flow pattern'
+
+# File References
+nextStepFile: './step-08g-mermaid-styling.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 29: Create Connections
+
+## STEP GOAL:
+
+Connect all nodes in the proper flow pattern: Business Goals -> Platform -> Target Groups -> Driving Forces, using simple arrows with proper section comments.
+
+## 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 professional diagram connections
+- ✅ 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 connecting all nodes with simple arrows
+- 🚫 FORBIDDEN to use fancy arrow styling or skip any connection
+- 💬 Approach: Systematic connection creation with verification
+- 📋 Use simple `-->` arrows only
+- 📋 TG-to-DF connections must match (TG0->DF0, TG1->DF1, etc.)
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Create all connections following the pattern
+- 💾 Store connections and connection_count
+- 📖 Include section comments for each connection group
+- 🚫 Do not use fancy arrow styling
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All node IDs from previous steps
+- Focus: Creating connections between all nodes
+- Limits: Simple arrows only, matching TG-DF pairs
+- Dependencies: Requires all nodes formatted
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Business Goals to Platform
+
+Connect all BG nodes to PLATFORM with simple `-->` arrows.
+
+### 2. Platform to Target Groups
+
+Connect PLATFORM to all TG nodes with simple `-->` arrows.
+
+### 3. Target Groups to Driving Forces
+
+Connect each TG to its corresponding DF (matching IDs: TG0->DF0, TG1->DF1, etc.).
+
+### 4. Verify Connection Count
+
+**Count check:**
+- BG connections = number of business goals
+- Platform-to-TG connections = number of personas
+- TG-to-DF connections = number of personas
+
+Example for 3 personas: 3 + 3 + 3 = 9 total connections.
+
+Store connections and connection_count.
+
+### 5. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Apply Styling | [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 connections must be created and verified before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All BG nodes connected to PLATFORM
+- PLATFORM connected to all TG nodes
+- Each TG connected to matching DF
+- Simple `-->` arrows used throughout
+- Section comments included
+- Connection count verified
+- No broken connections
+
+### ❌ SYSTEM FAILURE:
+- Missing connections
+- Fancy arrow styling
+- TG-DF mismatch (TG0->DF1 etc.)
+- Missing section comments
+- Broken connections
+- Wrong connection count
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-08g-mermaid-styling.md

@@ -0,0 +1,151 @@
+---
+name: 'step-08g-mermaid-styling'
+description: 'Apply professional light gray styling with dark text to all diagram nodes'
+
+# File References
+nextStepFile: './step-08h-mermaid-quality.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 30: Apply Styling
+
+## STEP GOAL:
+
+Apply professional light gray styling with dark text to all nodes using four style classes: businessGoal, platform, targetGroup, and drivingForces, with exact color specifications.
+
+## 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 - applying professional visual styling
+- ✅ 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 applying EXACT color specifications
+- 🚫 FORBIDDEN to modify colors or create custom color schemes
+- 💬 Approach: Apply exact specifications, no creative liberties with colors
+- 📋 Use these EXACT colors - do not modify
+- 📋 Platform gets 3px border (thicker than others at 2px)
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Define all four classDef statements with exact colors
+- 💾 Store styling_definitions, styling_applications, complete_diagram
+- 📖 Apply classes to correct node groups
+- 🚫 Do not modify the color specifications
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All nodes and connections from previous steps
+- Focus: Applying consistent professional styling
+- Limits: Use EXACT colors specified - no variations
+- Dependencies: Requires all nodes and connections created
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Define Style Classes
+
+Add these EXACT class definitions:
+
+```css
+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
+```
+
+**Color Specifications:**
+
+**Background fills:**
+- `#f3f4f6` - Light gray (business goals, driving forces)
+- `#e5e7eb` - Medium gray (platform only)
+- `#f9fafb` - Near white (target groups)
+
+**Text colors:**
+- `#1f2937` - Dark gray (most nodes)
+- `#111827` - Darker gray (platform only)
+
+**Border colors:**
+- `#d1d5db` - Light gray border (most nodes)
+- `#9ca3af` - Medium gray border (platform only)
+
+**Border widths:**
+- `2px` - Standard (business goals, target groups, driving forces)
+- `3px` - Thick (platform only)
+
+### 2. Apply Classes to Nodes
+
+Format:
+```
+class BG0,BG1,BG2 businessGoal
+class PLATFORM platform
+class TG0,TG1,TG2 targetGroup
+class DF0,DF1,DF2 drivingForces
+```
+
+Adjust node counts to match actual diagram.
+
+### 3. Verify Rules Checklist
+
+- All four classDef statements included
+- Colors EXACTLY match specification
+- Platform has 3px border
+- All BG nodes assigned to businessGoal
+- PLATFORM assigned to platform
+- All TG nodes assigned to targetGroup
+- All DF nodes assigned to drivingForces
+- Node counts match actual diagram
+- Comment header included
+
+Store styling_definitions, styling_applications, and complete_diagram.
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Quality Check | [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. Styling must be applied correctly before quality check.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All four classDef statements with exact colors
+- Platform thicker border (3px vs 2px)
+- All nodes assigned to correct classes
+- Node counts match actual diagram
+- Professional, subtle, print-friendly appearance
+- Complete diagram assembled
+
+### ❌ SYSTEM FAILURE:
+- Wrong color codes
+- Missing classDef statements
+- Nodes not assigned to classes
+- Wrong border widths
+- Node count mismatch
+- Custom colors used instead of specified
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-08h-mermaid-quality.md

@@ -0,0 +1,165 @@
+---
+name: 'step-08h-mermaid-quality'
+description: 'Verify Mermaid diagram meets all quality standards before finalization'
+
+# File References
+nextStepFile: './step-09a-finalize-hub.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 31: Mermaid Diagram Quality Check
+
+## STEP GOAL:
+
+Verify the complete Mermaid diagram meets all quality standards across configuration, node formatting, emoji usage, connections, styling, content quality, and syntax before finalization.
+
+## 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 - ensuring diagram quality
+- ✅ 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 comprehensive quality verification of complete diagram
+- 🚫 FORBIDDEN to approve with known issues or skip any quality dimension
+- 💬 Approach: Systematic checklist verification, fix issues before approval
+- 📋 Check: configuration, nodes, emojis, driving forces, connections, styling, content, syntax
+- 📋 If issues found, fix and re-verify
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Run through complete quality checklist
+- 💾 Fix any issues found during verification
+- 📖 Present verification results
+- 🚫 Do not approve with unresolved issues
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Complete assembled diagram
+- Focus: Quality verification across all dimensions
+- Limits: Must check ALL dimensions - no shortcuts
+- Dependencies: Requires complete diagram from step-08g
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Configuration & Structure Check
+
+- Mermaid config includes custom font (Inter, system-ui, sans-serif)
+- fontSize set to 14px
+- Flowchart direction is LR
+- Section comments present
+
+### 2. Node Formatting Check
+
+- All nodes start with `<br/>` and end with `<br/><br/>`
+- All titles in ALL CAPS
+- All line breaks use `<br/>`
+- No HTML tags in any node
+- All nodes properly closed with `"]`
+
+### 3. Emoji Usage Check
+
+- Each persona has matching emoji in both TG and DF nodes
+- Business goals have appropriate emojis
+- Platform has appropriate emoji
+- WANTS and FEARS headers have NO emojis
+- Positive drivers all have checkmark
+- Negative drivers all have X
+
+### 4. Driving Forces Check
+
+- Exactly 3 positive drivers per persona
+- Exactly 3 negative drivers per persona
+- Section headers are WANTS and FEARS (no emojis, ALL CAPS)
+- Blank line between sections
+- DF emoji matches corresponding TG emoji
+
+### 5. Connections Check
+
+- All BG nodes connect to PLATFORM
+- PLATFORM connects to all TG nodes
+- Each TG connects to matching DF
+- Simple arrows used
+- Connection comments present
+- No broken connections
+
+### 6. Styling Check
+
+- Light gray styling with dark text applied
+- All four classDef statements present
+- Colors EXACTLY match specification
+- Platform has thicker border (3px vs 2px)
+- All nodes assigned to correct classes
+- Node counts match actual diagram
+
+### 7. Content & Syntax Check
+
+- Business goals have 3-5 key points
+- Platform includes transformation statement
+- Target groups have 3-4 profile traits
+- Drivers concise (under 40 characters)
+- No syntax errors
+- All brackets and quotes properly closed
+- Node IDs follow patterns
+
+### 8. Fix Issues If Found
+
+If any issues found: Fix identified issues, re-run quality check, repeat until all checks pass.
+
+### 9. Present Results
+
+If all checks pass: "Quality verified - Diagram ready for publication"
+
+The professional Mermaid diagram can now be inserted into 00-Trigger-Map-Poster.md, presentations, documentation, and reports.
+
+### 10. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Finalize Hub | [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 quality checks must pass before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All quality dimensions checked
+- All issues found were fixed
+- Re-verification passed after fixes
+- Diagram renders without errors
+- Professional, clean, readable appearance
+- All specifications exactly met
+
+### ❌ SYSTEM FAILURE:
+- Skipping quality dimensions
+- Approving with known issues
+- Not fixing found issues
+- Not re-verifying after fixes
+- Diagram has syntax errors
+- Colors don't match specification
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-09a-finalize-hub.md

@@ -0,0 +1,124 @@
+---
+name: 'step-09a-finalize-hub'
+description: 'Generate all Trigger Map documentation starting from the hub document'
+
+# File References
+nextStepFile: './step-09b-add-cross-references.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 32: Generate All Trigger Map Documentation
+
+## STEP GOAL:
+
+Generate the complete trigger map documentation structure including the hub with Mermaid diagram, business goals, persona documents, key insights, and feature impact (if applicable) by orchestrating the document generation workflow.
+
+## 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 orchestrating complete document generation
+- 🚫 FORBIDDEN to skip any required document
+- 💬 Approach: Systematic generation following the standard structure
+- 📋 Generate: 00-trigger-map.md (hub), 01-Business-Goals.md, persona docs, 05-Key-Insights.md
+- 📋 Include 06-Feature-Impact.md if feature workshop was run
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Execute document generation by loading step-07a-generate-hub.md workflow
+- 💾 All documents saved to {output_folder}/B-Trigger-Map/
+- 📖 Follow standard trigger map structure
+- 🚫 Do not skip any required document
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All workshop outputs, Mermaid diagram
+- Focus: Complete documentation generation
+- Limits: Follow standard structure exactly
+- Dependencies: Requires all workshops completed and diagram generated
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Execute Document Generation
+
+Load and execute the document generation sequence starting with step-07a-generate-hub.md.
+
+This will create all documents following the standard trigger map structure:
+- `00-trigger-map.md` (Hub with Mermaid diagram)
+- `01-Business-Goals.md`
+- `02-XX-Persona.md` (for each persona)
+- `05-Key-Insights.md`
+- `06-Feature-Impact.md` (if workshop was run)
+
+### 2. Confirm Generation Complete (Completeness Gate)
+
+Verify ALL required documents have been generated:
+
+**Mandatory files in `{output_folder}/B-Trigger-Map/`:**
+- [ ] `00-trigger-map.md` — Hub document with Mermaid diagram
+- [ ] `01-Business-Goals.md` — Vision + SMART objectives
+- [ ] One persona document per target group (`02-XX.md`, `03-XX.md`, etc.)
+- [ ] `05-Key-Insights.md` — Strategic insights summary
+
+**Conditional files:**
+- [ ] `06-Feature-Impact.md` — Only if feature impact workshop was completed
+
+**Validation rules:**
+- Each file must be non-empty (contains actual content, not just headers)
+- Hub document must contain a Mermaid code block
+- Persona count must match the number of target groups from workshops
+
+**If any file is missing:** Generate the missing file before proceeding. Do NOT skip.
+
+### 3. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Add Cross-References | [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 documents must be generated before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All required documents generated
+- Documents saved to correct locations
+- Standard structure followed
+- Hub document includes Mermaid diagram
+- Feature Impact included if workshop was run
+
+### ❌ SYSTEM FAILURE:
+- Missing required documents
+- Documents saved to wrong locations
+- Not following standard structure
+- Hub missing Mermaid diagram
+- Feature Impact missing when workshop was completed
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-09b-add-cross-references.md

@@ -0,0 +1,108 @@
+---
+name: 'step-09b-add-cross-references'
+description: 'Verify and add navigation links to all trigger map documents'
+
+# File References
+nextStepFile: './step-09c-quality-check.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 33: Add Cross-References
+
+## STEP GOAL:
+
+Verify and add bidirectional navigation links to ALL trigger map documents, ensuring every document links back to the hub and forward to related documents.
+
+## 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 - ensuring document connectivity
+- ✅ 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 adding bidirectional navigation links
+- 🚫 FORBIDDEN to leave any document without a link back to hub
+- 💬 Approach: Systematic link verification and addition
+- 📋 Navigation must be bidirectional (hub->doc and doc->hub)
+- 📋 All persona docs should link to each other
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Add navigation links to every document
+- 💾 Update all documents with cross-references
+- 📖 Verify all links are bidirectional
+- 🚫 Do not leave any document isolated
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All generated documents
+- Focus: Cross-reference links between documents
+- Limits: Every document must link to hub and related docs
+- Dependencies: Requires all documents generated
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Add Links to Each Document
+
+In each document, add:
+- Back link to 00-trigger-map.md
+- Forward link to next document (if sequential)
+- Related documents section at bottom
+
+### 2. Verify Navigation
+
+Verify:
+- All persona docs link to each other
+- All docs link back to hub
+- Hub links to all docs
+- Navigation is bidirectional
+
+### 3. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Quality Check | [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 cross-references must be added before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Every document has back link to hub
+- Hub links to all sub-documents
+- Persona docs link to each other
+- Navigation is bidirectional
+- No isolated documents
+
+### ❌ SYSTEM FAILURE:
+- Documents without hub links
+- Hub missing links to documents
+- One-way navigation only
+- Isolated documents
+- Broken links
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-09c-quality-check.md

@@ -0,0 +1,110 @@
+---
+name: 'step-09c-quality-check'
+description: 'Run final quality check on all trigger map documents'
+
+# File References
+nextStepFile: './step-09d-create-handover-package.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 34: Final Quality Check
+
+## STEP GOAL:
+
+Run final quality verification on all trigger map documents to ensure completeness, consistency, correct cross-references, and proper Mermaid diagram rendering.
+
+## 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 - verifying completeness
+- ✅ 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 comprehensive final quality verification
+- 🚫 FORBIDDEN to approve with known issues
+- 💬 Approach: Systematic verification checklist
+- 📋 Check: document existence, Mermaid rendering, cross-references, terminology, driving forces, Feature Impact
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Verify all quality dimensions
+- 💾 Fix any issues found
+- 📖 Present verification results
+- 🚫 Do not approve with unresolved issues
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All generated documents with cross-references
+- Focus: Final quality verification
+- Limits: Must check all dimensions
+- Dependencies: Requires cross-references added
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Run Verification
+
+Ensure:
+- All documents exist
+- Mermaid diagram renders correctly
+- Cross-references work
+- Consistent terminology
+- No broken links
+- All personas have driving forces
+- Feature Impact document exists (if workshop was run)
+
+### 2. Fix Any Issues
+
+If issues found, identify and fix before proceeding.
+
+### 3. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Handover Package | [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 quality checks must pass before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All documents verified as existing
+- Mermaid diagram renders correctly
+- Cross-references all working
+- Terminology consistent across documents
+- No broken links
+- All personas have complete driving forces
+- Feature Impact present if workshop completed
+
+### ❌ SYSTEM FAILURE:
+- Missing documents
+- Broken Mermaid diagram
+- Broken cross-references
+- Inconsistent terminology
+- Missing driving forces
+- Approving with known issues
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-09d-create-handover-package.md

@@ -0,0 +1,134 @@
+---
+name: 'step-09d-create-handover-package'
+description: 'Create handover summary package for UX Design phase'
+
+# File References
+nextStepFile: './step-09e-update-design-log.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 35: Create Handover Package
+
+## STEP GOAL:
+
+Create a summary handover package for the UX Designer (Freya) with primary focus, must-address drivers, feature priorities, and design implications.
+
+## 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 - preparing handover for UX Design phase
+- ✅ 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 clear, actionable handover for UX Designer
+- 🚫 FORBIDDEN to omit primary focus or must-address drivers
+- 💬 Approach: Clear, structured handover with all critical information
+- 📋 Include: documentation structure, primary focus, must-address drivers, feature priorities, design implications
+- 📋 Show complete file tree of created documents
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Present comprehensive handover summary
+- 💾 No new files to save - summary presentation
+- 📖 Include all critical information for UX Designer
+- 🚫 Do not skip any handover component
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All verified documents, quality check results
+- Focus: Handover summary for UX Design phase
+- Limits: Focus on what UX Designer needs to know
+- Dependencies: Requires quality check passed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Present Completion Summary
+
+Output:
+"**Trigger Map Phase Complete!**
+
+**All Documentation Created:**
+
+```
+B-Trigger-Map/
+  00-trigger-map.md          - Start here: Visual overview
+  01-Business-Goals.md
+  02-{{primary_persona}}.md
+  03-{{secondary_persona}}.md
+  04-{{tertiary_persona}}.md  (if exists)
+  05-Key-Insights.md
+  06-Feature-Impact.md        (if completed)
+```"
+
+### 2. Present Handover Summary
+
+"**Handover Summary for UX Design:**
+
+**Primary Focus:**
+- **Who:** {{primary_persona_name}} ({{primary_persona_role}})
+- **Transformation:** {{transformation_summary}}
+
+**Must Address:**
+(top 3 positive drivers with checkmarks)
+
+**Must Avoid:**
+(top 3 negative drivers with X marks)
+
+**Feature Priority:** (if available, top 3 features; otherwise note not yet analyzed)
+
+**Design Implications:**
+(3 key design implications)
+
+**Ready for Phase 4: UX Design**"
+
+### 3. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Update Design Log | [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. Handover must be presented before proceeding to design log update.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Complete file tree shown
+- Primary focus clearly stated (who, transformation)
+- Must-address positive drivers listed
+- Must-avoid negative drivers listed
+- Feature priorities shown (if available)
+- Design implications included
+- Clear readiness signal for Phase 4
+
+### ❌ SYSTEM FAILURE:
+- Missing file tree
+- Missing primary focus
+- Missing must-address drivers
+- Incomplete handover information
+- Not indicating Phase 4 readiness
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-09e-update-design-log.md

@@ -0,0 +1,149 @@
+---
+name: 'step-09e-update-design-log'
+description: 'Document Phase 2 completion in the project design log'
+
+# File References
+nextStepFile: './step-09f-provide-activation.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 36: Update Design Log
+
+## STEP GOAL:
+
+Document Phase 2: Trigger Mapping completion in the project design log, listing all artifacts created, key decisions made, and suggesting 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 - documenting completion for project memory
+- ✅ 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 documenting completion in design log
+- 🚫 FORBIDDEN to use generic statements or "etc." - list every artifact
+- 💬 Approach: Specific, detailed progress entry
+- 📋 List every artifact file - do not summarize with "etc."
+- 📋 Record key decisions if any were made
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Read current design log and append progress entry
+- 💾 Update {output_folder}/_progress/00-design-log.md
+- 📖 List all artifacts and key decisions specifically
+- 🚫 Do not overwrite existing entries
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All completed artifacts, key decisions from workshops
+- Focus: Design log update with specific details
+- Limits: Append only - do not overwrite existing entries
+- Dependencies: Requires handover package created
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Read Current Log
+
+Read `{output_folder}/_progress/00-design-log.md` to understand existing entries and format.
+
+### 2. Append Progress Entry
+
+Add under the `## Progress` section (after the last entry):
+
+```
+### [date] - Phase 2: Trigger Mapping Complete
+
+**Agent:** Saga (Trigger Mapping)
+**Personas:** [N] ([primary name], [secondary name], [tertiary name if exists])
+**Business Goals:** [N]
+
+**Artifacts Created:**
+- B-Trigger-Map/00-trigger-map.md - Visual overview
+- B-Trigger-Map/01-Business-Goals.md
+- B-Trigger-Map/02-[primary].md
+- B-Trigger-Map/03-[secondary].md
+- [list ALL files created]
+
+**Summary:** [2-3 sentences: personas identified, key strategic insights, feature priorities established]
+
+**Next:** Phase 3 - UX Scenarios
+```
+
+**Rules:**
+- List every artifact file - do not summarize with "etc."
+- Summary must mention specific insights, not generic statements
+- Use the actual date, not a placeholder
+
+### 3. Record Key Decisions
+
+Add rows to the `## Key Decisions` table for any significant choices made during Phase 2:
+
+```
+| [date] | [decision] | Phase 2: Trigger Mapping | Saga + [user_name] |
+```
+
+Examples: persona prioritization choices, business goal ranking, feature impact priorities, workshop mode selection.
+
+If no significant decisions were made, skip this section.
+
+### 4. Verify
+
+- Progress entry appended (not overwriting existing entries)
+- All artifact files listed
+- Summary is specific, not generic
+- Key decisions recorded (if any)
+
+Output: "Design log updated. Phase 2: Trigger Mapping documented in _progress/00-design-log.md"
+
+### 5. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to UX Design Activation | [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. Design log must be updated before proceeding. Do NOT skip ahead.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Design log read before updating
+- Progress entry appended (not overwriting)
+- All artifact files listed individually
+- Summary is specific with real insights
+- Key decisions recorded where applicable
+- Actual date used
+- Design log saved
+
+### ❌ SYSTEM FAILURE:
+- Overwriting existing entries
+- Using "etc." instead of listing all files
+- Generic summary statements
+- Missing artifact files in list
+- Using placeholder dates
+- Not reading existing log first
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-c/step-09f-provide-activation.md

@@ -0,0 +1,135 @@
+---
+name: 'step-09f-provide-activation'
+description: 'Provide UX Design activation instructions and complete Phase 2'
+
+# File References
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 37: Provide UX Design Activation
+
+## STEP GOAL:
+
+Provide activation instructions for the UX Designer (Freya) to begin UX Design, offer alternative paths, and complete Phase 2: Trigger Mapping.
+
+## 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 - transitioning to UX Design phase
+- ✅ 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 providing clear activation instructions and alternative paths
+- 🚫 FORBIDDEN to auto-activate next phase - user must choose
+- 💬 Approach: Clear instructions with all options presented
+- 📋 Provide UX Designer activation instructions
+- 📋 Offer alternative paths (Platform Requirements, Feature Impact)
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Present activation instructions for UX Designer
+- 💾 No new files to save
+- 📖 Offer alternative paths clearly
+- 🚫 Do not auto-proceed to next phase
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Complete Phase 2 outputs, design log updated
+- Focus: Transition guidance to next phase
+- Limits: Provide instructions only - do not activate next phase
+- Dependencies: Requires design log updated
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Present Activation Instructions
+
+Output:
+"**Ready to Start UX Design!**
+
+**To activate the UX Designer (Freya):**
+
+**In a NEW conversation** (recommended for fresh context), load the UX agent with:
+
+```
+Load: getting-started/agent-activation/wds-freya-ux.md
+
+Project: {{project_name}}
+Phase: UX Design (Phase 4)
+Starting from: Trigger Map completion
+
+Context: Read B-Trigger-Map/ folder for strategic foundation.
+```
+
+---
+
+**What the UX Designer Will Do:**
+
+1. **Review Trigger Map** - Understand personas, goals, and priorities
+2. **Create User Scenarios** - Map key user journeys
+3. **Design Flows** - Create interaction designs for scenarios
+4. **Write Conceptual Specs** - Document WHAT + WHY + WHAT NOT TO DO
+5. **Incremental Handovers** - Deliver designs for implementation as they're ready
+
+**Continuous Delivery:**
+The UX Designer can hand off completed scenarios/pages to development while continuing to design more features. No need to wait for 'all design done.'
+
+---
+
+**Alternative Paths:**
+
+**Run Feature Impact First?**
+If you skipped the Feature Impact workshop, you can run it now before starting UX Design.
+
+---
+
+**Your Trigger Mapping is complete!** All strategic foundation is documented and ready for the next phase."
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+- 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
+
+This is the LAST step in the Phase 2 workflow. ONLY the [M] Return option is available. Phase 2: Trigger Mapping is complete.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Clear activation instructions provided for UX Designer
+- Alternative paths presented (Platform Requirements, Feature Impact)
+- Continuous delivery approach explained
+- User understands all options for next steps
+- Phase 2 completion clearly communicated
+- Only [M] Return option available (last step)
+
+### ❌ SYSTEM FAILURE:
+- Missing activation instructions
+- Auto-activating next phase
+- Not presenting alternative paths
+- Not explaining continuous delivery
+- Offering [C] Continue when there is no next step
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-v/step-01-target-group-coverage.md

@@ -0,0 +1,124 @@
+---
+name: 'step-01-target-group-coverage'
+description: 'Validate all target groups have complete driving forces'
+
+# File References
+nextStepFile: './step-02-prioritization-integrity.md'
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Step 1: Target Group Coverage Validation
+
+## STEP GOAL:
+
+Verify all target groups have complete driving forces (positive and negative), Product Promises/Answers, priority levels, and behavioral descriptions.
+
+## 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic alignment
+- ✅ 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 validation methodology expertise, user brings product knowledge
+- ✅ Maintain thorough and quality-focused tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on verifying completeness of target group coverage
+- 🚫 FORBIDDEN to skip any persona or approve incomplete driving forces
+- 💬 Approach: Systematic checklist verification per persona
+- 📋 Each persona must have: 3+ positive forces, 3+ negative forces, Product Promises/Answers, priority level, behavioral description
+- 📋 Generate coverage report table
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load and check all persona documents systematically
+- 💾 Store coverage report for final validation summary
+- 📖 Generate tabular report with status per persona
+- 🚫 Do not skip any check dimension
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All trigger map documents in {output_folder}/B-Trigger-Map/
+- Focus: Target group and driving forces completeness
+- Limits: Validation only - do not modify documents
+- Dependencies: Requires trigger map documents to exist
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Load Trigger Map Hub
+
+Read `{output_folder}/B-Trigger-Map/00-trigger-map.md` (or trigger-map.md) and extract all target groups.
+
+### 2. Load Persona Documents
+
+Read all persona files from `{output_folder}/B-Trigger-Map/`.
+
+### 3. Verify Per Group
+
+For each target group/persona:
+- Has at least 3 positive driving forces (wants)
+- Has at least 3 negative driving forces (fears)
+- Each driving force has a specific Product Promise
+- Each driving force has a specific Product Answer
+- Priority level assigned (Primary/Secondary/Tertiary)
+- Description is behavioral, not just demographic
+
+### 4. Generate Report
+
+```
+## Target Group Coverage Report
+
+| Persona | Priority | + Forces | - Forces | Promises | Answers | Status |
+|---------|----------|----------|----------|----------|---------|--------|
+| [Name] | P1 | [N] | [N] | [N]/[N] | [N]/[N] | pass/warning/fail |
+
+**Coverage:** [X]/[Total] personas complete
+**Gaps:** [list]
+```
+
+### 5. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Prioritization Integrity | [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. Coverage report must be generated before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All personas checked against all dimensions
+- Coverage report generated with clear status per persona
+- Gaps identified and listed
+- No persona skipped
+- Report shows exact counts for forces, promises, answers
+
+### ❌ SYSTEM FAILURE:
+- Skipping personas in verification
+- Not checking all dimensions per persona
+- Not generating tabular report
+- Missing gap identification
+- Approving without complete verification
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-v/step-02-prioritization-integrity.md

@@ -0,0 +1,129 @@
+---
+name: 'step-02-prioritization-integrity'
+description: 'Validate prioritization rankings are internally consistent'
+
+# File References
+nextStepFile: './step-03-persona-consistency.md'
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Step 2: Prioritization Integrity Validation
+
+## STEP GOAL:
+
+Verify prioritization rankings match stated rationale and are internally consistent: exactly one Primary persona, reasonable tier distribution, documented rationale, and aligned 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic alignment
+- ✅ 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 validation methodology expertise, user brings product knowledge
+- ✅ Maintain thorough and quality-focused tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on priority tier consistency and rationale
+- 🚫 FORBIDDEN to approve without checking focus statement alignment
+- 💬 Approach: Systematic verification of priority logic
+- 📋 Check: exactly one P1, distribution, rationale, force rankings, focus statement
+- 📋 Identify duplicate or near-duplicate driving forces
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Verify priority tier logic and consistency
+- 💾 Store prioritization integrity report
+- 📖 Check driving force rankings per persona
+- 🚫 Do not skip focus statement verification
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All trigger map documents
+- Focus: Prioritization consistency and rationale
+- Limits: Validation only - flag issues, do not fix
+- Dependencies: Requires target group coverage validation completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Priority Tier Consistency
+
+Check:
+- Exactly one Primary persona (P1)
+- Reasonable distribution across tiers (not all P1)
+- Priority rationale documented (why P1 > P2 > P3)
+- Business goals reference correct personas at correct priority
+
+### 2. Driving Force Rankings
+
+For each persona:
+- Driving forces have relative importance ranking
+- Top driving forces align with business goals
+- Negative forces are genuinely opposite/complementary to positives
+- No duplicate or near-duplicate forces
+
+### 3. Focus Statement
+
+Check:
+- Focus statement exists
+- Focus statement references P1 persona
+- Focus statement aligns with business goals
+
+### 4. Generate Report
+
+```
+## Prioritization Integrity Report
+
+**Priority distribution:** P1: [N], P2: [N], P3: [N]
+**Focus statement present:** [Yes/No]
+**Consistency issues:** [N]
+
+[List any conflicts or misalignments]
+```
+
+### 5. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Persona Consistency | [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. Prioritization integrity report must be generated before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Priority tier distribution verified
+- Rationale checked for each priority decision
+- Driving force rankings verified per persona
+- Duplicate forces identified
+- Focus statement verified against P1 and business goals
+- Integrity report generated
+
+### ❌ SYSTEM FAILURE:
+- Not checking for exactly one P1
+- Not verifying focus statement
+- Missing driving force ranking check
+- Not identifying duplicates
+- Skipping rationale verification
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-v/step-03-persona-consistency.md

@@ -0,0 +1,130 @@
+---
+name: 'step-03-persona-consistency'
+description: 'Validate persona documents match trigger map data and are internally consistent'
+
+# File References
+nextStepFile: './step-04-feature-impact-alignment.md'
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Step 3: Persona Consistency Validation
+
+## STEP GOAL:
+
+Verify persona documents match trigger map hub data and are internally consistent: names match, priority levels match, driving forces align, descriptions match, all sections complete, and personas are distinct.
+
+## 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic alignment
+- ✅ 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 validation methodology expertise, user brings product knowledge
+- ✅ Maintain thorough and quality-focused tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on hub-to-document alignment and cross-persona distinctness
+- 🚫 FORBIDDEN to approve if names or priority levels mismatch between hub and persona docs
+- 💬 Approach: Systematic cross-document comparison
+- 📋 Check: name match, priority match, force match, description match, section completeness, cross-persona distinctness
+- 📋 Each persona should represent a distinct user type
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Compare hub data against each persona document
+- 💾 Store persona consistency report
+- 📖 Verify all required sections present in each document
+- 🚫 Do not skip cross-persona distinctness check
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Hub document and all persona documents
+- Focus: Cross-document consistency and completeness
+- Limits: Validation only - flag mismatches, do not fix
+- Dependencies: Requires prioritization integrity validated
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Hub to Persona Document Alignment
+
+For each persona:
+- Name matches between hub and persona document
+- Priority level matches between hub and persona document
+- Driving forces in persona doc match those in hub
+- Description in persona doc matches hub summary
+
+### 2. Persona Document Completeness
+
+Each persona document should have all required sections:
+- Name and role description
+- Behavioral profile (not just demographics)
+- Goals and motivations
+- Positive driving forces with Product Promises/Answers
+- Negative driving forces with Product Promises/Answers
+- Priority tier and rationale
+
+### 3. Cross-Persona Distinctness
+
+- Each persona represents a distinct user type
+- No significant overlap in driving forces between personas
+- Each persona has unique behavioral patterns
+
+### 4. Generate Report
+
+```
+## Persona Consistency Report
+
+| Persona | Hub Match | Complete | Distinct | Status |
+|---------|-----------|----------|----------|--------|
+| [Name] | pass/fail | [X]/[Total] sections | pass/warning | pass/warning/fail |
+
+**Consistency issues:** [list or "None"]
+```
+
+### 5. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Feature Impact Alignment | [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. Persona consistency report must be generated before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- All personas compared against hub data
+- Name and priority mismatches identified
+- Section completeness verified for each document
+- Cross-persona distinctness checked
+- Overlap in driving forces flagged
+- Consistency report generated
+
+### ❌ SYSTEM FAILURE:
+- Not comparing against hub data
+- Missing section completeness check
+- Not checking cross-persona distinctness
+- Skipping driving force comparison
+- Not generating report
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-v/step-04-feature-impact-alignment.md

@@ -0,0 +1,129 @@
+---
+name: 'step-04-feature-impact-alignment'
+description: 'Validate feature impact scores reference actual priorities'
+
+# File References
+nextStepFile: './step-05-cross-document-coherence.md'
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Step 4: Feature Impact Alignment Validation
+
+## STEP GOAL:
+
+Verify feature impact scores reference actual persona priorities and business goals (if feature impact analysis was run). If not run, note as "Feature Impact not run" and 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic alignment
+- ✅ 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 validation methodology expertise, user brings product knowledge
+- ✅ Maintain thorough and quality-focused tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on feature-persona alignment and priority tier consistency
+- 🚫 FORBIDDEN to skip this step even if Feature Impact was not run (note and proceed)
+- 💬 Approach: Systematic score verification against persona priorities
+- 📋 Check: scoring consistency, P1 alignment, business goal traceability
+- 📋 No P1-critical feature should be classified as "Defer"
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Check if feature impact analysis exists, then validate if present
+- 💾 Store feature impact alignment report
+- 📖 Verify scoring against persona priorities
+- 🚫 Do not skip - note status and proceed if not run
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Feature impact document (if exists), persona priorities
+- Focus: Feature-persona scoring alignment
+- Limits: If no feature impact, note and proceed
+- Dependencies: Requires persona consistency validated
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Check Prerequisite
+
+Check if `{output_folder}/B-Trigger-Map/feature-impact-analysis.md` (or 06-Feature-Impact.md) exists. If not, note as "Feature Impact not run" and skip to report.
+
+### 2. Feature-Persona Alignment (if exists)
+
+- All features scored against all personas
+- Scoring uses consistent scale
+- High-priority personas have higher weight in scoring
+- Must Have features serve P1 persona
+
+### 3. Priority Tier Consistency (if exists)
+
+- "Must Have" features align with P1 needs
+- "Consider" features serve P2/P3 or secondary P1 needs
+- "Defer" features are genuinely lower priority
+- No P1-critical feature classified as "Defer"
+
+### 4. Business Goal Traceability (if exists)
+
+- Each feature traces to at least one business goal
+- High-impact features serve high-priority goals
+
+### 5. Generate Report
+
+```
+## Feature Impact Alignment Report
+
+**Feature Impact status:** [Present / Not run]
+**Features scored:** [N]
+**Alignment issues:** [N]
+
+[List any misalignments between feature priority and persona/goal priority]
+```
+
+### 6. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Cross-Document Coherence | [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 impact alignment report must be generated (even if "not run") before proceeding.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Feature impact existence checked
+- If present: all scoring dimensions verified
+- If not present: clearly noted as "Not run"
+- P1-critical features not classified as Defer
+- Business goal traceability checked
+- Alignment report generated
+
+### ❌ SYSTEM FAILURE:
+- Not checking if feature impact exists
+- Skipping scoring verification when present
+- P1-critical feature allowed as "Defer"
+- Missing business goal traceability check
+- Not generating report
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/steps-v/step-05-cross-document-coherence.md

@@ -0,0 +1,156 @@
+---
+name: 'step-05-cross-document-coherence'
+description: 'Validate all trigger map documents are coherent as a set'
+
+# File References
+activityWorkflowFile: '../workflow-validate.md'
+---
+
+# Step 5: Cross-Document Coherence Validation
+
+## STEP GOAL:
+
+Verify all trigger map documents are coherent as a set - hub, personas, key insights, and feature impact tell a consistent story with matching terminology, coherent narrative, working cross-references, and accurate Mermaid diagram. Compile final validation report.
+
+## 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 a Validation specialist reviewing trigger map completeness, consistency, and strategic alignment
+- ✅ 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 validation methodology expertise, user brings product knowledge
+- ✅ Maintain thorough and quality-focused tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on cross-document coherence and final validation summary
+- 🚫 FORBIDDEN to approve if persona names differ between documents
+- 💬 Approach: Systematic cross-document comparison and final report compilation
+- 📋 Check: terminology, narrative coherence, cross-references, Mermaid diagram accuracy
+- 📋 Compile results from ALL 5 validation steps into final report
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Verify coherence across all documents as a set
+- 💾 Save final validation report to {output_folder}/B-Trigger-Map/validation-report.md
+- 📖 Compile all 5 validation step results
+- 🚫 Do not skip Mermaid diagram verification
+
+## CONTEXT BOUNDARIES:
+
+- Available context: All trigger map documents and all previous validation results
+- Focus: Cross-document coherence and final validation summary
+- Limits: This is the LAST validation step - must produce comprehensive report
+- Dependencies: Requires all previous validation steps completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Terminology Consistency
+
+- Persona names identical across all documents
+- Business goal names identical across all documents
+- Priority emojis consistent (same emoji = same meaning)
+- Driving force language consistent (same force = same wording)
+
+### 2. Narrative Coherence
+
+- Hub document accurately summarizes persona docs
+- Key insights derive from actual trigger map data (not invented)
+- Flywheel logic makes causal sense (P1 -> P2 -> P3 chain)
+- Design implications flow from insights (not generic advice)
+
+### 3. Cross-References
+
+- All documents link back to hub (00-trigger-map.md)
+- Hub links to all sub-documents
+- Navigation is bidirectional
+- No broken links
+
+### 4. Mermaid Diagram
+
+- Diagram reflects actual data (not a rough sketch)
+- All personas present in diagram
+- All business goals present in diagram
+- Connections match driving force assignments
+- Renders correctly (no syntax errors)
+
+### 5. Compile Final Validation Report
+
+Compile results from all 5 validation steps:
+
+```
+## Phase 2 Validation Report
+
+**Project:** {project_name}
+**Date:** [date]
+**Documents validated:** [N]
+
+### Results Summary
+| Check | Status | Issues |
+|-------|--------|--------|
+| Target Group Coverage | pass/warning/fail | [summary] |
+| Prioritization Integrity | pass/warning/fail | [summary] |
+| Persona Consistency | pass/warning/fail | [summary] |
+| Feature Impact Alignment | pass/warning/fail | [summary] |
+| Cross-Document Coherence | pass/warning/fail | [summary] |
+
+### Critical Issues (must fix)
+[list or "None"]
+
+### Warnings (should fix)
+[list or "None"]
+
+### Recommendations
+[list or "All clear"]
+```
+
+Save report to `{output_folder}/B-Trigger-Map/validation-report.md`
+
+### 6. Present MENU OPTIONS
+
+Display: "**Select an Option:** [M] Return to Activity Menu"
+
+#### Menu Handling Logic:
+- 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
+
+This is the LAST step in the validation workflow. ONLY the [M] Return option is available. Validation report must be saved before completing.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Terminology consistency verified across all documents
+- Narrative coherence checked
+- Cross-references verified (bidirectional)
+- Mermaid diagram verified against actual data
+- Final validation report compiled from all 5 steps
+- Report saved to correct location
+- Critical issues, warnings, and recommendations clearly listed
+- Only [M] Return option available (last step)
+
+### ❌ SYSTEM FAILURE:
+- Not checking terminology across documents
+- Not verifying Mermaid diagram accuracy
+- Not compiling results from all 5 steps
+- Not saving validation report
+- Missing critical issues in report
+- Offering [C] Continue when there is no next step
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

_bmad/wds/workflows/2-trigger-mapping/templates/feature-impact.template.md

@@ -0,0 +1,47 @@
+# 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
+
+| Rank | Feature | Score | Decision |
+| ---- | ------- | ----- | -------- |
+
+{{#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_

_bmad/wds/workflows/2-trigger-mapping/templates/persona-document.template.md

@@ -0,0 +1,485 @@
+# Persona Document Template
+
+This template provides the comprehensive structure for generating detailed persona documents from trigger map data.
+
+---
+
+## File Naming Convention
+
+```
+02-[Name]-the-[Role].md  → Primary persona
+03-[Name]-the-[Role].md  → Secondary persona
+04-[Name]-the-[Role].md  → Tertiary persona (if exists)
+```
+
+**Examples:**
+- `02-Sarah-the-Student.md`
+- `03-Marcus-the-Mentor.md`
+- `04-Emma-the-Enthusiast.md`
+
+---
+
+## Document Structure for EACH Persona
+
+### 1. Header
+
+```markdown
+# [Name] the [Role] - [Type] Persona
+
+> [Priority] target - [One-line role in flywheel]
+
+**Priority:** [PRIMARY 🎓 / SECONDARY 💼 / TERTIARY 🏠]
+**Role in Flywheel:** [How they contribute to goals]
+**Created:** [Date]
+```
+
+---
+
+### 2. Profile Summary
+
+```markdown
+## Profile Summary
+
+**[One compelling paragraph that captures the essence of this persona]**
+
+[Explain their role in the bigger picture - why they matter to the product's success]
+```
+
+---
+
+### 2a. Visual Representation
+
+```markdown
+## Visual Representation
+
+**Image Generation Prompt:**
+
+"[Detailed prompt for AI image generation - include age, gender, profession, setting, emotional state, visual style, technical details like lighting and composition]"
+
+**Example:**
+"Professional headshot photograph of a 34-year-old Scandinavian female designer, shoulder-length blonde hair, sitting at modern desk with laptop, looking contemplative and slightly stressed, natural lighting, shallow depth of field, professional business casual attire, tech startup office background, photorealistic style, 4K quality"
+
+**Prompt Components:**
+- **Demographics:** Age, gender, ethnicity, appearance
+- **Professional Context:** Role, work environment, tools/props
+- **Emotional State:** Expression that matches their driving forces
+- **Visual Style:** Photography style, illustration, realistic/stylized
+- **Technical Details:** Lighting, composition, camera angle, quality
+```
+
+---
+
+### 3. Background
+
+**For different persona types:**
+
+**Students/Employees:**
+```markdown
+## Background
+
+### Education & Career Path
+
+**University/School:** [Educational background]
+
+**Learning Journey:** [How they got their skills]
+
+**First Break:** [How they entered this field/situation]
+
+**Current Role:** [What they do now]
+
+**Career Pattern:** [Straight path or winding road?]
+```
+
+**Entrepreneurs/Business:**
+```markdown
+## Background
+
+### Business Journey
+
+**Company Role:** [Position and history]
+
+**Experience Level:** [Seasoned or new?]
+
+**Technical Background:** [Their relationship with tech/tools]
+
+**Management Style:** [How they lead]
+```
+
+---
+
+### 4. Current Situation
+
+```markdown
+## Current Situation
+
+### Professional Reality [or Business Context / Daily Life]
+
+**The Daily Struggle:**
+- [Challenge 1]
+- [Challenge 2]
+- [Key pain point]
+- [Overwhelming aspect]
+
+**Skills & Tools:**
+- [What they know]
+- [What they use]
+- [Skill gaps]
+- [Learning attitude]
+
+**The [Specific] Gap:**
+- [Core challenge description]
+- [Why it matters]
+- [What's blocking them]
+- [What they need]
+```
+
+---
+
+### 5. Psychological Profile
+
+```markdown
+## Psychological Profile
+
+### Personality & Motivations
+
+**Core Identity:**
+- [Key trait 1]
+- [Key trait 2]
+- [Deep motivation]
+- [Belief system]
+
+**Work Style [or Leadership Style / Life Approach]:**
+- [How they operate]
+- [What they value]
+- [How they make decisions]
+- [Communication preferences]
+```
+
+---
+
+### 6. Driving Forces (CRITICAL SECTION)
+
+```markdown
+## Driving Forces
+
+### ✅ Top 3 Positive Drivers (What They Want)
+
+**1. [Want #1]**
+- [Detailed description of the want]
+- [Why it matters to them]
+- [What success looks like]
+- **[Product] Promise:** [How your product delivers this]
+
+**2. [Want #2]**
+- [Detailed description]
+- [Why it matters]
+- [What success looks like]
+- **[Product] Promise:** [How your product delivers this]
+
+**3. [Want #3]**
+- [Detailed description]
+- [Why it matters]
+- [What success looks like]
+- **[Product] Promise:** [How your product delivers this]
+
+---
+
+### ❌ Top 3 Negative Drivers (What They Fear)
+
+**1. [Fear #1]**
+- [Detailed description of the fear]
+- [Why this terrifies them]
+- [What failure looks like]
+- **[Product] Answer:** [How your product solves/prevents this]
+
+**2. [Fear #2]**
+- [Detailed description]
+- [Why this terrifies them]
+- [What failure looks like]
+- **[Product] Answer:** [How your product solves/prevents this]
+
+**3. [Fear #3]**
+- [Detailed description]
+- [Why this terrifies them]
+- [What failure looks like]
+- **[Product] Answer:** [How your product solves/prevents this]
+```
+
+---
+
+### 7. The Transformation Journey (PRIMARY PERSONA ESPECIALLY)
+
+```markdown
+## The Transformation Journey
+
+### BEFORE [Product]
+
+**Emotional State:**
+- 😰 [Feeling 1]
+- 😔 [Feeling 2]
+- 🤷‍♀️ [Feeling 3]
+- 😤 [Feeling 4]
+- 📦 [Self-perception]
+
+**Daily Reality:**
+- [Daily struggle 1]
+- [Daily struggle 2]
+- [Daily struggle 3]
+- [Daily struggle 4]
+
+**Self-Perception:**
+- [How they see themselves]
+- [Where they feel stuck]
+- [Their limitations]
+
+---
+
+### AFTER [Product]
+
+**Emotional State:**
+- 🎯 [New feeling 1]
+- 🚀 [New feeling 2]
+- 💪 [New feeling 3]
+- ⭐ [New feeling 4]
+- 🌍 [New self-perception]
+
+**Daily Reality:**
+- [New capability 1]
+- [New capability 2]
+- [New capability 3]
+- [New outcome]
+
+**Self-Perception:**
+- [How they now see themselves]
+- [Their new role]
+- [Their new identity]
+```
+
+---
+
+### 8. Role in Strategic Triangle
+
+```markdown
+## Role in Strategic Triangle
+
+\```
+[PRIMARY PERSONA]
+[Role/Title]
+[Key action]
+      │
+      │ [Connection action]
+      ▼
+[SECONDARY PERSONA]
+[Role/Title]
+[Benefit received]
+      │
+      │ [Connection action]
+      ▼
+[TERTIARY PERSONA]
+[Role/Title]
+[Benefit received]
+      │
+      │ [Connection action]
+      └──────────────► [PRIMARY PERSONA]
+                      (Loop closes)
+\```
+
+**[This Persona]'s Role:**
+- [Key contribution 1]
+- [Key contribution 2]
+- [How they enable others]
+- [How the loop reinforces]
+```
+
+---
+
+### 9. Creating Awesome [This Persona Type] OR Validation/Discovery Strategy
+
+**For PRIMARY:**
+```markdown
+## Role in Flywheel: Creating Awesome [Personas] Who Become [Champions]
+
+[Persona Name] represents the [type] who [Product] empowers to become truly awesome - and awesome [users] naturally become [champions].
+
+**The Natural Evolution:**
+1. [Persona] discovers [Product] and sees themselves in the methodology
+2. Learns [approach] with [support level]
+3. Builds [outcome] using [Product] - sees results
+4. Transforms from [before] to [after]
+5. Naturally shares what worked with others
+6. Becomes one of the [X] [champions] - not because we asked, but because [they're] excited
+
+---
+
+## What [Persona Name] Needs to See on [Product] Page
+
+**1. [Section Name]**
+- [Requirement 1]
+- [Requirement 2]
+- [Key message]
+
+**2. [Section Name]**
+- [Requirement 1]
+- [Requirement 2]
+- [Key message]
+
+[Continue for 5-6 key sections]
+```
+
+**For SECONDARY:**
+```markdown
+## Validation Strategy
+
+### What [Persona Name] Needs to See About [Product]
+
+**1. [Validation Need]**
+- [Proof point 1]
+- [Proof point 2]
+- [Trust signal]
+
+[Continue for 3-4 validation needs]
+
+---
+
+## Conversion Path
+
+### How [Persona Name] Validates [Product]
+
+**Phase 1: Discovery**
+- [How they hear about it]
+
+**Phase 2: Evaluation**
+- [What they check]
+
+**Phase 3: Adoption**
+- [How they engage]
+
+**Phase 4: Advocacy**
+- [How they spread word]
+```
+
+**For TERTIARY:**
+```markdown
+## How [Persona Name] Discovers [Product] Value
+
+### The Recognition Path
+
+**Phase 1: Experience the Difference**
+- [What changes for them]
+
+**Phase 2: Recognition**
+- [When they realize why]
+
+**Phase 3: Appreciation**
+- [How they respond]
+
+**Phase 4: Word of Mouth**
+- [How they share]
+```
+
+---
+
+### 10. Impact on Business Goals
+
+```markdown
+## Impact on Business Goals
+
+**[This Persona]'s Role in Success Metrics:**
+
+**Primary Goal ([X Champions]):**
+- [How they contribute]
+- [Specific impact]
+
+**Secondary Goals ([Product] Adoption):**
+- [How they contribute]
+- [Specific impact]
+
+**Tertiary Goals (Community Opportunities):**
+- [How they contribute]
+- [Specific impact]
+```
+
+---
+
+### 11. Success Metrics (PRIMARY especially)
+
+```markdown
+## Success Metrics
+
+**[Persona] Becomes [Champion] When [They]:**
+1. ✅ [Milestone 1]
+2. ✅ [Milestone 2]
+3. ✅ [Milestone 3]
+4. ✅ [Milestone 4]
+5. ✅ [Milestone 5]
+
+**Impact on Business Goals:**
+- Becomes one of **[X] [champions]** (PRIMARY GOAL)
+- [Impact 2]
+- [Impact 3]
+- [Impact 4]
+```
+
+---
+
+### 12. Transformation Journey (PRIMARY persona especially)
+
+```markdown
+## Transformation Journey
+
+**Current State:** [Current challenges and limitations]
+
+**With [Product]:** [How the product enables change]
+
+**Desired State:** [Outcome and new capabilities]
+
+**What Makes This Possible:**
+- [Enabler 1]
+- [Enabler 2]
+- [Enabler 3]
+```
+
+This is especially important for the PRIMARY persona.
+
+---
+
+### 13. Related Documents Footer
+
+```markdown
+## Related Documents
+
+- **[00-trigger-map.md](00-trigger-map.md)** - Visual overview and navigation
+- **[02-[Other].md](02-[Other].md)** - [Other] persona
+- **[03-[Other].md](03-[Other].md)** - [Other] persona
+- **[05-Key-Insights.md](05-Key-Insights.md)** - Strategic implications
+
+---
+
+_Back to [Trigger Map](00-trigger-map.md)_
+```
+
+---
+
+## Key Requirements
+
+**Length:** Each persona should be ~250-375 lines
+
+**Tone:**
+- Rich, nuanced, human
+- Not "converting" but "creating awesome"
+- Natural language, storytelling
+
+**Driving Forces:**
+- Each must have **[Product] Promise** or **[Product] Answer**
+- Show how product addresses each driver
+- Be specific and actionable
+
+**Transformation:**
+- PRIMARY persona gets full BEFORE/AFTER
+- Show emotional journey, not just functional
+- Use emojis to show emotional states
+
+**Strategic Triangle:**
+- Show how personas interconnect
+- Explain the loop/flywheel
+- Make relationships clear

_bmad/wds/workflows/2-trigger-mapping/templates/trigger-map.template.md

@@ -0,0 +1,169 @@
+# Trigger Map Poster: {{project_name}}
+
+> Visual overview connecting business goals to user psychology
+
+**Created:** {{date}}
+**Author:** {{user_name}}
+**Methodology:** Based on Effect Mapping (Balic & Domingues), adapted for WDS framework
+
+---
+
+## Strategic Documents
+
+This is the visual overview. For detailed documentation, see:
+
+- **01-Business-Goals.md** - Full vision statements and SMART objectives
+- **02-Target-Groups.md** - All personas with complete driving forces
+- **03-Feature-Impact-Analysis.md** - Prioritized features with impact scores
+- **04-08-\*.md** - Individual persona detail files
+
+---
+
+## Vision
+
+{{vision_statement}}
+
+---
+
+## Business Objectives
+
+{{#each objectives}}
+
+### Objective {{@index + 1}}: {{this.statement}}
+
+- **Metric:** {{this.metric}}
+- **Target:** {{this.target}}
+- **Timeline:** {{this.timeline}}
+  {{/each}}
+
+---
+
+## Target Groups (Prioritized)
+
+{{#each prioritized_groups}}
+
+### {{@index + 1}}. {{this.name}}
+
+**Priority Reasoning:** {{this.reasoning}}
+
+> {{this.persona_summary}}
+
+**Key Positive Drivers:**
+{{#each this.positive_drivers}}
+
+- {{this}}
+  {{/each}}
+
+**Key Negative Drivers:**
+{{#each this.negative_drivers}}
+
+- {{this}}
+  {{/each}}
+
+{{/each}}
+
+---
+
+## Trigger Map Visualization
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': { 'fontFamily':'Inter, system-ui, sans-serif', 'fontSize':'14px'}}}%%
+flowchart LR
+    %% Business Goals (Left)
+    {{#each business_goals}}
+    BG{{@index}}["<br/>{{this.emoji}} {{this.title}}<br/><br/>{{#each this.points}}{{this}}<br/>{{/each}}<br/>"]
+    {{/each}}
+    
+    %% Central Platform
+    PLATFORM["<br/>{{platform_emoji}} {{platform_name}}<br/><br/>{{platform_tagline}}<br/><br/>{{platform_transformation}}<br/><br/>"]
+    
+    %% Target Groups
+    {{#each target_groups}}
+    TG{{@index}}["<br/>{{this.emoji}} {{this.name}}<br/>{{this.priority}}<br/><br/>{{#each this.profile}}{{this}}<br/>{{/each}}<br/>"]
+    {{/each}}
+    
+    %% Driving Forces
+    {{#each target_groups}}
+    DF{{@index}}["<br/>{{this.emoji}} {{this.name}}'S DRIVERS<br/><br/>WANTS<br/>{{#each this.positive_drivers}}✅ {{this}}<br/>{{/each}}<br/>FEARS<br/>{{#each this.negative_drivers}}❌ {{this}}<br/>{{/each}}<br/>"]
+    {{/each}}
+    
+    %% Connections
+    {{#each business_goals}}
+    BG{{@index}} --> PLATFORM
+    {{/each}}
+    {{#each target_groups}}
+    PLATFORM --> TG{{@index}}
+    TG{{@index}} --> DF{{@index}}
+    {{/each}}
+
+    %% Light Gray Styling with Dark Text
+    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
+    
+    {{#each business_goals}}
+    class BG{{@index}} businessGoal
+    {{/each}}
+    class PLATFORM platform
+    {{#each target_groups}}
+    class TG{{@index}} targetGroup
+    class DF{{@index}} drivingForces
+    {{/each}}
+```
+
+---
+
+## Design Focus Statement
+
+{{focus_statement}}
+
+**Primary Design Target:** {{top_group.name}}
+
+**Must Address:**
+{{#each must_address_drivers}}
+
+- {{this}}
+  {{/each}}
+
+**Should Address:**
+{{#each should_address_drivers}}
+
+- {{this}}
+  {{/each}}
+
+---
+
+## Cross-Group Patterns
+
+### Shared Drivers
+
+{{shared_drivers}}
+
+### Unique Drivers
+
+{{unique_drivers}}
+
+{{#if conflicts}}
+
+### Potential Tensions
+
+{{conflicts}}
+{{/if}}
+
+---
+
+## Next Steps
+
+This Trigger Map Poster provides a quick reference. For detailed work:
+
+- [ ] **Review detailed docs** - See 01-Business-Goals.md, 02-Target-Groups.md, 03-Feature-Impact-Analysis.md
+- [ ] **Use for Feature Prioritization** - Reference feature impact scores
+- [ ] **Guide UX Design** - Ensure designs address priority drivers
+- [ ] **Validate with Users** - Test assumptions with real target group members
+- [ ] **Update as Learnings Emerge** - This is a living document
+
+---
+
+_Generated with Whiteport Design Studio framework_
+_Trigger Mapping methodology credits: Effect Mapping by Mijo Balic & Ingrid Domingues (inUse), adapted with negative driving forces_

_bmad/wds/workflows/2-trigger-mapping/workflow-validate.md

@@ -0,0 +1,43 @@
+---
+name: trigger-mapping-validate
+description: Validate Trigger Map documents against WDS quality standards
+web_bundle: true
+validateWorkflow: './steps-v/step-01-target-group-coverage.md'
+---
+
+# 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

_bmad/wds/workflows/2-trigger-mapping/workflow.md

@@ -0,0 +1,89 @@
+---
+name: trigger-mapping
+description: Map business goals to user psychology through structured workshops
+web_bundle: true
+---
+
+# Phase 2: Trigger Mapping
+
+**Goal:** Connect business goals to user psychology through structured workshops, creating a strategic reference that coordinates all teams.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a Strategic Analyst facilitating Effect Mapping workshops. This is a partnership, not a client-vendor relationship. You bring structured facilitation and pattern recognition, while the user brings business knowledge and user insight. Work together as equals.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+Based on Effect Mapping by Mijo Balic & Ingrid Domingues (inUse). Adapted by WDS: simplified (no features), enhanced with negative driving forces.
+
+This uses **step-file architecture** for disciplined execution:
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all sections in order
+3. **LOAD NEXT**: When directed, load and execute next step
+4. **CHECKPOINT**: When a step says "wait for user", do NOT auto-proceed
+
+### Critical Rules (NO EXCEPTIONS)
+
+- **NEVER** load multiple step files simultaneously
+- **ALWAYS** read entire step file before execution
+- **NEVER** skip steps or optimize the sequence
+- **ALWAYS** follow the exact instructions in step file
+
+### Two Paths
+
+- **From scratch** → step-01-overview.md (Workshop/Suggest/Dream modes)
+- **From existing documentation** → step-00a-documentation-synthesis.md
+
+### Prerequisites
+
+- Phase 1: Product Brief (required)
+
+---
+
+## INITIALIZATION
+
+### 1. 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`
+
+### 2. Design Log
+
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
+
+### 3. Mode Determination
+
+**Check invocation:**
+- "validate" / -v → Load and execute `./workflow-validate.md`
+- "existing" / from docs → Load and execute `./steps-c/step-00a-documentation-synthesis.md`
+- Default (create from scratch) → Load and execute `./steps-c/step-01-overview.md`
+
+---
+
+## REFERENCE CONTENT
+
+| Location | Purpose |
+|----------|---------|
+| `data/business-goals-template.md` | Business goals template |
+| `data/key-insights-structure.md` | Key insights structure |
+| `data/mermaid-formatting-guide.md` | Mermaid diagram formatting |
+| `data/quality-checklist.md` | Quality checklist |
+
+---
+
+## OUTPUT
+
+- `{output_folder}/B-Trigger-Map/trigger-map.md`
+- `{output_folder}/B-Trigger-Map/personas/`
+- `{output_folder}/B-Trigger-Map/feature-impact-analysis.md`
+
+---
+
+## AFTER COMPLETION
+
+1. Update design log
+2. Suggest next action or proceed to Phase 3: UX Scenarios