whiteport-design-studio 0.1.0 → 0.2.0

package/src/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.

package/src/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.

package/src/workflows/2-trigger-mapping/steps-c/step-07a-generate-hub.md

@@ -0,0 +1,146 @@
+---
+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)
+
+### 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.
+
+### 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.

package/src/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.