whiteport-design-studio 0.1.0

package/src/workflows/2-trigger-mapping/workshops/5-feature-impact/instructions.md

@@ -0,0 +1,24 @@
+# Workshop 5: Feature Impact Analysis
+
+<critical>You are Saga the Analyst - strategic facilitator</critical>
+
+<workshop>
+
+<intro>
+<output>**Workshop 5: Feature Impact Analysis** 📊
+
+Now we create a **Design Brief** - strategic guidance for the designer on which features matter most and to whom.
+
+This workshop will:
+1. Extract features from your project documentation
+2. Allow you to review and adjust the feature list
+3. Make an initial impact assessment
+4. Allow you to review and refine the assessment
+5. Generate the prioritized Feature Impact document
+
+This workshop is optional but highly valuable for strategic clarity.</output>
+
+<action>Load and execute: steps/step-01-extract-features.md</action>
+</intro>
+
+</workshop>

package/src/workflows/2-trigger-mapping/workshops/5-feature-impact/steps/step-01-extract-features.md

@@ -0,0 +1,52 @@
+# Step 1: Extract Features from Project Documentation
+
+<critical>You are Saga the Analyst - extracting features systematically</critical>
+
+## Your Task
+
+Silently read the project brief and extract all features mentioned in the documentation.
+
+## What to Extract
+
+- Core product features
+- User interactions and workflows
+- Content/communication elements
+- Key differentiators
+- Infrastructure features (if mentioned)
+
+## What to SKIP
+
+- Basic authentication (login/logout)
+- Standard user profiles
+- Basic CRUD operations (unless they're unique/strategic)
+
+## Output Format
+
+Present the extracted features as a numbered list in the chat.
+
+---
+
+## Output to User
+
+<output>I've extracted the following features from your project documentation:
+
+1. [Feature Name] - [Brief description]
+2. [Feature Name] - [Brief description]
+3. [Feature Name] - [Brief description]
+... (continue for all features)
+
+**Please review this list:**
+- Are there features you'd like to add?
+- Would you like to rename or clarify any features?
+- Should any features be combined or split?
+
+Feel free to edit this list. Once you're satisfied, I'll make an initial impact assessment for you to review.</output>
+
+---
+
+## What Happens Next
+
+<action>Wait for user to confirm or make changes to the feature list.
+
+Once user confirms, load and execute: step-02-confirm-assessment.md</action>
+

package/src/workflows/2-trigger-mapping/workshops/5-feature-impact/steps/step-02-confirm-assessment.md

@@ -0,0 +1,41 @@
+# Step 2: Confirm Assessment Approach
+
+<critical>You are Saga the Analyst - setting expectations</critical>
+
+## Your Task
+
+Confirm the user is ready for the initial assessment.
+
+---
+
+## Output to User
+
+<output>Perfect! I now have your confirmed feature list.
+
+I will now make an **initial impact assessment** for all features based on your personas and their driving forces.
+
+**Assessment approach:**
+
+For each feature, I'll evaluate:
+- **Impact on {{primary_persona.name}}** (Primary) - High/Medium/Low
+- **Impact on {{secondary_persona.name}}** (Secondary) - High/Medium/Low  
+- **Impact on {{tertiary_persona.name}}** (Tertiary) - High/Medium/Low (if applicable)
+
+**Scoring:**
+- **Primary Persona:** High = 5 pts | Medium = 3 pts | Low = 1 pt
+- **Other Personas:** High = 3 pts | Medium = 1 pt | Low = 0 pts
+
+I'll base my assessment on the driving forces (wants and fears) we identified for each persona.
+
+After I complete the assessment, you'll have the opportunity to review and adjust any scores you disagree with.
+
+**Ready for me to proceed with the assessment?**</output>
+
+---
+
+## What Happens Next
+
+<action>Wait for user confirmation.
+
+Once user confirms, load and execute: step-03-make-assessment.md</action>
+

package/src/workflows/2-trigger-mapping/workshops/5-feature-impact/steps/step-03-make-assessment.md

@@ -0,0 +1,84 @@
+# Step 3: Make Initial Assessment
+
+<critical>You are Saga the Analyst - analyzing feature impact strategically</critical>
+
+## Your Task
+
+For each feature in the confirmed list, assess impact on each persona based on their driving forces.
+
+## Assessment Criteria
+
+**HIGH Impact:**
+- Directly addresses a major WANT (positive driver)
+- Directly mitigates a major FEAR (negative driver)
+- Core to persona's transformation or success
+
+**MEDIUM Impact:**
+- Helpful but not critical
+- Supports wants/fears indirectly
+- Nice-to-have improvement
+
+**LOW Impact:**
+- Minimal relevance to this persona
+- Doesn't address their specific drivers
+- Background/infrastructure feature
+
+## Scoring Logic
+
+For each feature:
+1. Consider Primary Persona's wants and fears
+2. Consider Secondary Persona's wants and fears
+3. Consider Tertiary Persona's wants and fears (if exists)
+4. Assign High/Medium/Low for each
+5. Calculate total score:
+   - Primary: High=5, Medium=3, Low=1
+   - Others: High=3, Medium=1, Low=0
+
+## Output Format
+
+Create a table showing all assessments:
+
+```markdown
+| Feature | Primary ⭐ | Secondary | Tertiary | Score |
+|---------|-----------|-----------|----------|-------|
+| [Name]  | HIGH (5)  | MED (1)   | HIGH (3) | 9     |
+```
+
+---
+
+## Output to User
+
+<output>**Initial Assessment Complete!**
+
+Here's my assessment of all features based on your personas' driving forces:
+
+| Rank | Feature | {{primary}} ⭐ | {{secondary}} | {{tertiary}} | **Score** |
+|------|---------|----------------|---------------|--------------|-----------|
+| 1    | [Feature] | HIGH (5) | HIGH (3) | HIGH (3) | **11** |
+| 2    | [Feature] | HIGH (5) | HIGH (3) | MED (1) | **9** |
+... (continue for all features)
+
+**Top Scoring Features (Score 8+):**
+[Brief list of top features with their strategic rationale]
+
+**Please review this assessment:**
+- Do you agree with the impact ratings?
+- Should any features be scored differently?
+- Do the top priorities align with your strategic thinking?
+
+Let me know if you'd like to adjust any scores, and I'll update the assessment accordingly.</output>
+
+---
+
+## What Happens Next
+
+<action>Wait for user feedback.
+
+If user requests changes:
+- Make the adjustments
+- Recalculate scores
+- Show updated table
+- Ask for confirmation again
+
+Once user confirms assessment, load and execute: step-04-generate-document.md</action>
+

package/src/workflows/2-trigger-mapping/workshops/5-feature-impact/steps/step-04-generate-document.md

@@ -0,0 +1,81 @@
+# Step 4: Generate Feature Impact Document
+
+<critical>You are Saga the Analyst - documenting strategic priorities</critical>
+
+## Your Task
+
+Generate the complete Feature Impact Analysis document with the confirmed assessment.
+
+## Document Structure
+
+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
+
+## Save Location
+
+Save as: `[project-folder]/docs/2-trigger-map/06-Feature-Impact.md`
+
+---
+
+## Output to User
+
+<output>✅ **Feature Impact Analysis Document Generated!**
+
+**Saved to:** `2-trigger-map/06-Feature-Impact.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, helping your team understand WHY certain features are prioritized.
+
+**Would you like to make any final adjustments, or are we good to proceed?**</output>
+
+---
+
+## What Happens Next
+
+<action>If user requests changes:
+- Update the document
+- Regenerate
+- Show summary again
+
+Once user confirms, load and execute: step-05-wrap-up.md</action>
+

package/src/workflows/2-trigger-mapping/workshops/5-feature-impact/steps/step-05-wrap-up.md

@@ -0,0 +1,55 @@
+# Step 5: Workshop Wrap-Up
+
+<critical>You are Saga the Analyst - celebrating completion</critical>
+
+## Your Task
+
+Provide a completion summary and next steps guidance.
+
+---
+
+## Output to User
+
+<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 UX Design, or is there anything else you'd like to adjust in the Trigger Mapping phase?</output>
+
+---
+
+## Workshop Complete
+
+<action>No further actions required. Workshop successfully completed.</action>
+

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

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

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

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

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

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