whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/3-scenarios/steps-c/step-05-outline-scenario.md

@@ -13,7 +13,7 @@ scenarioTemplate: '../data/scenario-outline-template.md'
 
 ## STEP GOAL:
 
-Create a detailed outline for ONE scenario using all 7 required components, verify against quality gates, create the output file, then loop for each remaining scenario in the approved plan.
+Define ONE scenario through 8 strategic questions in natural conversation order. Start with the primary transaction (highest priority), complete it fully, then loop for each remaining scenario. A **transaction** is any meaningful user journey — purchasing, booking, researching content page-by-page, comparing options, or any interaction where the user moves through the site with intent.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -27,7 +27,7 @@ Create a detailed outline for ONE scenario using all 7 required components, veri
 
 ### Role Reinforcement:
 
-- ✅ You are a UX Scenario Architect collaborating with the project owner
+- ✅ You are a UX Scenario Facilitator — you ASK, the user DECIDES
 - ✅ 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
@@ -35,23 +35,23 @@ Create a detailed outline for ONE scenario using all 7 required components, veri
 
 ### Step-Specific Rules:
 
-- 🎯 Focus on ONE scenario at a time, complete it fully before moving to the next
-- 🚫 FORBIDDEN to skip any of the 7 required components
-- 💬 Approach: Collaborate with user on each scenario, using the template as structure
+- 🎯 Focus on ONE transaction at a time, complete it fully before moving to the next
+- 🚫 FORBIDDEN to skip any of the 8 strategic questions
+- 💬 Approach: Ask one question at a time, let the answer shape the next question naturally
 - 📋 Verify all quality gates before proceeding to the next scenario or step
 
 ## EXECUTION PROTOCOLS:
 
 - 📖 Load the scenario outline template before starting
-- 📋 Ensure all 7 components are present and high quality
+- 💬 Walk through 8 questions as a dialog — one question at a time, building on each answer
 - ✅ Run quality gates check before moving on
 - 💾 Create output file in the correct folder structure
-- 🔄 Loop back for each remaining scenario
+- 🔄 Loop back for each remaining scenario (next transaction, next target group)
 - 🚫 FORBIDDEN to proceed if any quality gate fails
 
 ## CONTEXT BOUNDARIES:
 
-- Available context: Approved scenario plan from Step 4, VTCs, page inventory, Trigger Map
+- Available context: Approved scenario plan from Step 4, strategic context, page inventory, Trigger Map
 - Focus: Detailed outlining of one scenario at a time
 - Limits: Only outline scenarios from the approved plan
 - Dependencies: User-approved scenario plan from Step 4
@@ -69,65 +69,79 @@ If returning from a loop, continue with the next unfinished scenario.
 
 Load the full template: `{scenarioTemplate}`
 
-### 3. Create Outline with 7 Required Components
+### 3. The 8-Question Scenario Dialog
 
-Every scenario outline MUST have all 7 components:
+**Two modes — same 8 questions, different driver:**
 
-#### Component 1: Scenario Name & ID
+- **Conversation mode** (default): YOU ask, the USER answers. One question at a time. Each answer shapes the next question naturally.
+- **Suggest mode** (when user asks you to suggest): YOU answer all 8 questions based on the Trigger Map, Product Brief, and strategic context. Present the complete scenario to the user for review and adjustment.
 
-- **Name:** Uses persona name + purpose (e.g., "Hasse's Emergency Search")
-- **ID:** 01, 02, etc.
-- **Slug:** `01-hasses-emergency-search`
+This IS the scenario — when all 8 are answered, the outline writes itself.
+
+> **What counts as a transaction:** Not just purchases or bookings. Clicking through a menu item by item to research site content is a transaction. Comparing options is a transaction. Any meaningful journey where the user moves through the site with intent.
 
-#### Component 2: Core Feature
+#### Q1: "What transaction do we need to get really right?"
 
-What this scenario covers, stated as user purpose (not feature name).
+Start with the WHY. What is the most important thing a user needs to accomplish on this site?
 
+- State as user purpose, not feature name
 - **Bad:** "Homepage and service pages"
 - **Good:** "Verify service availability before booking"
 
-Must align with a specific business goal from the Trigger Map.
+#### Q2: "If this transaction succeeds, which business goal does it add value to?"
 
-#### Component 3: Entry Point (Realistic)
+Connect to the Trigger Map immediately. Which specific business goal and objective does this serve?
 
-How the user ACTUALLY arrives. Be specific about:
-- **Device:** Mobile, desktop, tablet
-- **Context:** Where they are, what they are doing
-- **Discovery:** How they found the site (Google search, link, ad, bookmark)
+- Reference actual goals from the Trigger Map
+- This grounds the scenario in business strategy, not just user needs
 
-- **Bad:** "User opens app"
-- **Good:** "Googles 'car repair Oland' on mobile while parked at gas station, clicks top organic result"
+#### Q3: "Which user experiences this most, and in what real-life situation?"
 
-#### Component 4: Mental State (Trigger / Hope / Worry)
+Identify the persona AND their context. Not just "who" but "who, where, when."
 
-Three components, all required, all specific:
+- Use actual personas from the Trigger Map
+- **Bad:** "A customer looking for information"
+- **Good:** "Hasse, 55, motorhome tourist stranded in Byxelkrok with a broken vehicle during family vacation"
 
-- **Trigger:** What just happened that brought them here NOW
-- **Hope:** What they are hoping to find or achieve
-- **Worry:** What they are afraid of or want to avoid
+#### Q4: "What do they want and what do they fear going into this interaction?"
 
+The driving forces — hope and worry. These must be visceral and specific.
+
+- **Hope:** What they're hoping to find or achieve
+- **Worry:** What they're afraid of or want to avoid
 - **Bad:** "User is interested in the product"
-- **Good:** "Trigger: Motorhome broke down in Byxelkrok, family vacation at risk. Hope: Find trustworthy mechanic nearby, get back on road today. Worry: Being stranded for days, getting ripped off by unknown mechanic"
+- **Good:** "Hope: Find trustworthy mechanic nearby, get back on road today. Worry: Being stranded for days, getting ripped off by unknown mechanic"
+- **Length Rule:** ONE sentence max per component. Phrases, not paragraphs.
+
+#### Q5: "What device are they on?"
+
+Mobile, desktop, or tablet. This shapes the entire design approach.
 
-#### Component 5: Success Goals (Mutual Value)
+#### Q6: "What's the natural starting point — how do they actually arrive?"
 
-Both required, both specific and measurable:
+How the user ACTUALLY gets to the site. Be specific about discovery method.
+
+- **Bad:** "User opens the website"
+- **Good:** "Googles 'car repair Öland' on mobile while parked at gas station, clicks top organic result"
+- **Length Rule:** 1-2 sentences max. Device + context + discovery method.
+
+#### Q7: "What does the best possible outcome look like — for both sides?"
+
+Mutual success — user AND business. Both specific and measurable.
 
 - **User Success:** Tangible outcome the user achieves
 - **Business Success:** Measurable result for the business
-
 - **Bad:** User: "Successfully use the site" / Business: "Get more customers"
 - **Good:** User: "Confirmed mechanic fixes motorhomes, has location and hours, feels confident calling" / Business: "High-intent tourist call captured, positioned as emergency-capable, info call avoided"
 
-#### Component 6: Shortest Path (Linear Sunshine Path)
+#### Q8: "What's the shortest path through the site to get there?"
 
-Numbered steps. Each step has page name + what user accomplishes there.
+The linear sunshine path. Numbered steps, each with page name + what the user accomplishes.
 
 **Rules:**
 - Completely linear — ZERO "if" statements, ZERO branches
 - Minimum viable steps — can you remove any step without breaking the flow?
 - Each step moves meaningfully toward success
-- This is the happiest path when everything works perfectly
 
 **Format:**
 ```
@@ -136,59 +150,149 @@ Numbered steps. Each step has page name + what user accomplishes there.
 3. **[Page Name]** — [What user sees/does/achieves here] ✓
 ```
 
-#### Component 7: Trigger Map Connections
+### 4. Name the Scenario
+
+After the 8 questions, name the scenario using the persona:
 
-Explicitly link to Trigger Map data:
-- **Persona:** [Name] ([Priority level])
-- **Driving Forces Addressed:**
-  - Positive: [specific want from Trigger Map]
-  - Negative: [specific fear from Trigger Map]
-- **Business Goal:** [specific goal + objective number]
+- **Name:** Persona name + purpose (e.g., "Hasse's Emergency Search")
+- **ID:** 01, 02, etc.
+- **Slug:** `01-hasses-emergency-search`
 
-### 4. Quality Gates (Check Before Moving On)
+### 5. Quality Gates (Check Before Moving On)
 
-Before proceeding to the next scenario, verify:
+Before proceeding, verify the scenario outline:
 
+- [ ] All 8 questions answered with specific, concrete responses
 - [ ] Mental state is visceral and specific (not generic "interested")
 - [ ] Entry point is realistic with device + context + discovery method
 - [ ] Path is truly linear (zero "if" statements)
 - [ ] Both successes are specific and measurable (not vague)
 - [ ] Scenario name includes persona name
-- [ ] All 7 components present
+- [ ] Trigger Map connection is explicit (persona + business goal)
 
 **If any gate fails:** Fix before proceeding.
 
-### 5. Create the File
+### 6. Create the Scenario File
 
 1. Create folder: `{output_folder}/C-UX-Scenarios/[NN-slug]/`
 2. Create file: `{output_folder}/C-UX-Scenarios/[NN-slug]/[NN-slug].md`
-3. Use the template from data/ to structure the content
+3. Use the template from data/ to structure the content from the 8 answers
+
+### 7. After Scenario Creation — Outline Scenario Steps
+
+After the scenario file is saved (Q1-Q8 answered, quality gates passed), begin outlining scenario steps from the Q8 shortest path.
+
+#### Automatic First Step
+
+Process the first scenario step from Q8 automatically:
+1. Name it using Q8's first step name
+2. Create the page folder (see Page Folder Structure below)
+3. Fill first-step metadata from Q3 (user situation), Q4 (mental state), Q5 (device), Q6 (entry point)
+4. Present the result to the user
+
+Then show the Scenario Step Menu.
 
-### 6. Loop Check
+#### Scenario Step Menu
 
-**Are there more scenarios in the approved plan?**
+After each scenario step is outlined, present:
 
-- **Yes** → Loop back to instruction 1 for the next scenario
-- **No** → Proceed to menu options
+```
+Step [NN.X] "[step-name]" outlined!
+
+1. Outline next scenario step — [next step name from Q8]
+2. Start designing — enter the design loop from step 1
 
-### 7. Present MENU OPTIONS
+---
+[N] Define the next scenario
+[C] Continue to overview (when all scenarios are done)
+```
 
-Display: "Are you ready to [C] Continue to Generating the Overview?"
+**Adaptive labels:**
+- Option 1 shows the name of the next step from Q8
+- When all Q8 steps are outlined: Option 1 becomes unavailable — show "All [X] scenario steps outlined!"
+- Option 2: **"Start designing"** when only 1 step is outlined. **"Start designing pages"** when 2+ steps are outlined.
 
 #### Menu Handling Logic:
 
-- IF C: Load, read entire file, then execute {nextStepFile}
+- **IF 1 (Outline next):** Ask the two questions for the next step (see Per-Step Dialog below), create the folder, then show this menu again.
+- **IF 2 (Start designing):** Hand over to Phase 4 (UX Design) → Discuss activity. Phase 4 handles the creative dialog (D1, D2) and all design decisions. The design loop always starts from scenario step 1, regardless of how far the outline has progressed.
+- **IF N:** Loop back to instruction 1 for the next scenario. The current scenario's remaining steps can be outlined later.
+- **IF C:** Load, read entire file, then execute {nextStepFile} (only when all planned scenarios are complete).
 
 #### EXECUTION RULES:
 
 - ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu
-- User can chat or ask questions - always respond and then end with display again of the menu options
+- User can chat or ask questions — always respond and then redisplay the menu
+- The first step is processed automatically after scenario creation (no menu prompt first)
+
+#### Per-Step Dialog
+
+For each step after the first, refine Q8's outline into a concrete scenario step:
+
+**1. "What's the point of this step?"**
+
+What does the user need to accomplish here? This becomes the step purpose.
+- e.g., "See a list of news articles" or "Find the phone number and opening hours"
+
+**2. "What does the user do to move forward?"**
+
+What interaction takes them to the next step? This defines the exit action.
+- e.g., "Selects 'News' in the menu" → next step
+- e.g., "Clicks 'Read more' on an article" → next step
+
+**Two types of interactions:**
+- **Leaves the step** → new scenario step (new page folder, next number)
+- **Stays on the step** → storyboard item (documented within the page spec as an on-page interaction)
+
+After answering, create the page folder and return to the Scenario Step Menu.
+
+### Page Folder Structure
+
+**Naming convention:** `{scenario-number}.{step-number}-{page-slug}` (e.g., `1.1-start-page`, `1.2-news-listing`, `1.3-article-detail`)
+
+Each page folder contains:
+
+```
+{NN}.{step}-{page-slug}/
+├── {NN}.{step}-{page-slug}.md
+└── Sketches/
+```
+
+#### Page boilerplate:
+
+```markdown
+# {NN}.{step}-{page-name}
+
+## Page Metadata
+
+| Property | Value |
+|----------|-------|
+| **Scenario** | {scenario-name} |
+| **Page Number** | {NN}.{step} |
+| **Platform** | {Device from Q5} |
+
+## Overview
+
+**Page Purpose:** {What the user needs to accomplish here}
+
+**Entry Context:** {How the user arrived — previous page + interaction that brought them here}
+
+**Exit Action:** {What the user does to move to the next step}
+
+**On-Page Interactions:**
+- {Any interactions that keep the user on this page — storyboard items}
+```
+
+The **first step** additionally includes:
+- **User Situation** from Q3
+- **Mental State** (hope + worry) from Q4
+- **Discovery Method** from Q6
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [all scenarios from approved plan are outlined and pass quality gates], will you then load and read fully `{nextStepFile}` to execute and begin generating the overview.
+When [C] is selected, ALL scenarios from the approved plan must be outlined and pass quality gates. Then load and read fully `{nextStepFile}` to begin generating the overview.
+
+When **Start designing** is selected, hand over to Phase 4 with the current scenario context. The design loop starts from scenario step 1. The user can return to Phase 3 later for remaining scenarios or steps.
 
 ---
 
@@ -196,20 +300,29 @@ ONLY WHEN [C continue option] is selected and [all scenarios from approved plan
 
 ### ✅ SUCCESS:
 
-- Each scenario has all 7 required components
+- All 8 questions answered for each scenario with specific, concrete responses
 - All quality gates pass for every scenario
-- Output files created in correct folder structure
-- Scenarios processed in priority order
+- Scenario outline file created in correct folder structure
+- Scenarios processed in priority order (primary transaction first, then secondary, etc.)
 - All scenarios from approved plan completed before proceeding
-- Menu presented and user input handled correctly
+- Conversation mode: Dialog felt like a natural conversation, not a form to fill
+- Suggest mode: All 8 answers grounded in actual Trigger Map/Brief data, presented for user review
+- First scenario step processed automatically after scenario creation
+- User presented with clear two-option flow after each step (outline next / start designing)
+- "Start designing" always begins from scenario step 1
 
 ### ❌ SYSTEM FAILURE:
 
-- Missing any of the 7 required components
+- Skipping any of the 8 strategic questions
+- Conversation mode: Presenting all questions at once instead of one at a time
+- Suggest mode: Not presenting answers for user review before proceeding
 - Proceeding with failing quality gates
 - Skipping scenarios from the approved plan
 - Using generic mental states or vague success goals
 - Creating branching paths instead of linear sunshine paths
 - Not creating output files
+- Not automatically processing the first scenario step after scenario creation
+- Starting the design loop from a step other than step 1
+- Presenting the old [N]/[O]/[D]/[C] menu instead of the simplified two-option flow
 
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/3-scenarios/steps-c/step-06-generate-overview.md

@@ -24,7 +24,7 @@ Create the 00-ux-scenarios.md index file that links all scenarios, includes a co
 
 ### 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

package/src/workflows/3-scenarios/steps-c/step-07-quality-review.md

@@ -27,7 +27,7 @@ Self-review all scenarios against the quality rubric across four dimensions (com
 
 ### 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

package/src/workflows/3-scenarios/steps-c/step-08-update-design-log.md

@@ -24,7 +24,7 @@ Document Phase 3 completion in the project design log, recording all artifacts c
 
 ### 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
@@ -55,7 +55,7 @@ Document Phase 3 completion in the project design log, recording all artifacts c
 
 ### 1. Read the Current Log
 
-Read `{output_folder}/_progress/00-progress.md` to understand existing entries and format.
+Read `{output_folder}/_progress/00-design-log.md` to understand existing entries and format.
 
 ### 2. Append Progress Entry
 

package/src/workflows/3-scenarios/steps-c/step-09-handover.md

@@ -10,7 +10,7 @@ workflowFile: '../workflow.md'
 
 ## STEP GOAL:
 
-Complete Phase 3 by presenting a final summary, guiding the user through design intent selection for each scenario, explaining what comes next in Phase 4, and updating any agent dialogs.
+Complete Phase 3 by presenting a final summary, guiding the user through design intent selection for each scenario, explaining what comes next in Phase 4, and updating the design log.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -24,7 +24,7 @@ Complete Phase 3 by presenting a final summary, guiding the user through design
 
 ### 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
@@ -102,7 +102,7 @@ Your scenarios are ready for design. How would you like to approach each?
 
 **Approaches:**
 [K] Sketch — I will draw it myself, agent interprets later
-[C] Conceptualize — Let us explore what the design needs together
+[C] Discuss — Creative dialog for page design
 [S] Suggest — Agent proposes step by step, I confirm each
 [D] Dream Up — Agent creates the whole flow, I review the result
 [L] Later — Decide when I start Phase 4
@@ -121,7 +121,7 @@ Explain to user:
 
 **Phase 4: UX Design** takes each scenario outline and designs it using your chosen approach:
 - **Sketch** scenarios wait for your drawings
-- **Conceptualize** scenarios start with collaborative exploration
+- **Discuss** scenarios start with a creative dialog for each page
 - **Suggest** scenarios let the agent propose step by step
 - **Dream Up** scenarios let the agent create autonomously
 
@@ -130,9 +130,9 @@ You can always change approach in Phase 4.
 Would you like to continue to Phase 4, or take a break?
 ```
 
-### 4. Update Agent Dialog (If Exists)
+### 4. Update Design Log (If Exists)
 
-If tracking via agent dialog:
+If tracking via design log:
 - Mark Phase 3 as complete
 - Log scenario count and quality scores
 - Note any user adjustments made during the process
@@ -166,7 +166,7 @@ ONLY WHEN [M main menu option] is selected and [design intent captured for all s
 - Design intent selection offered for each scenario
 - Design intent and status saved to scenario frontmatter
 - Phase 4 approaches clearly explained
-- Agent dialog updated if applicable
+- Design log updated if applicable
 - User informed of next steps
 - Menu presented and user input handled correctly
 
@@ -176,6 +176,6 @@ ONLY WHEN [M main menu option] is selected and [design intent captured for all s
 - Skipping design intent selection
 - Not saving design intent to scenario files
 - Ending without explaining next steps
-- Not updating agent dialog when one exists
+- Not updating design log when one exists
 
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/3-scenarios/steps-v/step-01-scenario-coverage.md

@@ -1,6 +1,6 @@
 ---
 name: step-01-scenario-coverage
-description: Verify that all Value Trigger Chains from the Trigger Map are covered by at least one scenario
+description: Verify that all strategic context chains from the Trigger Map are covered by at least one scenario
 
 # File References
 nextStepFile: './step-02-navigation-patterns.md'
@@ -10,7 +10,7 @@ nextStepFile: './step-02-navigation-patterns.md'
 
 ## STEP GOAL:
 
-Verify that all Value Trigger Chains (VTCs) from the Trigger Map are covered by at least one scenario, with Priority 1 VTCs having dedicated scenarios.
+Verify that all strategic context chains from the Trigger Map are covered by at least one scenario, with Priority 1 chains having dedicated scenarios.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -32,22 +32,22 @@ Verify that all Value Trigger Chains (VTCs) from the Trigger Map are covered by
 
 ### Step-Specific Rules:
 
-- 🎯 Focus only on VTC-to-scenario coverage verification
+- 🎯 Focus only on strategic-context-to-scenario coverage verification
 - 🚫 FORBIDDEN to modify any scenario files during validation
-- 💬 Approach: Systematic cross-referencing of Trigger Map VTCs against scenarios
+- 💬 Approach: Systematic cross-referencing of Trigger Map strategic context against scenarios
 - 📋 Report findings with clear severity levels
 
 ## EXECUTION PROTOCOLS:
 
 - 📖 Load both Trigger Map and all scenario files
-- 🔗 Cross-reference every VTC against scenario coverage
+- 🔗 Cross-reference every strategic context chain against scenario coverage
 - 📊 Report with severity levels (Critical/Warning/Pass)
-- 🚫 FORBIDDEN to skip any VTC during verification
+- 🚫 FORBIDDEN to skip any chain during verification
 
 ## CONTEXT BOUNDARIES:
 
 - Available context: Trigger Map, all scenario outlines, scenario index
-- Focus: VTC coverage verification only
+- Focus: Strategic context coverage verification only
 - Limits: No scenario modifications, only verification and reporting
 - Dependencies: All scenario files must exist from Phase 3 creation workflow
 
@@ -55,7 +55,7 @@ Verify that all Value Trigger Chains (VTCs) from the Trigger Map are covered by
 
 ### 1. Load Trigger Map Data
 
-Read `{output_folder}/B-Trigger-Map/trigger-map.md` and extract all VTCs (Business Goal → Persona → Driving Force chains).
+Read `{output_folder}/B-Trigger-Map/trigger-map.md` and extract all strategic context chains (Business Goal → Persona → Driving Force chains).
 
 ### 2. Load All Scenario Files
 
@@ -63,28 +63,28 @@ Read all scenario outlines from `{output_folder}/C-UX-Scenarios/`.
 
 ### 3. Cross-Reference
 
-For each VTC, verify:
-- [ ] At least one scenario addresses this VTC
-- [ ] The scenario Trigger Map Connections section explicitly references the VTC components
-- [ ] Priority 1 VTCs have dedicated scenarios (not just secondary coverage)
+For each strategic context chain, verify:
+- [ ] At least one scenario addresses this chain
+- [ ] The scenario Trigger Map Connections section explicitly references the strategic context components
+- [ ] Priority 1 chains have dedicated scenarios (not just secondary coverage)
 
 ### 4. Generate Report
 
 ```
 ## Coverage Report
 
-| VTC | Persona | Driving Force | Scenario(s) | Status |
+| Chain | Persona | Driving Force | Scenario(s) | Status |
 |-----|---------|---------------|-------------|--------|
 | [Goal] | [Name] | [Force] | [Scenario ID] | ✅/⚠️/❌ |
 
-**Coverage:** [X]/[Total] VTCs covered ([X]%)
-**Gaps:** [list uncovered VTCs]
+**Coverage: [X]/[Total] chains covered ([X]%)
+**Gaps: [list uncovered chains]]
 ```
 
 **Severity:**
-- ❌ Critical: Priority 1 VTC with no scenario
-- ⚠️ Warning: Priority 2-3 VTC with no scenario
-- ✅ Pass: VTC covered by at least one scenario
+- ❌ Critical: Priority 1 chain with no scenario
+- ⚠️ Warning: Priority 2-3 chain with no scenario
+- ✅ Pass: Chain covered by at least one scenario
 
 ### 5. Present MENU OPTIONS
 
@@ -103,7 +103,7 @@ Display: "Are you ready to [C] Continue to Navigation Patterns validation?"
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [coverage report generated with all VTCs checked], will you then load and read fully `{nextStepFile}` to execute and begin navigation patterns validation.
+ONLY WHEN [C continue option] is selected and [coverage report generated with all chains checked], will you then load and read fully `{nextStepFile}` to execute and begin navigation patterns validation.
 
 ---
 
@@ -111,16 +111,16 @@ ONLY WHEN [C continue option] is selected and [coverage report generated with al
 
 ### ✅ SUCCESS:
 
-- All VTCs from Trigger Map identified and cross-referenced
-- Every VTC checked against scenario coverage
+- All strategic context chains from Trigger Map identified and cross-referenced
+- Every chain checked against scenario coverage
 - Severity levels correctly assigned
 - Coverage report generated with clear gaps identified
-- Priority 1 VTCs verified for dedicated scenario coverage
+- Priority 1 chains verified for dedicated scenario coverage
 - Menu presented and user input handled correctly
 
 ### ❌ SYSTEM FAILURE:
 
-- Missing any VTC from the cross-reference
+- Missing any chain from the cross-reference
 - Not loading all scenario files
 - Incorrect severity assignment
 - Not identifying coverage gaps

package/src/workflows/3-scenarios/workflow-validate.md

@@ -15,11 +15,8 @@ validateWorkflow: './steps-v/step-01-scenario-coverage.md'
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ### Configuration Loading
 

package/src/workflows/3-scenarios/workflow.md

@@ -8,7 +8,7 @@ web_bundle: true
 
 **Goal:** Transform the Trigger Map into concrete UX scenario outlines — linear sunshine paths that expose all pages for design scrutiny.
 
-**Your Role:** UX Scenario Architect collaborating with the project owner. You bring scenario thinking and user journey expertise. Work together as equals.
+**Your Role:** UX Scenario Facilitator collaborating with the project owner — you ASK, the user DECIDES. You bring scenario thinking and user journey expertise. Work together as equals.
 
 ---
 
@@ -51,7 +51,7 @@ This uses **step-file architecture** for disciplined execution:
 |---|------|---------|
 | 01 | [Load Context](steps-c/step-01-load-context.md) | Read all prerequisite artifacts, detect project state |
 | 02 | [Analyze Scope](steps-c/step-02-analyze-scope.md) | Determine site type, pages, scale strategy (user checkpoint) |
-| 03 | [Build VTCs](steps-c/step-03-build-vtcs.md) | Extract Value Trigger Chains from Trigger Map |
+| 03 | [Build Strategic Context](steps-c/step-03-build-strategic-context.md) | Extract strategic context from Trigger Map |
 | 04 | [Suggest Scenarios](steps-c/step-04-suggest-scenarios.md) | Present scenario plan for approval (user checkpoint) |
 | 05 | [Outline Scenario](steps-c/step-05-outline-scenario.md) | Detail ONE scenario (loops for each) |
 | 06 | [Generate Overview](steps-c/step-06-generate-overview.md) | Create 00-ux-scenarios.md index file |
@@ -69,11 +69,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 scenario 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