initial commit

_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.