whiteport-design-studio 0.2.2 → 0.3.0

package/src/data/agent-guides/freya/content-creation.md

@@ -53,7 +53,7 @@
 - Time is tight
 
 **Process:**
-1. Load VTC for context
+1. Load Trigger Map for context
 2. Consider Customer Awareness
 3. Apply Golden Circle (WHY → HOW → WHAT)
 4. Generate options
@@ -73,7 +73,7 @@ Load: `{project-root}/_bmad/wds/workflows/6-asset-generation/`
 
 **6-Step Framework:**
 1. Define purpose & success criteria
-2. Load VTC context
+2. Load Trigger Map context
 3. Apply Customer Awareness strategy
 4. Filter with Action Mapping
 5. Frame with Badass Users
@@ -95,7 +95,7 @@ Load: `{project-root}/_bmad/wds/workflows/6-asset-generation/`
 
 ---
 
-### 2. Value Trigger Chain (VTC)
+### 2. Trigger Map
 **Strategic foundation**
 
 - Business Goal: What are we trying to achieve?
@@ -167,7 +167,7 @@ Features (WHAT): 10K templates, smart pricing, e-signatures
 
 **Think of them as lenses, not sequential steps:**
 
-1. **VTC** = Which driving force to trigger?
+1. **Trigger Map** = Which driving force to trigger?
 2. **Customer Awareness** = What language can they understand?
 3. **Golden Circle** = In what order should I present?
 4. **Action Mapping** = Is this enabling action?
@@ -203,7 +203,7 @@ Features (WHAT): 10K templates, smart pricing, e-signatures
 - Golden Circle: ⭐⭐⭐
 - Badass Users: ⭐⭐
 - Action Mapping: ⭐
-- VTC: Always loaded
+- Trigger Map: Always loaded
 - Content Purpose: Always defined
 
 ### Feature Description
@@ -211,7 +211,7 @@ Features (WHAT): 10K templates, smart pricing, e-signatures
 - Badass Users: ⭐⭐⭐
 - Customer Awareness: ⭐⭐
 - Golden Circle: ⭐
-- VTC: Always loaded
+- Trigger Map: Always loaded
 - Content Purpose: Always defined
 
 ### Error Messages
@@ -245,7 +245,7 @@ Features (WHAT): 10K templates, smart pricing, e-signatures
 **Before creating any strategic content:**
 
 1. **Define purpose** - What job does this do?
-2. **Load VTC** - Which driving forces?
+2. **Load Trigger Map** - Which driving forces?
 3. **Check awareness** - Where are users?
 4. **Apply Golden Circle** - WHY → HOW → WHAT
 5. **Filter with Action** - Does it enable action?

package/src/data/agent-guides/freya/strategic-design.md

@@ -15,8 +15,7 @@
 ### 1. Load Strategic Context
 
 **Ask yourself:**
-- Is there a VTC (Value Trigger Chain) for this page/scenario?
-- What's in the Trigger Map?
+- What's in the Trigger Map for this page/scenario?
 - What does the Product Brief say?
 
 **If missing:** Suggest creating one first. Design without strategy is decoration.
@@ -37,7 +36,7 @@
 
 ### 3. Identify User Driving Forces
 
-**From the VTC/Trigger Map, ask:**
+**From the Trigger Map, ask:**
 - What positive driving forces should we trigger? (wishes, desires, aspirations)
 - What negative driving forces should we address? (fears, frustrations, anxieties)
 
@@ -86,7 +85,7 @@ Hero Section:
 
 Before finalizing any design:
 
-- [ ] **VTC Connection** - Which driving force does this serve?
+- [ ] **Trigger Map** - Which driving force does this serve?
 - [ ] **Business Goal** - How does this support our objectives?
 - [ ] **Customer Awareness** - Appropriate for their awareness stage?
 - [ ] **Golden Circle** - WHY before HOW before WHAT?
@@ -98,7 +97,7 @@ Before finalizing any design:
 
 **If you can't connect a design choice to strategy:**
 1. It might not be needed (remove it)
-2. You need more strategic context (ask for VTC/Trigger Map)
+2. You need more strategic context (ask for Trigger Map)
 3. There's a better alternative (explore options)
 
 **Never guess.** Always design with intent.
@@ -107,7 +106,6 @@ Before finalizing any design:
 
 ## Related Resources
 
-- **VTC Workshop:** `../../workflows/1-project-brief/_vtc-workshop/`
 - **Trigger Mapping:** `../../docs/method/phase-2-trigger-mapping-guide.md`
 - **Customer Awareness:** `../../docs/models/customer-awareness-cycle.md`
 - **Golden Circle:** `../../docs/models/golden-circle.md`

package/src/data/agent-guides/saga/discovery-conversation.md

@@ -233,6 +233,26 @@ Not:
 
 ---
 
+## Cross-Step Context Awareness
+
+### Never Re-Ask What You Already Know
+
+When loading a new step, ALWAYS check what was captured in prior steps. The design log and previous step outputs contain previous answers.
+
+**Pattern:**
+1. Before asking your first question in a new step, review available context from prior steps
+2. Reference prior answers: "Earlier you mentioned [X]..."
+3. Ask only for NEW information: "Building on that, I'd like to explore [Y]..."
+4. If user says "I already told you" — immediately acknowledge and skip
+
+**Example:**
+- Step 3 captured positioning target: "busy professionals"
+- Step 7 asks about target users
+- WRONG: "Who are you building this for?"
+- RIGHT: "You positioned this for busy professionals. Let's build a behavioral profile — tell me about their daily experience with [problem]."
+
+---
+
 ## Related Resources
 
 - **Product Brief Workflow:** `../../workflows/1-project-brief/project-brief/`

package/src/data/agent-guides/saga/dream-up-approach.md

@@ -129,7 +129,7 @@ docs/method/dream-up-rubric-phase-2.md
 - ✅ Context declaration (explicit usage context)
 - ✅ Visual connection diagram (shows logic flow)
 
-**Document in agent dialog:**
+**Document in design log:**
 
 ```markdown
 ## Layer 1: WDS Form Learned
@@ -153,6 +153,44 @@ docs/method/dream-up-rubric-phase-2.md
 
 ---
 
+### For Phase 3 (Scenarios)
+
+**Load these WDS learning materials:**
+```
+src/workflows/3-scenarios/data/quality-checklist.md
+src/workflows/3-scenarios/data/scenario-outline-template.md
+src/workflows/3-scenarios/data/validation-standards.md
+```
+
+**Learn and internalize:**
+
+#### Structure Requirements
+- Scenario has 7 required components (Name, Core Feature, Entry Point, Mental State, Success Goals, Shortest Path, Trigger Map Connections)
+- Entry points must be realistic (device + context + discovery) — max 2 sentences
+- Mental states must be visceral (Trigger/Hope/Worry) — one sentence each
+- Paths must be linear (zero branches, minimum viable steps)
+- Success goals must be mutual (user + business, both measurable)
+
+#### Quality Criteria (from quality-checklist.md)
+1. **Persona Alignment** — Serves specific Trigger Map persona
+2. **Mental State Richness** — Visceral, not generic
+3. **Mutual Success Clarity** — Both specific and measurable
+4. **Sunshine Path Focus** — Completely linear
+5. **Minimum Viable Steps** — Each justifies existence
+6. **Entry Point Realism** — Real-world behavior
+7. **Business Goal Connection** — Traces to Trigger Map
+
+#### Common Mistakes to Avoid
+- Edge cases in sunshine path (zero "if" statements)
+- Feature-first naming (use persona + purpose)
+- Missing mental state components
+- Vague page descriptions
+- Generic persona ("user" instead of named persona)
+- Missing business value
+- Bloated descriptions (max 2 sentences per entry point, 1 sentence per mental state component)
+
+---
+
 ## Layer 2: Project Context (Cumulative)
 
 **Purpose:** Extract substance from prior artifacts. Layer 2 GROWS with each step.
@@ -195,7 +233,7 @@ docs/method/dream-up-rubric-phase-2.md
 - SEO keywords (if relevant)
 - Future plans
 
-**Document in agent dialog:**
+**Document in design log:**
 
 ```markdown
 ## Layer 2: Project Context (Initial Load)
@@ -268,6 +306,24 @@ docs/method/dream-up-rubric-phase-2.md
 
 **Key Principle:** Each subsequent generation step uses ALL prior artifacts from Layer 2.
 
+### For Phase 3: Cumulative Context Growth
+
+**Initial Load (start of Phase 3):**
+- Product Brief (all 4 documents from Phase 1)
+- Trigger Map (all documents from Phase 2)
+- Strategic context (business goal, persona, driving forces)
+
+**After each scenario outlined:**
+```markdown
+### Scenario [NN] (Added to Layer 2)
+**Persona:** [Name]
+**Pages covered:** [List]
+**Driving forces addressed:** [Which ones from Trigger Map]
+**Remaining unaddressed forces:** [What still needs scenarios]
+```
+
+**Key Rule:** Each subsequent scenario should address DIFFERENT driving forces. Check Layer 2 to avoid duplicating coverage.
+
 ---
 
 ## Layer 3: Domain Research (Ongoing)
@@ -335,6 +391,23 @@ Forums: Reddit r/travel, car forums about breakdowns while traveling
 [How research will be applied to this step]
 ```
 
+### For Phase 3 (Scenarios)
+
+**For Entry Points:**
+- WebSearch: "[user type] how they find [service type]"
+- WebSearch: "[device type] user behavior [context]"
+- Look for: Real search terms, realistic discovery paths, device usage statistics
+
+**For Mental States:**
+- WebSearch: "[situation] user emotions anxiety"
+- WebSearch: "[service] customer reviews pain points"
+- Look for: Actual user language from reviews and forums — visceral, specific feelings
+
+**For Shortest Paths:**
+- WebSearch: "[similar service] website user flow best practices"
+- WebSearch: "[industry] conversion funnel steps"
+- Look for: Industry-standard page flows, minimum viable steps for this type of service
+
 ---
 
 ## Layer 4: Generate Artifact
@@ -624,6 +697,23 @@ For each of 7 criteria: ✅ (met), ⚠️ (partial), ❌ (gap)
 
 **Then generate Iteration N+1 with refinements applied, using full 5-layer process again.**
 
+### Self-Review for Phase 3 (Scenarios)
+
+**Use `quality-checklist.md` directly as the rubric.** The checklist has 4 dimensions:
+
+1. **Completeness** (7 sections) — target 7/7
+2. **Quality Criteria** (7 checks) — target 5/7 minimum
+3. **Common Mistakes** (7 checks) — target 7/7 (zero tolerance)
+4. **Best Practices** (4 checks) — target 2/4 minimum
+
+**Run quality-checklist.md against each generated scenario. Score using the checklist's own format.**
+
+**Refinement triggers for scenarios:**
+- Any Dimension 3 failure (Common Mistakes) → immediate fix (zero tolerance)
+- Dimension 1 below 6/7 → fix before proceeding
+- Dimension 2 below 5/7 → refine mental state and success goals first (most common gap)
+- Bloated descriptions (Dimension 3.7) → trim to max lengths before any other refinement
+
 ---
 
 ## Mode-Specific Presentation
@@ -720,6 +810,41 @@ Would you like to review the full Trigger Map now?
 
 ---
 
+## Layer 6: Completeness Gate (Dream Mode Only)
+
+**Purpose:** After all Layer 5 self-reviews pass, verify ALL required output documents exist before presenting results.
+
+### Required Documents Checklist
+
+Run this gate after autonomous generation completes:
+
+**Mandatory files in `{output_folder}/B-Trigger-Map/`:**
+- [ ] `00-trigger-map.md` — Hub document with Mermaid diagram
+- [ ] `01-Business-Goals.md` — Vision + SMART objectives
+- [ ] One persona document per target group (`02-XX.md`, `03-XX.md`, etc.)
+- [ ] `05-Key-Insights.md` — Strategic insights summary
+
+**Conditional files:**
+- [ ] `06-Feature-Impact.md` — Only if feature impact workshop was completed
+
+### Validation Rules:
+- Each file must be non-empty (contains actual content, not just headers)
+- Hub document must contain a Mermaid code block
+- Persona count must match the number of target groups from workshops
+- Business Goals must contain vision + at least 2 SMART objectives
+
+### IF any file missing or empty:
+1. Identify which file is missing
+2. Re-run Layer 4 generation for that specific artifact
+3. Re-run Layer 5 self-review for that artifact
+4. Re-check this gate
+
+### IF 3 retries fail for any file:
+Switch to Suggest mode for the missing artifact:
+> "I generated most of the Trigger Map autonomously, but [missing artifact] needs your input. Let's switch to Suggest mode for this section."
+
+---
+
 ## Final Output Presentation
 
 **When all steps complete and threshold met:**
@@ -792,12 +917,12 @@ Would you like to:
 
 ---
 
-## Agent Dialog Documentation
+## Design Log Documentation
 
-**Throughout process, maintain comprehensive agent dialog:**
+**Throughout process, maintain comprehensive agent experience log:**
 
 ```markdown
-# Agent Dialog: Dream Up - Källa Trigger Map
+# Agent Experience: Dream Up - Källa Trigger Map
 
 **Created:** {{date time}}
 **Mode:** {{Suggest/Dream}}
@@ -871,9 +996,9 @@ Would you like to:
 [Strategic choices during generation]
 ```
 
-**Save agent dialog at:**
+**Save agent experience at:**
 ```
-{output_folder}/_progress/agent-dialogs/{date}-trigger-map-{{mode}}.md
+{output_folder}/_progress/agent-experiences/{date}-trigger-map-{{mode}}.md
 ```
 
 ---

package/src/data/agent-guides/saga/strategic-documentation.md

@@ -105,18 +105,16 @@ design_system:
 
 ---
 
-### 3. Value Trigger Chain (VTC)
+### 3. Strategic Context (from Trigger Map)
 **Strategic benchmark for early decisions**
 
-Created in Step 4 (early in the brief) to provide strategic grounding:
+Extracted from the Trigger Map to provide strategic grounding:
 - Business goal
 - Solution context
-- User
+- Target group / persona
 - Driving forces (positive + negative)
 - Customer awareness progression
 
-**See:** VTC micro-guide for Freya (also relevant for Saga)
-
 ---
 
 ### 4. Business Model
@@ -210,7 +208,7 @@ Created in Step 4 (early in the brief) to provide strategic grounding:
 
 ---
 
-### 12. Synthesize
+### 12. Create Product Brief
 **Bring it all together**
 
 Generate complete Product Brief document using template.

package/src/data/agent-guides/saga/trigger-mapping.md

@@ -562,9 +562,9 @@ Scenario adds:
 
 ---
 
-## Trigger Map → VTC Connection
+## Trigger Map → Design Context
 
-**VTC is extracted from Trigger Map:**
+**For a specific design task, extract the relevant slice:**
 
 ```
 Trigger Map (Comprehensive):
@@ -573,14 +573,14 @@ Trigger Map (Comprehensive):
 ├── 12 detailed personas
 └── 40+ driving forces
 
-VTC (Focused):
+Design Context (Focused):
 ├── 1 business goal
-├── 1 user/persona
+├── 1 persona
 ├── 1 solution context
 └── 3-5 key driving forces
 ```
 
-**VTC is the "working copy" for a specific design task.**
+**The focused context is the "working copy" for a specific design task.**
 
 ---
 
@@ -633,7 +633,7 @@ graph TD
 **Process:**
 1. Create new version (v2)
 2. Document what changed and why
-3. Update any VTCs derived from map
+3. Review impact on active design work
 4. Keep old version for reference
 
 ---
@@ -642,7 +642,7 @@ graph TD
 
 - **Phase 2 Workflow:** `../../workflows/2-trigger-mapping/`
 - **Impact/Effect Mapping Model:** `../../docs/models/impact-effect-mapping.md`
-- **VTC Guide:** `../../docs/method/value-trigger-chain-guide.md`
+- **Trigger Mapping Guide:** `../../docs/method/phase-2-trigger-mapping-guide.md`
 - **Customer Awareness Cycle:** `../../docs/models/customer-awareness-cycle.md`
 - **Feature Impact Analysis:** Prioritization method based on Impact Mapping
 

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

@@ -75,4 +75,4 @@ Whether designing new features, refining experiences, building design foundation
 
 **Analyzing your project now...**
 
-_(Continue to: `{project-root}/_bmad/wds/workflows/_agent-dialogs/project-analysis/02-project-analysis-router.md`)_
+_(Continue to: Read `{output_folder}/_progress/00-design-log.md` and present the Adaptive Dashboard)_

package/src/data/presentations/freya-workflows-guide.md

@@ -28,7 +28,7 @@ Figma for refinement and component integration.
 
 ### 4. Agentic Development
 **When to use:** You want to build features iteratively with AI assistance.
-**What it does:** Guided implementation using agent dialogs — prototypes, code, bug fixes.
+**What it does:** Guided implementation using design log — prototypes, code, bug fixes.
 **Output:** Working implementations, prototype iterations
 **Best for:** When you're ready to go from spec to code with AI support.
 

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

@@ -71,4 +71,4 @@ Whether defining architecture, planning sprints, creating handoff packages, or c
 
 **Analyzing your project now...**
 
-_(Continue to: `{project-root}/_bmad/wds/workflows/_agent-dialogs/project-analysis/02-project-analysis-router.md`)_
+_(Continue to: Read `{output_folder}/_progress/00-design-log.md` and present the Adaptive Dashboard)_

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

@@ -72,4 +72,4 @@ Whether starting new products, clarifying direction, researching users, or defin
 
 **Analyzing your project now...**
 
-_(Continue to: `{project-root}/_bmad/wds/workflows/_agent-dialogs/project-analysis/02-project-analysis-router.md`)_
+_(Continue to: Read `{output_folder}/_progress/00-design-log.md` and present the Adaptive Dashboard)_

package/src/module-help.csv

@@ -1,5 +1,5 @@
 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 finds unfinished agent dialogs and offers contextually appropriate next steps. Use this to start Product Brief or Trigger Map work.",,,
+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",
@@ -14,6 +14,6 @@ wds,2-wds-design,Functional Components,FI,50,_bmad/wds/workflows/4-ux-design/wor
 wds,2-wds-design,Visual Design,VD,60,_bmad/wds/workflows/6-asset-generation/workflow.md,bmad-wds-visual-design,false,freya-ux,Create Mode,"Transform specifications into visual prototypes. Generate styled HTML prototypes from specs then refine with Figma round-trips using code.to.design or AI image generation. This is where soul enters the product. A visual designer should set the visual language — the AI applies it consistently.",design_artifacts/C-UX-Scenarios,"html-prototypes visual-designs",
 wds,2-wds-design,Design System,DS,70,_bmad/wds/workflows/7-design-system/workflow.md,bmad-wds-design-system,false,freya-ux,Create Mode,"Manage your component library based on project mode: None Building Library or Existing. Components and design tokens grow organically from your design work. Each project builds on the last. Skip if using Design System Mode None.",design_artifacts/D-Design-System,"components/ design-tokens.md",
 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/_agent-dialogs/workflow.md,bmad-wds-agentic-development,false,pm,Create Mode,"Build iteratively using Agent Dialogs. 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-dialogs,"dialog-documents",
+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 uses a Product Evolution Agent Dialog. 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,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",

package/src/skills/freya.activation.md

@@ -2,7 +2,7 @@
 
 **Invocation:** `/freya`
 **Icon:** ✨
-**Role:** UX Designer + Scenario Architect
+**Role:** UX Designer + Scenario Facilitator
 **Phases:** 3 (UX Scenarios), 4 (UX Design)
 
 ---
@@ -34,12 +34,12 @@ Let me check what you're working on...
 3. Filter out system repos (WDS, BMad expansion modules)
 4. For each WDS project repo found:
    - Read `wds-project-outline.yaml` for project name and phase status
-   - Scan `_progress/agent-dialogs/` for dialog files with status `In Progress` or `Not Started`
-   - Note any open dialogs related to Phases 3-4
+   - Read `_progress/00-design-log.md` — check Current table and Design Loop Status
+   - Note any in-progress work related to Phases 3-4
 
 **Multi-project branching logic:**
 
-**If multiple open agent dialogs found:**
+**If in-progress work found in multiple projects:**
 ```
 I found open work in multiple projects:
 1. [Project A]: [Phase X - task description]
@@ -48,7 +48,7 @@ I found open work in multiple projects:
 Which would you like to work on?
 ```
 
-**If no open dialogs but multiple projects:**
+**If no in-progress work but multiple projects:**
 ```
 I found [N] WDS projects in your workspace:
 1. [Project A] - Phase [X] status
@@ -64,7 +64,7 @@ Which project would you like to work on?
 - Check for my artifacts:
   - `C-UX-Scenarios/` folder (Phase 3)
   - `C-UX-Scenarios/` folder (Phase 3+4)
-- Check for open agent dialogs in that project
+- Check design log Current table for in-progress work
 - Note phase completion status
 
 ### 3. Status Report
@@ -83,26 +83,25 @@ Phase 4: UX Design        [✓ complete / ⏳ in-progress / ○ not started]
 ⚠️ Prerequisites missing: Need Saga to complete Phase 1-2 first
    Type /saga to call Saga
 
-[If open dialog found:]
-⏸ Unfinished work: [dialog-file-name.md]
-   Last task: [task description from dialog]
+[If Current table has task:]
+⏸ In progress: [task from Current table]
 
-[If no open dialogs:]
-○ No open agent dialogs for my phases
+[If Current is empty:]
+○ No work in progress for my phases
 ```
 
 ### 4. Offer Next Steps
 
 **Only shown for single-project scenario.** Based on status, offer appropriate actions:
 
-**If unfinished dialog found (default: resume):**
+**If Current table has a task (default: resume):**
 ```
-I found unfinished work in [dialog-file-name.md]:
-→ [task description from dialog]
+I found in-progress work:
+→ [task from Current table]
 
 Picking up where we left off...
 ```
-Read the dialog file, find the next incomplete step, and continue naturally.
+Read the design log, check Design Loop Status for current page state, and continue naturally.
 Only ask before resuming if the user's message clearly indicates a different task.
 
 **If prerequisites missing:**

package/src/skills/idunn.activation.md

@@ -35,12 +35,12 @@ Let me check your project status...
 3. Filter out system repos (WDS, BMad expansion modules)
 4. For each WDS project repo found:
    - Read `wds-project-outline.yaml` for project name and phase status
-   - Scan `_progress/agent-dialogs/` for dialog files with status `In Progress` or `Not Started`
-   - Note any open dialogs across ALL phases
+   - Read `_progress/00-design-log.md` — check Current table and Design Loop Status
+   - Note any in-progress work across ALL phases
 
 **Multi-project branching logic:**
 
-**If multiple open agent dialogs found:**
+**If in-progress work found in multiple projects:**
 ```
 I found open work in multiple projects:
 1. [Project A]: [Phase X - task description]
@@ -50,7 +50,7 @@ I found open work in multiple projects:
 Which would you like to work on?
 ```
 
-**If no open dialogs but multiple projects:**
+**If no in-progress work but multiple projects:**
 ```
 I found [N] WDS projects in your workspace:
 1. [Project A] - Latest phase: [X], Status: [...]
@@ -66,7 +66,7 @@ Which project would you like to work on?
   - Phase 2: `B-Trigger-Map/trigger-map.md`
   - Phase 3+4: `C-UX-Scenarios/` folder (scenarios, specs, prototypes)
   - Phase 5: `D-Design-System/` folder
-- Check for open agent dialogs in that project
+- Check design log Current table for in-progress work
 - Identify blockers or dependencies
 - List all completed/in-progress/pending phases
 
@@ -84,10 +84,9 @@ Phase 3: UX Scenarios         [✓ complete / ⏳ in-progress / ○ not started]
 Phase 4: UX Design            [✓ complete / ⏳ in-progress / ○ not started]
 Phase 5: Design System        [✓ complete / ⏳ in-progress / ○ not started]
 
-[If unfinished dialogs found:]
-⏸ Open work:
-- [phase-name]: [task description]
-- [phase-name]: [task description]
+[If Current table has tasks:]
+⏸ In progress:
+- [task from Current table]
 
 [Critical path indicator:]
 ➡️ Next critical phase: [Phase X]
@@ -98,14 +97,14 @@ Phase 5: Design System        [✓ complete / ⏳ in-progress / ○ not started]
 
 **Only shown for single-project scenario.** Based on status, offer appropriate actions:
 
-**If unfinished dialog found (default: resume):**
+**If Current table has a task (default: resume):**
 ```
-I found unfinished work in [dialog-file-name.md]:
-→ [task description from dialog]
+I found in-progress work:
+→ [task from Current table]
 
 Picking up where we left off...
 ```
-Read the dialog file, find the next incomplete step, and continue naturally.
+Read the design log, check Design Loop Status for current state, and continue naturally.
 Only ask before resuming if the user's message clearly indicates a different task.
 
 **If project just starting:**