whiteport-design-studio 0.2.2 → 0.3.0

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

@@ -19,17 +19,16 @@ WDS creates the **design artifacts** that development teams need to build except
 ### The Core Idea
 
 ```
-Vision → Clarity → UX Design → Design System → PRD Complete
-   │         │           │             │              │
-   │         │           │             │              └── Development
-   │         │           │             │                  gets everything
-   │         │           │             │
-   │         │           │             └── Components,
-   │         │           │                 tokens, patterns
-   │         │           │                 (optional, parallel)
-   │         │           │
-   │         │           └── Sketching, specifying,
-   │         │               prototyping, PRD grows
+Vision → Clarity → Scenarios → UX Design → Development Ready
+   │         │          │           │              │
+   │         │          │           │              └── AI or human
+   │         │          │           │                  development
+   │         │          │           │
+   │         │          │           └── Sketching, specifying,
+   │         │          │               prototyping, specs grow
+   │         │          │
+   │         │          └── 8-question scenario dialog,
+   │         │              user journeys, page outlines
    │         │
    │         └── Trigger mapping,
    │             Feature Impact Analysis
@@ -40,13 +39,22 @@ Vision → Clarity → UX Design → Design System → PRD Complete
 
 ---
 
-## The Six Phases
+## The Nine Phases
 
-WDS follows six phases, each producing artifacts in your project's `docs/` folder:
+WDS follows nine phases (0-8), each producing artifacts in your project's design artifacts folder:
+
+### Phase 0: Alignment & Signoff
+
+**Output:** `_alignment/`
+**Agent:** Saga the Analyst
+
+Generate alignment presentations and signoff documents. Used when you need stakeholder buy-in before proceeding.
+
+---
 
 ### Phase 1: Product Exploration (Product Brief)
 
-**Output:** `A-Product-Brief/`  
+**Output:** `A-Product-Brief/`
 **Agent:** Saga the Analyst
 
 Establish your strategic foundation through conversational discovery. Instead of filling out questionnaires, you have a conversation that builds understanding organically.
@@ -62,7 +70,7 @@ Establish your strategic foundation through conversational discovery. Instead of
 
 ### Phase 2: Trigger Mapping (Trigger Map)
 
-**Output:** `B-Trigger-Map/`  
+**Output:** `B-Trigger-Map/`
 **Agent:** Saga the Analyst
 
 Connect business goals to user psychology through Trigger Mapping. Discover not just WHO your users are, but WHY they act and WHAT triggers their decisions.
@@ -78,50 +86,87 @@ Connect business goals to user psychology through Trigger Mapping. Discover not
 
 ---
 
-### Phase 3: PRD Platform (Technical Foundation)
+### Phase 3: UX Scenarios (Scenario Outlines)
 
-**Output:** `C-Requirements/`  
-**Agent:** Freya the PM
+**Output:** `C-UX-Scenarios/`
+**Agent:** Saga the Analyst
 
-Prove your concept works technically - in parallel with design work. Validate platform decisions, create proofs of concept, and set up experimental endpoints.
+Transform your Trigger Map into concrete user journeys through the **8-question scenario dialog**. Define each meaningful transaction a user performs on your site — starting with the most important one.
 
 **What you create:**
 
-- Platform architecture decisions
-- Data model and integrations
-- Technical proofs of concept
-- Experimental endpoints
-- Security and performance framework
-- Technical constraints document (for UX Design)
+- Scenario outlines grounded in Trigger Map personas and business goals
+- Page folders with boilerplate specs ready for Phase 4 design
+- Scenario overview summarizing all scenarios with page assignments
 
----
+**The 8-Question Dialog:**
+
+| # | Question | What it establishes |
+|---|----------|-------------------|
+| Q1 | "What transaction do we need to get really right?" | The key user journey |
+| Q2 | "Which business goal does it serve?" | Trigger Map connection |
+| Q3 | "Which user, and in what real-life situation?" | Persona + context |
+| Q4 | "What do they want and fear going into this?" | Driving forces |
+| Q5 | "What device are they on?" | Platform |
+| Q6 | "What's the natural starting point?" | Entry point + discovery |
+| Q7 | "What's the best possible outcome — for both sides?" | Mutual success |
+| Q8 | "What's the shortest path through the site?" | Linear sunshine path |
 
-### Phase 4: UX Design (UX-Sketches & Usage Scenarios)
+See: [Phase 3: UX Scenarios Guide](./phase-3-ux-scenarios-guide.md)
 
-**Output:** `C-Scenarios/`  
-**Agent:** Baldr the UX Expert
+---
+
+### Phase 4: UX Design (Page Specifications)
 
-Transform ideas into detailed visual specifications. Your agent helps you think out the design, assists in sketching, creates specifications, and builds HTML prototypes. Each page adds functional requirements to the PRD.
+**Output:** `D-UX-Design/`
+**Agent:** Freya the Designer
 
-**The key insight:** Designs that can be logically explained without gaps are easy to develop. The specification process reveals gaps early - when they're easy to address.
+Transform scenarios into detailed visual specifications. Freya helps you conceptualize, sketch, specify, and prototype every interaction until your design can be logically explained without gaps.
 
 **What you create:**
 
-- Scenario folder structure (numbered hierarchy)
 - Page specifications with full detail
 - Component definitions with Object IDs
 - Interaction behaviors and states
 - HTML prototypes for validation
-- Functional requirements added to PRD (via step 4E)
+
+**Activities:** Conceptualize, Analyse Sketches, Suggest Interface, Dream Up Interface, Write Specifications, Visual Design, Manage Design System, Validate, Design Delivery
+
+See: [Phase 4: UX Design Guide](./phase-4-ux-design-guide.md)
 
 ---
 
-### Phase 5: Design System (Component Library)
+### Phase 5: Agentic Development
 
-**Output:** `D-Design-System/`  
-**Agent:** Baldr the UX Expert
+**Output:** Development artifacts
+**Agent:** Idunn the PM
 
-Build your component library following atomic design principles. This phase is **optional** and runs **in parallel** with Phase 4 - as you design pages, you extract reusable components.
+Bridge from design to development. Manage the development process with AI-assisted implementation, testing, and deployment.
+
+**What you create:**
+
+- Development tasks from design specifications
+- Implementation with AI assistance
+- Testing and validation
+- Deployment packages
+
+---
+
+### Phase 6: Asset Generation
+
+**Output:** Generated assets
+**Agent:** Freya the Designer
+
+Generate visual assets, icons, illustrations, and other design deliverables needed for the project.
+
+---
+
+### Phase 7: Design System (Component Library)
+
+**Output:** `D-Design-System/`
+**Agent:** Freya the Designer
+
+Build your component library following atomic design principles. This phase runs **in parallel** with Phase 4 — as you design pages, you extract reusable components.
 
 **What you create:**
 
@@ -130,30 +175,21 @@ Build your component library following atomic design principles. This phase is *
 - Molecular components (form groups, cards)
 - Organism components (headers, complex sections)
 - Interactive HTML component showcase
-- Figma/design tool integration with unified naming
 
 ---
 
-### Phase 6: PRD Finalization (Complete PRD)
+### Phase 8: Product Evolution
 
-**Output:** Complete PRD in `C-Requirements/` + `E-UI-Roadmap/`  
-**Agent:** Freya the PM
-
-Compile all functional requirements discovered during Phase 4 into a complete, development-ready PRD. This phase runs **continuously** - hand off as soon as you have MVP scope, then update as design progresses.
-
-**What you create:**
+**Output:** Evolution artifacts
+**Agent:** Idunn the PM
 
-- Complete PRD (Platform + Functional requirements)
-- Feature organization by epic/area
-- Development sequence with priorities
-- Handoff package in `E-UI-Roadmap/`
-- Scenario-to-epic mapping
+Iterate on existing products. Analyze usage, scope changes, design updates, implement, test, and deploy improvements.
 
 ---
 
 ## Folder Structure
 
-WDS creates an organized folder structure in your project's `docs/` folder. During setup, you make two choices:
+WDS creates an organized folder structure in your project's design artifacts folder. During setup, you make two choices:
 
 ### Your 4 Options
 
@@ -167,25 +203,21 @@ WDS creates an organized folder structure in your project's `docs/` folder. Duri
 **Letters + Title-Case** (default):
 
 ```
-docs/
+design-artifacts/
 ├── A-Product-Brief/
 ├── B-Trigger-Map/
-├── C-Platform-Requirements/
-├── C-Scenarios/
-├── D-Design-System/
-└── E-PRD-Finalization/
-```
-
-**Numbers + Title-Case**:
-
-```
-docs/
-├── 01-Product-Brief/
-├── 02-Trigger-Map/
-├── 03-Platform-Requirements/
-├── 03-Scenarios/
-├── 04-Design-System/
-└── 05-PRD-Finalization/
+├── C-UX-Scenarios/
+│   └── 01-hasses-emergency-search/
+│       ├── 01-hasses-emergency-search.md
+│       └── pages/
+│           ├── 01.1-start-page/
+│           │   ├── 01.1-start-page.md
+│           │   └── Sketches/
+│           └── 01.2-services/
+│               ├── 01.2-services.md
+│               └── Sketches/
+├── D-UX-Design/
+└── D-Design-System/
 ```
 
 **Default (Letters + Title-Case) is recommended because:**
@@ -198,16 +230,16 @@ docs/
 
 ## Phase-Selectable Workflow
 
-Not every project needs all six phases. Select what you need based on your situation:
+Not every project needs all nine phases. Select what you need based on your situation:
 
 | Project Type                  | Recommended Phases |
 | ----------------------------- | ------------------ |
-| **Landing page**              | 1, 4               |
-| **Full product (greenfield)** | All six            |
-| **Feature enhancement**       | 2, 4, 6            |
-| **Design system only**        | 4, 5               |
+| **Landing page**              | 1, 3, 4            |
+| **Full product (greenfield)** | All phases          |
+| **Feature enhancement**       | 2, 3, 4            |
+| **Design system only**        | 4, 7               |
 | **Strategic planning**        | 1, 2               |
-| **Quick prototype**           | 4 only             |
+| **Quick prototype**           | 3, 4               |
 
 Your agents will help you identify which phases fit your project.
 
@@ -217,38 +249,41 @@ Your agents will help you identify which phases fit your project.
 
 Three specialized agents guide you through WDS:
 
-### Saga the Analyst 📚
+### Saga the Analyst
 
 _"The one who tells your business story"_
 
-Saga guides you through discovery and research. She's curious, patient, and helps you uncover insights you might not have seen yourself.
+Saga guides you through discovery, research, and scenario creation. She's curious, patient, and helps you uncover insights you might not have seen yourself.
 
 **Works with you on:**
 
+- Phase 0: Alignment & Signoff
 - Phase 1: Product Exploration
 - Phase 2: Trigger Mapping
+- Phase 3: UX Scenarios
 
-### Freya the PM ⚔️
+### Freya the Designer
 
-_"The strategic leader who sees what must be done"_
+_"The one who brings light and beauty"_
 
-Freya helps you define technical requirements and finalize the PRD for development. She balances passion with strategy, knowing when to be fierce and when to be patient.
+Freya transforms your scenarios into beautiful, detailed specifications. She cares deeply about craft and ensures every detail serves the user experience.
 
 **Works with you on:**
 
-- Phase 3: PRD Platform
-- Phase 6: PRD Finalization
+- Phase 4: UX Design
+- Phase 6: Asset Generation
+- Phase 7: Design System
 
-### Baldr the UX Expert ✨
+### Idunn the PM
 
-_"The one who brings light and beauty"_
+_"The keeper of what endures"_
 
-Baldr transforms your ideas into beautiful, detailed specifications. He cares deeply about craft and ensures every detail serves the user experience.
+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 4: UX Design
-- Phase 5: Design System
+- Phase 5: Agentic Development
+- Phase 8: Product Evolution
 
 ---
 
@@ -286,31 +321,23 @@ It never feels like filling out a form.
 
 ## Getting Started
 
-### Prerequisites
-
-1. BMad Method installed with WDS module
-2. Project workspace ready
-3. Stakeholders available for workshop phases
-
 ### Quick Start
 
 ```
-# Install BMad with WDS
-npx bmad-method@alpha install
-
-# Activate any WDS agent
-# They'll guide you from there
+# Install WDS
+npx whiteport-design-studio install
 
-# Or run workflow-init for phase selection
-*workflow-init
+# Start a conversation with Saga
+# She'll guide you from there
 ```
 
 ### First Steps
 
 1. **Start with Phase 1** if you're building something new
 2. **Start with Phase 2** if you have existing vision but need user clarity
-3. **Start with Phase 4** if you have sketches ready to specify
-4. **Ask your agent** if you're not sure where to begin
+3. **Start with Phase 3** if you have a Trigger Map and need scenario outlines
+4. **Start with Phase 4** if you have scenarios ready to design
+5. **Ask your agent** if you're not sure where to begin
 
 ---
 
@@ -328,51 +355,34 @@ npx bmad-method@alpha install
 
 - Conversations that build understanding
 - Personas with psychological depth connected to business goals
+- 8-question scenario dialog grounding every design in real user psychology
 - Collaborative workshops building shared understanding
 - Specifications so clear they eliminate guesswork
 - Everyone aligned because they built it together
 
 ---
 
-## Integration with Development
-
-WDS focuses on **design** - creating the artifacts that guide development. The actual development process is handled by BMad Method (BMM) or your preferred development workflow.
-
-### The PRD Journey
-
-```
-Phase 3: PRD starts              Phase 4: PRD grows           Phase 6: PRD completes
-(Technical Foundation)           (Each page adds features)    (Organized for dev)
-        │                                │                            │
-        ▼                                ▼                            ▼
-C-Requirements/           ────►   C-Requirements/      ────►   E-UI-Roadmap/
-├── Platform arch                 ├── Platform arch            ├── Priority sequence
-├── Data model                    ├── Data model               ├── Epic mapping
-├── Integrations                  ├── Integrations             ├── Component inventory
-└── Security                      └── Functional reqs ◄──┐     └── Handoff checklist
-                                      (from each page)  │
-                                                        │
-                                  C-Scenarios/ ─────────┘
-                                  (Page specs add features via 4E)
-```
+## The Scenario → Design Flow
 
-### Parallel Streams
+The heart of WDS is the connection between Phase 3 (Scenarios) and Phase 4 (Design):
 
-Design and development can work in parallel:
+1. **Phase 3** defines the scenario through 8 strategic questions
+2. After completing a scenario, you choose to outline pages or jump to design
+3. **Page Outline Dialog** defines each page's purpose and exit action
+4. **Phase 4** designs each page with full context from the scenario
+5. The **Outline → Design loop** lets you outline and design pages continuously
 
-- Phase 3 complete → Backend/platform development can start
-- Phase 4 MVP scenarios complete → Phase 6 first handoff → Sprint 1 begins
-- Design continues → Regular Phase 6 updates → More sprints
+This ensures every page is designed with purpose — grounded in real user psychology, connected to business goals, and part of a coherent user journey.
 
 ---
 
 ## Learn More
 
 - **Phase guides:** Detailed documentation for each phase
-- **Examples:** Dog Week patterns showing real artifacts
+- **Examples:** Real project patterns showing complete artifacts
 - **Templates:** Ready-to-use templates for all deliverables
 - **Conversation examples:** See how agent sessions flow
 
 ---
 
-_Whiteport Design Studio - Part of the BMad ecosystem_
+_Whiteport Design Studio_

package/docs/models/action-mapping.md

@@ -672,7 +672,7 @@ Action 1: [Observable behavior]
 
 **Related Resources:**
 - [Phase 4: UX Design Guide](../method/phase-4-ux-design-guide.md) - Scenario design using action focus
-- [Value Trigger Chain Guide](../method/value-trigger-chain-guide.md) - Connect actions to driving forces
+- [Trigger Mapping Guide](../method/phase-2-trigger-mapping-guide.md) - Connect actions to driving forces
 - [Blog.Cathy-Moore.com](https://blog.cathy-moore.com) - Original source and examples
 
 ---

package/docs/models/customer-awareness-cycle.md

@@ -177,19 +177,6 @@ While Schwartz focused on advertising copy, his framework applies powerfully to:
 
 ## Whiteport Methods That Harness This Model
 
-### [Value Trigger Chain Guide](../method/value-trigger-chain-guide.md)
-
-VTCs include Customer Awareness positioning:
-- Starting point: Where is user NOW?
-- Target point: Where do we want to move them?
-- Design serves this progression
-
-**Example:**
-```
-Customer Awareness: Problem Aware → Product Aware
-Design Implication: Introduce OUR solution after establishing problem
-```
-
 ### [Trigger Mapping Guide](../method/phase-2-trigger-mapping-guide.md)
 
 Trigger Maps can include awareness positioning for each persona:
@@ -204,7 +191,7 @@ Each scenario defines awareness progression:
 - Exit point awareness level
 - Interactions designed to bridge the gap
 
-### [Content Creation Workflow](../method/value-trigger-chain-guide.md#using-vtcs-in-your-design-process)
+### Content Creation Workflow
 
 Before creating any content:
 1. Identify user's current awareness level
@@ -520,7 +507,6 @@ measurement:
 5. **Test and measure:** Track progression through awareness stages
 
 **Related Resources:**
-- [Value Trigger Chain Guide](../method/value-trigger-chain-guide.md) - Includes Customer Awareness positioning
 - [Trigger Mapping Guide](../method/phase-2-trigger-mapping-guide.md) - Uses awareness to position personas
 - [Phase 4: UX Design Guide](../method/phase-4-ux-design-guide.md) - Applies awareness to scenarios
 

package/docs/models/golden-circle.md

@@ -221,9 +221,9 @@ The Product Brief discovery conversation uses Golden Circle structure:
 
 **Result:** Product Brief grounded in purpose, not just feature list.
 
-### [Value Trigger Chain Guide](../method/value-trigger-chain-guide.md)
+### Trigger Mapping
 
-VTC implicitly uses Golden Circle:
+Trigger Maps implicitly use Golden Circle:
 
 - **Business Goal:** The WHY (organizational purpose)
 - **Driving Forces:** User's personal WHY (motivation)
@@ -523,7 +523,6 @@ We offer:
 
 **Related Resources:**
 - [Product Exploration Guide](../method/phase-1-product-exploration-guide.md) - Uses WHY-first discovery
-- [Value Trigger Chain Guide](../method/value-trigger-chain-guide.md) - Captures user's WHY (driving forces)
 - [Trigger Mapping Guide](../method/phase-2-trigger-mapping-guide.md) - Connects business WHY to user WHY
 
 ---

package/docs/models/impact-effect-mapping.md

@@ -4,7 +4,7 @@
 
 **Originated by:** Mijo Balic & Ingrid Domingues (Ottersten) at inUse, Sweden  
 **Popularized by:** Gojko Adzic, *Impact Mapping* (2012)  
-**Applied in WDS:** Trigger Mapping, Value Trigger Chains, strategic alignment
+**Applied in WDS:** Trigger Mapping, strategic alignment
 
 ---
 
@@ -247,15 +247,15 @@ A separate method (also derived from Impact Mapping) that uses the Trigger Map:
 
 **Note:** This is a distinct method that USES the Trigger Map data, to be fair to Impact Mapping's influence on this approach.
 
-### [Value Trigger Chain Guide](../method/value-trigger-chain-guide.md)
+### Trigger Mapping
 
-Lightweight version extracting core strategic elements:
+Whiteport's adaptation extracting core strategic elements:
 
 - Business Goal (from Effect/Impact Mapping)
 - Solution (combines Actor context + Impact)
 - User (Actor with psychological depth)
 - Driving Forces (Positive and negative impacts)
-- Customer Awareness (Added positioning layer)
+- Feature Impact Analysis (scored prioritization)
 
 **Result:** Minimum viable strategic context, perfect for quick projects or prototypes.
 
@@ -587,11 +587,10 @@ Goal
 1. **Read:** Get Gojko Adzic's book for full methodology
 2. **Try:** Run a simple Impact Mapping session for current project
 3. **Compare:** See how Whiteport's Trigger Mapping adapts the concepts
-4. **Choose:** Decide if you need quick VTC, full Impact Map, or comprehensive Trigger Map
+4. **Choose:** Decide if you need a slim Trigger Map, full Impact Map, or comprehensive Trigger Map
 
 **Related Resources:**
 - [Trigger Mapping Guide](../method/phase-2-trigger-mapping-guide.md) - Whiteport's adaptation
-- [Value Trigger Chain Guide](../method/value-trigger-chain-guide.md) - Lightweight version
 - [ImpactMapping.org](https://www.impactmapping.org) - Official resources
 
 ---

package/docs/models/kathy-sierra-badass-users.md

@@ -662,7 +662,7 @@ For each screen/component, ask:
 5. **Test:** Do users feel more confident after new version?
 
 **Related Resources:**
-- [Value Trigger Chain Guide](../method/value-trigger-chain-guide.md) - Driving forces include capability desires
+- [Trigger Mapping Guide](../method/phase-2-trigger-mapping-guide.md) - Driving forces include capability desires
 - [Action Mapping Model](./action-mapping.md) - Similar philosophy: focus on what users DO
 - [Phase 4: UX Design Guide](../method/phase-4-ux-design-guide.md) - Scenario design with user capability in mind
 

package/docs/models/models-guide.md

@@ -40,7 +40,6 @@ Each model includes:
 
 **Applied in WDS:**
 - Trigger Mapping (Whiteport's enhanced adaptation)
-- Value Trigger Chains (lightweight version)
 - Strategic alignment from why to what
 
 **When to Use:** Strategic planning, feature prioritization, aligning team on goals
@@ -287,7 +286,7 @@ Want to dive deeper? Each model guide includes books, articles, videos, and webs
 ## Related Documentation
 
 - **[WDS Method Guides](../method/)** - How Whiteport applies these models
-- **[Learn WDS Course](../learn-wds/)** - Step-by-step learning path
+- **[Learn WDS Course](../learn/)** - Step-by-step learning path
 - **[Examples](../examples/)** - See models in action
 - **[Getting Started](../getting-started/)** - Quick start with WDS
 

package/docs/models/smart-goals-model.md

@@ -275,8 +275,8 @@ SMART goals are now standard practice in:
 
 **Related WDS Resources:**
 - [Phase 2: Trigger Mapping Guide](../method/phase-2-trigger-mapping-guide.md)
-- [Module 05: Trigger Mapping](../learn-wds/module-05-trigger-mapping/module-05-overview.md)
-- [Lesson 3: The Five Workshops](../learn-wds/module-05-trigger-mapping/lesson-03-five-workshops.md)
+- [Module 05: Trigger Mapping](../learn/module-05-trigger-mapping/module-05-overview.md)
+- [Lesson 3: The Five Workshops](../learn/module-05-trigger-mapping/lesson-03-five-workshops.md)
 
 ---