initial commit

_bmad/wds/workflows/3-scenarios/data/quality-checklist.md

@@ -0,0 +1,161 @@
+# Scenario Quality Checklist
+
+**Used by:** step-07-quality-review.md
+**Source:** Adapted from dream-up-rubric-phase-4-scenarios.md
+
+---
+
+## Dimension 1: Completeness (7 sections)
+
+For each scenario, verify all 7 components exist:
+
+- [ ] **Core Feature** — Clear statement of what scenario covers, aligned to business goal
+- [ ] **Entry Point** — Specific starting location with device, context, and discovery method
+- [ ] **Mental State** — All three present: Trigger (what happened), Hope (what they want), Worry (what they fear)
+- [ ] **Success Goals** — Both present: User success (tangible) + Business success (measurable)
+- [ ] **Shortest Path** — Linear steps listed with name + purpose, no branches
+- [ ] **Scenario Name** — Persona name in title, ID assigned (01, 02...)
+- [ ] **Trigger Map Connections** — Persona named, driving forces listed, business goal referenced
+
+**Minimum:** 6/7 present (Trigger Map Connections can be implicit if obvious from other sections)
+
+---
+
+## Dimension 2: Quality Criteria (7 checks)
+
+### 2.1 Persona Alignment
+- Scenario serves a specific persona from Trigger Map (not generic "user")
+- Mental state matches persona's psychological profile
+- Entry point reflects persona's behavior patterns
+
+### 2.2 Mental State Richness
+- All three components (Trigger/Hope/Worry) are specific and visceral
+- You can FEEL the user's emotional state
+- Mental state informs design decisions
+
+**Bad:** "User is interested in the product"
+**Good:** "Panicked — motorhome broke down, family vacation at risk, unfamiliar area"
+
+### 2.3 Mutual Success Clarity
+- Both successes are specific and measurable
+- Business success is not just "revenue" or "engagement"
+- User success is tangible (not "satisfied" or "happy")
+
+**Bad:** Business: "Get more customers" / User: "Successfully use the site"
+**Good:** Business: "High-intent tourist call captured, info call avoided" / User: "Confirmed capability, got location, feels confident calling"
+
+### 2.4 Sunshine Path Focus
+- Path is completely linear (no "if" statements)
+- Error states and edge cases deferred
+- This is the absolute happiest path
+
+### 2.5 Minimum Viable Steps
+- Each step moves meaningfully toward success
+- No unnecessary pages or detours
+- Can you remove any step without breaking the flow?
+
+### 2.6 Entry Point Realism
+- Describes HOW user actually discovered this
+- Includes device context
+- Reflects real-world behavior
+
+**Bad:** "User opens app"
+**Good:** "Tourist googles 'car repair Öland' on mobile at gas station, clicks top result"
+
+### 2.7 Business Goal Connection
+- Traces to specific business goal from Trigger Map
+- Business value is explicit, not assumed
+- User success drives business success (not competes)
+
+**Minimum:** 5/7 fully met
+
+---
+
+## Dimension 3: Common Mistakes (7 checks)
+
+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?
+**Fix:** Remove all conditional logic. Document edge cases separately.
+
+### 3.2 Feature-First Naming
+**Check:** Does the scenario name describe a feature or a user goal?
+**Fix:** Rename to persona + purpose format.
+- Bad: "Homepage and Services"
+- Good: "Hasse's Emergency Search"
+
+### 3.3 Missing Mental State
+**Check:** Is mental state present with all three components?
+**Fix:** Add Trigger/Hope/Worry with specific, visceral descriptions.
+
+### 3.4 Vague Page Descriptions
+**Check:** Do pages have just names, or names + purpose?
+**Fix:** Add what user accomplishes at each step.
+- Bad: "1. Homepage 2. Services 3. Contact"
+- Good: "1. Homepage — confirms mechanic fixes motorhomes 2. Contact — gets phone + directions"
+
+### 3.5 Generic Persona
+**Check:** Does scenario use a Trigger Map persona with name?
+**Fix:** Replace "user" with specific persona name and driving forces.
+
+### 3.6 Missing Business Value
+**Check:** Is business success explicitly defined and measurable?
+**Fix:** Add specific business outcome connected to Trigger Map goal.
+
+### 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)
+
+---
+
+## Dimension 4: Best Practices (4 checks)
+
+### 4.1 Persona in Scenario Name
+Scenario title includes persona name (e.g., "Hasse's Emergency Search")
+
+### 4.2 Highest-Value Persona First
+Scenario 01 serves the Primary persona. Design scenarios for Primary first, then Secondary.
+
+### 4.3 One Job Per Scenario
+Each scenario accomplishes ONE clear job-to-be-done. No scope creep.
+
+### 4.4 Driving Forces Explicitly Linked
+Scenario states which specific wants/fears from Trigger Map it addresses, with checkmark format:
+- ✅ Want: [specific force]
+- ❌ Fear: [specific force]
+
+**Minimum:** 2/4 followed
+
+---
+
+## Scoring Summary Template
+
+```
+## Quality Review: [Scenario ID]
+
+**Completeness:** [X]/7
+**Quality:** [X]/7
+**Mistakes Avoided:** [X]/7
+**Best Practices:** [X]/4
+
+**Status:** [Excellent / Good / Needs Work]
+**Gaps:** [list or "None"]
+```
+
+---
+
+## Thresholds
+
+| Level | Complete | Quality | Mistakes | Practices |
+|-------|----------|---------|----------|-----------|
+| 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.
+
+---
+
+_Quality checklist for Step 07: Quality Review_

_bmad/wds/workflows/3-scenarios/data/scenario-outline-template.md

@@ -0,0 +1,121 @@
+# Scenario Outline Template
+
+**Used by:** step-05-outline-scenario.md
+**Purpose:** Structure the answers from the 8-question scenario dialog into a complete scenario outline.
+
+---
+
+## Template
+
+```markdown
+# [NN]: [Persona Name]'s [Purpose]
+
+**Project:** [project_name]
+**Created:** [date]
+**Method:** Whiteport Design Studio (WDS)
+
+---
+
+## Transaction (Q1)
+
+**What this scenario covers:**
+[The key transaction — stated as user purpose, not feature name]
+
+---
+
+## Business Goal (Q2)
+
+**Goal:** [Which specific business goal this serves]
+**Objective:** [Objective reference from Trigger Map]
+
+---
+
+## User & Situation (Q3)
+
+**Persona:** [Name] ([Priority level: Primary/Secondary/Tertiary])
+**Situation:** [Real-life context — who they are, where they are, what's happening]
+
+---
+
+## Driving Forces (Q4)
+
+**Hope:** [What they're hoping to find or achieve — one sentence]
+
+**Worry:** [What they're afraid of or want to avoid — one sentence]
+
+> CONSTRAINT: One sentence per component. Phrases, not paragraphs.
+
+---
+
+## Device & Starting Point (Q5 + Q6)
+
+**Device:** [Mobile / Desktop / Tablet]
+**Entry:** [How they actually arrive] — max 2 sentences
+
+---
+
+## Best Outcome (Q7)
+
+**User Success:**
+[Tangible, measurable outcome the user achieves]
+
+**Business Success:**
+[Specific, measurable result the business gets]
+
+---
+
+## Shortest Path (Q8)
+
+[Linear sunshine path — NO branches, NO "if" statements. Minimum viable steps.]
+
+1. **[Page Name]** — [What user sees/does/achieves at this step]
+2. **[Page Name]** — [What user sees/does/achieves at this step]
+3. **[Page Name]** — [What user sees/does/achieves at this step] ✓
+
+---
+
+## Trigger Map Connections
+
+**Persona:** [Name] ([Priority level])
+
+**Driving Forces Addressed:**
+- ✅ **Want:** [Specific positive driver from Trigger Map]
+- ❌ **Fear:** [Specific negative driver from Trigger Map]
+
+**Business Goal:** [Specific goal + objective from Trigger Map]
+
+---
+
+## 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] ✓ |
+
+**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.
+```
+
+---
+
+## Quality Reminders
+
+When filling this template, check:
+
+**Transaction** — Is this a real user journey? Browsing content page-by-page counts. Comparing options counts. Any meaningful path through the site with intent.
+
+**Driving Forces** — Can you FEEL the user's state? "Interested" is not enough. "Panicked because family vacation is at risk" is.
+
+**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.
+
+**Trigger Map** — Don't invent a user. Use the actual persona with their actual driving forces.
+
+---
+
+_Template for Step 05: Outline Scenario (8-Question Dialog)_

_bmad/wds/workflows/3-scenarios/data/validation-standards.md

@@ -0,0 +1,58 @@
+# WDS Scenario Validation Standards
+
+Reference document for Phase 3 validation steps.
+
+---
+
+## What Makes a Valid Scenario
+
+### Minimum Requirements (must pass)
+1. All 7 components present (name, feature, entry, mental state, success, path, TM connections)
+2. Path is truly linear (zero branches)
+3. Mental state is specific and visceral
+4. Both success goals are measurable
+5. Trigger Map connections are explicit
+
+### Quality Thresholds
+- Completeness: 6/7 minimum
+- Quality: 5/7 minimum
+- Mistakes avoided: 6/6 (all must be avoided)
+- Best practices: 2/4 minimum
+
+---
+
+## WDS Navigation Conventions
+
+### Page Naming
+- Use user-facing names (not technical: "Tjänster", not "services-page")
+- Consistent naming across scenarios (same page = same name)
+- Include page purpose in descriptions
+
+### Flow Rules
+- Entry page must be reachable from the described discovery method
+- Each step transitions naturally to the next
+- Final step has clear success marker (✓)
+- No dead ends, no impossible jumps
+
+### Shared Pages
+- Pages appearing in 2+ scenarios must serve consistent purposes
+- Shared pages should accommodate all relevant personas
+
+---
+
+## SEO Integration
+
+### Phase 1 → Phase 3 Connection
+- Every page should map to at least one keyword from the Phase 1 keyword map
+- Page names should be compatible with planned URL slugs
+- No keyword cannibalization (two pages competing for same keyword)
+
+---
+
+## Validation Severity Levels
+
+| Level | Meaning | Action |
+|-------|---------|--------|
+| ❌ Critical | Blocks Phase 4 progress | Must fix before handover |
+| ⚠️ Warning | Quality concern | Should fix, can proceed |
+| ✅ Pass | Meets standards | No action needed |