diff --git a/docs/learn/00-course-overview/00-course-overview.md b/docs/learn/00-course-overview/00-course-overview.md index f15f8ab07..91e33ff18 100644 --- a/docs/learn/00-course-overview/00-course-overview.md +++ b/docs/learn/00-course-overview/00-course-overview.md @@ -105,20 +105,20 @@ Each module contains: | 12 | [Functional Components](../module-12-functional-components/module-12-functional-components-overview.md) | Freya | UX | 45 min | | 13 | [Design System](../module-13-design-system/module-13-design-system-overview.md) | Freya | Systems | 30 min | -### Build & Deliver Phase (Modules 14-16) — Agents: Freya + Idunn +### Build & Deliver Phase (Modules 14-16) — Agent: Freya | Module | Title | Agent | Focus | Time | |--------|-------|-------|-------|------| -| 14 | [Agentic Development](../module-14-agentic-development/module-14-agentic-development-overview.md) | Idunn | 7-activity menu | 60 min | +| 14 | [Agentic Development](../module-14-agentic-development/module-14-agentic-development-overview.md) | Freya | 7-activity menu | 60 min | | 15 | [Visual Design & Assets](../module-15-visual-design/module-15-visual-design-overview.md) | Freya | Asset pipeline | 60 min | | 16 | [Design Delivery](../module-16-design-delivery/module-16-design-delivery-overview.md) | Freya | Handover | 45 min | -### Validate & Evolve (Modules 17-18) — Agents: Freya + Idunn +### Validate & Evolve (Modules 17-18) — Agent: Freya | Module | Title | Agent | Time | |--------|-------|-------|------| | 17 | [Usability Testing](../module-17-usability-testing/module-17-usability-testing-overview.md) | Freya | 45 min | -| 18 | [Product Evolution](../module-18-product-evolution/module-18-product-evolution-overview.md) | Idunn | 30 min | +| 18 | [Product Evolution](../module-18-product-evolution/module-18-product-evolution-overview.md) | Freya | 30 min | --- @@ -138,19 +138,18 @@ Each module contains: --- -## The Three Agents +## The Two Agents -WDS uses three AI agents, each with a specific domain: +WDS uses two AI agents, each with a specific domain: | Agent | Domain | Phase | Modules | |-------|--------|-------|---------| | **Saga** | Strategy | Strategy | 3-6 | -| **Freya** | UX, Visual Design & Assets | Design & Deliver | 7-13, 15-17 | -| **Idunn** | Development & Evolution | Build & Evolve | 14, 18 | +| **Freya** | UX, Visual Design, Development & Evolution | Design, Build & Evolve | 7-18 | -Each agent maintains focus on their domain while coordinating with the others. +Each agent maintains focus on their domain while coordinating with the other. -**Idunn's 7 activities** (Module 14): Prototyping, Development, Bugfixing, Evolution, Analysis, Reverse Engineering, and Acceptance Testing — all menu-driven from a single entry point. +**Freya's 7 activities** (Module 14): Prototyping, Development, Bugfixing, Evolution, Analysis, Reverse Engineering, and Acceptance Testing — all menu-driven from a single entry point. --- diff --git a/docs/learn/module-01-why-wds-matters/lesson-02-designer-as-strategic-thinker.md b/docs/learn/module-01-why-wds-matters/lesson-02-designer-as-strategic-thinker.md index 6b62c2e92..177ac05b1 100644 --- a/docs/learn/module-01-why-wds-matters/lesson-02-designer-as-strategic-thinker.md +++ b/docs/learn/module-01-why-wds-matters/lesson-02-designer-as-strategic-thinker.md @@ -408,7 +408,7 @@ Amateur designers make AI code faster. **The methodology empowers you:** - Saga helps you think strategically about business and users - Freya helps you forge complete UX specifications -- Idunn helps you generate implementations +- Freya helps you generate implementations **The guard rails keep you strategic:** - Every decision traces to business goals diff --git a/docs/learn/module-02-installation-setup/lesson-04-wds-initialization.md b/docs/learn/module-02-installation-setup/lesson-04-wds-initialization.md index 296824a2d..989141a2a 100644 --- a/docs/learn/module-02-installation-setup/lesson-04-wds-initialization.md +++ b/docs/learn/module-02-installation-setup/lesson-04-wds-initialization.md @@ -36,7 +36,7 @@ The installer will guide you through: - **Experience level** — Beginner, Intermediate, or Expert - **IDE configuration** — Sets up your AI IDE automatically -**✅ Checkpoint:** Installer completes, `_wds/` folder appears in your project +**✅ Checkpoint:** Installer completes, `_bmad/wds/` folder appears in your project --- @@ -46,11 +46,10 @@ After installation, your project has: ``` your-project/ -├── _wds/ ← WDS system files +├── _bmad/wds/ ← WDS system files │ ├── agents/ ← Agent files (.md) │ │ ├── saga-analyst.md │ │ ├── freya-ux.md -│ │ └── idunn-pm.md │ ├── workflows/ ← Phase workflows │ ├── data/ ← Standards, frameworks │ ├── gems/ ← Reusable prompt components @@ -63,11 +62,11 @@ your-project/ │ ├── C-UX-Scenarios/ │ ├── D-Design-System/ │ ├── E-PRD/ -│ └── F-Agent-Dialogs/ +│ └── _progress/ └── .claude/instructions.md ← IDE configuration ``` -**Key insight:** `_wds/` contains the methodology. `docs/` is where your design work lives. +**Key insight:** `_bmad/wds/` contains the methodology. `docs/` is where your design work lives. --- @@ -79,7 +78,6 @@ WDS has three specialized agents: |-------|-------------|-------------| | **Saga** | Business & Product Analyst | Product Brief, Trigger Mapping | | **Freya** | UX/UI Designer | Scenarios, UX Design, Visual Design | -| **Idunn** | Project Manager | Platform Requirements, Design System | ### Start with Saga @@ -88,7 +86,7 @@ For a new project, start with Saga to create your Product Brief: Tell your AI IDE: ``` -Read and activate the agent in _wds/agents/saga-analyst.md +Read and activate the agent in _bmad/wds/agents/saga-analyst.md ``` Saga will: @@ -104,7 +102,7 @@ Saga will: **Issue:** `npx` command not found → Install Node.js from **Issue:** Installer fails → Make sure you're in your project folder -**Issue:** Agent file not found → Check `_wds/agents/` folder exists +**Issue:** Agent file not found → Check `_bmad/wds/agents/` folder exists --- diff --git a/docs/learn/module-02-installation-setup/tutorial-02.md b/docs/learn/module-02-installation-setup/tutorial-02.md index 3246790ac..8a619593b 100644 --- a/docs/learn/module-02-installation-setup/tutorial-02.md +++ b/docs/learn/module-02-installation-setup/tutorial-02.md @@ -132,11 +132,11 @@ npx whiteport-design-studio install ``` - [ ] Follow the installer prompts (project type, experience level, IDE) -- [ ] ✅ `_wds/` folder appears in your project +- [ ] ✅ `_bmad/wds/` folder appears in your project ### Activate an Agent -- [ ] Tell your AI IDE: `Read and activate the agent in _wds/agents/saga-analyst.md` +- [ ] Tell your AI IDE: `Read and activate the agent in _bmad/wds/agents/saga-analyst.md` - [ ] ✅ Saga responds and welcomes you! --- diff --git a/docs/learn/module-05-platform-requirements/lesson-01-why-boundaries-matter.md b/docs/learn/module-05-platform-requirements/lesson-01-why-boundaries-matter.md index 70a793da5..d03ad6f7a 100644 --- a/docs/learn/module-05-platform-requirements/lesson-01-why-boundaries-matter.md +++ b/docs/learn/module-05-platform-requirements/lesson-01-why-boundaries-matter.md @@ -180,9 +180,9 @@ This document travels with your Product Brief because it's strategic context — Here's a powerful pattern: -Once you document platform requirements, you can **send them to Idunn immediately**. +Once you document platform requirements, you can **hand them off to development immediately**. -While you move into UX design (Freya), Idunn can: +While you move into UX design, Freya can also handle development tasks in parallel: - Research knowledge gaps - Spike complex integrations diff --git a/docs/learn/module-05-platform-requirements/lesson-02-defining-platform-requirements.md b/docs/learn/module-05-platform-requirements/lesson-02-defining-platform-requirements.md index 02644671e..9c411c84a 100644 --- a/docs/learn/module-05-platform-requirements/lesson-02-defining-platform-requirements.md +++ b/docs/learn/module-05-platform-requirements/lesson-02-defining-platform-requirements.md @@ -309,9 +309,9 @@ Needs Team Decision: ### Why this matters: -**Knowledge gaps become tasks for Idunn.** +**Knowledge gaps become development tasks.** -While you design with Freya, Idunn can: +While you focus on design, the development agent can: - Research the unknowns - Spike the complex integrations - Test the assumptions @@ -383,11 +383,11 @@ Just like the Product Brief, this document gets referenced throughout the projec Once this document exists: -1. **Send to Idunn** — Technical investigation begins +1. **Hand off to development** — Technical investigation begins 2. **Reference in design** — Every decision respects these boundaries 3. **Update as you learn** — New discoveries get documented -**This is a living document.** As Idunn investigates knowledge gaps, the document gets updated. As the project evolves, constraints may change. Keep it current. +**This is a living document.** As knowledge gaps get investigated, the document gets updated. As the project evolves, constraints may change. Keep it current. --- @@ -396,7 +396,7 @@ Once this document exists: - The five sections of platform requirements - How to document each section effectively - Why constraints inform rather than limit design -- How knowledge gaps become parallel work for Idunn +- How knowledge gaps become parallel development work - Where the document lives and how it's used --- diff --git a/docs/learn/module-05-platform-requirements/module-05-platform-requirements-overview.md b/docs/learn/module-05-platform-requirements/module-05-platform-requirements-overview.md index 39ef3f344..8c436ad1f 100644 --- a/docs/learn/module-05-platform-requirements/module-05-platform-requirements-overview.md +++ b/docs/learn/module-05-platform-requirements/module-05-platform-requirements-overview.md @@ -81,7 +81,7 @@ What do we **not** know yet? - No team expertise? - Needs a spike or proof-of-concept? -**Surface these gaps explicitly.** They become tasks for Idunn to investigate in parallel. +**Surface these gaps explicitly.** They become development tasks to investigate in parallel. --- @@ -106,11 +106,11 @@ This document lives with your Product Brief because it's part of the strategic f --- -## Handoff to Idunn +## Handoff to Development -Once platform requirements are documented, you can **send them to Idunn** immediately. +Once platform requirements are documented, you can **hand them off to development** immediately. -While you continue with UX design (Freya), Idunn can: +While you continue with UX design, Freya can also handle development tasks: - Research knowledge gaps - Spike complex integrations diff --git a/docs/learn/module-05-platform-requirements/tutorial-05.md b/docs/learn/module-05-platform-requirements/tutorial-05.md index c7c5f68a6..2be75d5f0 100644 --- a/docs/learn/module-05-platform-requirements/tutorial-05.md +++ b/docs/learn/module-05-platform-requirements/tutorial-05.md @@ -28,7 +28,7 @@ This tutorial walks you through creating a platform requirements document that c - Ask the right questions - Identify gaps you might miss - Document clearly and consistently -- Prepare handoff to Idunn +- Prepare handoff to development --- @@ -168,7 +168,7 @@ This gives Saga the context to ask relevant questions. ### Saga summarizes: -> "So we have medium complexity on push notifications and offline sync, with lower complexity on core features. I'll flag the iOS push notification limitations as something Idunn should research." +> "So we have medium complexity on push notifications and offline sync, with lower complexity on core features. I'll flag the iOS push notification limitations as something that needs research." --- @@ -237,15 +237,15 @@ If anything is missing or wrong, tell Saga: --- -## Step 9: Handoff to Idunn (Optional) +## Step 9: Handoff to Development (Optional) ### If you want parallel development: -> "Please prepare a handoff for Idunn with the knowledge gaps that need investigation." +> "Please prepare a handoff for development with the knowledge gaps that need investigation." ### Saga creates handoff: -> "Handoff prepared for Idunn: +> "Handoff prepared for development: > > **Research Tasks:** > - iOS 17+ PWA push notification behavior @@ -257,7 +257,7 @@ If anything is missing or wrong, tell Saga: > **Pending Decisions:** > - React Native vs PWA long-term strategy > -> Idunn can start investigating while you continue to UX design with Freya." +> Development can start while you continue to UX design with Freya." --- @@ -305,7 +305,7 @@ If anything is missing or wrong, tell Saga: ### Immediate: - Platform requirements inform all design decisions -- Knowledge gaps become Idunn's research tasks +- Knowledge gaps become development research tasks - You have a clear picture of what's possible ### Next Phase: @@ -337,7 +337,7 @@ If anything is missing or wrong, tell Saga: ## Common Questions **Q: What if I don't know the technical details?** -A: That's what knowledge gaps are for. Document what you don't know and let Idunn investigate. +A: That's what knowledge gaps are for. Document what you don't know and let the development agent investigate. **Q: Should I talk to developers before creating this?** A: Helpful but not required. Saga will ask questions that surface what you know. Mark unknowns as knowledge gaps. diff --git a/docs/learn/module-07-design-phase/lesson-01-entering-design.md b/docs/learn/module-07-design-phase/lesson-01-entering-design.md index ae57371b1..3b3b5600b 100644 --- a/docs/learn/module-07-design-phase/lesson-01-entering-design.md +++ b/docs/learn/module-07-design-phase/lesson-01-entering-design.md @@ -192,7 +192,7 @@ By the end of this phase: | **Component definitions** | Reusable patterns identified | | **Visual designs** | Final look and feel | | **Design system** | Your component library | -| **Delivery package** | Ready for Idunn to implement | +| **Delivery package** | Ready for implementation | --- diff --git a/docs/learn/module-07-design-phase/lesson-02-why-specifications-matter.md b/docs/learn/module-07-design-phase/lesson-02-why-specifications-matter.md index e298c8cd7..0b1f8f0ff 100644 --- a/docs/learn/module-07-design-phase/lesson-02-why-specifications-matter.md +++ b/docs/learn/module-07-design-phase/lesson-02-why-specifications-matter.md @@ -550,7 +550,7 @@ Spec phase: Define exactly what you want (upfront investment) Specifications: Document every detail (with Freya) Code phase: Agent builds it correctly (first time) - Idunn reads specs + Freya reads specs Generates code matching specifications exactly Includes tests from specs diff --git a/docs/learn/module-07-design-phase/lesson-03-meet-freya.md b/docs/learn/module-07-design-phase/lesson-03-meet-freya.md index 3e8bde55d..37181e4bc 100644 --- a/docs/learn/module-07-design-phase/lesson-03-meet-freya.md +++ b/docs/learn/module-07-design-phase/lesson-03-meet-freya.md @@ -146,18 +146,17 @@ Finally, Freya helps apply visual language to your specifications and packages e **Don't start with Freya when:** - You haven't completed the strategic foundation yet (go back to Saga) -- You want to write code (that's Idunn's domain) +- You want to write code (that's handled in a development session) - You're still figuring out business goals or target groups -### The Three Agents — Quick Reference +### The Two Agents — Quick Reference | Agent | Domain | When to Use | |-------|--------|------------| | **Saga** | Strategy | Product Brief, Trigger Mapping, Platform Requirements | | **Freya** | Design | Scenarios, Sketching, Specifications, Components, Visual Design | -| **Idunn** | Implementation | Prototyping, Development, Verification | -Saga hands off to Freya. Freya hands off to Idunn. But the handoff isn't one-way — you'll often loop back to earlier stages as you learn from design and implementation. +Saga hands off to Freya. Freya handles both design and development. But the workflow isn't one-way — you'll often loop back to earlier stages as you learn from design and implementation. --- diff --git a/docs/learn/module-14-agentic-development/lesson-01-iterative-building.md b/docs/learn/module-14-agentic-development/lesson-01-iterative-building.md index adf253c74..bcb5c26a6 100644 --- a/docs/learn/module-14-agentic-development/lesson-01-iterative-building.md +++ b/docs/learn/module-14-agentic-development/lesson-01-iterative-building.md @@ -1,6 +1,6 @@ # Module 14: Agentic Development -## Lesson 1: The Development Agent Dialog +## Lesson 1: The Development Design Log **How the process is organized** @@ -8,7 +8,7 @@ ## Every Session Starts with a Plan -When you ask Freya or Idunn to develop something, the first thing the agent does is create an **Agent Dialog**. +When you ask Freya to develop something, the first thing the agent does is create a **Design Log**. This isn't documentation after the fact. It's the plan *before* anything is built. @@ -23,15 +23,15 @@ Then the agent starts executing. One step at a time. --- -## The Agent Dialog Document +## The Design Log Document ```markdown -# Agent Dialog: Signup Form +# Design Log: Signup Form ## Meta - Date: 2026-02-10 - Input: P02-signup-form.md (specification) -- Agent: Idunn +- Agent: Freya - Status: In Progress ## Scope @@ -128,15 +128,15 @@ The plan is not a contract. It's a compass. ## Types of Agentic Sessions -The same Agent Dialog structure works for all types: +The same Design Log structure works for all types: | Type | Example | Agent | |------|---------|-------| | **Concept exploration** | "Dream up a dashboard layout for dog trainers" | Freya | -| **Proof of concept** | "Can we do infinite scroll with this data model?" | Idunn | -| **Prototype** | "Build a working signup form from this spec" | Idunn | +| **Proof of concept** | "Can we do infinite scroll with this data model?" | Freya | +| **Prototype** | "Build a working signup form from this spec" | Freya | | **Design inspiration** | "Generate 3 visual directions for the landing page" | Freya | -| **Production code** | "Implement the complete registration scenario" | Idunn | +| **Production code** | "Implement the complete registration scenario" | Freya | The scope and depth change. The process doesn't. @@ -146,11 +146,11 @@ The scope and depth change. The process doesn't. ### Starting a new session -Load the Agent Dialog into your new conversation: +Load the Design Log into your new conversation: ``` "I'm continuing the signup form implementation. -Here's the current Agent Dialog with plan and log: +Here's the current Design Log with plan and log: [Paste dialog.md content] @@ -161,9 +161,9 @@ The agent picks up from the log, not from memory. ### Handing off between agents -Freya dreamed up a component. Now Idunn needs to build it. +You dreamed up a component in a design session. Now you need to build it. -The Agent Dialog travels with the work. Idunn reads Freya's dialog and continues where she left off. +The Design Log travels with the work. The agent reads the previous design log and continues where it left off. --- diff --git a/docs/learn/module-14-agentic-development/lesson-02-documenting-decisions.md b/docs/learn/module-14-agentic-development/lesson-02-documenting-decisions.md index 6b02f4199..c67c5a88b 100644 --- a/docs/learn/module-14-agentic-development/lesson-02-documenting-decisions.md +++ b/docs/learn/module-14-agentic-development/lesson-02-documenting-decisions.md @@ -101,7 +101,7 @@ Not everything is in the spec. Use your design judgment: ## Re-evaluating the Plan -After evaluation, open the Agent Dialog and update the task list. +After evaluation, open the Design Log and update the task list. **Before step 3:** ```markdown diff --git a/docs/learn/module-14-agentic-development/lesson-03-when-you-get-stuck.md b/docs/learn/module-14-agentic-development/lesson-03-when-you-get-stuck.md index d820aa4d7..0fb762ddf 100644 --- a/docs/learn/module-14-agentic-development/lesson-03-when-you-get-stuck.md +++ b/docs/learn/module-14-agentic-development/lesson-03-when-you-get-stuck.md @@ -118,9 +118,9 @@ This is the hardest moment for a designer working with AI: admitting the agent c ### How to Ask -Don't come empty-handed. Bring your Agent Dialog: +Don't come empty-handed. Bring your Design Log: -> "I've been building the signup form. Here's my Agent Dialog with everything we tried. +> "I've been building the signup form. Here's my Design Log with everything we tried. > > The issue: error messages work on desktop but disappear on mobile. The agent tried 4 different approaches (logged in the dialog). None worked. > @@ -130,7 +130,7 @@ The dialog shows what you've tried. The developer doesn't start from zero. ### What to Document -When a developer fixes the issue, add it to your Agent Dialog: +When a developer fixes the issue, add it to your Design Log: ```markdown ### Step 4: Error states on mobile (resolved with developer help) diff --git a/docs/learn/module-14-agentic-development/lesson-04-working-with-code.md b/docs/learn/module-14-agentic-development/lesson-04-working-with-code.md index 0944db44d..71058497f 100644 --- a/docs/learn/module-14-agentic-development/lesson-04-working-with-code.md +++ b/docs/learn/module-14-agentic-development/lesson-04-working-with-code.md @@ -108,7 +108,7 @@ Your design tokens (Module 13) define the rules. The component library implement | Spacing: 8px scale | `spacing: { 1: '8px', 2: '16px', ... }` | | Button: primary variant | `