whiteport-design-studio 0.3.1 → 0.3.3

package/README.md

@@ -51,19 +51,19 @@ Saga will greet you by name and guide you through creating your Product Brief.
 | 1. Product Brief | Vision, positioning, success criteria | Saga | `A-Product-Brief/` |
 | 2. Trigger Mapping | User psychology, business goals | Saga | `B-Trigger-Map/` |
 | 3. UX Scenarios | Scenario outlines via 8-question dialog | Freya | `C-UX-Scenarios/` |
-| 4. UX Design | Page specifications, interactions | Freya | `D-UX-Design/` |
-| 5. Agentic Development | AI-assisted development & testing | Freya | `G-Product-Development/` |
+| 4. UX Design | Page specifications, interactions | Freya | `C-UX-Scenarios/` |
+| 5. Agentic Development | AI-assisted development & testing | Freya | — |
 | 6. Asset Generation | Visual and text assets from specs | Freya | — |
 | 7. Design System | Component library, design tokens | Freya | `D-Design-System/` |
 | 8. Product Evolution | Brownfield improvements | Freya | — |
 
-Output folders are created inside your configured design artifacts directory (default: `design-artifacts/`).
+Output folders are created inside your configured design output directory (default: `design-process/`).
 
 ---
 
 ## Supported Design Tools
 
-WDS offers agenttic design capabilities with several visual design and prototyping services on the market:
+WDS offers agentic design capabilities with several visual design and prototyping services on the market:
 
 | Tool | What it does | MCP |
 |------|-------------|-----|
@@ -98,14 +98,11 @@ your-project/
 │   ├── method/
 │   ├── models/
 │   └── tools/
-├── design-artifacts/        # Design output (created by agents)
+├── design-process/          # Design output (created by agents)
 │   ├── A-Product-Brief/
 │   ├── B-Trigger-Map/
 │   ├── C-UX-Scenarios/
-│   ├── D-Design-System/
-│   ├── E-PRD/
-│   ├── F-Testing/
-│   └── G-Product-Development/
+│   └── D-Design-System/
 └── .claude/instructions.md  # IDE configuration (varies by IDE)
 ```
 

package/docs/getting-started/MANUAL-INIT-GUIDE.md

@@ -55,7 +55,6 @@ your-project/
 │       └── wds/
 │           ├── agents/
 │           │   ├── freya-ux.agent.yaml
-│           │   ├── idunn-pm.agent.yaml
 │           │   └── saga-analyst.agent.yaml
 │           ├── workflows/
 │           │   ├── 1-project-brief/
@@ -79,8 +78,7 @@ your-project/
 3. **Reference the WDS agent** you want to use:
 
 ```
-@wds/agents/freya-ux    - For UX Design & Prototyping
-@wds/agents/idunn-pm     - For Product Management & Analysis
+@wds/agents/freya-ux    - For UX Design, Prototyping & Product Management
 @wds/agents/saga-analyst - For Scenario Analysis
 ```
 
@@ -148,8 +146,7 @@ Choose a workflow to start:
 
 | Agent | Purpose | Reference |
 |-------|---------|-----------|
-| **Freya** | UX Design & Prototyping | `@wds/agents/freya-ux` |
-| **Idunn** | Product Management | `@wds/agents/idunn-pm` |
+| **Freya** | UX Design, Prototyping & Product Management | `@wds/agents/freya-ux` |
 | **Saga** | Scenario Analysis | `@wds/agents/saga-analyst` |
 
 ### Key Workflows

package/docs/getting-started/agent-activation/activation/step-01-load-agent-definition.md

@@ -11,7 +11,6 @@ Read and fully embody the persona from your agent definition file.
 **Your agent definition file**:
 - Saga: `src/modules/wds/agents/saga-analyst.agent.yaml`
 - Freya: `src/modules/wds/agents/freya-ux.agent.yaml`
-- Idunn: `src/modules/wds/agents/idunn-pm.agent.yaml`
 
 **What to do**:
 1. Read the entire agent definition file

package/docs/getting-started/agent-activation/activation/step-04-handoff-presentation.md

@@ -13,7 +13,6 @@ Show your full presentation even though this is a handoff.
 **Your presentation file**:
 - Saga: `src/modules/wds/data/presentations/saga-presentation.md`
 - Freya: `src/modules/wds/data/presentations/freya-presentation.md`
-- Idunn: `src/modules/wds/data/presentations/idunn-presentation.md`
 
 **What to do**:
 1. Load and show your full presentation

package/docs/getting-started/agent-activation/activation/step-04-standard-presentation.md

@@ -11,7 +11,6 @@ Show your full presentation to introduce yourself.
 **Your presentation file**:
 - Saga: `src/modules/wds/data/presentations/saga-presentation.md`
 - Freya: `src/modules/wds/data/presentations/freya-presentation.md`
-- Idunn: `src/modules/wds/data/presentations/idunn-presentation.md`
 
 **What to do**:
 1. Load and show your full presentation

package/docs/getting-started/agent-activation/agent-launchers.md

@@ -20,12 +20,6 @@ Simply reference one of these files in your IDE chat to activate the correspondi
 **Specializes in**: Project Briefs, User Research, Strategy  
 **Phases**: 1, 2
 
-### Idunn - Product Manager 📋
-
-**File**: `@wds-idunn-pm.md`  
-**Specializes in**: Technical Requirements, Architecture, Delivery  
-**Phases**: 3, 6
-
 ---
 
 ## How It Works
@@ -65,11 +59,10 @@ All agents use a **router pattern** for predictable behavior:
 
 Each agent focuses on specific WDS phases:
 
-| Agent       | Primary Phases | Key Expertise                |
-| ----------- | -------------- | ---------------------------- |
-| **Saga**    | 1-2            | Strategy, research, personas |
-| **Freya**  | 4-5, 7         | Design, prototypes, testing  |
-| **Idunn**   | 3, 6           | Architecture, delivery, PM   |
+| Agent       | Primary Phases | Key Expertise                              |
+| ----------- | -------------- | ------------------------------------------ |
+| **Saga**    | 1-2            | Strategy, research, personas               |
+| **Freya**   | 4-8            | Design, prototypes, testing, delivery, PM  |
 
 If you select a task outside the current agent's domain, they'll seamlessly hand over to the specialist.
 

package/docs/getting-started/agent-activation/wds-freya-ux.md

@@ -25,8 +25,9 @@ I guide you through the creative heart of the WDS journey - from scenarios and u
 **I receive handoff from:**
 - **Saga** - Strategic foundation and user personas
 
-**I hand off to:**
-- **Idunn** - When designs are ready for technical implementation planning
+**I also handle:**
+- Design delivery packaging for development handoff
+- Product evolution and continuous improvement
 
 ---
 

package/docs/getting-started/agent-activation/wds-saga-analyst.md

@@ -25,7 +25,6 @@ I work at the very beginning of your journey - where vision meets reality. Toget
 
 **I hand off to:**
 - **Freya** - When strategy is ready for design execution
-- **Idunn** - When technical architecture planning begins
 
 ---
 

package/docs/method/wds-method-guide.md

@@ -139,7 +139,7 @@ See: [Phase 4: UX Design Guide](./phase-4-ux-design-guide.md)
 ### Phase 5: Agentic Development
 
 **Output:** Development artifacts
-**Agent:** Idunn the PM
+**Agent:** Freya the Designer
 
 Bridge from design to development. Manage the development process with AI-assisted implementation, testing, and deployment.
 
@@ -181,7 +181,7 @@ Build your component library following atomic design principles. This phase runs
 ### Phase 8: Product Evolution
 
 **Output:** Evolution artifacts
-**Agent:** Idunn the PM
+**Agent:** Freya the Designer
 
 Iterate on existing products. Analyze usage, scope changes, design updates, implement, test, and deploy improvements.
 
@@ -247,7 +247,7 @@ Your agents will help you identify which phases fit your project.
 
 ## Your Agents
 
-Three specialized agents guide you through WDS:
+Two specialized agents guide you through WDS:
 
 ### Saga the Analyst
 
@@ -266,23 +266,14 @@ Saga guides you through discovery, research, and scenario creation. She's curiou
 
 _"The one who brings light and beauty"_
 
-Freya transforms your scenarios into beautiful, detailed specifications. She cares deeply about craft and ensures every detail serves the user experience.
+Freya transforms your scenarios into beautiful, detailed specifications. She cares deeply about craft and ensures every detail serves the user experience. She also bridges design to development and guides product evolution.
 
 **Works with you on:**
 
 - Phase 4: UX Design
+- Phase 5: Agentic Development
 - Phase 6: Asset Generation
 - Phase 7: Design System
-
-### Idunn the PM
-
-_"The keeper of what endures"_
-
-Idunn manages the bridge from design to development and guides product evolution. She ensures nothing is lost in translation and that products continue to improve.
-
-**Works with you on:**
-
-- Phase 5: Agentic Development
 - Phase 8: Product Evolution
 
 ---

package/docs/tools/cursor-windsurf.md

@@ -8,14 +8,14 @@
 
 ## What It Is
 
-Cursor and Windsurf are AI-powered IDEs built on VS Code that enable natural language interaction with WDS agents (Freya, Saga, Idunn). They provide the environment where agents can read, write, and modify code while maintaining full context of your project.
+Cursor and Windsurf are AI-powered IDEs built on VS Code that enable natural language interaction with WDS agents (Freya, Saga). They provide the environment where agents can read, write, and modify code while maintaining full context of your project.
 
 ---
 
 ## Why WDS Recommends It
 
 **AI Agent Integration:**
-- Native support for AI agents like Freya, Saga, Idunn
+- Native support for AI agents like Freya, Saga
 - Agents can read/write files, run commands, analyze code
 - Context-aware suggestions and automation
 
@@ -103,7 +103,7 @@ Create workspace settings for WDS projects:
 ### DO ✅
 
 **1. Use Agent Chat Effectively**
-- Be specific with requests to Freya, Saga, or Idunn
+- Be specific with requests to Freya or Saga
 - Reference files using @ mentions
 - Provide context about what you're trying to achieve
 

package/docs/tools/wds-tools-guide.md

@@ -18,7 +18,7 @@ WDS works best with a curated set of tools that support the concept-first, itera
 
 **[Cursor/Windsurf IDE](cursor-windsurf.md)**
 - AI-powered IDE for WDS agent workflows
-- Development environment for Freya, Saga, Idunn
+- Development environment for Freya, Saga
 - **Status:** Required for all WDS phases
 
 **[Git](git.md)**

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "whiteport-design-studio",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "description": "Whiteport Design Studio - Strategic design methodology for AI-powered workflows",
   "keywords": [
     "design",

package/src/agents/freya-ux.agent.yaml

@@ -24,7 +24,7 @@ agent:
       than skimming many. Keeps responses focused and actionable — leads with decisions, follows
       with rationale. Suggests workshops when strategic thinking is needed.
     principles: |
-      - Domain: Phases 4 (UX Design), 6 (Asset Generation), 7 (Design System - optional). Hand over other domains to specialist agents.
+      - Domain: Phases 4 (UX Design), 5 (Agentic Development), 6 (Asset Generation), 7 (Design System - optional), 8 (Product Evolution). Hand over other domains to specialist agents.
       - Replaces BMM Sally (UX Designer) when WDS is installed.
       - Load strategic context BEFORE designing — always connect to Trigger Map.
       - Specifications must be logical and complete — if you can't explain it, it's not ready.
@@ -63,3 +63,7 @@ agent:
     - trigger: DD or fuzzy match on design-delivery
       exec: "{project-root}/_bmad/wds/workflows/4-ux-design/workflow-handover.md"
       description: "[DD] Design Delivery — Package flows for development handoff"
+
+    - trigger: PE or fuzzy match on product-evolution
+      exec: "{project-root}/_bmad/wds/workflows/8-product-evolution/workflow.md"
+      description: "[PE] Product Evolution — Continuous improvement for living products"

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/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

package/src/workflows/8-product-evolution/steps-p/step-02-hand-off.md

@@ -25,7 +25,7 @@ Hand off the Design Delivery (small scope) to BMad Developer for implementation
 
 ### 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 handoff process expertise, user brings design delivery

package/src/workflows/8-product-evolution/steps-t/step-01-validate.md

@@ -28,7 +28,7 @@ Validate that the Design Delivery (small scope) was implemented correctly accord
 
 ### 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 testing methodology expertise, user brings product knowledge