Transform the Trigger Map into concrete UX scenario outlines — linear sunshine paths that expose
all pages for design scrutiny. Each step must be completed in sequence. User checkpoints at
steps 2 and 4 enforce that no scenario is created without explicit user approval of scope and plan.
Read {project-root}/_bmad/wds/config.yaml and resolve: project_name, output_folder,
user_name, communication_language, document_output_language.
Read {output_folder}/_progress/00-design-log.md. Check Current and Backlog sections
for any in-progress work from a previous session.
Check invocation mode:
- If invoked with "validate" or -v flag: load and execute ./workflow-validate.md instead.
- Default: proceed to Step 1.
Read {project-root}/_bmad/wds/config.yaml completely and extract all required fields.
Read {output_folder}/A-Product-Brief/product-brief.md completely. Extract and note:
site/app type, business context, technical platform, page count, navigation structure.
Read {output_folder}/B-Trigger-Map/trigger-map.md completely. Extract and note:
business goals with priority tiers, all personas (name, priority, wants, fears, flywheel role).
Also read any linked persona documents (02-*.md, 03-*.md, 04-*.md) if they exist.
Check for existing work: does {output_folder}/C-UX-Scenarios/ exist? Are there scenario files?
Is there in-progress work in the design log? If YES — present options to resume, review, or start fresh.
Wait for user response before proceeding.
Present context summary to user: project name, site type, business goal count, persona list,
primary persona + top driving force. Wait for user acknowledgment.
Classify the site type from Product Brief data:
- Presentation Site → Screen Flow format, expose all pages.
- Dynamic App → Storyboard format, focus on core workflow.
- Mixed → use both formats as needed.
Create a complete numbered page inventory from the Product Brief. Include every page mentioned
or implied by navigation and business goals. Exclude shared elements (header, footer, nav).
Assess scale and recommend approach mode:
- Small (fewer than 20 pages): Comprehensive coverage, recommend Dream or Suggest.
- Medium (20-50 pages): Comprehensive coverage with groupings, recommend Suggest.
- Large (100+ pages): Selective ignorance, recommend Dialog.
Determine page documentation strategy: separate pages (high variation) vs. template with
content variations (low variation, many structurally identical pages).
Present the full scope analysis to the user — site type, total pages, scale, recommended mode,
scenario format, page inventory, page strategy. Ask: "Does this look right? Any pages missing
or that should be grouped differently?" WAIT for explicit user approval. Do not proceed until
the user confirms the scope.
For each business goal from the Trigger Map, trace the complete strategic context chain:
Business Goal → Persona → Driving Force → Transaction → Candidate Scenario.
Answer all 7 Decision Matrix questions for every chain:
(1) business goal, (2) persona, (3) driving force, (4) transaction,
(5) where user comes from, (6) user value, (7) business value.
Assign pages from the approved inventory (Step 2) to each scenario chain.
Rules: each page appears in exactly ONE chain. If a page fits multiple chains,
assign it to the highest-priority one. Exclude shared elements.
Prioritize scenario chains:
- Priority 1 (Critical Path): top business goal + primary persona + core product value.
- Priority 2 (Supporting): secondary persona or alternative entry paths.
- Priority 3 (Edge Cases): admin tasks, rare segments, error recovery.
Run coverage check: every page from inventory assigned to exactly one chain,
primary persona has at least one Priority 1 scenario, top business goal addressed,
no page appears in multiple chains. If pages are unassigned, expand chains to cover them.
Present the complete strategic context chain list with priorities and page assignments.
Include coverage count (X/Y pages assigned). Wait for user to confirm before proceeding.
Format the complete scenario plan using the exact template from step-04-suggest-scenarios.md:
- Site Analysis header (type, total pages, format, scenario count).
- For each scenario: persona name + purpose, page list, persona driving force,
user value, business value, format. Scenario IDs as 01, 02, 03 etc.
- Scenario names MUST use persona names (e.g., "Hasse's Emergency Search",
NOT "Emergency Booking Flow"). This is non-negotiable.
Include a Coverage Check section with four verifications:
all pages assigned, no page repetition, primary persona covered, top business goal addressed.
Present the complete scenario plan to the user and WAIT for explicit approval.
Handle feedback: combine scenarios, add scenarios, apply selective ignorance, add missing pages.
Re-present adjusted plan after any changes. Do NOT proceed to outlining until user explicitly approves.
After user approval, record the final scenario count, page assignments, and any user adjustments.
Assign folder slugs: 01-persona-name-slug, 02-persona-name-slug, etc.
Load the scenario outline template from data/scenario-outline-template.md before starting.
Determine which scenario to work on: process in priority order (Priority 1 first).
If returning from a loop, continue with the next unfinished scenario.
Run the 8-Question Scenario Dialog for the current scenario. Default is Conversation Mode
(agent asks, user answers one question at a time). Suggest Mode available if user requests it.
Questions must be asked one at a time — never all at once.
Q1: What transaction do we need to get really right? (user purpose, not feature name)
Q2: Which business goal does a successful transaction add value to? (reference Trigger Map)
Q3: Which user experiences this most, and in what real-life situation? (persona + context)
Q4: What do they want and what do they fear? (hope + worry, ONE sentence each, visceral)
Q5: What device are they on? (mobile / desktop / tablet)
Q6: What is the natural starting point — how do they actually arrive? (1-2 sentences, specific)
Q7: What does the best possible outcome look like — for both sides? (measurable, both parties)
Q8: What is the shortest path through the site to get there? (linear, numbered, zero branches)
Name the scenario after the persona: Name + Purpose. Assign ID and slug.
Run all 7 quality gates before creating any file:
- 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, zero branches).
- Both successes are specific and measurable.
- Scenario name includes persona name.
- Trigger Map connection is explicit.
Fix any failing gates before proceeding.
Create folder: {output_folder}/C-UX-Scenarios/[NN-slug]/
Create file: {output_folder}/C-UX-Scenarios/[NN-slug]/[NN-slug].md
Use the template structure with all 8 answers filled in.
After saving the scenario file, begin outlining scenario steps from Q8's path.
Process the FIRST step automatically: name it from Q8 step 1, create the page folder,
fill metadata from Q3 (situation), Q4 (mental state), Q5 (device), Q6 (entry point).
Present the result, then show the Scenario Step Menu.
Page folder naming: {NN}.{step-number}-{page-slug}
Each page folder contains: {NN}.{step}-{page-slug}.md + Sketches/
Scenario Step Menu after each step:
1. Outline next scenario step — [next step name from Q8]
2. Start designing — enter the design loop from step 1
---
[N] Define the next scenario
[C] Continue to overview (when all scenarios are done)
Handle menu choices:
- 1: ask the two per-step questions (step purpose + exit action), create folder, re-show menu.
- 2: hand over to Phase 4 (Discuss activity), starting from scenario step 1.
- N: loop back to the next unfinished scenario (Instruction 2 above).
- C: only when ALL scenarios from approved plan are outlined. Proceed to Step 6.
Loop back — present Scenario Step Menu option [N] for next scenario
All scenarios complete — proceed to Step 6
Create {output_folder}/C-UX-Scenarios/00-ux-scenarios.md using the exact document
structure from step-06-generate-overview.md:
- Header with project name, date, author, method.
- Scenario Summary table (ID, name, persona, pages, priority, status).
- Per-scenario sections with persona, pages, user value, business value, link.
- Page Coverage Matrix (every page, which scenario, purpose in flow).
- Coverage count (X/Y pages assigned).
- Next Phase section.
Verify all links before completing:
- Each scenario link points to the correct folder/file.
- All scenarios from the approved plan are listed.
- Page coverage matrix is complete — no pages missing.
Load the full quality checklist from data/quality-checklist.md before starting.
Review EVERY scenario across all four dimensions:
Dimension 1 — Completeness (7 components, minimum 6/7):
Core feature, entry point, mental state, success goals, shortest path, scenario name, Trigger Map connections.
Dimension 2 — Quality Criteria (7 checks, minimum 5/7):
Persona-specific, visceral mental state, measurable successes, zero "if" statements, minimum viable steps,
realistic entry point, explicit business goal connection.
Dimension 3 — Mistakes Avoided (6 checks, ALL 6 required):
No edge cases in path, goal-first naming, mental state present, page descriptions include purpose,
uses Trigger Map persona, business value defined.
Dimension 4 — Best Practices (4 checks, minimum 2/4):
Named after persona, started with highest-value persona, one job-to-be-done per scenario,
driving forces linked.
Fix any failing items: go back to the scenario file, correct the specific gaps, re-verify.
If still failing after corrections, present gaps to user for guidance before proceeding.
Present the quality review summary table to the user (per scenario: scores for all four
dimensions + status). Include overall rating and list of any remaining gaps.
Read the existing {output_folder}/_progress/00-design-log.md before making any changes.
Understand the current format and find the last entry.
APPEND (never overwrite) a Phase 3 progress entry under the Progress section:
- Date, phase label, agent name, scenario count, page count, quality rating.
- Artifacts: list EVERY file created individually — no summarizing with "etc."
Include 00-ux-scenarios.md and ALL scenario + page folder files.
- Summary: 2-3 specific sentences mentioning actual decisions made, page coverage status.
- Next: Phase 4 — UX Design.
Add rows to the Key Decisions table for any significant Phase 3 choices:
scenario count changes, page reassignments, priority reordering, scope decisions.
Skip this section only if truly no significant decisions were made.
Verify before completing:
- Progress entry is appended, not overwriting existing entries.
- All artifact files listed individually.
- Summary is specific, not generic.
- Key decisions recorded where applicable.
Present the final completion summary: project name, scenario count, scenario table (ID, name,
persona, pages, priority), coverage stats, quality rating, all files created.
Guide the user through Design Intent selection for each scenario. For each scenario,
present the five options:
[K] Sketch — user draws, agent interprets later
[C] Discuss — creative dialog
[S] Suggest — agent proposes step by step, user confirms
[D] Dream Up — agent creates autonomously, user reviews
[L] Later — decide at Phase 4 start
Save the chosen approach as design_intent in each scenario's frontmatter.
Also add design_status: not-started to each scenario file.
Explain Phase 4 clearly: how each design intent maps to a Phase 4 activity,
that the user can always change approach in Phase 4, and how the adaptive dashboard
reads the design log to suggest where to continue.
Ask the user: "Would you like to continue to Phase 4, or take a break?"
Present [M] Main Menu option to return to workflow start.
{output_folder}/C-UX-Scenarios/00-ux-scenarios.md
{output_folder}/C-UX-Scenarios/{NN-scenario-slug}/{NN-scenario-slug}.md
{output_folder}/C-UX-Scenarios/{NN-scenario-slug}/{NN}.{step}-{page-slug}/{NN}.{step}-{page-slug}.md
wds-4-ux-design