whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/2-trigger-mapping/workflow.md

@@ -51,11 +51,9 @@ Load and read full config from `{project-root}/_bmad/wds/config.yaml` and resolv
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 
-### 2. Agent Dialog Gate
+### 2. Design Log
 
-1. Check `{output_folder}/_progress/agent-dialogs/` for pending trigger mapping dialogs
-2. If pending, present with status
-3. If none, suggest creating one
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ### 3. Mode Determination
 

package/src/workflows/3-scenarios/data/quality-checklist.md

@@ -71,9 +71,9 @@ For each scenario, verify all 7 components exist:
 
 ---
 
-## Dimension 3: Common Mistakes (6 checks)
+## Dimension 3: Common Mistakes (7 checks)
 
-All 6 must be avoided — any single mistake requires correction.
+All 7 must be avoided — any single mistake requires correction.
 
 ### 3.1 Edge Cases in Sunshine Path
 **Check:** Are there any "if" statements, error states, or branches?
@@ -103,7 +103,11 @@ All 6 must be avoided — any single mistake requires correction.
 **Check:** Is business success explicitly defined and measurable?
 **Fix:** Add specific business outcome connected to Trigger Map goal.
 
-**Minimum:** 6/6 avoided (zero tolerance for mistakes)
+### 3.7 Bloated Descriptions
+**Check:** Does any single component (Entry Point, Mental State, Success Goals) exceed 2 sentences?
+**Fix:** Trim to bullet-point essentials. Entry points: device + context + discovery. Mental state: one phrase per component. Success: one measurable statement each.
+
+**Minimum:** 7/7 avoided (zero tolerance for mistakes)
 
 ---
 
@@ -134,7 +138,7 @@ Scenario states which specific wants/fears from Trigger Map it addresses, with c
 
 **Completeness:** [X]/7
 **Quality:** [X]/7
-**Mistakes Avoided:** [X]/6
+**Mistakes Avoided:** [X]/7
 **Best Practices:** [X]/4
 
 **Status:** [Excellent / Good / Needs Work]
@@ -147,8 +151,8 @@ Scenario states which specific wants/fears from Trigger Map it addresses, with c
 
 | Level | Complete | Quality | Mistakes | Practices |
 |-------|----------|---------|----------|-----------|
-| Minimum | 6/7 | 5/7 | 6/6 | 2/4 |
-| Excellent | 7/7 | 7/7 | 6/6 | 4/4 |
+| Minimum | 6/7 | 5/7 | 7/7 | 2/4 |
+| Excellent | 7/7 | 7/7 | 7/7 | 4/4 |
 
 **If not meeting Minimum after corrections:** Note gaps and consult user for guidance.
 

package/src/workflows/3-scenarios/data/scenario-outline-template.md

@@ -1,7 +1,7 @@
 # Scenario Outline Template
 
 **Used by:** step-05-outline-scenario.md
-**Purpose:** Complete template for one scenario outline with all 7 required components.
+**Purpose:** Structure the answers from the 8-question scenario dialog into a complete scenario outline.
 
 ---
 
@@ -16,47 +16,55 @@
 
 ---
 
-## Core Feature
+## Transaction (Q1)
 
 **What this scenario covers:**
-[State as user purpose, not feature name]
-
-**Business Goal Alignment:**
-[Which specific business goal this serves, with objective reference]
+[The key transaction — stated as user purpose, not feature name]
 
 ---
 
-## Entry Point
+## Business Goal (Q2)
 
-**Device:** [Mobile / Desktop / Tablet]
-**Context:** [Where the user is, what they're doing, what just happened]
-**Discovery:** [How they found the site — Google search terms, link from email, bookmark, ad, etc.]
+**Goal:** [Which specific business goal this serves]
+**Objective:** [Objective reference from Trigger Map]
+
+---
 
-**Specific entry:** [Full realistic description]
+## User & Situation (Q3)
+
+**Persona:** [Name] ([Priority level: Primary/Secondary/Tertiary])
+**Situation:** [Real-life context — who they are, where they are, what's happening]
 
 ---
 
-## Mental State
+## Driving Forces (Q4)
+
+**Hope:** [What they're hoping to find or achieve — one sentence]
 
-**Trigger:** [What just happened that brought them here NOW]
+**Worry:** [What they're afraid of or want to avoid — one sentence]
 
-**Hope:** [What they're hoping to find or achieve — be specific]
+> CONSTRAINT: One sentence per component. Phrases, not paragraphs.
 
-**Worry:** [What they're afraid of or want to avoid — be specific]
+---
+
+## Device & Starting Point (Q5 + Q6)
+
+**Device:** [Mobile / Desktop / Tablet]
+**Entry:** [How they actually arrive] — max 2 sentences
 
 ---
 
-## Success Goals
+## Best Outcome (Q7)
 
 **User Success:**
-[Tangible, measurable outcome the user achieves when scenario completes]
+[Tangible, measurable outcome the user achieves]
 
 **Business Success:**
-[Specific, measurable result the business gets when scenario completes]
+[Specific, measurable result the business gets]
 
 ---
 
-## Shortest Path
+## Shortest Path (Q8)
 
 [Linear sunshine path — NO branches, NO "if" statements. Minimum viable steps.]
 
@@ -68,7 +76,7 @@
 
 ## Trigger Map Connections
 
-**Persona:** [Name] ([Priority level: Primary/Secondary/Tertiary])
+**Persona:** [Name] ([Priority level])
 
 **Driving Forces Addressed:**
 - ✅ **Want:** [Specific positive driver from Trigger Map]
@@ -78,13 +86,18 @@
 
 ---
 
-## Pages in This Scenario
+## Scenario Steps
+
+Steps are outlined one at a time after scenario creation. The first step is processed automatically.
+
+| Step | Folder | Purpose | Exit Action |
+|------|--------|---------|-------------|
+| [NN].1 | `[NN].1-[page-slug]/` | [Step purpose] | [Interaction that leads to next step] |
+| [NN].2 | `[NN].2-[page-slug]/` | [Step purpose] | [Interaction that leads to next step] |
+| [NN].3 | `[NN].3-[page-slug]/` | [Step purpose] | [Final — scenario success] ✓ |
 
-| # | Page | Purpose in Flow | Template? |
-|---|------|----------------|-----------|
-| 1 | [Page Name] | [What it does in this scenario] | [Unique / Template: group name] |
-| 2 | [Page Name] | [What it does in this scenario] | [Unique / Template: group name] |
-| 3 | [Page Name] | [What it does in this scenario] | [Unique / Template: group name] |
+**First step** ([NN].1) includes full entry context (Q3 + Q4 + Q5 + Q6).
+**On-step interactions** (that don't leave the step) are documented as storyboard items within each page spec.
 ```
 
 ---
@@ -93,16 +106,16 @@
 
 When filling this template, check:
 
-**Entry Point** — Would a real person arrive this way? Include device, location, search terms.
+**Transaction** — Is this a real user journey? Browsing content page-by-page counts. Comparing options counts. Any meaningful path through the site with intent.
 
-**Mental State** — Can you FEEL the user's emotional state? "Interested" is not enough. "Panicked because family vacation is at risk" is.
+**Driving Forces** — Can you FEEL the user's state? "Interested" is not enough. "Panicked because family vacation is at risk" is.
 
-**Success Goals** — "Get more customers" fails. "Reduce info calls by 40% by giving tourists the info they need online" passes.
+**Best Outcome** — "Get more customers" fails. "Reduce info calls by 40% by giving tourists the info they need online" passes.
 
-**Shortest Path** — Count the steps. Can you remove any? Each step must justify its existence. If you can't defend why a step is there, remove it.
+**Shortest Path** — Count the steps. Can you remove any? Each step must justify its existence.
 
-**Trigger Map** — Don't invent a user. Use the actual persona from the Trigger Map with their actual driving forces.
+**Trigger Map** — Don't invent a user. Use the actual persona with their actual driving forces.
 
 ---
 
-_Template for Step 05: Outline Scenario_
+_Template for Step 05: Outline Scenario (8-Question Dialog)_

package/src/workflows/3-scenarios/steps-c/step-01-load-context.md

@@ -24,7 +24,7 @@ Read all prerequisite artifacts (Product Brief, Trigger Map) and detect whether
 
 ### Role Reinforcement:
 
-- ✅ You are a UX Scenario Architect collaborating with the project owner
+- ✅ You are a UX Scenario Facilitator collaborating with the project owner
 - ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring scenario thinking and user journey expertise, user brings their project knowledge, together we create concrete UX scenario outlines
@@ -96,7 +96,7 @@ Read `{output_folder}/B-Trigger-Map/trigger-map.md` (the hub document)
 **Check for resume situation:**
 - Does `{output_folder}/C-UX-Scenarios/` exist?
 - Are there any scenario files already?
-- Are there unfinished agent dialogs in `{output_folder}/_progress/agent-dialogs/`?
+- Is there in-progress work in the design log (`{output_folder}/_progress/00-design-log.md`)?
 
 **If existing work found:**
 ```

package/src/workflows/3-scenarios/steps-c/step-02-analyze-scope.md

@@ -3,7 +3,7 @@ name: 'step-02-analyze-scope'
 description: 'Determine site type, list all pages/views, assess scale, and select approach mode'
 
 # File References
-nextStepFile: './step-03-build-vtcs.md'
+nextStepFile: './step-03-build-strategic-context.md'
 ---
 
 # Step 2: Analyze Scope & Scale Strategy
@@ -24,7 +24,7 @@ Determine site type, list all pages/views, assess scale, select approach mode, a
 
 ### Role Reinforcement:
 
-- ✅ You are a UX Scenario Architect collaborating with the project owner
+- ✅ You are a UX Scenario Facilitator collaborating with the project owner
 - ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring scenario thinking and user journey expertise, user brings their project knowledge, together we create concrete UX scenario outlines
@@ -48,7 +48,7 @@ Determine site type, list all pages/views, assess scale, select approach mode, a
 
 - Available context: Product Brief data, Trigger Map data loaded in Step 1
 - Focus: Site classification, page inventory, scale assessment
-- Limits: No scenario creation, no VTC building — only scope analysis
+- Limits: No scenario creation, no strategic context building — only scope analysis
 - Dependencies: Step 1 context must be loaded
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
@@ -150,7 +150,7 @@ Present to user and **wait for approval**:
 
 ### 6. Present MENU OPTIONS
 
-Display: "Are you ready to [C] Continue to Building Value Trigger Chains?"
+Display: "Are you ready to [C] Continue to Building Strategic Context?"
 
 #### Menu Handling Logic:
 
@@ -165,7 +165,7 @@ Display: "Are you ready to [C] Continue to Building Value Trigger Chains?"
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [user has explicitly approved the scope analysis], will you then load and read fully `{nextStepFile}` to execute and begin building VTCs.
+ONLY WHEN [C continue option] is selected and [user has explicitly approved the scope analysis], will you then load and read fully `{nextStepFile}` to execute and begin building strategic context.
 
 ---
 

package/src/workflows/3-scenarios/steps-c/{step-03-build-vtcs.md → step-03-build-strategic-context.md}

@@ -1,16 +1,16 @@
 ---
-name: 'step-03-build-vtcs'
-description: 'Extract Value Trigger Chains from Trigger Map to identify which scenarios to create'
+name: 'step-03-build-strategic-context'
+description: 'Build strategic context from Trigger Map to identify which scenarios to create'
 
 # File References
 nextStepFile: './step-04-suggest-scenarios.md'
 ---
 
-# Step 3: Build Value Trigger Chains
+# Step 3: Build Strategic Context
 
 ## STEP GOAL:
 
-Extract Value Trigger Chains (VTCs) from the Trigger Map, assign pages to each VTC, prioritize them, and verify complete coverage of all pages.
+Extract strategic context from the Trigger Map — tracing paths from business goals through personas and driving forces to transactions — assign pages to each scenario chain, prioritize them, and verify complete coverage of all pages.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -24,7 +24,7 @@ Extract Value Trigger Chains (VTCs) from the Trigger Map, assign pages to each V
 
 ### Role Reinforcement:
 
-- ✅ You are a UX Scenario Architect collaborating with the project owner
+- ✅ You are a UX Scenario Facilitator collaborating with the project owner
 - ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring scenario thinking and user journey expertise, user brings their project knowledge, together we create concrete UX scenario outlines
@@ -32,32 +32,32 @@ Extract Value Trigger Chains (VTCs) from the Trigger Map, assign pages to each V
 
 ### Step-Specific Rules:
 
-- 🎯 Focus only on building VTCs, assigning pages, and prioritizing
+- 🎯 Focus only on building strategic context, assigning pages, and prioritizing
 - 🚫 FORBIDDEN to create scenario outlines — only identify and plan scenarios
 - 💬 Approach: Systematically trace paths from business goals to user actions
-- 📋 Every page from the inventory must be assigned to exactly one VTC
+- 📋 Every page from the inventory must be assigned to exactly one scenario chain
 
 ## EXECUTION PROTOCOLS:
 
 - 🔗 Trace complete chains from Business Goal → Persona → Force → Transaction → Scenario
-- 📋 Answer all 7 Decision Matrix questions for each VTC
+- 📋 Answer all 7 Decision Matrix questions for each scenario chain
 - 📊 Assign pages ensuring no repetition and full coverage
 - 🚫 FORBIDDEN to leave any page unassigned
 
 ## CONTEXT BOUNDARIES:
 
 - Available context: Product Brief, Trigger Map, approved page inventory from Step 2
-- Focus: VTC extraction, page assignment, prioritization
+- Focus: Strategic context extraction, page assignment, prioritization
 - Limits: No scenario outlining, no file creation — only planning
 - Dependencies: Approved scope analysis from Step 2
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
-### 1. Build VTCs
+### 1. Build Strategic Context Chains
 
-**What is a Value Trigger Chain?**
+**What is a strategic context chain?**
 
-A VTC traces the path from business strategy to user action:
+A strategic context chain traces the path from business strategy to user action:
 
 ```
 Business Goal → Persona → Driving Force → Transaction → Scenario
@@ -79,7 +79,7 @@ For **each business goal** from the Trigger Map:
 3. Determine the specific transaction/action that fulfills it
 4. Name a candidate scenario using the persona's name
 
-**For each VTC, answer the Decision Matrix (all 7 required):**
+**For each scenario chain, answer the Decision Matrix (all 7 required):**
 
 | # | Question | Answer |
 |---|----------|--------|
@@ -91,18 +91,18 @@ For **each business goal** from the Trigger Map:
 | 6 | What value does user get? | [Tangible outcome] |
 | 7 | What value does business get? | [Measurable result] |
 
-### 2. Assign Pages to VTCs
+### 2. Assign Pages to Scenario Chains
 
-For each VTC, list which pages from the inventory (Step 02) the user visits.
+For each scenario chain, list which pages from the inventory (Step 02) the user visits.
 
 **Rules:**
-- Each page appears in exactly ONE VTC/scenario (no repetition)
+- Each page appears in exactly ONE scenario chain (no repetition)
 - If a page could fit multiple scenarios, assign it to the highest-priority one
 - Shared elements (navigation, footer) are excluded from page assignment
 
 ### 3. Prioritize
 
-Rank the VTCs:
+Rank the scenario chains:
 
 **Priority 1 — Critical Path:**
 - Top business goal + primary persona + core product value
@@ -118,29 +118,29 @@ Rank the VTCs:
 
 ### 4. Coverage Check
 
-After building all VTCs, verify:
+After building all scenario chains, verify:
 
-- [ ] Every page from inventory is assigned to exactly one VTC
+- [ ] Every page from inventory is assigned to exactly one scenario chain
 - [ ] Primary persona has at least one Priority 1 scenario
 - [ ] Top business goal is addressed by at least one scenario
 - [ ] No page appears in multiple scenarios
 
-**If pages are unassigned:** Create additional VTCs or expand existing ones to cover them.
+**If pages are unassigned:** Create additional scenario chains or expand existing ones to cover them.
 
-### 5. Present VTC List
+### 5. Present Scenario Chain List
 
-Present the complete VTC list:
+Present the complete scenario chain list:
 
 ```
-## Value Trigger Chains
+## Strategic Context Chains
 
 ### Priority 1
-**VTC-01:** [Business Goal] → [Persona] → [Force] → [Transaction]
+**Chain 01:** [Business Goal] → [Persona] → [Force] → [Transaction]
 - Scenario: 01-[slug]
 - Pages: [list]
 
 ### Priority 2
-**VTC-02:** [Business Goal] → [Persona] → [Force] → [Transaction]
+**Chain 02:** [Business Goal] → [Persona] → [Force] → [Transaction]
 - Scenario: 02-[slug]
 - Pages: [list]
 
@@ -164,7 +164,7 @@ Display: "Are you ready to [C] Continue to Scenario Suggestions?"
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [VTC list with full page coverage presented], will you then load and read fully `{nextStepFile}` to execute and begin scenario suggestions.
+ONLY WHEN [C continue option] is selected and [scenario chain list with full page coverage presented], will you then load and read fully `{nextStepFile}` to execute and begin scenario suggestions.
 
 ---
 
@@ -172,18 +172,18 @@ ONLY WHEN [C continue option] is selected and [VTC list with full page coverage
 
 ### ✅ SUCCESS:
 
-- All business goals traced through complete VTC chains
-- All 7 Decision Matrix questions answered for each VTC
-- Every page from inventory assigned to exactly one VTC
-- VTCs prioritized with clear rationale
+- All business goals traced through complete strategic context chains
+- All 7 Decision Matrix questions answered for each scenario chain
+- Every page from inventory assigned to exactly one scenario chain
+- Scenario chains prioritized with clear rationale
 - Coverage check passes (all pages assigned, no duplicates)
-- Complete VTC list presented to user
+- Complete scenario chain list presented to user
 - Menu presented and user input handled correctly
 
 ### ❌ SYSTEM FAILURE:
 
 - Leaving pages unassigned
-- Assigning pages to multiple VTCs
+- Assigning pages to multiple scenario chains
 - Skipping Decision Matrix questions
 - Creating scenario outlines during this step
 - Not verifying coverage before proceeding

package/src/workflows/3-scenarios/steps-c/step-04-suggest-scenarios.md

@@ -24,7 +24,7 @@ Present the complete scenario plan to the user for approval before creating any
 
 ### Role Reinforcement:
 
-- ✅ You are a UX Scenario Architect collaborating with the project owner
+- ✅ You are a UX Scenario Facilitator collaborating with the project owner
 - ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
 - ✅ You bring scenario thinking and user journey expertise, user brings their project knowledge, together we create concrete UX scenario outlines
@@ -46,10 +46,10 @@ Present the complete scenario plan to the user for approval before creating any
 
 ## CONTEXT BOUNDARIES:
 
-- Available context: VTCs from Step 3, page inventory, Trigger Map data
+- Available context: Strategic context from Step 3, page inventory, Trigger Map data
 - Focus: Presenting and getting approval for the scenario plan
 - Limits: No scenario outlining, no file creation — only planning approval
-- Dependencies: Complete VTC list from Step 3
+- Dependencies: Complete strategic context chains from Step 3
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
@@ -124,7 +124,7 @@ Scenario names MUST use persona names:
 User may:
 - **"Looks good, proceed"** → Continue to menu options
 - **"Combine X and Y"** → Adjust and re-present
-- **"Add a scenario for [purpose]"** → Add VTC and re-present
+- **"Add a scenario for [purpose]"** → Add scenario chain and re-present
 - **"Focus on just [one flow]"** → Apply selective ignorance, re-present
 - **"Missing page [X]"** → Add to inventory and assign