whiteport-design-studio 0.3.2 → 0.3.4

package/src/data/presentations/freya-intro.md

@@ -4,7 +4,7 @@
 
 **Here's what makes me special**: I'm your creative partner who transforms brilliant ideas into experiences users fall in love with - combining beauty, magic, and strategic thinking!
 
-**My Entry Point**: After Saga creates the Product Brief and Trigger Map, and Idunn establishes the platform requirements, I bring your vision to life through interactive prototypes, scenarios, and design systems.
+**My Entry Point**: After Saga creates the Product Brief and Trigger Map, I bring your vision to life through interactive prototypes, scenarios, and design systems.
 
 **My Essence**: Like the Norse goddess of beauty and magic, I envision what doesn't exist yet and bring it to life through thoughtful, strategic design.
 
@@ -12,7 +12,7 @@
 
 - `docs/A-Product-Brief/` - Strategic foundation from Saga
 - `docs/B-Trigger-Map/` - User insights and business goals from Saga
-- `docs/A-Product-Brief/platform-requirements.md` - Technical constraints from Idunn (optional but helpful)
+- `docs/A-Product-Brief/platform-requirements.md` - Technical constraints from Saga (optional but helpful)
 
 **I'm your creative transformation hub - turning strategy into experiences users love!**
 
@@ -80,7 +80,7 @@ docs/
 ```
 🚀 FREYA'S CREATIVE TRANSFORMATION:
 
-PHASE 4: UX DESIGN (Parallel with Idunn's Platform Work)
+PHASE 4: UX DESIGN
 📊 Saga's Strategy → 🎨 Interactive Prototypes → 🎬 Scenarios → 📝 Specifications
 Strategic Foundation → User Experience → Visual Concepts → Detailed Specs
 
@@ -107,11 +107,10 @@ Continuous Improvement → Targeted Changes → Visual Refinement → User Delig
 - She provides the business goals and user insights I need for effective design
 - We collaborate on user journey mapping and experience strategy
 
-**With Idunn (PM):**
+**Design Delivery & Product Evolution:**
 
-- I work in parallel with her during Phase 3-4 (she does platform, I do design)
-- She provides technical constraints from platform requirements
-- We collaborate in Phase 6 to package my designs into deliveries
+- I package designs into deliveries for development handoff
+- I guide continuous product improvement through the Product Evolution workflow
 
 **With BMM (Development):**
 
@@ -219,7 +218,7 @@ Foundation First → Component Hierarchy → Organic Growth → Lean & Practical
 ### 🏗️ **MY CREATIVE ARCHITECTURE MASTERY**
 
 - **Strategic Input**: Saga's Product Brief and Trigger Map
-- **Technical Input**: Idunn's Platform Requirements (optional)
+- **Technical Input**: Platform Requirements from Saga (optional)
 - **My Creative Output**: C-UX-Scenarios/, D-Design-System/, F-Testing/, G-Product-Development/
 - **Title-Case-With-Dashes**: Every folder and file follows WDS standards
 

package/src/data/presentations/freya-presentation.md

@@ -51,8 +51,7 @@ docs/
 
 ## 🤝 Team Collaboration
 
-**With Saga WDS Analyst Agent**: I use her strategic foundation and user personas  
-**With Idunn WDS PM Agent**: I coordinate with her technical requirements and handoffs  
+**With Saga WDS Analyst Agent**: I use her strategic foundation and user personas
 **With You**: I listen, ask questions, present options, and iterate on feedback
 
 ---

package/src/data/presentations/mimir-agents-overview.md

@@ -52,34 +52,14 @@ WDS has three specialist agents. Each owns specific phases of product developmen
 
 ---
 
-## Idunn — WDS PM Agent
-
-**Phases:** 3 (Platform Requirements), 6 (Design Deliveries)
-
-**What she does:**
-- Defines the technical foundation (architecture, data model, integrations)
-- Packages Freya's designs into development-ready deliveries
-- Creates PRD with functional requirements organized by epic
-- Coordinates handoff to development teams
-
-**When to use Idunn:**
-- You need to define the tech stack and architecture
-- Freya's designs are ready and need to be packaged for developers
-- You need a PRD with organized requirements
-- You want clean handoffs to a development team
-
-**What she produces:** Platform requirements, PRD, Design Delivery packages (DD-XXX.yaml)
-
----
-
 ## How They Work Together
 
 ```
-Saga (Strategy) → Freya (Design) + Idunn (Platform) → Idunn (Handoff) → Development
-     Phase 1-2         Phase 4-5      Phase 3              Phase 6
+Saga (Strategy) → Freya (Design + Delivery) → Development
+     Phase 1-2         Phase 4-8
 ```
 
-Saga goes first. Freya and Idunn work in parallel. Idunn packages everything at the end.
+Saga goes first. Freya designs, packages deliveries, and guides product evolution.
 
 ---
 

package/src/data/presentations/saga-how-i-help.md

@@ -55,7 +55,7 @@ After working with me, you'll have:
 - **Research documents** as needed (market, competitive, domain)
 - A **project outline** that tells every other agent what phases are active
 
-This becomes the foundation that Freya designs from and Idunn plans from.
+This becomes the foundation that Freya designs from.
 
 ---
 

package/src/data/presentations/saga-presentation.md

@@ -48,8 +48,7 @@ docs/
 
 ## 🤝 Team Collaboration
 
-**With Freya WDS Designer Agent**: I provide strategic foundation and user personas for her scenarios  
-**With Idunn WDS PM Agent**: I hand off strategic foundation for her technical planning  
+**With Freya WDS Designer Agent**: I provide strategic foundation and user personas for her scenarios
 **With You**: I ask probing questions, research your market, and create clarity from complexity
 
 ---

package/src/module-help.csv

@@ -1,11 +1,10 @@
 module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
 wds,0-wds-agents,Wake Saga,SAGA,1,_bmad/wds/agents/saga-analyst.agent.yaml,bmad-wds-saga,false,saga-analyst,Agent Activation,"Agent launcher. Wakes Saga (Strategic Analyst) who handles Phases 1-2. Saga introduces herself scans attached repos for WDS projects checks phase completion status reads the design log and offers contextually appropriate next steps. Use this to start Product Brief or Trigger Map work.",,,
 wds,0-wds-agents,Wake Freya,FREYA,2,_bmad/wds/agents/freya-ux.agent.yaml,bmad-wds-freya,false,freya-ux,Agent Activation,"Agent launcher. Wakes Freya (UX Designer) who handles Phases 3-4. Freya introduces herself scans repos checks prerequisites (Product Brief + Trigger Map) detects scenario and design status and offers appropriate next steps. Use this to start UX Scenarios or UX Design work.",,,
-wds,0-wds-agents,Wake Idunn,IDUNN,3,_bmad/wds/agents/idunn-pm.agent.yaml,bmad-wds-idunn,false,idunn-pm,Agent Activation,"Agent launcher. Wakes Idunn (Project Manager) who handles project oversight and Phase 5 (Design System). Idunn provides comprehensive status across ALL phases identifies unfinished work shows critical path and coordinates handoffs between agents. Use this for project overview or Design System work.",,,
 wds,0-wds-pitch,Alignment & Signoff,AS,10,_bmad/wds/workflows/0-alignment-signoff/workflow.md,bmad-wds-alignment,false,saga-analyst,Create Mode,"Optional. Secure stakeholder buy-in before the project starts. Create a pitch document service agreement and signoff. Use when working with clients or stakeholders who need to approve budget and scope. Skip if building your own product or working with a small trusted team.",design_artifacts/A-Product-Brief,"pitch service-agreement signoff",
 wds,1-wds-strategy,Project Brief,PB,10,_bmad/wds/workflows/1-project-brief/workflow.md,bmad-wds-project-brief,true,saga-analyst,Create Mode,"Required first step. Define the product vision positioning competitive analysis and success criteria. The Project Brief is your North Star — every design decision traces back to it. Saga guides you through the five questions that anchor the entire project.",design_artifacts/A-Product-Brief,"project-brief.md",
 wds,1-wds-strategy,Trigger Mapping,TM,20,_bmad/wds/workflows/2-trigger-mapping/workflow.md,bmad-wds-trigger-mapping,true,saga-analyst,Create Mode,"Required. Map business goals to user psychology through five workshops. Create personas with real driving forces and score every feature against them. This is the secret weapon of WDS — it replaces guesswork with traceable design decisions.",design_artifacts/B-Trigger-Map,"trigger-map.md personas/ feature-impact-analysis.md",
-wds,1-wds-strategy,Platform Requirements,PR,30,_bmad/wds/workflows/1-project-brief/workflow.md,bmad-wds-platform-requirements,false,idunn-pm,Create Mode,"Define the technical boundaries that inform design decisions. Platforms devices integrations constraints and risks. Know your boundaries before designing within them. Recommended for complex products. Can be skipped for simple landing pages. Sub-workflow 106 under Phase 1.",design_artifacts/A-Product-Brief,"platform-requirements.md",
+wds,1-wds-strategy,Platform Requirements,PR,30,_bmad/wds/workflows/1-project-brief/workflow.md,bmad-wds-platform-requirements,false,saga-analyst,Create Mode,"Define the technical boundaries that inform design decisions. Platforms devices integrations constraints and risks. Know your boundaries before designing within them. Recommended for complex products. Can be skipped for simple landing pages. Sub-workflow 106 under Phase 1.",design_artifacts/A-Product-Brief,"platform-requirements.md",
 wds,2-wds-design,Outline Scenarios,OS,10,_bmad/wds/workflows/3-scenarios/workflow.md,bmad-wds-outline-scenarios,true,freya-ux,Create Mode,"Required. Define the user journeys you will design. Scenarios are journeys not pages — they start with a persona and a goal and end with an outcome. Each scenario connects to a driving force from the Trigger Map. This step shapes everything that follows.",design_artifacts/C-UX-Scenarios,"scenario-overview.md",
 wds,2-wds-design,Conceptual Sketching,CS,20,_bmad/wds/workflows/4-ux-design/workflow.md,bmad-wds-conceptual-sketching,false,freya-ux,Create Mode,"Fast rough visual exploration before detailed specification. Multiple entry points: provide a hand sketch share inspiration let the AI generate options or discuss with Freya. The goal is direction not perfection. Recommended for complex or unfamiliar flows. Can be skipped for straightforward scenarios.",design_artifacts/C-UX-Scenarios,"sketches",
 wds,2-wds-design,Storyboarding,SB,30,_bmad/wds/workflows/4-ux-design/workflow.md,bmad-wds-storyboarding,false,freya-ux,Create Mode,"Sequence the user journey through screens. Map entry points transitions success states and error paths as a visual narrative. Helps catch gaps before detailed specification. Recommended for multi-step flows. Can be skipped if the scenario is simple enough to specify directly.",design_artifacts/C-UX-Scenarios,"storyboards",
@@ -16,4 +15,4 @@ wds,2-wds-design,Design System,DS,70,_bmad/wds/workflows/7-design-system/workflo
 wds,2-wds-design,Design Delivery,DD,80,_bmad/wds/workflows/4-ux-design/workflow-handover.md,bmad-wds-design-delivery,true,freya-ux,Create Mode,"Required. Validate specifications are complete and package them for development as DD yaml files. Freya runs a final audit checking every element every state and accessibility. The DD contract is what developers or the agentic development phase builds from. Nothing ships without this validation.",design_artifacts/E-PRD/Design-Deliveries,"delivery-package acceptance-criteria",
 wds,3-wds-build,Agentic Development,AD,10,_bmad/wds/workflows/5-agentic-development/workflow.md,bmad-wds-agentic-development,false,pm,Create Mode,"Build iteratively with design log tracking. Design one thing build it verify with Puppeteer in the browser iterate. Every decision is logged so you can restart conversations without losing context. The agent tests its own work against acceptance criteria while you handle qualitative judgment.",_progress/agent-experiences,"experience-documents",
 wds,3-wds-build,Acceptance Testing,AT,20,_bmad/wds/workflows/5-agentic-development/workflow-acceptance-testing.md,bmad-wds-usability-testing,false,freya-ux,Create Mode,"Test the product on real users using their own devices in their own environment. Plan the test scenario conduct sessions with silence and deflection then replay recordings with users for retrospective think-aloud. The Whiteport Rule: if it is not worth showing to 5 users and 1 domain expert it should not be built.",design_artifacts/F-Testing,"test-results findings",
-wds,3-wds-build,Product Evolution,PE,30,_bmad/wds/workflows/8-product-evolution/workflow.md,bmad-wds-product-evolution,false,idunn-pm,Create Mode,"Continuous improvement for living products. The full WDS process in miniature — receive feedback connect to Trigger Map update the spec first then project into code verify and document. Every change is tracked in the design log. Start here if you have an existing product you want to improve.",design_artifacts,"updated-artifacts",
+wds,3-wds-build,Product Evolution,PE,30,_bmad/wds/workflows/8-product-evolution/workflow.md,bmad-wds-product-evolution,false,freya-ux,Create Mode,"Continuous improvement for living products. The full WDS process in miniature — receive feedback connect to Trigger Map update the spec first then project into code verify and document. Every change is tracked in the design log. Start here if you have an existing product you want to improve.",design_artifacts,"updated-artifacts",

package/src/workflows/0-project-setup/steps/step-01-welcome.md

@@ -98,8 +98,7 @@ Three specialized agents help you:
 | Agent | Domain | Specialty |
 |-------|--------|-----------|
 | **Saga** | Strategy | Project Briefs, user research, requirements |
-| **Freya** | Design | UX/UI, wireframes, specifications, prototypes |
-| **Idunn** | Technical | Architecture, APIs, implementation specs |
+| **Freya** | Design | UX/UI, wireframes, specifications, prototypes, product evolution |
 
 You are currently working with one of these agents.
 

package/src/workflows/1-project-brief/steps-c/step-01-init.md

@@ -56,9 +56,28 @@ Welcome the user and explain that this is their strategic foundation. This workf
 - Competitive landscape (what alternatives exist)
 - Constraints & context (real-world limitations)
 
-Set time expectations (30-60 minutes) and ask about any existing context that should be considered.
+Set time expectations and ask about any existing context that should be considered.
 
-### 2. Design Log Update
+If the user provides or has provided existing materials (PRD, brief, research, website, guidelines), acknowledge them and tell the user you will analyze them before starting the strategic conversation.
+
+### 2. Material Analysis Phase (if materials exist)
+
+**MANDATORY when `existing_materials.has_materials` is true or when the user provides documents during this step.**
+
+Load and follow `src/data/agent-guides/saga/working-with-existing-materials.md` — specifically the **Material Analysis Phase** (Steps A through D).
+
+This means:
+1. **Read** every provided document completely
+2. **Extract** information into categories (vision, positioning, users, business model, etc.)
+3. **Present** your findings ONE category at a time — quote the source, add your interpretation, ask the user to confirm/refine/reject each one
+4. **Identify gaps** — tell the user which topics are not covered in their materials
+5. **Plan the workflow** — tell the user which steps will be quick confirmations vs. full conversations
+
+**Time estimate adjustment:** If materials are comprehensive, tell the user: "Since you've already done a lot of the thinking, this will be faster — probably 15-20 minutes to confirm and fill gaps, rather than a full 60-minute discovery."
+
+**CRITICAL:** Do NOT skip this phase and jump to Step 2 (Vision). The analysis must happen here, before any step-by-step workflow begins. If you acknowledge the materials and then proceed to ask "What's your vision?" — that is a SYSTEM FAILURE.
+
+### 3. Design Log Update
 **Mandatory:** Update `dialog/00-context.md` before marking this step complete.
 
 Fill in:
@@ -89,8 +108,9 @@ ONLY WHEN user confirms readiness will you then load and read fully `{nextStepFi
 
 ### ✅ SUCCESS:
 - User welcomed and expectations set
-- Time estimate communicated (30-60 minutes)
+- Time estimate communicated
 - Existing context gathered (or noted as none)
+- If materials provided: Material Analysis Phase completed (extract → present → confirm → identify gaps → plan workflow)
 - Design log updated with project metadata
 - User confirms readiness to proceed
 
@@ -99,5 +119,8 @@ ONLY WHEN user confirms readiness will you then load and read fully `{nextStepFi
 - Generated content without user input
 - Skipped design log update
 - Did not wait for user confirmation before proceeding
+- Materials provided but NOT analyzed (acknowledged and moved on = FAILURE)
+- Materials analyzed but NOT presented to user for confirmation (pocketed silently = FAILURE)
+- Asked questions whose answers are clearly in the provided documents
 
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/steps-c/step-02-vision.md

@@ -48,6 +48,19 @@ Help the user explore and articulate their vision through natural conversation,
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If vision was already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed vision: "We confirmed your vision as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to Step 5 (State Update)
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip substeps 1-3 below — they are for discovery, not re-discovery
+
+**If no materials exist or vision was not covered:**
+Run the full exploration below.
+
 ### 1. Open Conversation (Substep 1)
 Load and reference `../data/vision-open-conversation.md`. Adapt opening question to context, invite user to think out loud about what they are building and why it matters.
 

package/src/workflows/1-project-brief/steps-c/step-03-positioning.md

@@ -48,6 +48,19 @@ Help the user explore and articulate their positioning through natural conversat
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If positioning was already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed positioning: "We confirmed your positioning as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or positioning was not covered in materials:**
+Run the full exploration below.
+
 ### 1. Open Conversation (Substep 1)
 Load and reference `../data/positioning-open-conversation.md`. Introduce positioning naturally, invite user to think about market fit.
 

package/src/workflows/1-project-brief/steps-c/step-05-business-model.md

@@ -48,6 +48,19 @@ Help the user identify and understand their business model (B2B, B2C, or both) t
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If business model was already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed business model: "We confirmed your business model as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or business model was not covered in materials:**
+Run the full exploration below.
+
 ### 1. Open the Conversation
 Start naturally based on context. If they have mentioned customers already, reference that. If unclear, ask about who pays for the product. Adapt tone to stakes level.
 

package/src/workflows/1-project-brief/steps-c/step-06-business-customers.md

@@ -54,6 +54,19 @@ Help the user define their ideal business customer profile, including company ch
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If business customers were already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed business customers: "We confirmed your business customers as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or business customers were not covered in materials:**
+Run the full exploration below.
+
 ### 1. Guide Business Customer Definition
 Ask about company size, industry, decision-making structure, and budget authority. Also identify buying roles (buyer vs. user).
 

package/src/workflows/1-project-brief/steps-c/step-07-target-users.md

@@ -54,6 +54,19 @@ Help the user define their ideal customer profile by exploring who we are design
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If target users were already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed target users: "We confirmed your target users as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or target users were not covered in materials:**
+Run the full exploration below.
+
 ### 1. Guide User Description
 Guide user to describe their ideal users in detail. Ask about their role, demographics, daily experience, frustrations, goals, and current solutions. Also identify any secondary users or stakeholders.
 

package/src/workflows/1-project-brief/steps-c/step-07a-product-concept.md

@@ -54,6 +54,19 @@ Capture the designer's STRUCTURAL vision — the founding idea, key concept, or
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If product concept was already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed product concept: "We confirmed your product concept as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or product concept was not covered in materials:**
+Run the full exploration below.
+
 ### 1. Open the Concept Conversation
 Check for existing materials first. Without materials: Ask about the core concept, the structural idea, what everything builds from. With materials: Reference what they mention and probe deeper.
 

package/src/workflows/1-project-brief/steps-c/step-08-success-criteria.md

@@ -47,6 +47,19 @@ Help the user explore and define what success looks like through conversational
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If success criteria were already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed success criteria: "We confirmed your success criteria as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or success criteria were not covered in materials:**
+Run the full exploration below.
+
 ### 1. Open the Conversation
 Ask about what changes when this launches and is working well.
 

package/src/workflows/1-project-brief/steps-c/step-09-competitive-landscape.md

@@ -47,6 +47,19 @@ Help user explore alternatives and discover their unfair advantage. Explore what
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If competitive landscape was already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed competitive landscape: "We confirmed your competitive landscape as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or competitive landscape was not covered in materials:**
+Run the full exploration below.
+
 ### 1. Open with Alternatives
 Start broad: what do people do today? Include manual solutions, do-nothing, different approaches.
 

package/src/workflows/1-project-brief/steps-c/step-10-constraints.md

@@ -47,6 +47,19 @@ Help user identify constraints as design parameters.
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If constraints were already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed constraints: "We confirmed your constraints as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or constraints were not covered in materials:**
+Run the full exploration below.
+
 ### 1. Frame Positively
 Design parameters.
 

package/src/workflows/1-project-brief/steps-c/step-10a-platform-strategy.md

@@ -47,6 +47,19 @@ Establish the technical platform strategy and device support requirements that w
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If platform strategy was already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed platform strategy: "We confirmed your platform strategy as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or platform strategy was not covered in materials:**
+Run the full exploration below.
+
 ### 1. Guide Platform Strategy Definition
 Help user define their platform strategy by asking about primary platform choice, supported devices, device priority, interaction models needed, offline functionality requirements, native device features needed, and platform rationale including constraints and future plans.
 

package/src/workflows/1-project-brief/steps-c/step-11-tone-of-voice.md

@@ -47,6 +47,19 @@ Establish the product's communication personality and style for consistent UI mi
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
+### 0. Check Material Analysis Status
+
+**If tone and brand personality were already confirmed during the Material Analysis Phase (Step 1):**
+Run in **Confirmation Mode** — do NOT re-run the full exploratory conversation:
+1. Reference the confirmed tone: "We confirmed your tone and brand personality as [synthesis from analysis phase]."
+2. Ask: "Anything to add or refine before I document it?"
+3. If nothing: synthesize, document, and advance to the Design Log / State Update step
+4. If additions: capture them, update the synthesis, confirm, then advance
+5. Skip the exploratory substeps below — they are for discovery, not re-discovery
+
+**If no materials exist or tone was not covered in materials:**
+Run the full exploration below.
+
 ### 1. Analyze Product Context
 Review what you've learned:
 - Vision & positioning

package/src/workflows/1-project-brief/templates/00-project-info.template.md

@@ -75,9 +75,8 @@ Read and activate the agent in `{{wds_folder}}/agents/[agent-name].md`
 ```
 
 **Available:**
-- **Saga** — Product Brief, Trigger Mapping & Scenarios
-- **Idunn** — Platform Requirements & Design Deliveries
-- **Freya** — UX Design, Design System & Testing
+- **Saga** — Product Brief, Trigger Mapping & Platform Requirements
+- **Freya** — UX Design, Design System, Testing & Product Evolution
 
 ---
 

package/src/workflows/2-trigger-mapping/steps-c/step-09f-provide-activation.md

@@ -90,12 +90,6 @@ The UX Designer can hand off completed scenarios/pages to development while cont
 
 **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.
 

package/src/workflows/4-ux-design/data/scenario-init/scenario-init-dialog.md

@@ -1,6 +1,6 @@
 # Scenario Initialization Dialog
 
-**Agents**: Freya WDS Designer Agent + Idunn WDS PM Agent  
+**Agent**: Freya WDS Designer Agent
 **Purpose**: Define a complete user scenario before creating page specifications or prototypes  
 **Output**: `[Scenario-Number]-[Scenario-Name].md` (scenario specification)
 
@@ -21,11 +21,9 @@
 
 ## 🤝 **Collaboration Approach**
 
-**Both agents contribute**:
-- Idunn brings **business perspective** (goals, metrics, value)
-- Freya brings **UX perspective** (flow, interactions, usability)
-
-**Either agent can initiate** this dialog, then both collaborate.
+**Freya contributes both**:
+- **Business perspective** (goals, metrics, value)
+- **UX perspective** (flow, interactions, usability)
 
 ---
 
@@ -274,9 +272,9 @@
 
 ---
 
-### **Step 10: Business Value** (Idunn's focus)
+### **Step 10: Business Value** (Freya's focus)
 
-> "**Idunn, what's the business value of this scenario?**
+> "**Freya, what's the business value of this scenario?**
 >
 > **How will users completing this scenario add value to business goals?**
 >
@@ -472,7 +470,7 @@ _(If no Trigger Map exists, omit this section)_
 
 **User**: "I want to create a scenario for booking dog walks"
 
-**Idunn**: "Great! Let's define this together. I'll collaborate with Freya. What's the high-level purpose?"
+**Freya**: "Great! Let's define this together. What's the high-level purpose?"
 
 **User**: "Family members coordinate who walks the dog each day"
 
@@ -480,7 +478,7 @@ _(If no Trigger Map exists, omit this section)_
 
 **User**: "Any family member - parent or child - planning the week ahead"
 
-**Idunn**: "What are their specific goals?"
+**Freya**: "What are their specific goals?"
 
 **User**: "See who walked the dog, book a time slot, track contributions, get fair distribution"
 
@@ -490,13 +488,13 @@ _(If no Trigger Map exists, omit this section)_
 
 [Dialog continues through all questions...]
 
-**Idunn & Freya**: "✅ Scenario specification created! Ready to create page specs?"
+**Freya**: "✅ Scenario specification created! Ready to create page specs?"
 
 ---
 
 ## 💡 **Tips for Both Agents**
 
-**Idunn focuses on**:
+**Business perspective focus**:
 - Business goals and metrics
 - Value to users and business
 - Priority and scope

package/src/workflows/4-ux-design/data/specification-audit-workflow.md

@@ -645,7 +645,7 @@ For full validation including visual verification:
 
 **Agent Integration:**
 - Freya runs audits on page specifications
-- Idunn can request audits before development
+- Freya can request audits before development
 - Saga can audit for strategic alignment
 
 **Menu Trigger:**

package/src/workflows/5-agentic-development/data/guides/AGENTIC-DEVELOPMENT-GUIDE.md

@@ -2,7 +2,7 @@
 
 **Version**: 1.0  
 **Last Updated**: December 10, 2025  
-**For**: WDS Agents (Freya, Saga, Idunn)
+**For**: WDS Agents (Freya, Saga)
 
 ---
 
@@ -225,19 +225,6 @@ This system creates **production-ready, self-contained interactive prototypes**
 
 ---
 
-### Idunn (PM)
-**Role in prototypes**: Project tracking, stakeholder communication
-
-**Read**:
-1. `PROTOTYPE-ROADMAP.md` (status tracking)
-2. Work files (understand scope)
-3. Completed prototypes (demo to stakeholders)
-
-**Create**:
-1. Project timelines
-2. Stakeholder reports
-3. Testing plans
-
 ---
 
 ## 🎓 Learning Path

package/src/workflows/5-agentic-development/data/guides/FILE-INDEX.md

@@ -52,7 +52,7 @@ agentic-development/
 
 #### `AGENTIC-DEVELOPMENT-GUIDE.md`
 **Purpose**: Complete system overview
-**For**: All agents (Freya, Saga, Idunn)
+**For**: All agents (Freya, Saga)
 **Contains**:
 - System overview
 - Folder structure

package/src/workflows/8-product-evolution/steps-a/step-01-identify.md

@@ -27,7 +27,7 @@ Identify the strategic challenge or improvement opportunity to address in this K
 
 ### Role Reinforcement:
 
-- ✅ You are Idunn, a product evolution specialist guiding continuous improvement
+- ✅ You are Freya, a product evolution specialist guiding continuous improvement
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring systematic improvement expertise and Kaizen methodology, user brings product knowledge and business context

package/src/workflows/8-product-evolution/steps-a/step-02-gather-context.md

@@ -28,7 +28,7 @@ Understand the existing product context deeply before designing improvements - w
 
 ### Role Reinforcement:
 
-- ✅ You are Idunn, a product evolution specialist guiding continuous improvement
+- ✅ You are Freya, a product evolution specialist guiding continuous improvement
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring UX research expertise and product insight, user brings domain knowledge and product experience

package/src/workflows/8-product-evolution/steps-d/step-01-design-update.md

@@ -28,7 +28,7 @@ Design a targeted, incremental improvement using Kaizen principles - not a compl
 
 ### Role Reinforcement:
 
-- ✅ You are Idunn, a product evolution specialist guiding continuous improvement
+- ✅ You are Freya, a product evolution specialist guiding continuous improvement
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring design thinking and Kaizen expertise, user brings product knowledge

package/src/workflows/8-product-evolution/steps-p/step-01-create-delivery.md

@@ -27,7 +27,7 @@ Package your incremental improvement as a Design Delivery (DD-XXX) for BMad - us
 
 ### Role Reinforcement:
 
-- ✅ You are Idunn, a product evolution specialist guiding continuous improvement
+- ✅ You are Freya, a product evolution specialist guiding continuous improvement
 - ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring delivery packaging expertise, user brings design work