whiteport-design-studio 0.3.2 → 0.3.4

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.2",
+  "version": "0.3.4",
   "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/agent-guides/saga/working-with-existing-materials.md

@@ -1,16 +1,16 @@
 # Working with Existing Materials
 
-**Purpose:** Guide for naturally incorporating existing materials into conversational PB workflow.
+**Purpose:** Guide for incorporating existing materials into the PB workflow. When users provide documentation, Saga MUST analyze it first, present findings for confirmation, and only ask questions about gaps.
 
 ---
 
 ## Core Principles
 
-1. **Reference, don't re-ask** - Build on documented work
-2. **Validate currency** - "Is this still accurate?"
-3. **Focus on gaps** - What's missing or needs refinement?
-4. **Document refinement** - Capture UPDATE conversation, not just creation
-5. **Stay casual** - No judgment about what exists or doesn't
+1. **Analyze first, ask second** — Read and extract before any questions
+2. **Present, don't pocket** — Show the user what you found, structured by topic
+3. **Confirm step by step** — Each extracted insight gets a yes/no/refine from the user
+4. **Only ask about gaps** — If the answer is in the document, don't ask the question
+5. **Stay casual** — No judgment about what exists or doesn't
 
 ---
 
@@ -29,26 +29,126 @@ existing_materials:
   context_notes: "[brief notes]"
 ```
 
-**If materials exist:** Read them before starting PB steps
+**If materials exist:** Read them COMPLETELY before starting PB steps. Then run the Material Analysis Phase.
 
 ---
 
-## Adaptation Pattern
+## Material Analysis Phase (MANDATORY when materials exist)
 
-### Opening Adaptation
+This phase runs ONCE, after Step 1 (Init) and BEFORE Step 2 (Vision). It replaces the old "reference and ask" pattern with "analyze, present, confirm, then fill gaps."
 
-**Without materials:**
-> "Let's start with vision. What are you envisioning?"
+### Step A: Read and Extract
 
-**With materials:**
-> "I see you mentioned [reference from materials]. Let's build on that - tell me more."
+Read every provided document completely. Extract information into these categories:
 
-### Follow-Up Patterns
+| Category | What to look for |
+|----------|-----------------|
+| **Vision** | Purpose, mission, "why this exists", aspirational statements |
+| **Positioning** | Target market, differentiators, alternatives, category |
+| **Business Model** | Revenue, pricing, monetization, cost structure |
+| **Target Users** | User types, personas, segments, pain points |
+| **Product Concept** | Core features, key interactions, product shape |
+| **Success Criteria** | KPIs, metrics, milestones, definition of done |
+| **Competitive Landscape** | Named competitors, alternatives, market gaps |
+| **Constraints** | Technical limits, budget, timeline, team, regulations |
+| **Tone & Brand** | Voice, personality, visual direction, existing brand |
 
-- **Validate:** "You wrote X - is that still accurate?"
-- **Fill gaps:** "Your brief mentions Y, but I'm curious about Z..."
-- **Refine:** "When you said X, did you mean [interpretation]?"
-- **Update:** "Has your thinking evolved since you wrote this?"
+For each category, note:
+- **Complete** — enough information to draft this section
+- **Partial** — some information, needs clarification or expansion
+- **Missing** — not covered in the materials
+
+### Step B: Present the Analysis
+
+Present your findings to the user, organized by category. Use this pattern:
+
+```
+I've read through your materials. Here's what I found — let me walk you through
+it section by section so you can confirm, correct, or add to each one.
+
+**Vision**
+From your [document name]: "[relevant quote or paraphrase]"
+My interpretation: [your synthesis in one sentence]
+→ Does this capture it? Anything that's evolved?
+
+**Positioning**
+From your [document name]: "[relevant quote or paraphrase]"
+My interpretation: [your synthesis]
+→ Still the direction?
+
+[...continue for each category that has content...]
+```
+
+**Rules for presentation:**
+- Present ONE category at a time. Wait for user response before moving to the next.
+- Quote or closely paraphrase the source material so the user can see what you're working from
+- Add your interpretation — this is where your strategic thinking adds value
+- Ask for confirmation explicitly: ✓ confirm / ✗ reject / ~ refine
+- If the user refines, capture the refinement before moving on
+
+### Step C: Identify Gaps
+
+After all extracted categories are confirmed, present the gaps:
+
+```
+That covers what I found in your materials. Here's what we still need to explore:
+
+- [Gap 1]: Not covered in your documents
+- [Gap 2]: Mentioned briefly but needs more depth
+- [Gap 3]: Implied but not explicit
+
+These are the topics I'll focus our conversation on.
+The rest is already solid from your materials.
+```
+
+### Step D: Adjusted Workflow Plan
+
+Tell the user which steps will be quick confirmations vs. full conversations:
+
+```
+Here's how the rest of the workflow will go:
+
+Quick confirmation (already covered):
+- Vision ✓ — confirmed from your materials
+- Target Users ✓ — confirmed from your materials
+
+Needs conversation (gaps to fill):
+- Competitive Landscape — not covered yet
+- Success Criteria — mentioned but needs specifics
+- Constraints — partially covered, need technical details
+
+This should be much faster since you've already done a lot of the thinking.
+```
+
+---
+
+## Adapted Step Execution (after Material Analysis)
+
+Once the Material Analysis Phase is complete, each subsequent step runs in one of two modes:
+
+### Confirmation Mode (category = Complete)
+
+The step's content was already extracted and confirmed during the analysis phase. The step becomes a quick pass:
+
+1. Reference the confirmed content: "We already confirmed your vision as [synthesis]. I've documented it."
+2. Ask if anything to add: "Anything else before we move on?"
+3. If nothing: document and advance
+4. If additions: capture them, update, confirm, advance
+
+**This replaces the full exploratory conversation.** Do NOT re-ask questions the user already answered during the analysis phase.
+
+### Gap-Filling Mode (category = Partial or Missing)
+
+The step needs real conversation, but scoped to what's missing:
+
+1. Reference what IS known: "From your materials, I know [X]. What I'm missing is [Y]."
+2. Explore only the gap — do not re-cover confirmed ground
+3. Synthesize the gap content with the confirmed content
+4. Present the combined picture for confirmation
+
+### CRITICAL RULE
+
+**Never re-ask a question whose answer was already confirmed in the Material Analysis Phase.** If the user confirmed their vision during analysis, Step 2 (Vision) should take 30 seconds, not 10 minutes. The exploratory conversation pattern is for discovery — when materials exist, the discovery already happened.
 
 ---
 
@@ -56,15 +156,14 @@ existing_materials:
 
 **Apply to all conversational steps** (2, 3, 5, 7, 7a, 8, 9, 10, 11, 12):
 
-| Step | No Materials | With Materials |
-|------|-------------|----------------|
-| Vision (2) | "What are you envisioning?" | "You mentioned [vision]. Tell me more." |
-| Positioning (3) | "Let's explore positioning." | "Your brief positions this as [quote]. Still accurate?" |
-| Users (7) | "Who are ideal users?" | "You described [archetypes]. Still primary users?" |
-| Concept (7a) | "What's the core concept?" | "I see [concept from materials]. Tell me more about that principle." |
-| Success (8) | "What does success look like?" | "You mentioned success means [quote]. Still the goal?" |
-
-**Pattern:** Reference existing → Validate → Build on it
+| Step | No Materials | With Materials (Confirmed) | With Materials (Gap) |
+|------|-------------|---------------------------|---------------------|
+| Vision (2) | Full exploration | "Confirmed as [X]. Anything to add?" | "You mentioned [X] but I need [Y]." |
+| Positioning (3) | Full exploration | "Confirmed as [X]. Anything to add?" | "Target is clear, but differentiator needs work." |
+| Business Model (5) | Full exploration | "Confirmed as [X]. Anything to add?" | "Revenue model clear, pricing needs detail." |
+| Users (7) | Full exploration | "Confirmed as [X]. Anything to add?" | "Primary users clear, need to explore secondary." |
+| Concept (7a) | Full exploration | "Confirmed as [X]. Anything to add?" | "Core concept clear, need interaction model." |
+| Success (8) | Full exploration | "Confirmed as [X]. Anything to add?" | "Goals clear, need measurable KPIs." |
 
 ---
 
@@ -73,83 +172,91 @@ existing_materials:
 When materials exist, capture:
 
 1. **What existed:** Quote/summarize existing material
-2. **Validation:** User's response to "Is this still accurate?"
-3. **Refinement:** What changed, added, or clarified
-4. **Why:** Rationale for changes
-5. **Synthesis:** Updated version (old + new integrated)
+2. **Analysis presented:** What Saga extracted and interpreted
+3. **User response:** Confirmed / Refined / Rejected
+4. **Gaps identified:** What was missing
+5. **Gap conversation:** Discovery for missing pieces only
+6. **Synthesis:** Final version (confirmed material + gap fills + refinements)
 
 **Template:**
 
 ```markdown
-**Existing context:** [What was documented]
+**Source material:** [Document name, relevant section]
 
-**Opening:** "I see [reference]. [Question]"
+**Saga's extraction:**
+> [Quote from material]
+Interpretation: [Saga's synthesis]
 
-**User response:** [Confirmed/refined/changed]
+**User response:** [Confirmed ✓ / Refined ~ / Rejected ✗]
+[If refined/rejected: what changed and why]
 
-**Key exchanges:**
-- [Exploration]
-- [Gaps filled]
-- [Evolution]
+**Gaps explored:**
+- [Gap topic]: [Discovery conversation summary]
 
-**Reflection checkpoint:**
-"Building on your earlier work: [synthesis].
-Keeps [solid parts], adds [new], refines [changed].
-Does that capture it?"
+**Final synthesis:** [Confirmed content + gap fills integrated]
 
 **User confirmation:** [Confirmed / Corrected]
-
-**Final:** [Updated artifact]
 ```
 
 ---
 
 ## Common Scenarios
 
+**Scenario: Comprehensive PRD provided**
+1. Read it thoroughly — this is the primary source
+2. Run full Material Analysis Phase (Steps A-D)
+3. Most categories will be Complete — workflow becomes mostly confirmations
+4. Focus conversation on strategic gaps (positioning nuance, success metrics, constraints)
+5. Result: 15-minute workflow instead of 60-minute workflow
+
 **Scenario: Previous brief exists**
 1. Read it thoroughly
-2. Identify solid vs gaps/unclear
-3. Open: "I read your brief. [Strong points] captured well. Questions about [gaps]."
-4. Explore gaps conversationally
-5. Dialog: what was there + what we added + why
+2. Run Material Analysis Phase
+3. Identify what's solid vs outdated vs missing
+4. Present: "Your brief from [date] covers X, Y, Z well. Has anything evolved?"
+5. Focus on evolution and gaps
 
 **Scenario: Existing website**
 1. Review site (if URL in materials)
-2. Note current positioning/tone/UX
-3. Reference: "I looked at your site. It positions you as [observation]. Still the direction?"
+2. Extract positioning, tone, target audience signals
+3. Present observations: "Your site positions you as [X], targets [Y], tone is [Z]"
 4. Use as baseline for "what's changing?"
 
 **Scenario: Brand guidelines exist**
 1. Read guidelines (voice, values, identity)
-2. Reference when discussing tone: "Your guidelines describe tone as [quote]. Match exactly or evolve?"
-3. Don't re-ask defined things (colors, values)
-4. Focus on how brand translates to this project
-
-**Scenario: Research exists**
-1. Review findings
-2. Reference insights: "Your research showed [finding]. Great insight for..."
-3. Validate currency: "Is this still what you hear from customers?"
+2. Extract: personality, tone, visual direction, constraints
+3. Present: "Your brand guidelines define [X]. These carry forward unless you say otherwise."
+4. Mark brand-related categories as Complete
+5. Focus on how brand translates to this specific product
+
+**Scenario: Research / user interviews exist**
+1. Review findings thoroughly
+2. Extract: user pain points, needs, behaviors, quotes
+3. Present: "Your research identified these user patterns: [list]"
+4. Validate currency: "Is this still what you hear from users?"
+5. Use as foundation for Target Users and Success Criteria steps
 
 ---
 
 ## What NOT to Do
 
-❌ Ignore existing materials (if outline says they exist)
-❌ Make users repeat documented work
-❌ Assume everything is still current (validate!)
-❌ Judge quality of existing work
-❌ Create separate "refinement workflow" (same conversational pattern, just adapt openings)
+- Say "thank you" and move on as if nothing was provided
+- Pocket the information silently and only reference it in passing
+- Ask questions whose answers are clearly in the provided documents
+- Make the user repeat or re-explain documented work
+- Assume everything is still current without asking (validate!)
+- Judge quality of existing work
+- Skip the Material Analysis Phase and go straight to step-by-step questions
 
 ---
 
 ## Benefits
 
-✅ Efficiency - Don't re-explore documented areas
-✅ Continuity - Build on previous work
-✅ Respect - Acknowledge existing thinking
-✅ Focus - Spend time on gaps/unclear areas
-✅ Natural flow - Same pattern, context-aware
-✅ Rich dialog - Captures refinement, not just creation
+- Efficiency — 15 minutes instead of 60 when materials are comprehensive
+- Respect — Acknowledges the thinking already done
+- Trust — User sees that Saga actually read and understood their materials
+- Focus — Conversation time spent on real gaps, not re-discovery
+- Quality — Final brief builds on confirmed foundation, not fresh guesses
 
 ---
 
@@ -157,16 +264,18 @@ Does that capture it?"
 
 **Check:** `existing_materials.has_materials` in outline
 
-**If true:**
-1. Read materials before starting PB
-2. Adapt openings to reference what exists
-3. Validate currency with each step
-4. Fill gaps conversationally
-5. Document: old + new + why
+**If true — run Material Analysis Phase:**
+1. Read ALL materials completely
+2. Extract information into categories (vision, positioning, users, etc.)
+3. Present findings ONE category at a time, wait for confirmation
+4. Identify gaps after all categories confirmed
+5. Tell user which steps will be quick vs. need conversation
+6. Execute steps in Confirmation Mode or Gap-Filling Mode accordingly
 
-**Dialog pattern:** Existing → Validate → Refine → Synthesize → Confirm
+**If false — run standard discovery:**
+1. Full exploratory conversation per step
+2. Standard pattern: Open → Explore → Reflect → Synthesize → Confirm
 
 ---
 
-**Remember:** Not a separate workflow - same conversational pattern, just context-aware.
-If materials exist, read and adapt. If not, explore from scratch. Either way, natural conversation.
+**The golden rule:** If the user gave you a document, they expect you to USE it — not just acknowledge it. Analyze it, show them what you found, and only ask about what's missing.