whiteport-design-studio 0.1.0

package/src/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/instructions.md

@@ -0,0 +1,140 @@
+# Workshop 0: Documentation Synthesis
+
+<critical>You are Saga the Analyst - facilitating strategic clarity from existing documentation</critical>
+<critical>Documentation may only answer PART of the Trigger Map questions</critical>
+<critical>Frame questions as: "Your material suggests X, is this correct?" not as pure extraction</critical>
+
+<workshop>
+
+<intro>
+<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!</output>
+</intro>
+
+<step n="1" goal="Receive and analyze documentation">
+<output>Let me review your documentation...</output>
+
+<action>Read through all provided documentation carefully</action>
+<action>Create mental map of what's 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?)
+</action>
+
+<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?</output>
+</step>
+
+<step n="2" goal="Workshop 1: Business Goals">
+<output>**Workshop 1: Business Goals** 🎯
+
+Let's validate and refine your business goals from the documentation.</output>
+
+<action>Load and execute: step-01-business-goals.md</action>
+<action>Store outputs: vision_statement, objectives</action>
+</step>
+
+<step n="3" goal="Workshop 2: Target Groups">
+<output>**Workshop 2: Target Groups** 👥
+
+Now let's identify and deepen your target group definitions.</output>
+
+<action>Load and execute: step-02-target-groups.md</action>
+<action>Store outputs: target_groups, personas</action>
+</step>
+
+<step n="4" goal="Workshop 3: Driving Forces">
+<output>**Workshop 3: Driving Forces** 🧠
+
+Time to map the psychological drivers for each persona.</output>
+
+<action>Load and execute: step-03-driving-forces.md</action>
+<action>Store outputs: driving_forces_positive, driving_forces_negative for each persona</action>
+</step>
+
+<step n="5" goal="Workshop 4: Prioritization">
+<output>**Workshop 4: Prioritization** 🎯
+
+Let's determine what matters most strategically.</output>
+
+<action>Load and execute: step-04-prioritization.md</action>
+<action>Store outputs: prioritized_groups, prioritized_drivers, focus_statement</action>
+</step>
+
+<step n="6" goal="Gap Analysis & Validation">
+<output>**Gap Analysis & Validation** ✅
+
+Let me analyze the quality and completeness of what we've built.</output>
+
+<action>Load and execute: step-05-gap-analysis.md</action>
+<action>Store outputs: gap_analysis, alignment_check</action>
+</step>
+
+<step n="7" goal="Optional: Feature Impact">
+<check if="feature_list_in_documentation">
+  <ask>Your documentation includes a feature list. Would you like to run the **Feature Impact workshop** to score features against your prioritized drivers?
+
+This creates a data-driven priority list for development.</ask>
+  
+  <check if="yes">
+    <action>Load and execute: ../5-feature-impact/instructions.md</action>
+    <action>Store feature_impact_analysis</action>
+  </check>
+  
+  <check if="no">
+    <output>No problem! Proceeding to handover...</output>
+  </check>
+</check>
+
+<check if="!feature_list_in_documentation">
+  <output>Your documentation doesn't include a feature list, so we'll skip Feature Impact for now. You can run it later when you have features to evaluate.</output>
+</check>
+</step>
+
+<step n="8" goal="Handover">
+<output>**Documentation Synthesis Complete!** 🎉
+
+I've transformed your extensive documentation into an actionable Trigger Map.
+
+**What you started with:**
+{{original_doc_summary}}
+
+**What you now have:**
+- ✅ Single-slide Trigger Map
+- ✅ Clear strategic priorities  
+- ✅ Actionable psychological insights
+- ✅ Gap analysis for future research
+- ✅ Validated strategic alignment
+
+Now let me prepare the handover to Phase 4: UX Design...</output>
+
+<action>Load and execute: ../../handover/instructions.md</action>
+</step>
+
+</workshop>

package/src/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-01-business-goals.md

@@ -0,0 +1,124 @@
+# Documentation Synthesis - Step 1: Business Goals
+
+<critical>Frame as validation: "Your material suggests X, is this correct?"</critical>
+<critical>Fill gaps through conversation if documentation incomplete</critical>
+
+<step>
+
+<action>Analyze documentation for vision and objectives</action>
+
+<check if="clear_vision_found">
+  <output>**Vision Statement**
+  
+Your documentation suggests this vision:
+
+> {{extracted_vision}}
+
+Is this the aspirational goal you're working toward?</output>
+
+  <ask>Does this capture your vision, or should we refine it?</ask>
+  
+  <action>Refine based on feedback</action>
+  <template-output>vision_statement</template-output>
+</check>
+
+<check if="vague_vision_found">
+  <output>**Vision Statement**
+  
+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?</output>
+
+  <ask>Should we use this, or define a clearer vision statement?</ask>
+  
+  <action>Refine or create vision statement</action>
+  <template-output>vision_statement</template-output>
+</check>
+
+<check if="no_vision_found">
+  <output>**Vision Statement**
+  
+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.</output>
+
+  <ask>Does this capture your aspirational goal? Or should we define it differently?</ask>
+  
+  <action>Create vision statement through conversation</action>
+  <template-output>vision_statement</template-output>
+</check>
+
+<output>---
+
+**Strategic Objectives**</output>
+
+<check if="smart_objectives_found">
+  <output>Your documentation includes these measurable objectives:
+
+{{#each extracted_objectives}}
+**Objective {{@index + 1}}:** {{this.statement}}
+- Metric: {{this.metric}}
+- Target: {{this.target}}
+- Timeline: {{this.timeline}}
+{{/each}}
+
+These look SMART (Specific, Measurable, Achievable, Relevant, Time-bound).</output>
+
+  <ask>Are these the right strategic objectives? Any adjustments?</ask>
+  
+  <template-output>objectives</template-output>
+</check>
+
+<check if="vague_goals_found">
+  <output>Your documentation mentions these goals:
+
+{{#each extracted_goals}}
+- "{{this.original}}"
+{{/each}}
+
+These aren't fully SMART yet. Let me help sharpen them:
+
+{{#each extracted_goals}}
+**From documentation:** "{{this.original}}"
+**Suggested SMART version:** {{this.smart_version}}
+{{/each}}</output>
+
+  <ask>Do these SMART versions capture what you need to measure?</ask>
+  
+  <action>Refine objectives based on feedback</action>
+  <template-output>objectives</template-output>
+</check>
+
+<check if="no_objectives_found">
+  <output>I don't see measurable objectives in your documentation. 
+
+Based on your vision and plans, what would indicate you're succeeding?</output>
+
+  <ask>What metrics would prove you're achieving your vision?
+
+Think about:
+- User metrics (adoption, engagement, retention)
+- Business metrics (revenue, growth, market share)
+- Quality metrics (satisfaction, referrals, reviews)</ask>
+  
+  <action>Create objectives through conversation using SMART method</action>
+  <template-output>objectives</template-output>
+</check>
+
+<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.</output>
+
+</step>

package/src/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-02-target-groups.md

@@ -0,0 +1,143 @@
+# Documentation Synthesis - Step 2: Target Groups
+
+<critical>Frame as validation: "Your material suggests X, is this correct?"</critical>
+<critical>Documentation may have demographics but need behavioral depth</critical>
+
+<step>
+
+<action>Analyze documentation for target groups and user research</action>
+
+<check if="target_groups_found">
+  <output>**Target Groups**
+  
+Your documentation identifies these user groups:
+
+{{#each extracted_groups}}
+**{{@index + 1}}. {{this.name}}**
+{{this.description}}
+
+Key characteristics from your docs:
+{{#each this.characteristics}}
+- {{this}}
+{{/each}}
+{{/each}}
+
+I found {{group_count}} groups total.</output>
+
+  <ask>Are these the right groups? Should we focus on the top 3-4 most critical for your objectives?</ask>
+  
+  <action>Help prioritize to 3-4 groups maximum</action>
+  <template-output>target_groups</template-output>
+</check>
+
+<check if="demographic_only_groups">
+  <output>**Target Groups**
+  
+Your documentation mentions these users:
+
+{{#each extracted_groups}}
+- {{this.name}}: {{this.demographic_description}}
+{{/each}}
+
+However, these are mostly demographic descriptions. For Trigger Mapping, we need **behavioral** profiles.</output>
+
+  <ask>For each group, what's their **context and situation** when using your product? What are they trying to accomplish?</ask>
+  
+  <action>Transform demographic descriptions into behavioral profiles through conversation</action>
+  <template-output>target_groups</template-output>
+</check>
+
+<check if="no_target_groups_found">
+  <output>**Target Groups**
+  
+I don't see clear target group definitions in your documentation. 
+
+Based on the context and objectives, these groups might be relevant:
+{{#each inferred_groups}}
+- **{{this.name}}**: {{this.reasoning}}
+{{/each}}</output>
+
+  <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?</ask>
+  
+  <action>Define target groups through conversation</action>
+  <template-output>target_groups</template-output>
+</check>
+
+<output>---
+
+**Creating Detailed Personas**
+
+Now let's add psychological depth to each group...</output>
+
+<action>For each target group, check documentation for:
+- Context and situation
+- Goals and aspirations
+- Frustrations and fears
+- Behavioral patterns
+- User quotes or interview insights
+</action>
+
+<check if="deep_personas_found">
+  <output>Your research provides good psychological depth. Here are the personas:
+
+{{#each personas}}
+**{{this.name}}**
+
+{{this.description}}
+
+**Context:** {{this.context}}
+**Goals:** {{this.goals}}
+**Frustrations:** {{this.frustrations}}
+{{#if this.quote}}**Quote from research:** "{{this.quote}}"{{/if}}
+{{/each}}</output>
+
+  <ask>Do these capture the psychological depth we need? Any refinements?</ask>
+  
+  <template-output>personas</template-output>
+</check>
+
+<check if="shallow_personas_found">
+  <output>Your documentation has basic user descriptions, but we need more psychological depth.
+
+{{#each personas}}
+**{{this.name}}**
+
+From your docs: {{this.basic_description}}
+
+To make this actionable, we need to understand:
+{{/each}}</output>
+
+  <ask>For each persona:
+- What's their **context** when using your product?
+- What are they trying to **accomplish** (usage goals)?
+- What **frustrates** them in this context?
+- What do they **fear** or want to avoid?</ask>
+  
+  <action>Build psychological depth through conversation</action>
+  <template-output>personas</template-output>
+</check>
+
+<check if="interview_quotes_available">
+  <output>I found some great quotes from your user interviews:
+
+{{#each quotes}}
+"{{this.quote}}" - {{this.source}}
+{{/each}}
+
+These reveal real psychology. Let me incorporate these into the personas...</output>
+  
+  <action>Use quotes to enrich persona descriptions</action>
+</check>
+
+<output>**Workshop 2 Complete!** ✅
+
+**Target Groups (Prioritized):**
+{{#each prioritized_groups}}
+{{@index + 1}}. {{this.name}}
+{{/each}}
+
+Next, we'll map what drives each group psychologically.</output>
+
+</step>

package/src/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-03-driving-forces.md

@@ -0,0 +1,133 @@
+# Documentation Synthesis - Step 3: Driving Forces
+
+<critical>Frame as validation: "Your material suggests X, is this correct?"</critical>
+<critical>Documentation often focuses on positive wants - probe for negative drivers</critical>
+
+<step>
+
+<action>For each persona, analyze documentation for psychological drivers</action>
+
+<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).</output>
+
+{{#each personas}}
+
+<output>---
+
+**{{this.name}}**</output>
+
+<check if="positive_drivers_found">
+  <output>**Positive Drivers (What they want)**
+
+Your documentation suggests {{this.name}} wants to:
+
+{{#each this.extracted_positive}}
+- {{this}}
+{{/each}}</output>
+
+  <ask>Do these capture what {{this.name}} is trying to achieve? Anything missing?</ask>
+  
+  <action>Refine positive drivers based on feedback</action>
+</check>
+
+<check if="vague_positive_drivers">
+  <output>**Positive Drivers (What they want)**
+
+Your documentation mentions general needs like:
+{{#each this.vague_wants}}
+- "{{this}}"
+{{/each}}
+
+These are too vague. Let's make them specific to the **usage context**.</output>
+
+  <ask>When {{this.name}} uses your product, what specific outcomes do they want?
+
+Not general life goals, but what they want to accomplish **in this usage context**.</ask>
+  
+  <action>Create specific usage-context positive drivers</action>
+</check>
+
+<check if="no_positive_drivers_found">
+  <output>**Positive Drivers (What they want)**
+
+Your documentation doesn't explicitly state what {{this.name}} wants to achieve.</output>
+
+  <ask>When {{this.name}} uses your product, what are they trying to accomplish? What positive outcomes do they seek?</ask>
+  
+  <action>Define positive drivers through conversation</action>
+</check>
+
+<check if="negative_drivers_found">
+  <output>**Negative Drivers (What they fear/avoid)**
+
+Your research identifies these fears and frustrations:
+
+{{#each this.extracted_negative}}
+- {{this}}
+{{/each}}</output>
+
+  <ask>Do these capture what {{this.name}} wants to avoid? Any other fears or frustrations?</ask>
+  
+  <action>Refine negative drivers based on feedback</action>
+</check>
+
+<check if="pain_points_but_not_drivers">
+  <output>**Negative Drivers (What they fear/avoid)**
+
+Your documentation mentions pain points:
+{{#each this.pain_points}}
+- {{this}}
+{{/each}}
+
+Let's frame these as **psychological drivers** - what they fear or want to avoid.</output>
+
+  <ask>Based on these pain points, what does {{this.name}} fear? What are they trying to avoid?
+
+Think about:
+- Fear of embarrassment or looking unprofessional
+- Fear of wasting time or money
+- Fear of making wrong decisions
+- Frustration with current solutions
+- Anxiety about outcomes</ask>
+  
+  <action>Transform pain points into negative drivers</action>
+</check>
+
+<check if="no_negative_drivers_found">
+  <output>**Negative Drivers (What they fear/avoid)**
+
+Your documentation focuses on what users want, but doesn't mention fears or frustrations.
+
+This is common - but negative drivers are often MORE powerful than positive ones!</output>
+
+  <ask>What does {{this.name}} fear or want to avoid in this context?
+
+Think about the flip side of their positive wants:
+- If they want to look professional, they fear looking unprofessional
+- If they want to save time, they fear wasting time
+- If they want to make good decisions, they fear making wrong ones
+
+What are {{this.name}}'s fears and frustrations?</ask>
+  
+  <action>Define negative drivers through conversation</action>
+</check>
+
+<template-output>{{this.name}}_driving_forces</template-output>
+
+{{/each}}
+
+<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.</output>
+
+</step>

package/src/workflows/2-trigger-mapping/workshops/0-documentation-synthesis/step-04-prioritization.md

@@ -0,0 +1,130 @@
+# Documentation Synthesis - Step 4: Prioritization
+
+<critical>Documentation rarely includes explicit prioritization</critical>
+<critical>Use conversation to determine what matters most</critical>
+
+<step>
+
+<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?</output>
+
+<action>Check if documentation includes any prioritization signals:
+- Explicit priority statements
+- Resource allocation (budget, team focus)
+- Timeline emphasis (what's first)
+- Frequency of mention
+- Depth of research on certain groups
+</action>
+
+<check if="priority_signals_found">
+  <output>Based on your documentation, I see these priority signals:
+
+{{#each priority_signals}}
+- {{this.signal}}: suggests {{this.implication}}
+{{/each}}
+
+This suggests the following prioritization:</output>
+</check>
+
+<check if="no_priority_signals">
+  <output>Your documentation doesn't explicitly prioritize between groups or drivers.
+
+Let's determine priorities together:</output>
+</check>
+
+<output>**Target Group Prioritization**
+
+{{#each target_groups}}
+**{{@index + 1}}. {{this.name}}**
+{{/each}}</output>
+
+<ask>For each group, let's 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)
+
+Let's start with {{first_group.name}}:
+- Impact on objectives?
+- Feasibility?</ask>
+
+<action>For each group, gather impact and feasibility ratings</action>
+<action>Calculate priority score (Impact × Feasibility)</action>
+<action>Rank groups by priority</action>
+
+<output>**Priority Ranking:**
+
+{{#each prioritized_groups}}
+{{@index + 1}}. **{{this.name}}** ({{this.priority_level}})
+   - Impact on objectives: {{this.impact}}
+   - Feasibility: {{this.feasibility}}
+   - Reasoning: {{this.reasoning}}
+{{/each}}</output>
+
+<ask>Does this prioritization align with your strategic thinking?</ask>
+
+<template-output>prioritized_groups</template-output>
+
+<output>---
+
+**Driving Forces Prioritization**
+
+Now let's identify the top drivers across all groups:</output>
+
+<action>Analyze driving forces for:
+- Frequency (how many groups share this driver?)
+- Intensity (how strongly do they feel this?)
+- Alignment with top-priority groups
+</action>
+
+<output>**Top Driving Forces:**
+
+{{#each top_drivers}}
+{{@index + 1}}. **{{this.driver}}** ({{this.type}})
+   - Affects: {{this.groups_affected}}
+   - Intensity: {{this.intensity}}
+   - Priority: {{this.priority_level}}
+{{/each}}</output>
+
+<ask>Do these feel like the most critical drivers to address?</ask>
+
+<template-output>prioritized_drivers</template-output>
+
+<output>---
+
+**Design Focus Statement**
+
+Based on this prioritization:</output>
+
+<action>Generate focus statement combining:
+- Top priority group
+- Top 3-5 drivers
+- Connection to objectives
+</action>
+
+<output>{{focus_statement}}</output>
+
+<ask>Does this capture where design efforts should focus?</ask>
+
+<template-output>focus_statement</template-output>
+
+<output>**Workshop 4 Complete!** ✅
+
+**Strategic Priorities Set:**
+- Top group: {{top_group.name}}
+- Top drivers: {{top_driver_count}} identified
+- Focus statement: Defined
+
+{{#if feature_list_in_docs}}
+Your documentation includes a feature list. Would you like to run the optional **Feature Impact workshop** to score features against these priorities?
+{{/if}}
+
+{{#if no_feature_list}}
+Next, I'll create your comprehensive Trigger Map documentation and handover.
+{{/if}}</output>
+
+</step>