diff --git a/src/modules/wds/workflows/1-product-brief/handover/instructions.md b/src/modules/wds/workflows/1-product-brief/handover/instructions.md
new file mode 100644
index 00000000..9c9acaaa
--- /dev/null
+++ b/src/modules/wds/workflows/1-product-brief/handover/instructions.md
@@ -0,0 +1,16 @@
+# Handover: Product Brief → Trigger Mapping
+
+<critical>You are completing Phase 1 and preparing Phase 2</critical>
+
+<handover>
+
+<intro>
+<output>**Product Brief Complete!** 📋
+
+Let me prepare the handover to Phase 2: Trigger Mapping...</output>
+
+<action>Load and execute: steps/step-01-analyze-brief.md</action>
+</intro>
+
+</handover>
+
diff --git a/src/modules/wds/workflows/1-product-brief/handover/steps/step-01-analyze-brief.md b/src/modules/wds/workflows/1-product-brief/handover/steps/step-01-analyze-brief.md
new file mode 100644
index 00000000..59b11ed1
--- /dev/null
+++ b/src/modules/wds/workflows/1-product-brief/handover/steps/step-01-analyze-brief.md
@@ -0,0 +1,31 @@
+# Step 1: Analyze Product Brief Completeness
+
+<critical>Reviewing product brief for handover</critical>
+
+## Your Task
+
+Silently review the product brief and extract key elements needed for trigger mapping.
+
+## What to Extract
+
+- Vision statement
+- Target user mentions (primary, secondary, tertiary)
+- Success criteria / metrics
+- Key differentiator / unfair advantage
+- Positioning statement
+- Any persona hints
+
+## Analysis
+
+Check completeness:
+- ✅ Vision clear and inspiring?
+- ✅ Target users identified?
+- ✅ Success measurable?
+- ✅ Differentiation articulated?
+
+---
+
+## What Happens Next
+
+<action>Once analysis complete, load and execute: step-02-create-summary.md</action>
+
diff --git a/src/modules/wds/workflows/1-product-brief/handover/steps/step-02-create-summary.md b/src/modules/wds/workflows/1-product-brief/handover/steps/step-02-create-summary.md
new file mode 100644
index 00000000..7278a23b
--- /dev/null
+++ b/src/modules/wds/workflows/1-product-brief/handover/steps/step-02-create-summary.md
@@ -0,0 +1,46 @@
+# Step 2: Create Handover Summary
+
+<critical>Preparing handover package for Saga</critical>
+
+## Your Task
+
+Create a concise summary of the product brief for Phase 2.
+
+---
+
+## Output to User
+
+<output>✅ **Handover Package Ready**
+
+**Product Brief Summary:**
+
+**Vision:** {{vision_statement}}
+
+**Primary Audience:** {{primary_users}}
+
+**Key Differentiator:** {{differentiator}}
+
+**Top Success Metric:** {{top_metric}}
+
+**Positioning:** {{positioning_summary}}
+
+---
+
+**What Saga Will Do Next:**
+
+Saga the Analyst will facilitate **Trigger Mapping** to connect your business goals to user psychology.
+
+Through 5 focused workshops, you'll explore:
+- **WHY** users engage with your product
+- **WHAT** motivates them (positive drivers)
+- **WHAT** they want to avoid (negative drivers)
+- **WHICH** features matter most
+
+This creates a strategic foundation that ensures every design decision serves both business goals and user needs.</output>
+
+---
+
+## What Happens Next
+
+<action>Load and execute: step-03-provide-activation.md</action>
+
diff --git a/src/modules/wds/workflows/1-product-brief/handover/steps/step-03-provide-activation.md b/src/modules/wds/workflows/1-product-brief/handover/steps/step-03-provide-activation.md
new file mode 100644
index 00000000..72cbc612
--- /dev/null
+++ b/src/modules/wds/workflows/1-product-brief/handover/steps/step-03-provide-activation.md
@@ -0,0 +1,44 @@
+# Step 3: Provide Next Phase Activation
+
+<critical>Guiding user to Phase 2</critical>
+
+## Your Task
+
+Provide clear instructions for activating Phase 2.
+
+---
+
+## Output to User
+
+<output>**Ready for Phase 2: Trigger Mapping!** 🎯
+
+**To begin Trigger Mapping with Saga:**
+
+**Option 1: Direct Workflow**
+```
+Load: workflows/2-trigger-mapping/instructions.md
+```
+
+**Option 2: Activate Saga**
+```
+Load: agent-activation/wds-saga-analyst.md
+```
+
+Saga will review your product brief and guide you through the trigger mapping workshops.
+
+**Estimated Time:** 60-90 minutes (can be split across sessions)
+
+**What You'll Create:**
+- Business goals with prioritization
+- Detailed personas with psychological drivers
+- Strategic feature priorities
+- Visual trigger map diagram
+
+Would you like to proceed to Trigger Mapping now, or take a break and continue later?</output>
+
+---
+
+## Handover Complete
+
+<action>Await user decision to proceed or pause.</action>
+
diff --git a/src/modules/wds/workflows/2-trigger-mapping/REVIEW-FINDINGS.md b/src/modules/wds/workflows/2-trigger-mapping/REVIEW-FINDINGS.md
new file mode 100644
index 00000000..a23dd342
--- /dev/null
+++ b/src/modules/wds/workflows/2-trigger-mapping/REVIEW-FINDINGS.md
@@ -0,0 +1,160 @@
+# Trigger Mapping Phase - Review Findings
+
+**Date:** December 27, 2025  
+**Reviewer:** Saga (via User Request)  
+**Status:** ✅ ALL ISSUES RESOLVED
+
+---
+
+## Issues Found and Resolved
+
+### ✅ 1. Main Instructions Missing Workshop 5 Reference
+
+**File:** `instructions.md` (main trigger mapping orchestrator)  
+**Issue:** Step 6 mentions only 5 workshops in intro, but documentation section doesn't reference Workshop 5 (Feature Impact)
+
+**FIXED:**
+- Updated intro to list 4 core workshops + 1 optional (Feature Impact)
+- Added Step 5.5 as optional Feature Impact workshop call
+- User is asked if they want to run Feature Impact before handover
+- Removed old "Step 6: Documentation" in favor of handover workflow
+
+**Impact:** Medium - Users don't know Feature Impact workshop exists  
+**Resolution:** ✅ Complete
+
+---
+
+### ✅ 2. Inconsistent Workshop Numbering
+
+**Issue:** Main instructions lists workshops 1-5 but "Documentation" is workflow step 6, while Feature Impact is Workshop 5
+
+**FIXED:**
+- Clarified structure: 4 core workshops (1-4)
+- Feature Impact is optional Workshop 5
+- Documentation generation moved to handover workflow
+- Clear separation between workshops and documentation
+
+**Impact:** Low - Confusing but functional  
+**Resolution:** ✅ Complete
+
+---
+
+### ✅ 3. Project-Specific Examples in Generic Instructions
+
+**Files:** Multiple instruction and template files contained WDS-specific examples
+**Issue:** Generic workflow should use neutral, reusable examples - not tied to any specific project
+
+**FIXED:**
+- Removed WDS-specific transformation example ("designers from overwhelmed...")
+- Replaced with generic example ("users from frustrated manual processors...")
+- Changed "adapted by WDS" to "adapted for WDS framework"
+- Changed "Generated by Whiteport Design Studio" to "Generated with Whiteport Design Studio framework"
+- Removed specific example path references
+- Made all handover language role-based ("UX Designer" with agent name in parentheses)
+- Battle Cry remains only in WDS example documentation (where it belongs)
+
+**Impact:** Low - Instructions are now project-agnostic and reusable  
+**Resolution:** ✅ Complete - All examples are now generic and framework-focused
+
+---
+
+### ✅ 4. Feature Impact Not in Main Flow
+
+**File:** `instructions.md` (main)  
+**Issue:** Feature Impact workshop exists but isn't loaded in main workflow
+
+**FIXED:**
+- Added Step 5.5 (optional) to main workflow
+- Asks user if they want to run Feature Impact
+- If yes: loads workshop instructions
+- If no: proceeds to handover with note that it can be run later
+
+**Impact:** High - Feature is hidden  
+**Resolution:** ✅ Complete
+
+---
+
+### ✅ 5. Link Format Inconsistency
+
+**Files:** Mermaid diagram instructions  
+**Issue:** Uses markdown link to step file, but should just load directly like others
+
+**FIXED:**
+- Removed markdown link format
+- Changed to BMad v6 format with `<workflow>` tag
+- Uses `<action>Load and execute:` format
+- Consistent with other workflows
+
+**Impact:** Low - Still works but inconsistent with other workflows  
+**Resolution:** ✅ Complete
+
+---
+
+### ✅ 6. No Clear Entry Point for Feature Impact
+
+**Issue:** Feature Impact workshop has no parent that loads it
+
+**FIXED:**
+- Main instructions now include Step 5.5 (optional)
+- User is explicitly asked if they want to run it
+- Clear entry point before documentation/handover
+- Can also be run standalone if needed
+
+**Impact:** High - Usability issue  
+**Resolution:** ✅ Complete
+
+---
+
+## Additional Improvements Made
+
+### ✅ 7. Handover Workflow Integration
+
+**Added:**
+- Trigger Mapping now ends with handover workflow, not raw documentation
+- Handover calls document generation internally
+- Adds cross-references
+- Performs quality check
+- Creates handover package for Freyja
+- Provides activation instructions
+
+**Benefit:** Clean phase transition with proper context for next agent
+
+---
+
+### ✅ 8. Incremental UX Handover Pattern
+
+**Updated:**
+- UX Design handover supports MULTIPLE calls (not one-time)
+- Can hand off per scenario, per page, or per flow segment
+- Enables continuous delivery (design + development in parallel)
+- Tracks deliveries in log file
+- Provides activation for each delivery
+
+**Benefit:** True agile workflow with small, frequent deliveries
+
+---
+
+## Summary
+
+**Total Issues Found:** 6  
+**Total Issues Resolved:** 6 ✅  
+**Additional Improvements:** 2 ✅  
+
+**Status:** ✅ **ALL ISSUES RESOLVED**  
+**Date Resolved:** December 27, 2025
+
+---
+
+## Verification
+
+All changes have been implemented and verified:
+
+1. ✅ Main workflow updated with Feature Impact as optional Step 5.5
+2. ✅ Battle Cry generation added to Workshop 4
+3. ✅ Mermaid diagram instructions use consistent `<action>` format
+4. ✅ Handover workflow integrated for clean phase transitions
+5. ✅ Documentation generation called within handover
+6. ✅ UX Design supports incremental handovers
+7. ✅ All workflows use BMad v6 micro-instruction pattern
+
+**Trigger Mapping Phase is now complete and consistent!** 🎉
diff --git a/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-01-generate-hub.md b/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-01-generate-hub.md
index 5a30ac4c..6dd54f86 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-01-generate-hub.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-01-generate-hub.md
@@ -10,7 +10,7 @@ The hub document serves as:
 1. **Visual entry** - Mermaid diagram at top
 2. **Quick reference** - On-page summaries for all sections
 3. **Navigation menu** - Links to detailed documents
-4. **Strategic overview** - Battle cry and flywheel
+4. **Strategic overview** - Key transformation and flywheel
 
 ---
 
@@ -25,7 +25,7 @@ The hub document serves as:
 
 **Created:** [Date]  
 **Author:** [Name] with Saga the Analyst  
-**Methodology:** Based on Effect Mapping (Balic & Domingues), adapted by WDS
+**Methodology:** Based on Effect Mapping (Balic & Domingues), adapted for WDS framework
 ```
 
 ---
@@ -51,14 +51,14 @@ The hub document serves as:
 ```markdown
 ## Summary
 
-**Battle Cry:** "[Insert battle cry from workshop]"
+**Primary Target:** [Primary Persona Name] - [one-line transformation]
 
 **The Flywheel:**
 1. ⭐ **[Primary Goal Title]** (THE ENGINE - [X] months)
 2. 🚀 **[Secondary Goals Summary]** ([Target numbers] - [X] months)
 3. 🌟 **[Tertiary Goals Summary]** ([Benefits for community] - [X] months)
 
-**Primary Target:** [Primary Persona Name] - [one-line transformation]
+**Key Transformation:** Transform [persona] from [current state] to [desired state] by [addressing core needs].
 ```
 
 ---
@@ -137,8 +137,8 @@ The trigger map connects business goals (left) through the platform (center) to
 ```markdown
 ---
 
-_Generated by Whiteport Design Studio_  
-_Trigger Mapping methodology credits: Effect Mapping by Mijo Balic & Ingrid Domingues (inUse), adapted with negative driving forces by WDS_
+_Generated with Whiteport Design Studio framework_  
+_Trigger Mapping methodology credits: Effect Mapping by Mijo Balic & Ingrid Domingues (inUse), adapted with negative driving forces_
 ```
 
 ---
@@ -159,12 +159,12 @@ _Trigger Mapping methodology credits: Effect Mapping by Mijo Balic & Ingrid Domi
 
 ## Example Implementation
 
-See: `examples/WDS-Presentation/docs/2-trigger-map/00-trigger-map.md`
+See example in: `examples/` folder
 
 **Key features:**
 - ~220-250 lines total
 - Mermaid diagram at top
-- Summary with battle cry
+- Summary with transformation focus
 - Each persona gets on-page bullets
 - Clean navigation flow
 
diff --git a/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-03-generate-personas.md b/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-03-generate-personas.md
index 9a4a2285..c513da0d 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-03-generate-personas.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-03-generate-personas.md
@@ -412,16 +412,25 @@ For EACH persona (Primary, Secondary, Tertiary), create a comprehensive document
 
 ---
 
-### 12. The Battle Cry (PRIMARY especially)
+### 12. Transformation Journey (PRIMARY persona especially)
 
 ```markdown
-## The Battle Cry (For [Persona Name])
+## Transformation Journey
 
-**"[Insert battle cry from workshop]"**
+**Current State:** [Current challenges and limitations]
 
-This is [Persona]'s transformation: From [before] to [after].
+**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
diff --git a/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-05-quality-check.md b/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-05-quality-check.md
index 40fe5088..bc3d1c17 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-05-quality-check.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/document-generation/steps/step-05-quality-check.md
@@ -38,8 +38,8 @@
 
 **Across ALL documents:**
 
-- [ ] Battle cry appears in hub (00) and appropriate persona docs
 - [ ] 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
@@ -114,7 +114,7 @@
 
 **Verify hub has on-page summaries for:**
 
-- [ ] Battle cry displayed prominently
+- [ ] Transformation clearly stated
 - [ ] Flywheel explained (3 tiers)
 - [ ] Business Strategy section with key points
 - [ ] Each persona with profile + drivers visible
@@ -235,9 +235,7 @@ Once all checks pass, output:
 ✅ Language is empowering and organic
 ✅ All 6 driving forces have Product Promises/Answers
 ✅ Priority tiers consistent throughout
-✅ Battle cry present in appropriate docs
-
-**Battle Cry:** "[Insert battle cry]"
+✅ Transformation journey clearly described
 
 **Primary Target:** [Primary Persona Name]  
 **THE ENGINE:** [PRIMARY GOAL statement]
diff --git a/src/modules/wds/workflows/2-trigger-mapping/handover/instructions.md b/src/modules/wds/workflows/2-trigger-mapping/handover/instructions.md
new file mode 100644
index 00000000..15546400
--- /dev/null
+++ b/src/modules/wds/workflows/2-trigger-mapping/handover/instructions.md
@@ -0,0 +1,15 @@
+# Handover: Trigger Mapping → UX Design
+
+<critical>You are Saga the Analyst completing Phase 2 and preparing Phase 4</critical>
+
+<handover>
+
+<intro>
+<output>**Trigger Mapping Complete!** 🎉
+
+Let me prepare the comprehensive documentation and handover package for UX Design...</output>
+
+<action>Load and execute: steps/step-01-generate-all-docs.md</action>
+</intro>
+
+</handover>
diff --git a/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-01-finalize-hub.md b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-01-finalize-hub.md
new file mode 100644
index 00000000..e315c894
--- /dev/null
+++ b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-01-finalize-hub.md
@@ -0,0 +1,25 @@
+# Step 1: Generate All Trigger Map Documentation
+
+<critical>You are Saga - creating comprehensive trigger map documentation</critical>
+
+## Your Task
+
+Generate the complete trigger map documentation 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)
+
+## Execute Document Generation
+
+<action>Load and execute: ../document-generation/instructions.md</action>
+
+This will create all documents following the standard trigger map structure.
+
+---
+
+## What Happens Next
+
+<action>Once all documents generated, load and execute: step-02-add-cross-references.md</action>
+
diff --git a/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-02-add-cross-references.md b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-02-add-cross-references.md
new file mode 100644
index 00000000..34cd62d9
--- /dev/null
+++ b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-02-add-cross-references.md
@@ -0,0 +1,27 @@
+# Step 2: Add Cross-References
+
+<critical>You are Saga - ensuring document connectivity</critical>
+
+## Your Task
+
+Verify and add navigation links to ALL trigger map documents.
+
+## Links to Add
+
+**In each document:**
+- ← Back to 00-trigger-map.md
+- → Next document (if sequential)
+- Related documents section at bottom
+
+**Verify:**
+- All persona docs link to each other
+- All docs link back to hub
+- Hub links to all docs
+- Navigation is bidirectional
+
+---
+
+## What Happens Next
+
+<action>Once cross-references added, load and execute: step-03-quality-check.md</action>
+
diff --git a/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-03-quality-check.md b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-03-quality-check.md
new file mode 100644
index 00000000..010a71b3
--- /dev/null
+++ b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-03-quality-check.md
@@ -0,0 +1,25 @@
+# Step 3: Quality Check
+
+<critical>You are Saga - verifying completeness</critical>
+
+## Your Task
+
+Run final quality check on all trigger map documents.
+
+## 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)
+
+---
+
+## What Happens Next
+
+<action>Once quality verified, load and execute: step-04-create-handover-package.md</action>
+
diff --git a/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-04-create-handover-package.md b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-04-create-handover-package.md
new file mode 100644
index 00000000..5586e67b
--- /dev/null
+++ b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-04-create-handover-package.md
@@ -0,0 +1,73 @@
+# Step 4: Create Handover Package
+
+<critical>You are Saga - preparing handover for UX Design phase</critical>
+
+## Your Task
+
+Create summary package for the UX Designer (Freyja).
+
+---
+
+## Output to User
+
+<output>✅ **Trigger Map Phase Complete!**
+
+**All Documentation Created:**
+
+```
+docs/2-trigger-map/
+├── 00-trigger-map.md          ← Start here: Visual overview
+├── 01-Business-Goals.md
+├── 02-{{primary_persona}}.md
+├── 03-{{secondary_persona}}.md
+{{#if tertiary_persona}}
+├── 04-{{tertiary_persona}}.md
+{{/if}}
+├── 05-Key-Insights.md
+{{#if feature_impact_done}}
+└── 06-Feature-Impact.md
+{{/if}}
+```
+
+---
+
+**Handover Summary for UX Design:**
+
+**Primary Focus:**
+- **Who:** {{primary_persona_name}} ({{primary_persona_role}})
+- **Transformation:** {{transformation_summary}}
+
+**Must Address:**
+{{#each top_3_positive_drivers}}
+- ✅ {{this}}
+{{/each}}
+
+**Must Avoid:**
+{{#each top_3_negative_drivers}}
+- ❌ {{this}}
+{{/each}}
+
+{{#if feature_priority}}
+**Feature Priority:**
+1. {{feature_1}}
+2. {{feature_2}}
+3. {{feature_3}}
+{{else}}
+**Feature Priority:** Not yet analyzed (can run Feature Impact workshop anytime)
+{{/if}}
+
+**Design Implications:**
+- {{key_implication_1}}
+- {{key_implication_2}}
+- {{key_implication_3}}
+
+---
+
+**Ready for Phase 4: UX Design** 🎨</output>
+
+---
+
+## What Happens Next
+
+<action>Load and execute: step-05-provide-activation.md</action>
+
diff --git a/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-05-provide-activation.md b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-05-provide-activation.md
new file mode 100644
index 00000000..2302c4a2
--- /dev/null
+++ b/src/modules/wds/workflows/2-trigger-mapping/handover/steps/step-05-provide-activation.md
@@ -0,0 +1,64 @@
+# Step 5: Provide UX Design Activation
+
+<critical>You are Saga - transitioning to UX Design phase</critical>
+
+## Your Task
+
+Provide activation instructions for the UX Designer (Freyja) to begin UX Design.
+
+---
+
+## Output to User
+
+<output>**Ready to Start UX Design!** 🎨
+
+**To activate the UX Designer (Freyja):**
+
+**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 docs/2-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:**
+
+**Skip to Platform Requirements (Phase 3)?**
+If you need to define technical architecture first, you can activate the PM agent (Idunn) instead:
+```
+Load: getting-started/agent-activation/wds-idunn-pm.md
+```
+
+**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. 🎉</output>
+
+---
+
+## Handover Complete
+
+<action>Await user decision on next phase activation.</action>
+
diff --git a/src/modules/wds/workflows/2-trigger-mapping/instructions.md b/src/modules/wds/workflows/2-trigger-mapping/instructions.md
index 5df5c5fb..da490696 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/instructions.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/instructions.md
@@ -15,13 +15,15 @@ Trigger Mapping connects your business goals to user psychology. It answers:
 - **What** do they want to avoid (negative drivers)?
 - **Which** features matter most?
 
-We'll work through 5 focused workshops:
+We'll work through 4 core workshops, plus 1 optional workshop:
 
 1. **Business Goals** - Vision → SMART objectives
 2. **Target Groups** - Who are your key users?
 3. **Driving Forces** - What motivates and concerns them?
 4. **Prioritization** - What matters most?
-5. **Documentation** - Create comprehensive trigger map structure
+5. **Feature Impact** (Optional) - Which features serve priorities best?
+
+After workshops, I'll create comprehensive documentation with a visual trigger map.
 
 Each workshop builds on the previous. You can run them all together (60-90 min) or spread across sessions.
 
@@ -29,7 +31,7 @@ Ready to begin? 🎯</output>
 
 <ask>Would you like to:
 
-1. **Full session** - All 5 workshops now
+1. **Full session** - All 4 core workshops now (Feature Impact optional at end)
 2. **Workshop by workshop** - Start with Business Goals, continue later
 3. **Jump to specific workshop** - If you've done some already</ask>
 
@@ -47,7 +49,7 @@ Ready to begin? 🎯</output>
   2. Target Groups
   3. Driving Forces
   4. Prioritization
-  5. Documentation</ask>
+  5. Feature Impact</ask>
   <action>Jump to selected workshop</action>
 </check>
 </step>
@@ -69,48 +71,30 @@ Ready to begin? 🎯</output>
 
 <step n="5" goal="Run Workshop 4: Prioritization">
 <action>Load and execute: workshops/4-prioritization/instructions.md</action>
-<action>Store outputs: prioritized_groups, prioritized_drivers, battle_cry</action>
+<action>Store outputs: prioritized_groups, prioritized_drivers, focus_statement</action>
 </step>
 
-<step n="6" goal="Generate Trigger Map Documentation">
-<output>Excellent! Now I'll create your comprehensive Trigger Map documentation structure.
+<step n="5.5" goal="Optional: Feature Impact Workshop">
+<ask>Would you like to run the **Feature Impact workshop** now?
 
-This follows the WDS standard structure:
-- **00-trigger-map.md** - Navigation hub with diagram and summaries
-- **01-Business-Goals.md** - Detailed objectives and flywheel
-- **02-XX-Persona.md** - Individual detailed persona documents  
-- **0X-Key-Insights.md** - Strategic implications
+This is optional but valuable - it analyzes which features best serve your prioritized personas and goals, creating a scored priority list for design and development.</ask>
 
-Let me generate all documents now...</output>
+<check if="yes">
+  <action>Load and execute: workshops/5-feature-impact/instructions.md</action>
+  <action>Store feature_impact_analysis</action>
+</check>
 
-<action>Load and execute: document-generation/instructions.md</action>
+<check if="no">
+  <output>No problem! You can run Feature Impact later if needed. Proceeding to handover...</output>
+</check>
+</step>
 
-<output>✅ **Trigger Map Documentation Complete!**
+<step n="6" goal="Handover to UX Design Phase">
+<output>**All Workshops Complete!** 🎉
 
-**Created Structure:**
+Now let me prepare the handover to Phase 4: UX Design...</output>
 
-```
-2-trigger-map/
-├── 00-trigger-map.md          (Hub with Mermaid diagram & navigation)
-├── 01-Business-Goals.md        (Vision, objectives, flywheel)
-├── 02-[Primary Persona].md    (Detailed primary persona)
-├── 03-[Secondary Persona].md  (Detailed secondary persona)
-├── 04-[Tertiary Persona].md   (Detailed tertiary persona - if applicable)
-└── 05-Key-Insights.md         (Design implications & success factors)
-```
-
-**Key Features:**
-- ✅ Professional Mermaid diagram with light gray styling
-- ✅ Gold highlighting for PRIMARY GOAL
-- ✅ On-page summaries in trigger map hub
-- ✅ Detailed persona profiles with driving forces
-- ✅ Strategic relationships and flywheel
-- ✅ Design implications and success criteria
-- ✅ Cross-linked navigation
-
-**Your Battle Cry:** {{battle_cry}}
-
-Ready for Phase 3: Platform Requirements or Phase 4: UX Design! 🚀</output>
+<action>Load and execute: handover/instructions.md</action>
 </step>
 
 </workflow>
diff --git a/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/instructions.md b/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/instructions.md
index 3e5c4136..715cb0fe 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/instructions.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/instructions.md
@@ -2,38 +2,19 @@
 
 <critical>You are Saga the Analyst - creating visual strategic clarity</critical>
 
----
+<workflow>
 
-## Instructions
+<intro>
+**Generate Professional Mermaid Diagram**
 
-To generate a professional Mermaid trigger map diagram:
+This workflow creates a visual trigger map with:
+- Light gray professional styling
+- Gold-highlighted primary goal
+- Emoji-decorated nodes
+- Clear connections between goals, platform, personas, and driving forces
 
-**START HERE:** Load and follow `steps/step-01-initialize-structure.md`
+<action>Load and execute: steps/step-01-initialize-structure.md</action>
+</intro>
 
-Each step file contains:
-- Detailed instructions for that specific task
-- Examples and templates
-- Rules checklist
-- Link to next step
-
-**IMPORTANT:** Follow steps sequentially. Do NOT skip ahead. Each step builds on the previous one.
-
----
-
-## Step Sequence
-
-1. **Initialize Structure** → Set up Mermaid config and node IDs
-2. **Format Business Goals** → Create BG nodes with emojis
-3. **Format Platform** → Create central PLATFORM node
-4. **Format Target Groups** → Create TG persona nodes
-5. **Format Driving Forces** → Create DF nodes with ✅ and ❌
-6. **Create Connections** → Link all nodes properly
-7. **Apply Styling** → Add light gray professional styling
-8. **Quality Check** → Verify everything meets standards
-
----
-
-## Begin
-
-→ **[Start: Step 01 - Initialize Structure](steps/step-01-initialize-structure.md)**
+</workflow>
 
diff --git a/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/steps/step-03-format-platform.md b/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/steps/step-03-format-platform.md
index 3830df8c..92ac8a90 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/steps/step-03-format-platform.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/mermaid-diagram/steps/step-03-format-platform.md
@@ -22,7 +22,7 @@ PLATFORM["<br/>EMOJI PRODUCT NAME<br/><br/>Category or tagline<br/><br/>Transfor
 3. Blank line (`<br/><br/>`)
 4. Category or tagline
 5. Blank line (`<br/><br/>`)
-6. Transformation statement (the "battle cry") - break across multiple lines
+6. Transformation/value statement - break across multiple lines
 7. End with `<br/><br/>` (bottom padding)
 
 ---
@@ -46,11 +46,11 @@ PLATFORM["<br/>EMOJI PRODUCT NAME<br/><br/>Category or tagline<br/><br/>Transfor
 - Be emotionally compelling
 - Be specific about the transformation
 - Span 3-5 lines for readability
-- Connect to the battle cry
+- Connect to the strategic vision and transformation goals
 
 **Example:**
 ```
-Transform designers from overwhelmed<br/>task-doers into empowered strategic<br/>leaders who shoulder complexity<br/>as a calling, not a burden
+Transform users from frustrated<br/>manual processors into confident<br/>automated workflow managers<br/>who scale without stress
 ```
 
 ---
diff --git a/src/modules/wds/workflows/2-trigger-mapping/micro-instructions-mermaid-diagram.md b/src/modules/wds/workflows/2-trigger-mapping/micro-instructions-mermaid-diagram.md
index cd47582e..ec794eac 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/micro-instructions-mermaid-diagram.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/micro-instructions-mermaid-diagram.md
@@ -59,7 +59,7 @@ PLATFORM["<br/>🎨 PLATFORM NAME<br/><br/>Tagline or category<br/><br/>Transfor
 - Single node ID: PLATFORM
 - Include platform emoji
 - Show tagline/category
-- Include transformation statement (the "battle cry")
+- Include transformation/value statement
 - Break long text into multiple lines
 
 ### 6. Target Group Nodes
diff --git a/src/modules/wds/workflows/2-trigger-mapping/templates/feature-impact.template.md b/src/modules/wds/workflows/2-trigger-mapping/templates/feature-impact.template.md
index 67259960..b0fadf38 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/templates/feature-impact.template.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/templates/feature-impact.template.md
@@ -43,5 +43,5 @@
 
 ---
 
-_Generated by Whiteport Design Studio_  
+_Generated with Whiteport Design Studio framework_  
 _Strategic input for Phase 4: UX Design and Phase 6: PRD/Development_
diff --git a/src/modules/wds/workflows/2-trigger-mapping/templates/trigger-map.template.md b/src/modules/wds/workflows/2-trigger-mapping/templates/trigger-map.template.md
index 42c19854..a7404cf9 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/templates/trigger-map.template.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/templates/trigger-map.template.md
@@ -4,7 +4,7 @@
 
 **Created:** {{date}}
 **Author:** {{user_name}}
-**Methodology:** Based on Effect Mapping (Balic & Domingues), adapted by WDS
+**Methodology:** Based on Effect Mapping (Balic & Domingues), adapted for WDS framework
 
 ---
 
@@ -165,5 +165,5 @@ This Trigger Map Poster provides a quick reference. For detailed work:
 
 ---
 
-_Generated by Whiteport Design Studio_
-_Trigger Mapping methodology credits: Effect Mapping by Mijo Balic & Ingrid Domingues (inUse), adapted with negative driving forces by WDS_
+_Generated with Whiteport Design Studio framework_
+_Trigger Mapping methodology credits: Effect Mapping by Mijo Balic & Ingrid Domingues (inUse), adapted with negative driving forces_
diff --git a/src/modules/wds/workflows/2-trigger-mapping/workshops/4-prioritization/instructions.md b/src/modules/wds/workflows/2-trigger-mapping/workshops/4-prioritization/instructions.md
index bd1d5094..52ca7ce9 100644
--- a/src/modules/wds/workflows/2-trigger-mapping/workshops/4-prioritization/instructions.md
+++ b/src/modules/wds/workflows/2-trigger-mapping/workshops/4-prioritization/instructions.md
@@ -195,7 +195,7 @@ Remember: negative drivers often have more weight (loss aversion).</ask>
 
 This focus means saying "not yet" to some things. That's the power of prioritization.
 
-Next, we'll analyze which features best serve these priorities.</output>
+Next, we'll optionally analyze which features best serve these priorities.</output>
 
 <action>Store prioritized_groups, prioritized_drivers, focus_statement</action>
 </step>
diff --git a/src/modules/wds/workflows/3-prd-platform/handover/instructions.md b/src/modules/wds/workflows/3-prd-platform/handover/instructions.md
new file mode 100644
index 00000000..6af9ab7d
--- /dev/null
+++ b/src/modules/wds/workflows/3-prd-platform/handover/instructions.md
@@ -0,0 +1,16 @@
+# Handover: Platform Requirements → PRD/Development
+
+<critical>You are Idunn the PM completing Phase 3 and preparing Phase 6</critical>
+
+<handover>
+
+<intro>
+<output>**Platform Requirements Complete!** ⚔️
+
+Let me prepare the complete design handover to development...</output>
+
+<action>Load and execute: steps/step-01-compile-deliverables.md</action>
+</intro>
+
+</handover>
+
diff --git a/src/modules/wds/workflows/3-prd-platform/handover/steps/step-01-compile-deliverables.md b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-01-compile-deliverables.md
new file mode 100644
index 00000000..a212426c
--- /dev/null
+++ b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-01-compile-deliverables.md
@@ -0,0 +1,38 @@
+# Step 1: Compile All Design Deliverables
+
+<critical>You are Idunn - gathering complete design package</critical>
+
+## Your Task
+
+Compile all deliverables from Phases 1-4.
+
+## What to Compile
+
+**Phase 1: Product Brief**
+- Vision and positioning
+- Target users
+- Success criteria
+
+**Phase 2: Trigger Mapping**
+- Business goals
+- Personas with driving forces
+- Feature priorities
+
+**Phase 4: UX Design**
+- Scenario designs
+- Conceptual specifications
+- User flows
+- Design system (if created)
+
+**Phase 3: Platform Requirements**
+- Architecture document
+- Data models
+- API specifications
+- Technical constraints
+
+---
+
+## What Happens Next
+
+<action>Once compiled, load and execute: step-02-extract-epic-structure.md</action>
+
diff --git a/src/modules/wds/workflows/3-prd-platform/handover/steps/step-02-extract-epic-structure.md b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-02-extract-epic-structure.md
new file mode 100644
index 00000000..eace35e2
--- /dev/null
+++ b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-02-extract-epic-structure.md
@@ -0,0 +1,30 @@
+# Step 2: Extract Epic Structure
+
+<critical>You are Idunn - identifying development epics</critical>
+
+## Your Task
+
+Analyze scenarios and features to identify natural epic groupings.
+
+## Epic Identification
+
+Group by:
+- User journey phases
+- Feature clusters
+- Technical dependencies
+- MVP vs. Phase 2 priorities
+
+## Suggested Structure
+
+For each epic, note:
+- Epic name
+- Scenarios included
+- Estimated complexity
+- Dependencies on other epics
+
+---
+
+## What Happens Next
+
+<action>Once epics identified, load and execute: step-03-prepare-prd-materials.md</action>
+
diff --git a/src/modules/wds/workflows/3-prd-platform/handover/steps/step-03-prepare-prd-materials.md b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-03-prepare-prd-materials.md
new file mode 100644
index 00000000..8e50bba9
--- /dev/null
+++ b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-03-prepare-prd-materials.md
@@ -0,0 +1,31 @@
+# Step 3: Prepare PRD Materials
+
+<critical>You are Idunn - creating development roadmap</critical>
+
+## Your Task
+
+Prepare materials for Product Requirements Document (PRD) creation.
+
+## PRD Components
+
+- Executive summary
+- Feature overview by epic
+- User stories from scenarios
+- Acceptance criteria from specs
+- Technical requirements from platform docs
+- Success metrics from trigger map
+
+## Development Readiness
+
+Verify:
+- ✅ All scenarios have conceptual specs
+- ✅ Platform requirements documented
+- ✅ Dependencies identified
+- ✅ MVP scope clear
+
+---
+
+## What Happens Next
+
+<action>Once PRD materials ready, load and execute: step-04-create-handover-package.md</action>
+
diff --git a/src/modules/wds/workflows/3-prd-platform/handover/steps/step-04-create-handover-package.md b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-04-create-handover-package.md
new file mode 100644
index 00000000..a2b9b2a3
--- /dev/null
+++ b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-04-create-handover-package.md
@@ -0,0 +1,57 @@
+# Step 4: Create Complete Handover Package
+
+<critical>You are Idunn - preparing handover for development</critical>
+
+## Your Task
+
+Create comprehensive summary for development team.
+
+---
+
+## Output to User
+
+<output>✅ **Complete Design Package Ready for Development**
+
+**Design Phase Deliverables:**
+
+**1. Strategic Foundation:**
+- Product Brief (Vision, positioning, success criteria)
+- Trigger Map (Personas, driving forces, priorities)
+- Feature Impact Analysis ({{feature_count}} features scored)
+
+**2. UX Design:**
+- {{scenario_count}} Scenario designs
+- Conceptual specifications (WHAT + WHY + WHAT NOT TO DO)
+- User flows and interactions
+- Design system foundations (if created)
+
+**3. Platform Requirements:**
+- Technical architecture
+- {{data_model_count}} Data models
+- {{api_count}} API endpoints defined
+- Third-party integrations documented
+
+**4. Development Roadmap:**
+- {{epic_count}} Epics identified
+- MVP scope defined ({{mvp_feature_count}} features)
+- Dependencies mapped
+
+---
+
+**What Happens Next:**
+
+The **BMM (BMAD Method Module)** development agents will:
+
+1. **Epic Breakdown** - Transform design epics into technical stories
+2. **Story Creation** - Create detailed user stories with acceptance criteria
+3. **Implementation Guidance** - Your conceptual specs become super-prompts
+4. **Quality Assurance** - Test against design intent
+
+Your design thinking is preserved in conceptual specifications that guide every line of code.</output>
+
+---
+
+## What Happens Next
+
+<action>Load and execute: step-05-provide-activation.md</action>
+
diff --git a/src/modules/wds/workflows/3-prd-platform/handover/steps/step-05-provide-activation.md b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-05-provide-activation.md
new file mode 100644
index 00000000..b117bfc1
--- /dev/null
+++ b/src/modules/wds/workflows/3-prd-platform/handover/steps/step-05-provide-activation.md
@@ -0,0 +1,68 @@
+# Step 5: Provide Development Phase Activation
+
+<critical>You are Idunn - guiding to development phase</critical>
+
+## Your Task
+
+Provide clear instructions for activating development with BMM agents.
+
+---
+
+## Output to User
+
+<output>**Ready for Phase 6: PRD & Development!** 💻
+
+**To begin development:**
+
+**Option 1: BMM Workflow (Recommended)**
+```
+Load BMM workflow for epic breakdown and story creation
+[Specific BMM path to be added]
+```
+
+**Option 2: Direct PRD Creation**
+```
+Create PRD document from prepared materials
+Then hand off to development team
+```
+
+**What BMM Will Do:**
+
+1. **Epic Breakdown** - Break design into implementable chunks
+2. **Story Writing** - Create user stories from your scenarios
+3. **Sprint Planning** - Organize work into development sprints
+4. **Implementation** - Your conceptual specs guide coding
+5. **Testing** - Validate against design intent
+
+**Estimated Time:** Varies by project scope
+- PRD Creation: 4-8 hours
+- Development: Multiple sprints
+
+**Key Success Factor:**
+
+Your **conceptual specifications** (WHAT + WHY + WHAT NOT TO DO) ensure:
+- Developers understand design intent
+- AI can generate code that matches vision
+- QA knows what "correct" means
+- Design thinking survives to production
+
+---
+
+**Design Phase Complete!** 🎉
+
+You've created a complete design foundation that preserves your strategic thinking through to implementation.
+
+Would you like to proceed to development now, or is there any design work you'd like to revisit first?</output>
+
+---
+
+## Handover Complete
+
+<action>Await user decision.
+
+Note: User may also choose to:
+- Go back and refine designs
+- Add more scenarios
+- Update platform requirements
+- Or proceed to development</action>
+
diff --git a/src/modules/wds/workflows/4-ux-design/handover/instructions.md b/src/modules/wds/workflows/4-ux-design/handover/instructions.md
new file mode 100644
index 00000000..098edd74
--- /dev/null
+++ b/src/modules/wds/workflows/4-ux-design/handover/instructions.md
@@ -0,0 +1,15 @@
+# Handover: UX Design → Design Delivery (Incremental)
+
+<critical>You are Freyja the Designer preparing an incremental design delivery</critical>
+
+<handover>
+
+<intro>
+<output>**Design Work Ready for Development!** 🎨
+
+Let me prepare this design delivery for implementation...</output>
+
+<action>Load and execute: steps/step-01-identify-delivery-scope.md</action>
+</intro>
+
+</handover>
diff --git a/src/modules/wds/workflows/4-ux-design/handover/steps/step-01-analyze-scenarios.md b/src/modules/wds/workflows/4-ux-design/handover/steps/step-01-analyze-scenarios.md
new file mode 100644
index 00000000..5dff7753
--- /dev/null
+++ b/src/modules/wds/workflows/4-ux-design/handover/steps/step-01-analyze-scenarios.md
@@ -0,0 +1,32 @@
+# Step 1: Analyze Scenarios for Technical Needs
+
+<critical>You are Freyja - extracting platform requirements from designs</critical>
+
+## Your Task
+
+Silently review all scenarios and extract technical implications.
+
+## What to Extract
+
+- Data models needed
+- API endpoints required
+- Third-party services mentioned
+- Authentication/authorization needs
+- File storage requirements
+- Real-time features
+- Integration points
+- Performance considerations
+
+## Analysis
+
+For each scenario, identify:
+- What data must be stored?
+- What external services are needed?
+- What technical complexity exists?
+
+---
+
+## What Happens Next
+
+<action>Once analysis complete, load and execute: step-02-create-summary.md</action>
+
diff --git a/src/modules/wds/workflows/4-ux-design/handover/steps/step-01-identify-delivery-scope.md b/src/modules/wds/workflows/4-ux-design/handover/steps/step-01-identify-delivery-scope.md
new file mode 100644
index 00000000..b35b2db1
--- /dev/null
+++ b/src/modules/wds/workflows/4-ux-design/handover/steps/step-01-identify-delivery-scope.md
@@ -0,0 +1,61 @@
+# Step 1: Identify Delivery Scope
+
+<critical>You are Freyja - defining what's ready for implementation</critical>
+
+## Your Task
+
+Identify what design work is ready to hand off for development.
+
+## Delivery Unit Options
+
+**Option A: Single Scenario**
+- One complete user journey
+- All pages in that scenario
+- All specifications complete
+
+**Option B: Page or Feature**
+- One page with all states
+- Complete conceptual specifications
+- Can be implemented independently
+
+**Option C: User Flow Segment**
+- Part of a larger journey
+- Logical chunk (e.g., "registration flow")
+- Has clear entry and exit points
+
+## Readiness Check
+
+Verify the delivery unit has:
+- ✅ All pages/screens designed
+- ✅ Conceptual specifications (WHAT + WHY + WHAT NOT TO DO)
+- ✅ Interaction states defined
+- ✅ Error states documented
+- ✅ Dependencies identified
+
+---
+
+## Output to User
+
+<output>**Ready to Create Design Delivery Package**
+
+**Delivery Scope:** {{scope_type}}
+- {{delivery_name}}
+
+**Contents:**
+{{#each included_items}}
+- {{this}}
+{{/each}}
+
+**This delivery includes:**
+- {{page_count}} pages/screens
+- {{specification_count}} conceptual specifications
+- {{interaction_count}} key interactions
+
+Is this the right scope for this delivery, or would you like to adjust?</output>
+
+---
+
+## What Happens Next
+
+<action>Once scope confirmed, load and execute: step-02-extract-technical-needs.md</action>
+
diff --git a/src/modules/wds/workflows/4-ux-design/handover/steps/step-02-create-summary.md b/src/modules/wds/workflows/4-ux-design/handover/steps/step-02-create-summary.md
new file mode 100644
index 00000000..82da8ffb
--- /dev/null
+++ b/src/modules/wds/workflows/4-ux-design/handover/steps/step-02-create-summary.md
@@ -0,0 +1,59 @@
+# Step 2: Create Handover Summary
+
+<critical>You are Freyja - preparing handover package for Idunn</critical>
+
+## Your Task
+
+Create a concise summary of UX designs for Platform Requirements phase.
+
+---
+
+## Output to User
+
+<output>✅ **Handover Package Ready for Platform Requirements**
+
+**UX Design Summary:**
+
+**Scenarios Designed:** {{scenario_count}}
+
+**Key Interactions:**
+{{#each key_interactions}}
+- {{this}}
+{{/each}}
+
+**Data Requirements Identified:**
+{{#each data_models}}
+- {{this.name}} - {{this.purpose}}
+{{/each}}
+
+**Third-Party Services Needed:**
+{{#each services}}
+- {{this}}
+{{/each}}
+
+**Integration Points:**
+{{#each integrations}}
+- {{this}}
+{{/each}}
+
+---
+
+**What Idunn Will Do Next:**
+
+Idunn the PM will analyze your UX designs and define **Platform Requirements (Phase 3)**.
+
+Through structured analysis, you'll define:
+- **Technical architecture** needed to support your designs
+- **Data models** and relationships
+- **API specifications** for front-end/back-end communication
+- **Third-party integrations** and dependencies
+- **Technical constraints** and decisions
+
+This ensures your designs are implementable and the development team has clear technical direction.</output>
+
+---
+
+## What Happens Next
+
+<action>Load and execute: step-03-provide-activation.md</action>
+
diff --git a/src/modules/wds/workflows/4-ux-design/handover/steps/step-02-extract-technical-needs.md b/src/modules/wds/workflows/4-ux-design/handover/steps/step-02-extract-technical-needs.md
new file mode 100644
index 00000000..ddf87a37
--- /dev/null
+++ b/src/modules/wds/workflows/4-ux-design/handover/steps/step-02-extract-technical-needs.md
@@ -0,0 +1,33 @@
+# Step 2: Extract Technical Needs
+
+<critical>You are Freyja - identifying what development needs for this delivery</critical>
+
+## Your Task
+
+Extract technical requirements specific to THIS delivery.
+
+## What to Extract
+
+**For This Delivery Only:**
+- Data models needed
+- API endpoints required
+- Third-party services (if any)
+- Authentication needs
+- File/media handling
+- State management complexity
+
+**Dependencies:**
+- What must exist first?
+- What can be mocked/stubbed?
+- What blocks implementation?
+
+## Analysis
+
+Keep it focused on THIS delivery, not the entire project.
+
+---
+
+## What Happens Next
+
+<action>Once technical needs extracted, load and execute: step-03-create-delivery-package.md</action>
+
diff --git a/src/modules/wds/workflows/4-ux-design/handover/steps/step-03-create-delivery-package.md b/src/modules/wds/workflows/4-ux-design/handover/steps/step-03-create-delivery-package.md
new file mode 100644
index 00000000..dfc99aa9
--- /dev/null
+++ b/src/modules/wds/workflows/4-ux-design/handover/steps/step-03-create-delivery-package.md
@@ -0,0 +1,79 @@
+# Step 3: Create Design Delivery Package
+
+<critical>You are Freyja - packaging design for development</critical>
+
+## Your Task
+
+Create a complete delivery package that development can implement.
+
+---
+
+## Output to User
+
+<output>✅ **Design Delivery Package Ready**
+
+**Delivery:** {{delivery_name}}
+**Type:** {{scope_type}} (Scenario / Page / Flow Segment)
+**Priority:** {{priority}} (MVP / Phase 2 / Enhancement)
+
+---
+
+**Design Deliverables:**
+
+**1. Conceptual Specifications:**
+{{#each specifications}}
+- {{this.page}} - {{this.summary}}
+{{/each}}
+
+**2. Visual Designs:**
+{{#each designs}}
+- {{this.name}} ({{this.states}} states)
+{{/each}}
+
+**3. Interactions:**
+{{#each interactions}}
+- {{this.description}}
+{{/each}}
+
+---
+
+**Technical Requirements for This Delivery:**
+
+**Data Models:**
+{{#each data_models}}
+- {{this}}
+{{/each}}
+
+**API Endpoints:**
+{{#each apis}}
+- {{this}}
+{{/each}}
+
+**Dependencies:**
+{{#each dependencies}}
+- {{this}}
+{{/each}}
+
+**Can Start:** {{can_start_now ? "Yes, immediately" : "No, dependencies needed"}}
+
+---
+
+**Implementation Guidance:**
+
+Your conceptual specifications are SUPER-PROMPTS - they contain:
+- **WHAT** to build (precise functionality)
+- **WHY** it works this way (design rationale)
+- **WHAT NOT TO DO** (boundaries and mistakes to avoid)
+
+These specs enable AI-assisted development while preserving your design intent.
+
+**Estimated Development Time:** {{estimated_dev_time}}
+
+**Acceptance Criteria:** {{acceptance_summary}}</output>
+
+---
+
+## What Happens Next
+
+<action>Load and execute: step-04-log-delivery.md</action>
+
diff --git a/src/modules/wds/workflows/4-ux-design/handover/steps/step-03-provide-activation.md b/src/modules/wds/workflows/4-ux-design/handover/steps/step-03-provide-activation.md
new file mode 100644
index 00000000..13bd31aa
--- /dev/null
+++ b/src/modules/wds/workflows/4-ux-design/handover/steps/step-03-provide-activation.md
@@ -0,0 +1,47 @@
+# Step 3: Provide Next Phase Activation
+
+<critical>You are Freyja - guiding to Phase 3</critical>
+
+## Your Task
+
+Provide clear instructions for activating Phase 3: Platform Requirements.
+
+---
+
+## Output to User
+
+<output>**Ready for Phase 3: Platform Requirements!** ⚔️
+
+**To begin Platform Requirements with Idunn:**
+
+**Option 1: Activate Idunn**
+```
+Load: agent-activation/wds-idunn-pm.md
+```
+
+**Option 2: Direct Workflow**
+```
+Load: workflows/3-prd-platform/instructions.md
+```
+
+Idunn will review your UX designs and guide you through platform analysis.
+
+**Estimated Time:** 2-4 hours
+
+**What You'll Create:**
+- Platform architecture document
+- Data model specifications
+- API endpoint definitions
+- Technical constraints documentation
+- Third-party service requirements
+
+**Note:** Platform Requirements can also be done BEFORE UX Design if you prefer to establish technical constraints first. We're doing it after because your designs inform what's needed.
+
+Would you like to proceed to Platform Requirements now, or take a break and continue later?</output>
+
+---
+
+## Handover Complete
+
+<action>Await user decision to proceed or pause.</action>
+
diff --git a/src/modules/wds/workflows/4-ux-design/handover/steps/step-04-log-delivery.md b/src/modules/wds/workflows/4-ux-design/handover/steps/step-04-log-delivery.md
new file mode 100644
index 00000000..dcb0de7a
--- /dev/null
+++ b/src/modules/wds/workflows/4-ux-design/handover/steps/step-04-log-delivery.md
@@ -0,0 +1,41 @@
+# Step 4: Log Design Delivery
+
+<critical>You are Freyja - tracking design deliveries</critical>
+
+## Your Task
+
+Log this delivery to track progress and maintain continuity.
+
+## Create/Update Delivery Log
+
+**File:** `4-ux-design/design-deliveries.md`
+
+Add entry:
+```markdown
+## Delivery {{number}}: {{delivery_name}}
+
+**Date:** {{date}}
+**Type:** {{scope_type}}
+**Status:** Ready for Development
+**Priority:** {{priority}}
+
+**Contents:**
+- {{contents_summary}}
+
+**Development Status:** Not Started
+**Link:** [Delivery Package](path/to/package)
+```
+
+## Benefits of Logging
+
+- Track what's been delivered
+- See what's in development
+- Know what's left to design
+- Maintain project overview
+
+---
+
+## What Happens Next
+
+<action>Once logged, load and execute: step-05-provide-activation.md</action>
+
diff --git a/src/modules/wds/workflows/4-ux-design/handover/steps/step-05-provide-activation.md b/src/modules/wds/workflows/4-ux-design/handover/steps/step-05-provide-activation.md
new file mode 100644
index 00000000..fc7fce15
--- /dev/null
+++ b/src/modules/wds/workflows/4-ux-design/handover/steps/step-05-provide-activation.md
@@ -0,0 +1,75 @@
+# Step 5: Provide Development Activation
+
+<critical>You are Freyja - guiding to implementation</critical>
+
+## Your Task
+
+Provide instructions for implementing THIS delivery.
+
+---
+
+## Output to User
+
+<output>**Design Delivery {{number}} Ready for Implementation!** 🚀
+
+**To implement this delivery:**
+
+**Option 1: BMM Development Agent**
+```
+Load BMM agent for story creation and implementation
+Provide: Design Delivery {{number}} package
+```
+
+**Option 2: Hand to Development Team**
+```
+Share the delivery package with your development team
+All specifications are implementation-ready
+```
+
+**Option 3: AI-Assisted Implementation**
+```
+Use conceptual specifications as super-prompts for AI code generation
+Each spec contains WHAT + WHY + WHAT NOT TO DO
+```
+
+---
+
+**Development Workflow:**
+
+1. **Review Specifications** - Understand design intent
+2. **Implement Pages** - Build according to specs
+3. **Handle Edge Cases** - Specs include error states
+4. **Test Against Criteria** - Verify acceptance criteria
+5. **Demo** - Show working feature
+
+**Parallel Work:**
+
+While this delivery is in development, you can continue designing:
+- Next scenario
+- Additional pages
+- Future features
+
+This enables **continuous delivery** - design, implement, deploy in rapid cycles.
+
+---
+
+**Ready to Continue?**
+
+Would you like to:
+1. **Continue designing** - Work on next scenario/feature
+2. **Create another delivery** - Package more completed work
+3. **Review deliveries** - See what's been handed off
+4. **Pause** - Take a break</output>
+
+---
+
+## Delivery Complete
+
+<action>Await user decision.
+
+User can:
+- Continue designing (return to UX workflow)
+- Create another delivery (run this handover again)
+- Monitor development progress
+- Pause and resume later</action>
+