refactor: complete display tag migration across all workflows

Convert remaining bare quote output blocks and Display: patterns
to <display> tags in 48 files across product-brief, ux-design,
architecture, check-implementation-readiness, quick-spec, research,
brainstorming, party-mode, generate-project-context, and
document-project workflows. Fix orphaned quote artifact in
step-09-functional.md.

.claude/commands/bmad-bmm-generate-project-context.md

@@ -1,14 +0,0 @@
----
-name: 'generate-project-context'
-description: 'Scan existing codebase to generate a lean LLM-optimized project-context.md with critical implementation rules and patterns for AI agents'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md
-3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/skills/gh-triage/SKILL.md

@@ -0,0 +1,158 @@
+---
+name: gh-triage
+description: Fetch all GitHub issues via gh CLI and use AI agents to deeply analyze, cluster, and prioritize issues with actual understanding. Use for issue triage, backlog cleanup, or when user mentions "issues", "triage", or "backlog".
+license: MIT
+disable-model-invocation: true
+metadata:
+  author: bmad-code-org
+  version: "3.0.0"
+  anthropic-internal: Core team issue triage tool for BMad Method repositories
+  min-github-cli-version: "2.0"
+compatibility: Requires gh CLI, git repository, and BMad Method with Task tool support
+---
+
+# GitHub Issue Triage with AI Analysis
+
+**CRITICAL RULES:**
+- NEVER include time or effort estimates in output or recommendations
+- Focus on WHAT needs to be done, not HOW LONG it takes
+- Use Bash tool with gh CLI for all GitHub operations
+
+## Execution Plan
+
+You will perform GitHub issue triage using AI agents for deep analysis:
+
+### Step 1: Fetch Issues
+Use `gh issue list` to fetch all open issues from the current repository in JSON format.
+
+### Step 2: Batch Creation
+Split issues into batches of ~10 issues each for parallel analysis.
+
+### Step 3: Parallel Agent Analysis
+For EACH batch, use the Task tool with `subagent_type=general-purpose` to launch an agent with this prompt:
+
+```
+You are analyzing a batch of GitHub issues for deep understanding and triage.
+
+**YOUR TASK:**
+Read the issues in your batch and provide DEEP analysis:
+
+1. **For EACH issue, analyze:**
+   - What is this ACTUALLY about? (beyond keywords)
+   - What component/system does it affect?
+   - What's the impact and severity?
+   - Is it a bug, feature request, or something else?
+   - What specific theme does it belong to?
+
+2. **PRIORITY ASSESSMENT:**
+   - CRITICAL: Blocks users, security issues, data loss, broken installers
+   - HIGH: Major functionality broken, important features missing
+   - MEDIUM: Workarounds available, minor bugs, nice-to-have features
+   - LOW: Edge cases, cosmetic issues, questions
+
+3. **RELATIONSHIPS:**
+   - Duplicates: Near-identical issues about the same problem
+   - Related: Issues connected by theme or root cause
+   - Dependencies: One issue blocks or requires another
+
+**YOUR BATCH:**
+[Paste the batch of issues here - each with number, title, body, labels]
+
+**OUTPUT FORMAT (JSON only, no markdown):**
+{
+  "issues": [
+    {
+      "number": 123,
+      "title": "issue title",
+      "deep_understanding": "2-3 sentences explaining what this is really about",
+      "affected_components": ["installer", "workflows", "docs"],
+      "issue_type": "bug/feature/question/tech-debt",
+      "priority": "CRITICAL/HIGH/MEDIUM/LOW",
+      "priority_rationale": "Why this priority level",
+      "theme": "installation/workflow/integration/docs/ide-support/etc",
+      "relationships": {
+        "duplicates_of": [456],
+        "related_to": [789, 101],
+        "blocks": [111]
+      }
+    }
+  ],
+  "cross_repo_issues": [
+    {"number": 123, "target_repo": "bmad-builder", "reason": "about agent builder"}
+  ],
+  "cleanup_candidates": [
+    {"number": 456, "reason": "v4-related/outdated/duplicate"}
+  ],
+  "themes_found": {
+    "Installation Blockers": {
+      "count": 5,
+      "root_cause": "Common pattern if identifiable"
+    }
+  }
+}
+
+Return ONLY valid JSON. No explanations outside the JSON structure.
+```
+
+### Step 4: Consolidate & Generate Report
+After all agents complete, create a comprehensive markdown report saved to `_bmad-output/triage-reports/triage-YYYY-MM-DD.md` with:
+
+## Report Structure
+
+### Executive Summary
+- Total issues analyzed
+- Issue count by priority (CRITICAL, HIGH, MEDIUM, LOW)
+- Major themes discovered
+- Top 5 critical issues requiring immediate attention
+
+### Critical Issues (CRITICAL Priority)
+For each CRITICAL issue:
+- **#123 - [Issue Title](url)**
+- **What it's about:** [Deep understanding]
+- **Affected:** [Components]
+- **Why Critical:** [Rationale]
+- **Suggested Action:** [Specific action]
+
+### High Priority Issues (HIGH Priority)
+Same format as Critical, grouped by theme.
+
+### Theme Clusters
+For each major theme:
+- **Theme Name** (N issues)
+- **What connects these:** [Pattern]
+- **Root cause:** [If identifiable]
+- **Consolidated actions:** [Bulk actions if applicable]
+- **Issues:** #123, #456, #789
+
+### Relationships & Dependencies
+- **Duplicates:** List pairs with `gh issue close` commands
+- **Related Issues:** Groups of related issues
+- **Dependencies:** Blocking relationships
+
+### Cross-Repo Issues
+Issues that should be migrated to other repositories (bmad-builder, bmad-module-creative-intelligence-suite, bmad-module-game-dev-studio, bmad-method-test-architecture-enterprise).
+
+For each, provide:
+```
+gh issue close XXX --repo CURRENT_REPO --comment "This issue belongs in REPO. Please report at https://github.com/TARGET_REPO/issues/new"
+```
+
+### Cleanup Candidates
+- **v4-related:** Deprecated version issues with close commands
+- **Stale:** No activity >30 days
+- **Low priority + old:** Low priority issues >60 days old
+
+### Actionable Next Steps
+Specific, prioritized actions:
+1. [CRITICAL] Fix broken installer - affects all new users
+2. [HIGH] Resolve Windows path escaping issues
+3. [HIGH] Address workflow integration bugs
+etc.
+
+Include `gh` commands where applicable for bulk actions.
+
+---
+
+## Execute Now
+
+Begin by fetching issues from the current repository and follow the plan above.

.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -0,0 +1,124 @@
+name: Bug Report
+description: File a bug report to help us improve BMad Method
+title: "[BUG] "
+labels: bug
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for filing a bug report! Please fill out the information below to help us reproduce and fix the issue.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Clear and concise description of what the bug is
+      placeholder: e.g., When I run /dev-story, it crashes on step 3
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      description: Step-by-step instructions to reproduce the behavior
+      placeholder: |
+        1. Run 'npx bmad-method install'
+        2. Select option X
+        3. Run workflow Y
+        4. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: What you expected to happen
+      placeholder: The workflow should complete successfully
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual behavior
+      description: What actually happened
+      placeholder: The workflow crashed with error "..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: Add screenshots if applicable (paste images directly)
+      placeholder: Paste any relevant screenshots here
+
+  - type: dropdown
+    id: module
+    attributes:
+      label: Which module is this for?
+      description: Select the BMad module this issue relates to
+      options:
+        - BMad Method (BMM) - Core Framework
+        - BMad Builder (BMB) - Agent Builder Tool
+        - Test Architect (TEA) - Test Strategy Module
+        - Game Dev Studio (BMGD) - Game Development Module
+        - Creative Intelligence Suite (CIS) - Innovation Module
+        - Not sure / Other
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: BMad Version
+      description: "Check with: npx bmad-method --version or check package.json"
+      placeholder: e.g., 6.0.0-Beta.4
+    validations:
+      required: true
+
+  - type: dropdown
+    id: ide
+    attributes:
+      label: Which AI IDE are you using?
+      options:
+        - Claude Code
+        - Cursor
+        - Windsurf
+        - Copilot CLI / GitHub Copilot
+        - Kilo Code
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: platform
+    attributes:
+      label: Operating System
+      options:
+        - macOS
+        - Windows
+        - Linux
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Copy and paste any relevant log output
+      render: shell
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Confirm
+      options:
+        - label: I've searched for existing issues
+          required: true
+        - label: I'm using the latest version
+          required: false

.github/ISSUE_TEMPLATE/documentation.yaml

@@ -0,0 +1,55 @@
+name: Documentation
+description: Report issues or suggest improvements to documentation
+title: "[DOCS] "
+labels: documentation
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Help us improve the BMad Method documentation!
+
+  - type: dropdown
+    id: doc-type
+    attributes:
+      label: What type of documentation issue is this?
+      options:
+        - Error or inaccuracy
+        - Missing information
+        - Unclear or confusing
+        - Outdated content
+        - Request for new documentation
+        - Typo or grammar
+    validations:
+      required: true
+
+  - type: textarea
+    id: location
+    attributes:
+      label: Documentation location
+      description: Where is the documentation that needs improvement?
+      placeholder: e.g., http://docs.bmad-method.org/tutorials/getting-started/ or "In the README"
+    validations:
+      required: true
+
+  - type: textarea
+    id: issue
+    attributes:
+      label: What's the issue?
+      description: Describe the documentation issue in detail
+      placeholder: e.g., Step 3 says to run command X but it should be command Y
+    validations:
+      required: true
+
+  - type: textarea
+    id: suggestion
+    attributes:
+      label: Suggested improvement
+      description: How would you like to see this improved?
+      placeholder: e.g., Change the command to X and add an example
+
+  - type: input
+    id: version
+    attributes:
+      label: BMad Version (if applicable)
+      placeholder: e.g., 6.0.0-Beta.4

.gitignore

@@ -50,7 +50,7 @@ _bmad-output
 .qwen
 .rovodev
 .kilocodemodes
-.claude
+.claude/commands
 .codex
 .github/chatmodes
 .github/agents

docs/bmgd/game-types.md

@@ -0,0 +1,374 @@
+---
+title: "Game Types Reference"
+---
+
+BMGD supports 24 game type templates. Each adds genre-specific sections to your GDD.
+
+## Game Types
+
+### Action & Combat
+
+#### Action Platformer
+
+Side-scrolling or 3D platforming with combat mechanics.
+
+**Examples:** Hollow Knight, Mega Man, Celeste
+
+**GDD sections:**
+
+- Movement systems (jumps, dashes, wall mechanics)
+- Combat mechanics (melee/ranged, combos)
+- Level design patterns
+- Boss design
+
+#### Shooter
+
+Projectile combat with aiming mechanics.
+
+**Examples:** Doom, Call of Duty, Splatoon
+
+**GDD sections:**
+
+- Weapon systems
+- Aiming and accuracy
+- Enemy AI patterns
+- Level/arena design
+- Multiplayer considerations
+
+#### Fighting
+
+1v1 combat with combos and frame data.
+
+**Examples:** Street Fighter, Tekken, Super Smash Bros.
+
+**GDD sections:**
+
+- Frame data systems
+- Combo mechanics
+- Character movesets
+- Competitive balance
+- Netcode requirements
+
+### Strategy & Tactics
+
+#### Strategy
+
+Resource management with tactical decisions.
+
+**Examples:** StarCraft, Civilization, Europa Universalis
+
+**GDD sections:**
+
+- Resource systems
+- Unit/building design
+- AI opponent behavior
+- Map/scenario design
+- Victory conditions
+
+#### Turn-Based Tactics
+
+Grid-based movement with turn order.
+
+**Examples:** XCOM, Fire Emblem, Into the Breach
+
+**GDD sections:**
+
+- Grid and movement systems
+- Turn order mechanics
+- Cover and positioning
+- Unit progression
+- Procedural mission generation
+
+#### Tower Defense
+
+Wave-based defense with tower placement.
+
+**Examples:** Bloons TD, Kingdom Rush, Plants vs. Zombies
+
+**GDD sections:**
+
+- Tower types and upgrades
+- Wave design and pacing
+- Economy systems
+- Map design patterns
+- Meta-progression
+
+### RPG & Progression
+
+#### RPG
+
+Character progression with stats, inventory, and quests.
+
+**Examples:** Final Fantasy, The Witcher, Baldur's Gate
+
+**GDD sections:**
+
+- Character stats and leveling
+- Inventory and equipment
+- Quest system design
+- Combat system (action/turn-based)
+- Skill trees and builds
+
+#### Roguelike
+
+Procedural generation with permadeath and run-based progression.
+
+**Examples:** Hades, Dead Cells, Spelunky
+
+**GDD sections:**
+
+- Procedural generation rules
+- Permadeath and persistence
+- Run structure and pacing
+- Item/ability synergies
+- Meta-progression systems
+
+#### Metroidvania
+
+Interconnected world with ability gating.
+
+**Examples:** Metroid, Castlevania: Symphony of the Night, Ori
+
+**GDD sections:**
+
+- World map connectivity
+- Ability gating design
+- Backtracking flow
+- Secret and collectible placement
+- Power-up progression
+
+### Narrative & Story
+
+#### Adventure
+
+Story-driven exploration with puzzle elements.
+
+**Examples:** Monkey Island, Myst, Life is Strange
+
+**GDD sections:**
+
+- Puzzle design
+- Narrative delivery
+- Exploration mechanics
+- Dialogue systems
+- Story branching
+
+#### Visual Novel
+
+Narrative choices with branching story.
+
+**Examples:** Doki Doki Literature Club, Phoenix Wright, Steins;Gate
+
+**GDD sections:**
+
+- Branching narrative structure
+- Choice and consequence
+- Character routes
+- UI/presentation
+- Save/load states
+
+#### Text-Based
+
+Text input/output games with parser or choice mechanics.
+
+**Examples:** Zork, 80 Days, Dwarf Fortress (adventure mode)
+
+**GDD sections:**
+
+- Parser or choice systems
+- World model
+- Narrative structure
+- Text presentation
+- Save state management
+
+### Simulation & Management
+
+#### Simulation
+
+Realistic systems with management and building.
+
+**Examples:** SimCity, RollerCoaster Tycoon, The Sims
+
+**GDD sections:**
+
+- Core simulation loops
+- Economy modeling
+- AI agents/citizens
+- Building/construction
+- Failure states
+
+#### Sandbox
+
+Creative freedom with building and minimal objectives.
+
+**Examples:** Minecraft, Terraria, Garry's Mod
+
+**GDD sections:**
+
+- Creation tools
+- Physics/interaction systems
+- Persistence and saving
+- Sharing/community features
+- Optional objectives
+
+### Sports & Racing
+
+#### Racing
+
+Vehicle control with tracks and lap times.
+
+**Examples:** Mario Kart, Forza, Need for Speed
+
+**GDD sections:**
+
+- Vehicle physics model
+- Track design
+- AI opponents
+- Progression/career mode
+- Multiplayer racing
+
+#### Sports
+
+Team-based or individual sports simulation.
+
+**Examples:** FIFA, NBA 2K, Tony Hawk's Pro Skater
+
+**GDD sections:**
+
+- Sport-specific rules
+- Player/team management
+- AI opponent behavior
+- Season/career modes
+- Multiplayer modes
+
+### Multiplayer
+
+#### MOBA
+
+Multiplayer team battles with hero selection.
+
+**Examples:** League of Legends, Dota 2, Smite
+
+**GDD sections:**
+
+- Hero/champion design
+- Lane and map design
+- Team composition
+- Matchmaking
+- Economy (gold/items)
+
+#### Party Game
+
+Local multiplayer with minigames.
+
+**Examples:** Mario Party, Jackbox, Overcooked
+
+**GDD sections:**
+
+- Minigame design patterns
+- Controller support
+- Round/game structure
+- Scoring systems
+- Player count flexibility
+
+### Horror & Survival
+
+#### Survival
+
+Resource gathering with crafting and persistent threats.
+
+**Examples:** Don't Starve, Subnautica, The Forest
+
+**GDD sections:**
+
+- Resource gathering
+- Crafting systems
+- Hunger/health/needs
+- Threat systems
+- Base building
+
+#### Horror
+
+Atmosphere and tension with limited resources.
+
+**Examples:** Resident Evil, Silent Hill, Amnesia
+
+**GDD sections:**
+
+- Fear mechanics
+- Resource scarcity
+- Sound design
+- Lighting and visibility
+- Enemy/threat design
+
+### Casual & Progression
+
+#### Puzzle
+
+Logic-based challenges and problem-solving.
+
+**Examples:** Tetris, Portal, The Witness
+
+**GDD sections:**
+
+- Puzzle mechanics
+- Difficulty progression
+- Hint systems
+- Level structure
+- Scoring/rating
+
+#### Idle/Incremental
+
+Passive progression with upgrades and automation.
+
+**Examples:** Cookie Clicker, Adventure Capitalist, Clicker Heroes
+
+**GDD sections:**
+
+- Core loop design
+- Prestige systems
+- Automation unlocks
+- Number scaling
+- Offline progress
+
+#### Card Game
+
+Deck building with card mechanics.
+
+**Examples:** Slay the Spire, Hearthstone, Magic: The Gathering Arena
+
+**GDD sections:**
+
+- Card design framework
+- Deck building rules
+- Mana/resource systems
+- Rarity and collection
+- Competitive balance
+
+### Rhythm
+
+#### Rhythm
+
+Music synchronization with timing-based gameplay.
+
+**Examples:** Guitar Hero, Beat Saber, Crypt of the NecroDancer
+
+**GDD sections:**
+
+- Note/beat mapping
+- Scoring systems
+- Difficulty levels
+- Music licensing
+- Input methods
+
+## Hybrid Types
+
+Multiple game types can be combined. GDD sections from all selected types are included.
+
+| Hybrid | Components | Combined Sections |
+|--------|------------|-------------------|
+| Action RPG | Action Platformer + RPG | Movement, combat, stats, inventory |
+| Survival Horror | Survival + Horror | Resources, crafting, atmosphere, fear |
+| Roguelike Deckbuilder | Roguelike + Card Game | Run structure, procedural gen, cards |
+| Tactical RPG | Turn-Based Tactics + RPG | Grid movement, stats, progression |
+| Open World Survival | Sandbox + Survival | Building, crafting, exploration |

docs/bmgd/index.md

@@ -0,0 +1,113 @@
+---
+title: "BMGD Quick Guide"
+description: Quick reference for BMad Game Dev Studio
+---
+
+![BMGD Logo](bmgd-logo.png)
+
+# BMGD Quick Guide
+
+BMad Game Dev Studio (BMGD) extends BMM with game-specific capabilities. Developed by game industry veterans, it guides you through product research, technical design, narrative design, and a full epic-driven production cycle.
+
+## Under Construction
+
+Documentation is under heavy construction catching up with the new beta release. We'll have complete documentation up as soon as possible. For now, please ask in the BMGD section of the Discord if you have any questions.
+
+![BMGD Workflow](workflow.jpg)
+
+## Quick Start
+
+**Install → Game Brief → GDD → (Narrative) → Architecture → Build**
+
+BMGD is an optional module installed via BMAD Method: `npx bmad-method install`
+
+See [How-To Reference](#how-to-reference) for commands.
+
+## Development Phases
+
+| Phase | Name | Key Activities |
+|-------|------|----------------|
+| 1 | **Preproduction** | Brainstorm Game, Game Brief, market research |
+| 2 | **Design** | GDD creation, Narrative Design (for story-driven games) |
+| 3 | **Technical** | Game Architecture (engine, systems, patterns) |
+| 4 | **Production** | Sprint planning, story development, code review, testing |
+
+## BMGD Agents
+
+| Agent | Purpose |
+|-------|---------|
+| Game Designer | Game mechanics, balance, player psychology |
+| Game Developer | Implementation with engine-specific patterns |
+| Game Architect | Engine selection, systems design, technical structure |
+| Game Scrum Master | Sprint planning and epic management |
+| Game QA | Playtesting, engine-specific testing, performance profiling |
+| Game Solo Dev | Full-stack game development for solo projects |
+
+## Key Documents
+
+| Document | Purpose |
+|----------|---------|
+| **Game Brief** | Vision, market positioning, fundamentals |
+| **GDD** | Core loop, mechanics, progression, art/audio direction |
+| **Narrative Design** | Story structure, characters, world-building, dialogue |
+| **Architecture** | Engine, systems, patterns, project structure |
+
+## Game Type Templates
+
+BMGD includes 24 game type templates that auto-configure GDD sections:
+
+Action, Adventure, Puzzle, RPG, Strategy, Simulation, Sports, Racing, Fighting, Horror, Platformer, Shooter, and more.
+
+Each template provides genre-specific GDD sections, mechanics patterns, testing considerations, and common pitfalls to avoid.
+
+## Explanation: BMGD vs BMM
+
+### When to Use Each
+
+| Use BMGD for | Use BMM for |
+|--------------|-------------|
+| Video games | Web applications |
+| Interactive experiences | APIs and services |
+| Game prototyping | Mobile apps (non-game) |
+| Game jams | General software projects |
+
+### Phase Mapping
+
+| BMM Phase | BMGD Phase | Key Difference |
+|-----------|------------|----------------|
+| Analysis | Preproduction | Game concepts, Game Brief instead of Product Brief |
+| Planning | Design | GDD instead of PRD; optional Narrative Design |
+| Solutioning | Technical | Focus on engine selection, game-specific patterns |
+| Implementation | Production | Game QA replaces TEA; engine-specific testing |
+
+### Document Differences
+
+| BMM | BMGD | Notes |
+|-----|------|-------|
+| Product Brief | Game Brief | Captures vision, market, fundamentals |
+| PRD | GDD | Includes mechanics, balance, player experience |
+| N/A | Narrative Design | Story, characters, world (story-driven games) |
+| Architecture | Architecture | BMGD version includes engine-specific patterns and considerations |
+
+### Testing Differences
+
+**BMM (TEA):** Web-focused testing with Playwright, Cypress, API testing, E2E for web apps.
+
+**BMGD (Game QA):** Engine-specific frameworks (Unity, Unreal, Godot), gameplay testing, performance profiling, playtest planning, balance validation.
+
+## How-To Reference
+
+| I need to... | Action                                                                                                 |
+|--------------|--------------------------------------------------------------------------------------------------------|
+| Install BMGD | Run `npx bmad-method install` and select BMGD during module installation                               |
+| Start a new game | Run `/bmad-gds-brainstorm-game`, then `/bmad:gds:create-game-brief`                                    |
+| Design my game | Run `/bmad-gds-create-gdd`; add `/bmad:gds:narrative` if story-heavy                                   |
+| Plan architecture | Run `/bmad-gds-game-architecture` with Game Architect                                                  |
+| Build my game | Use Phase 4 production workflows - Run `/bmad-help` to see what's next                       |
+| Test an idea quickly | Use [Quick-Flow](quick-flow-workflows.md) for rapid prototyping |
+
+## Further Reading
+
+- [Game Types Guide](game-types.md)
+- [Quick-Flow Guide](quick-flow-workflows.md)
+

docs/bmgd/quick-flow-workflows.md

@@ -0,0 +1,160 @@
+---
+title: "Quick Flow Workflows"
+---
+
+How to create tech specs and execute implementations with Quick Flow.
+
+## Choosing a Workflow
+
+| Situation | Workflow | Command |
+|-----------|----------|---------|
+| Need to document before implementing | Quick-Spec | `/bmad-gds-quick-spec` |
+| Multiple approaches to evaluate | Quick-Spec | `/bmad-gds-quick-spec` |
+| Have a completed tech-spec | Quick-Dev | `/bmad-gds-quick-dev path/to/spec.md` |
+| Have clear, direct instructions | Quick-Dev | `/bmad-gds-quick-dev` |
+| Building complete game system | Full GDS | `/bmad-gds-workflow-init` |
+| Epic-level features | Full GDS | `/bmad-gds-workflow-init` |
+
+---
+
+## How to Create a Tech Spec (Quick-Spec)
+
+### Step 1: Start the workflow
+
+```bash
+/bmad-gds-quick-spec
+```
+
+### Step 2: Describe your requirement
+
+Provide your feature request. The agent scans the codebase and asks clarifying questions.
+
+**Checkpoint options:**
+- `[a]` Advanced Elicitation - explore requirements deeper
+- `[c]` Continue to investigation
+- `[p]` Party Mode - consult expert agents
+
+### Step 3: Review investigation findings
+
+The agent analyzes the codebase for patterns, constraints, and similar implementations. Review the findings.
+
+**Checkpoint options:**
+- `[c]` Continue to spec generation
+- `[p]` Party Mode - get technical review
+
+### Step 4: Review generated spec
+
+The agent creates an ordered task list with file paths and acceptance criteria. Verify completeness.
+
+**Checkpoint options:**
+- `[c]` Continue to final review
+- `[p]` Party Mode - technical review
+
+### Step 5: Finalize
+
+Confirm the spec meets these standards:
+- Every task has a file path and specific action
+- Tasks ordered by dependency
+- Acceptance criteria in Given/When/Then format
+- No placeholders or TBD sections
+
+**Options:**
+- `[d]` Start Quick-Dev immediately
+- `[done]` Save spec and exit
+
+**Output:** `{planning_artifacts}/tech-spec-{slug}.md`
+
+---
+
+## How to Execute Implementation (Quick-Dev)
+
+### With a Tech-Spec
+
+```bash
+/bmad-gds-quick-dev path/to/tech-spec-feature.md
+```
+
+The agent:
+1. Captures baseline git commit
+2. Loads and validates the spec
+3. Executes tasks in order
+4. Runs self-check
+5. Performs adversarial review
+6. Resolves findings
+7. Validates against acceptance criteria
+
+### With Direct Instructions
+
+```bash
+/bmad-gds-quick-dev
+```
+
+Then describe what you want implemented:
+1. Captures baseline git commit
+2. Evaluates complexity (may suggest planning)
+3. Gathers context from codebase
+4. Executes implementation
+5. Runs self-check and adversarial review
+6. Resolves findings
+
+**Escalation:** If the agent detects complexity (multiple components, system-level scope, uncertainty), it offers:
+- `[t]` Create tech-spec first
+- `[w]` Use full GDS workflow
+- `[e]` Execute anyway
+
+---
+
+## Troubleshooting
+
+### Spec has placeholders or TBD sections
+
+Return to investigation step. Complete missing research, inline all findings, re-run review.
+
+### Workflow lost context mid-step
+
+Check frontmatter for `stepsCompleted`. Resume from last completed step.
+
+### Agent suggested planning but you want to execute
+
+You can override with `[e]`, but document your assumptions. Escalation heuristics exist because planning saves time on complex tasks.
+
+### Tests failing after implementation
+
+Return to the resolve-findings step. Review failures, fix issues, ensure test expectations are correct, re-run full suite.
+
+### Need help
+
+```bash
+/bmad-help
+```
+
+---
+
+## Reference
+
+### File Locations
+
+| File | Location |
+|------|----------|
+| Work in progress | `{implementation_artifacts}/tech-spec-wip.md` |
+| Completed specs | `{planning_artifacts}/tech-spec-{slug}.md` |
+| Archived specs | `{implementation_artifacts}/tech-spec-{slug}-archived-{date}.md` |
+| Workflow files | `_bmad/gds/workflows/gds-quick-flow/` |
+
+### Validation Criteria
+
+**Self-check (before adversarial review):**
+- All tasks/instructions completed
+- Tests written and passing
+- Follows existing patterns
+- No obvious bugs
+- Acceptance criteria met
+- Code is readable
+
+**Adversarial review:**
+- Correctness
+- Security
+- Performance
+- Maintainability
+- Test coverage
+- Error handling

docs/tutorials/getting-started.md

@@ -65,7 +65,11 @@ The installer creates two folders:
 - `_bmad/` — agents, workflows, tasks, and configuration
 - `_bmad-output/` — empty for now, but this is where your artifacts will be saved
 
-Open your AI IDE in the project folder. Run the `help` workflow (`/bmad-help` on most platforms) to see what to do next — it detects what you've completed and recommends the next step.
+Open your AI IDE in the project folder. Run the `help` workflow (`/bmad-help`) to see what to do next — it detects what you've completed and recommends the next step.
+
+:::note[How to Load Agents and Run Workflows]
+Each workflow has a **slash command** you run in your IDE (e.g., `/bmad-bmm-create-prd`). Running a workflow command automatically loads the appropriate agent — you don't need to load agents separately. You can also load an agent directly for general conversation (e.g., `/bmad-agent-bmm-pm` for the PM agent).
+:::
 
 :::caution[Fresh Chats]
 Always start a fresh chat for each workflow. This prevents context limitations from causing issues.
@@ -78,29 +82,29 @@ Work through phases 1-3. **Use fresh chats for each workflow.**
 ### Phase 1: Analysis (Optional)
 
 All workflows in this phase are optional:
-- **brainstorming** — Guided ideation
+- **brainstorming** (`/bmad-brainstorming`) — Guided ideation
-- **research** — Market and technical research
+- **research** (`/bmad-bmm-research`) — Market and technical research
-- **create-product-brief** — Recommended foundation document
+- **create-product-brief** (`/bmad-bmm-create-product-brief`) — Recommended foundation document
 
 ### Phase 2: Planning (Required)
 
 **For BMad Method and Enterprise tracks:**
-1. Load the **PM agent** in a new chat
+1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat
-2. Run the `prd` workflow
+2. Run the `prd` workflow (`/bmad-bmm-create-prd`)
 3. Output: `PRD.md`
 
 **For Quick Flow track:**
-- Use the `quick-spec` workflow instead of PRD, then skip to implementation
+- Use the `quick-spec` workflow (`/bmad-bmm-quick-spec`) instead of PRD, then skip to implementation
 
 :::note[UX Design (Optional)]
-If your project has a user interface, load the **UX-Designer agent** and run the UX design workflow after creating your PRD.
+If your project has a user interface, load the **UX-Designer agent** (`/bmad-agent-bmm-ux-designer`) and run the UX design workflow (`/bmad-bmm-create-ux-design`) after creating your PRD.
 :::
 
 ### Phase 3: Solutioning (BMad Method/Enterprise)
 
 **Create Architecture**
-1. Load the **Architect agent** in a new chat
+1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat
-2. Run `create-architecture`
+2. Run `create-architecture` (`/bmad-bmm-create-architecture`)
 3. Output: Architecture document with technical decisions
 
 **Create Epics and Stories**
@@ -109,13 +113,13 @@ If your project has a user interface, load the **UX-Designer agent** and run the
 Epics and stories are now created *after* architecture. This produces better quality stories because architecture decisions (database, API patterns, tech stack) directly affect how work should be broken down.
 :::
 
-1. Load the **PM agent** in a new chat
+1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat
-2. Run `create-epics-and-stories`
+2. Run `create-epics-and-stories` (`/bmad-bmm-create-epics-and-stories`)
 3. The workflow uses both PRD and Architecture to create technically-informed stories
 
 **Implementation Readiness Check** *(Highly Recommended)*
-1. Load the **Architect agent** in a new chat
+1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat
-2. Run `check-implementation-readiness`
+2. Run `check-implementation-readiness` (`/bmad-bmm-check-implementation-readiness`)
 3. Validates cohesion across all planning documents
 
 ## Step 2: Build Your Project
@@ -124,19 +128,19 @@ Once planning is complete, move to implementation. **Each workflow should run in
 
 ### Initialize Sprint Planning
 
-Load the **SM agent** and run `sprint-planning`. This creates `sprint-status.yaml` to track all epics and stories.
+Load the **SM agent** (`/bmad-agent-bmm-sm`) and run `sprint-planning` (`/bmad-bmm-sprint-planning`). This creates `sprint-status.yaml` to track all epics and stories.
 
 ### The Build Cycle
 
 For each story, repeat this cycle with fresh chats:
 
-| Step | Agent | Workflow       | Purpose                            |
+| Step | Agent | Workflow       | Command                    | Purpose                            |
-| ---- | ----- | -------------- | ---------------------------------- |
+| ---- | ----- | -------------- | -------------------------- | ---------------------------------- |
-| 1    | SM    | `create-story` | Create story file from epic        |
+| 1    | SM    | `create-story` | `/bmad-bmm-create-story`  | Create story file from epic        |
-| 2    | DEV   | `dev-story`    | Implement the story                |
+| 2    | DEV   | `dev-story`    | `/bmad-bmm-dev-story`     | Implement the story                |
-| 3    | DEV   | `code-review`  | Quality validation *(recommended)* |
+| 3    | DEV   | `code-review`  | `/bmad-bmm-code-review`   | Quality validation *(recommended)* |
 
-After completing all stories in an epic, load the **SM agent** and run `retrospective`.
+After completing all stories in an epic, load the **SM agent** (`/bmad-agent-bmm-sm`) and run `retrospective` (`/bmad-bmm-retrospective`).
 
 ## What You've Accomplished
 
@@ -162,17 +166,17 @@ your-project/
 
 ## Quick Reference
 
-| Workflow                         | Agent     | Purpose                              |
+| Workflow                         | Command                                    | Agent     | Purpose                              |
-| -------------------------------- | --------- | ------------------------------------ |
+| -------------------------------- | ------------------------------------------ | --------- | ------------------------------------ |
-| `help`                           | Any       | Get guidance on what to do next      |
+| `help`                           | `/bmad-help`                               | Any       | Get guidance on what to do next      |
-| `prd`                            | PM        | Create Product Requirements Document |
+| `prd`                            | `/bmad-bmm-create-prd`                     | PM        | Create Product Requirements Document |
-| `create-architecture`            | Architect | Create architecture document         |
+| `create-architecture`            | `/bmad-bmm-create-architecture`            | Architect | Create architecture document         |
-| `create-epics-and-stories`       | PM        | Break down PRD into epics            |
+| `create-epics-and-stories`       | `/bmad-bmm-create-epics-and-stories`       | PM        | Break down PRD into epics            |
-| `check-implementation-readiness` | Architect | Validate planning cohesion           |
+| `check-implementation-readiness` | `/bmad-bmm-check-implementation-readiness` | Architect | Validate planning cohesion           |
-| `sprint-planning`                | SM        | Initialize sprint tracking           |
+| `sprint-planning`                | `/bmad-bmm-sprint-planning`                | SM        | Initialize sprint tracking           |
-| `create-story`                   | SM        | Create a story file                  |
+| `create-story`                   | `/bmad-bmm-create-story`                   | SM        | Create a story file                  |
-| `dev-story`                      | DEV       | Implement a story                    |
+| `dev-story`                      | `/bmad-bmm-dev-story`                      | DEV       | Implement a story                    |
-| `code-review`                    | DEV       | Review implemented code              |
+| `code-review`                    | `/bmad-bmm-code-review`                    | DEV       | Review implemented code              |
 
 ## Common Questions
 
@@ -180,10 +184,10 @@ your-project/
 Only for BMad Method and Enterprise tracks. Quick Flow skips from tech-spec to implementation.
 
 **Can I change my plan later?**
-Yes. The SM agent has a `correct-course` workflow for handling scope changes.
+Yes. The SM agent has a `correct-course` workflow (`/bmad-bmm-correct-course`) for handling scope changes.
 
 **What if I want to brainstorm first?**
-Load the Analyst agent and run `brainstorming` before starting your PRD.
+Load the Analyst agent (`/bmad-agent-bmm-analyst`) and run `brainstorming` (`/bmad-brainstorming`) before starting your PRD.
 
 **Do I need to follow a strict order?**
 Not strictly. Once you learn the flow, you can run workflows directly using the Quick Reference above.
@@ -192,14 +196,14 @@ Not strictly. Once you learn the flow, you can run workflows directly using the
 
 - **During workflows** — Agents guide you with questions and explanations
 - **Community** — [Discord](https://discord.gg/gk8jAdXWmj) (#bmad-method-help, #report-bugs-and-issues)
-- **Stuck?** — Run `help` to see what to do next
+- **Stuck?** — Run `help` (`/bmad-help`) to see what to do next
 
 ## Key Takeaways
 
 :::tip[Remember These]
 - **Always use fresh chats** — Start a new chat for each workflow
 - **Track matters** — Quick Flow uses quick-spec; Method/Enterprise need PRD and architecture
-- **Use `help` when stuck** — It detects your progress and suggests next steps
+- **Use `help` (`/bmad-help`) when stuck** — It detects your progress and suggests next steps
 :::
 
 Ready to start? Install BMad and let the agents guide you through your first project.

src/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -18,9 +18,9 @@ agent:
       - Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't.
 
   menu:
-    - trigger: TS or fuzzy match on tech-spec
+    - trigger: QS or fuzzy match on quick-spec
       exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md"
-      description: "[TS] Tech Spec: Architect a quick but complete technical spec with implementation-ready stories/specs"
+      description: "[QS] Quick Spec: Architect a quick but complete technical spec with implementation-ready stories/specs"
 
     - trigger: QD or fuzzy match on quick-dev
       workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md"

src/bmm/agents/quinn.agent.yaml

@@ -27,7 +27,7 @@ agent:
     - Focus on realistic user scenarios
 
   menu:
-    - trigger: QA
+    - trigger: qa
       workflow: "{project-root}/_bmad/bmm/workflows/qa/automate/workflow.yaml"
       description: "[QA] Automate - Generate tests for existing features (simplified)"
 

src/bmm/agents/tech-writer/tech-writer.agent.yaml

@@ -7,7 +7,7 @@ agent:
     title: Technical Writer
     icon: 📚
     module: bmm
-    hasSidecar: false
+    hasSidecar: true
 
   persona:
     role: Technical Documentation Specialist + Knowledge Curator
@@ -28,9 +28,9 @@ agent:
       action: "Engage in multi-turn conversation until you fully understand the ask, use subprocess if available for any web search, research or document review required to extract and return only relevant info to parent context. Author final document following all `_bmad/_memory/tech-writer-sidecar/documentation-standards.md`. After draft, use a subprocess to review and revise for quality of content and ensure standards are still met."
       description: "[WD] Write Document: Describe in detail what you want, and the agent will follow the documentation best practices defined in agent memory."
 
-    - trigger: WD or fuzzy match on write-document
+    - trigger: US or fuzzy match on update-standards
       action: "Update `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` adding user preferences to User Specified CRITICAL Rules section. Remove any contradictory rules as needed. Share with user the updates made."
-      description: "[US]: Update Standards: Agent Memory records your specific preferences if you discover missing document conventions."
+      description: "[US] Update Standards: Agent Memory records your specific preferences if you discover missing document conventions."
 
     - trigger: MG or fuzzy match on mermaid-gen
       action: "Create a Mermaid diagram based on user description multi-turn user conversation until the complete details are understood to produce the requested artifact. If not specified, suggest diagram types based on ask. Strictly follow Mermaid syntax and CommonMark fenced code block standards."

src/bmm/module-help.csv

@@ -1,23 +1,28 @@
 module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
-bmm,anytime,Document Project,DP,10,_bmad/bmm/workflows/document-project/workflow.yaml,bmad-bmm-document-project,false,analyst,Create Mode,"Analyze an existing project to produce useful documentation",project-knowledge,*,
+bmm,anytime,Document Project,DP,,_bmad/bmm/workflows/document-project/workflow.yaml,bmad-bmm-document-project,false,analyst,Create Mode,"Analyze an existing project to produce useful documentation",project-knowledge,*,
-bmm,anytime,Generate Project Context,GPC,15,_bmad/bmm/workflows/generate-project-context/workflow.md,bmad-bmm-generate-project-context,false,analyst,Create Mode,"Scan existing codebase to generate a lean LLM-optimized project-context.md containing critical implementation rules patterns and conventions for AI agents. Essential for brownfield projects and quick-flow.",output_folder,"project context",
+bmm,anytime,Generate Project Context,GPC,,_bmad/bmm/workflows/generate-project-context/workflow.md,bmad-bmm-generate-project-context,false,analyst,Create Mode,"Scan existing codebase to generate a lean LLM-optimized project-context.md containing critical implementation rules patterns and conventions for AI agents. Essential for brownfield projects and quick-flow.",output_folder,"project context",
-bmm,anytime,Quick Spec,TS,20,_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md,bmad-bmm-quick-spec,false,quick-flow-solo-dev,Create Mode,"Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method. Quick one-off tasks small changes simple apps utilities without extensive planning",planning_artifacts,"tech spec",
+bmm,anytime,Quick Spec,QS,,_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md,bmad-bmm-quick-spec,false,quick-flow-solo-dev,Create Mode,"Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method. Quick one-off tasks small changes simple apps brownfield additions to well established patterns utilities without extensive planning",planning_artifacts,"tech spec",
-bmm,anytime,Quick Dev,QD,30,_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md,bmad-bmm-quick-dev,false,quick-flow-solo-dev,Create Mode,"Quick one-off tasks small changes simple apps utilities without extensive planning - Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method, unless the user is already working through the implementation phase and just requests a 1 off things not already in the plan",,,
+bmm,anytime,Quick Dev,QD,,_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md,bmad-bmm-quick-dev,false,quick-flow-solo-dev,Create Mode,"Quick one-off tasks small changes simple apps utilities without extensive planning - Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method, unless the user is already working through the implementation phase and just requests a 1 off things not already in the plan",,,
-bmm,anytime,Correct Course,CC,40,_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml,bmad-bmm-correct-course,false,sm,Create Mode,"Anytime: Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories",planning_artifacts,"change proposal",
+bmm,anytime,Correct Course,CC,,_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml,bmad-bmm-correct-course,false,sm,Create Mode,"Anytime: Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories",planning_artifacts,"change proposal",
+bmm,anytime,Create Dataflow,CDF,,_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml,bmad-bmm-create-excalidraw-dataflow,false,ux-designer,Create Mode,"Create data flow diagrams (DFD) in Excalidraw format - can be called standalone or during any workflow to add visual documentation",planning_artifacts,"dataflow diagram",
+bmm,anytime,Create Diagram,CED,,_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml,bmad-bmm-create-excalidraw-diagram,false,ux-designer,Create Mode,"Create system architecture diagrams ERDs UML diagrams or general technical diagrams in Excalidraw format - use anytime or call from architecture workflow to add visual documentation",planning_artifacts,"diagram",
+bmm,anytime,Create Flowchart,CFC,,_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml,bmad-bmm-create-excalidraw-flowchart,false,ux-designer,Create Mode,"Create a flowchart visualization in Excalidraw format for processes pipelines or logic flows - use anytime or during architecture to add process documentation",planning_artifacts,"flowchart",
+bmm,anytime,Create Wireframe,CEW,,_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml,bmad-bmm-create-excalidraw-wireframe,false,ux-designer,Create Mode,"Create website or app wireframes in Excalidraw format - use anytime standalone or call from UX workflow to add UI mockups",planning_artifacts,"wireframe",
+bmm,anytime,Write Document,WD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,bmad-bmm-write-document,false,tech-writer,,"Describe in detail what you want, and the agent will follow the documentation best practices defined in agent memory. Multi-turn conversation with subprocess for research/review.",project-knowledge,"document",
+bmm,anytime,Update Standards,US,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,bmad-bmm-update-standards,false,tech-writer,,"Update agent memory documentation-standards.md with your specific preferences if you discover missing document conventions.",_bmad/_memory/tech-writer-sidecar,"standards",
+bmm,anytime,Mermaid Generate,MG,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,bmad-bmm-mermaid-generate,false,tech-writer,,"Create a Mermaid diagram based on user description. Will suggest diagram types if not specified.",planning_artifacts,"mermaid diagram",
+bmm,anytime,Validate Document,VD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,bmad-bmm-validate-document,false,tech-writer,,"Review the specified document against documentation standards and best practices. Returns specific actionable improvement suggestions organized by priority.",planning_artifacts,"validation report",
+bmm,anytime,Explain Concept,EC,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,bmad-bmm-explain-concept,false,tech-writer,,"Create clear technical explanations with examples and diagrams for complex concepts. Breaks down into digestible sections using task-oriented approach.",project_knowledge,"explanation",
 bmm,1-analysis,Brainstorm Project,BP,10,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,data=_bmad/bmm/data/project-context-template.md,"Expert Guided Facilitation through a single or multiple techniques",planning_artifacts,"brainstorming session",
-bmm,1-analysis,Market Research,MR,20,_bmad/bmm/workflows/1-analysis/research/workflow.md,bmad-bmm-research,false,analyst,Create Mode research_type=market,"Market analysis competitive landscape customer needs and trends","planning_artifacts|project-knowledge","research documents"
+bmm,1-analysis,Market Research,MR,20,_bmad/bmm/workflows/1-analysis/research/workflow.md,bmad-bmm-research,false,analyst,Create Mode research_type=market,"Market analysis competitive landscape customer needs and trends","planning_artifacts|project-knowledge","research documents",
-bmm,1-analysis,Domain Research,DR,21,_bmad/bmm/workflows/1-analysis/research/workflow.md,bmad-bmm-research,false,analyst,Create Mode research_type=domain,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project-knowledge","research documents"
+bmm,1-analysis,Domain Research,DR,21,_bmad/bmm/workflows/1-analysis/research/workflow.md,bmad-bmm-research,false,analyst,Create Mode research_type=domain,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project_knowledge","research documents",
-bmm,1-analysis,Technical Research,TR,22,_bmad/bmm/workflows/1-analysis/research/workflow.md,bmad-bmm-research,false,analyst,Create Mode research_type=technical,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project-knowledge","research documents"
+bmm,1-analysis,Technical Research,TR,22,_bmad/bmm/workflows/1-analysis/research/workflow.md,bmad-bmm-research,false,analyst,Create Mode research_type=technical,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project_knowledge","research documents",
 bmm,1-analysis,Create Brief,CB,30,_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md,bmad-bmm-create-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
 bmm,1-analysis,Validate Brief,VB,40,_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md,bmad-bmm-validate-brief,false,analyst,Validate Mode,"Validates product brief completeness",planning_artifacts,"brief validation report",
-bmm,2-planning,Create PRD,CP,10,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md,bmad-bmm-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
+bmm,2-planning,Create PRD,CP,10,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
-bmm,2-planning,Validate PRD,VP,20,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md,bmad-bmm-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report",
+bmm,2-planning,Validate PRD,VP,20,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md,bmad-bmm-validate-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report",
 bmm,2-planning,Create UX,CU,30,_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md,bmad-bmm-create-ux-design,false,ux-designer,Create Mode,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project",planning_artifacts,"ux design",
 bmm,2-planning,Validate UX,VU,40,_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md,bmad-bmm-create-ux-design,false,ux-designer,Validate Mode,"Validates UX design deliverables",planning_artifacts,"ux validation report",
-,anytime,Create Dataflow,CDF,50,_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml,bmad-bmm-create-excalidraw-dataflow,false,ux-designer,Create Mode,"Create data flow diagrams (DFD) in Excalidraw format - can be called standalone or during any workflow to add visual documentation",planning_artifacts,"dataflow diagram",
-,anytime,Create Diagram,CED,51,_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml,bmad-bmm-create-excalidraw-diagram,false,ux-designer,Create Mode,"Create system architecture diagrams ERDs UML diagrams or general technical diagrams in Excalidraw format - use anytime or call from architecture workflow to add visual documentation",planning_artifacts,"diagram",
-,anytime,Create Flowchart,CFC,52,_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml,bmad-bmm-create-excalidraw-flowchart,false,ux-designer,Create Mode,"Create a flowchart visualization in Excalidraw format for processes pipelines or logic flows - use anytime or during architecture to add process documentation",planning_artifacts,"flowchart",
-,anytime,Create Wireframe,CEW,53,_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml,bmad-bmm-create-excalidraw-wireframe,false,ux-designer,Create Mode,"Create website or app wireframes in Excalidraw format - use anytime standalone or call from UX workflow to add UI mockups",planning_artifacts,"wireframe",
 bmm,3-solutioning,Create Architecture,CA,10,_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md,bmad-bmm-create-architecture,true,architect,Create Mode,"Guided Workflow to document technical decisions",planning_artifacts,architecture,
 bmm,3-solutioning,Validate Architecture,VA,20,_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md,bmad-bmm-create-architecture,false,architect,Validate Mode,"Validates architecture completeness",planning_artifacts,"architecture validation report",
 bmm,3-solutioning,Create Epics and Stories,CE,30,_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md,bmad-bmm-create-epics-and-stories,true,pm,Create Mode,"Create the Epics and Stories Listing",planning_artifacts,"epics and stories",
@@ -25,9 +30,9 @@ bmm,3-solutioning,Validate Epics and Stories,VE,40,_bmad/bmm/workflows/3-solutio
 bmm,3-solutioning,Check Implementation Readiness,IR,70,_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md,bmad-bmm-check-implementation-readiness,true,architect,Validate Mode,"Ensure PRD UX Architecture and Epics Stories are aligned",planning_artifacts,"readiness report",
 bmm,4-implementation,Sprint Planning,SP,10,_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml,bmad-bmm-sprint-planning,true,sm,Create Mode,"Generate sprint plan for development tasks - this kicks off the implementation phase by producing a plan the implementation agents will follow in sequence for every story in the plan.",implementation_artifacts,"sprint status",
 bmm,4-implementation,Sprint Status,SS,20,_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml,bmad-bmm-sprint-status,false,sm,Create Mode,"Anytime: Summarize sprint status and route to next workflow",,,
-bmm,4-implementation,Create Story,CS,30,_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml,bmad-bmm-create-story,true,sm,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story,
 bmm,4-implementation,Validate Story,VS,35,_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml,bmad-bmm-create-story,false,sm,Validate Mode,"Validates story readiness and completeness before development work begins",implementation_artifacts,"story validation report",
+bmm,4-implementation,Create Story,CS,30,_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml,bmad-bmm-create-story,true,sm,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story,
 bmm,4-implementation,Dev Story,DS,40,_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml,bmad-bmm-dev-story,true,dev,Create Mode,"Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed",,,
 bmm,4-implementation,Code Review,CR,50,_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml,bmad-bmm-code-review,false,dev,Create Mode,"Story cycle: If issues back to DS if approved then next CS or ER if epic complete",,,
+bmm,4-implementation,QA Automation Test,QA,45,_bmad/bmm/workflows/qa/automate/workflow.yaml,bmad-bmm-qa-automate,false,quinn,Create Mode,"Generate automated API and E2E tests for implemented code using the project's existing test framework (detects existing well known in use test frameworks). Use after implementation to add test coverage. NOT for code review or story validation - use CR for that.",implementation_artifacts,"test suite",
 bmm,4-implementation,Retrospective,ER,60,_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml,bmad-bmm-retrospective,false,sm,Create Mode,"Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC",implementation_artifacts,retrospective,
-bmm,4-implementation,Automate,QA,45,_bmad/bmm/workflows/qa/automate/workflow.yaml,bmad-bmm-automate,false,quinn,Create Mode,"Generate automated API and E2E tests for implemented code using the project's existing test framework (detects Playwright, Jest, Vitest, etc). Use after implementation to add test coverage. NOT for code review or story validation - use CR for that.",implementation_artifacts,"test suite",

src/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md

@@ -117,7 +117,8 @@ Try to discover the following:
 #### C. Present Initialization Results
 
 **Setup Report to User:**
-"Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}.
+<display>
+Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}.
 
 **Document Setup:**
 
@@ -133,11 +134,14 @@ Try to discover the following:
 
 **Files loaded:** {list of specific file names or "No additional documents found"}
 
-Do you have any other documents you'd like me to include, or shall we continue to the next step?"
+Do you have any other documents you'd like me to include, or shall we continue to the next step?
+</display>
 
 ### 4. Present MENU OPTIONS
 
-Display: "**Proceeding to product vision discovery...**"
+<display>
+**Proceeding to product vision discovery...**
+</display>
 
 #### Menu Handling Logic:
 

src/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md

@@ -75,7 +75,8 @@ Review the frontmatter to understand:
 ### 3. Present Current Progress
 
 **Progress Report to User:**
-"Welcome back {{user_name}}! I'm resuming our product brief collaboration for {{project_name}}.
+<display>
+Welcome back {{user_name}}! I'm resuming our product brief collaboration for {{project_name}}.
 
 **Current Progress:**
 
@@ -88,7 +89,8 @@ Review the frontmatter to understand:
 - Current product brief is ready with all completed sections
 - Ready to continue from where we left off
 
-Does this look right, or do you want to make any adjustments before we proceed?"
+Does this look right, or do you want to make any adjustments before we proceed?
+</display>
 
 ### 4. Determine Continuation Path
 
@@ -104,7 +106,8 @@ Based on `lastStep` value, determine which step to load next:
 ### 5. Handle Workflow Completion
 
 **If workflow already complete (`lastStep = 6`):**
-"Great news! It looks like we've already completed the product brief workflow for {{project_name}}.
+<display>
+Great news! It looks like we've already completed the product brief workflow for {{project_name}}.
 
 The final document is ready at `{outputFile}` with all sections completed through step 6.
 
@@ -114,14 +117,17 @@ Would you like me to:
 - Suggest next workflow steps (like PRD creation)
 - Start a new product brief revision
 
-What would be most helpful?"
+What would be most helpful?
+</display>
 
 ### 6. Present MENU OPTIONS
 
 **If workflow not complete:**
-Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
+<display>
+Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
 
-**Select an Option:** [C] Continue to Step {nextStepNumber}"
+**Select an Option:** [C] Continue to Step {nextStepNumber}
+</display>
 
 #### Menu Handling Logic:
 

src/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md

@@ -61,7 +61,8 @@ Conduct comprehensive product vision discovery to define the core problem, solut
 ### 1. Begin Vision Discovery
 
 **Opening Conversation:**
-"As your PM peer, I'm excited to help you shape the vision for {{project_name}}. Let's start with the foundation.
+<display>
+As your PM peer, I'm excited to help you shape the vision for {{project_name}}. Let's start with the foundation.
 
 **Tell me about the product you envision:**
 
@@ -70,7 +71,8 @@ Conduct comprehensive product vision discovery to define the core problem, solut
 - What would success look like for the people you're helping?
 - What excites you most about this solution?
 
-Let's start with the problem space before we get into solutions."
+Let's start with the problem space before we get into solutions.
+</display>
 
 ### 2. Deep Problem Understanding
 
@@ -147,12 +149,14 @@ Prepare the following structure for document append:
 ### 7. Present MENU OPTIONS
 
 **Content Presentation:**
-"I've drafted the executive summary and core vision based on our conversation. This captures the essence of {{project_name}} and what makes it special.
+<display>
+I've drafted the executive summary and core vision based on our conversation. This captures the essence of {{project_name}} and what makes it special.
 
 **Here's what I'll add to the document:**
 [Show the complete markdown content from step 6]
 
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+</display>
 
 #### Menu Handling Logic:
 

src/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md

@@ -61,7 +61,8 @@ Define target users with rich personas and map their key interactions with the p
 ### 1. Begin User Discovery
 
 **Opening Exploration:**
-"Now that we understand what {{project_name}} does, let's define who it's for.
+<display>
+Now that we understand what {{project_name}} does, let's define who it's for.
 
 **User Discovery:**
 
@@ -70,7 +71,8 @@ Define target users with rich personas and map their key interactions with the p
 - Who gets the most value from this solution?
 - Are there primary users and secondary users we should consider?
 
-Let's start by identifying the main user groups."
+Let's start by identifying the main user groups.
+</display>
 
 ### 2. Primary User Segment Development
 
@@ -150,12 +152,14 @@ Prepare the following structure for document append:
 ### 6. Present MENU OPTIONS
 
 **Content Presentation:**
-"I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
+<display>
+I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
 
 **Here's what I'll add to the document:**
 [Show the complete markdown content from step 5]
 
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+</display>
 
 #### Menu Handling Logic:
 

src/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md

@@ -61,7 +61,8 @@ Define comprehensive success metrics that include user success, business objecti
 ### 1. Begin Success Metrics Discovery
 
 **Opening Exploration:**
-"Now that we know who {{project_name}} serves and what problem it solves, let's define what success looks like.
+<display>
+Now that we know who {{project_name}} serves and what problem it solves, let's define what success looks like.
 
 **Success Discovery:**
 
@@ -69,7 +70,8 @@ Define comprehensive success metrics that include user success, business objecti
 - What would make users say 'this was worth it'?
 - What metrics show we're creating real value?
 
-Let's start with the user perspective."
+Let's start with the user perspective.
+</display>
 
 ### 2. User Success Metrics
 
@@ -153,12 +155,14 @@ Prepare the following structure for document append:
 ### 7. Present MENU OPTIONS
 
 **Content Presentation:**
-"I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
+<display>
+I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
 
 **Here's what I'll add to the document:**
 [Show the complete markdown content from step 6]
 
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+</display>
 
 #### Menu Handling Logic:
 

src/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md

@@ -61,7 +61,8 @@ Define MVP scope with clear boundaries and outline future vision through collabo
 ### 1. Begin Scope Definition
 
 **Opening Exploration:**
-"Now that we understand what {{project_name}} does, who it serves, and how we'll measure success, let's define what we need to build first.
+<display>
+Now that we understand what {{project_name}} does, who it serves, and how we'll measure success, let's define what we need to build first.
 
 **Scope Discovery:**
 
@@ -69,7 +70,8 @@ Define MVP scope with clear boundaries and outline future vision through collabo
 - What features would make users say 'this solves my problem'?
 - How do we balance ambition with getting something valuable to users quickly?
 
-Let's start with the MVP mindset: what's the smallest version that creates real value?"
+Let's start with the MVP mindset: what's the smallest version that creates real value?
+</display>
 
 ### 2. MVP Core Features Definition
 
@@ -167,12 +169,14 @@ Prepare the following structure for document append:
 ### 7. Present MENU OPTIONS
 
 **Content Presentation:**
-"I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
+<display>
+I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
 
 **Here's what I'll add to the document:**
 [Show the complete markdown content from step 6]
 
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+</display>
 
 #### Menu Handling Logic:
 

src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md

@@ -56,22 +56,24 @@ Complete the product brief workflow, update status files, and provide guidance o
 ### 1. Announce Workflow Completion
 
 **Completion Announcement:**
-"🎉 **Product Brief Complete, {{user_name}}!**
+<display>
+**Product Brief Complete, {{user_name}}!**
 
 I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
 
 **What we've accomplished:**
 
-- ✅ Executive Summary with clear vision and problem statement
+- Executive Summary with clear vision and problem statement
-- ✅ Core Vision with solution definition and unique differentiators
+- Core Vision with solution definition and unique differentiators
-- ✅ Target Users with rich personas and user journeys
+- Target Users with rich personas and user journeys
-- ✅ Success Metrics with measurable outcomes and business objectives
+- Success Metrics with measurable outcomes and business objectives
-- ✅ MVP Scope with focused feature set and clear boundaries
+- MVP Scope with focused feature set and clear boundaries
-- ✅ Future Vision that inspires while maintaining current focus
+- Future Vision that inspires while maintaining current focus
 
 **The complete Product Brief is now available at:** `{outputFile}`
 
-This brief serves as the foundation for all subsequent product development activities and strategic decisions."
+This brief serves as the foundation for all subsequent product development activities and strategic decisions.
+</display>
 
 ### 2. Document Quality Check
 
@@ -116,7 +118,9 @@ Provide guidance on logical next workflows:
 
 ### 4. Congrats to the user
 
-"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**"
+<display>
+**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**
+</display>
 
 Recap that the brief captures everything needed to guide subsequent product development:
 

src/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md

@@ -37,7 +37,9 @@ Confirm domain research scope and approach for **{{research_topic}}** with the u
 ### 1. Begin Scope Confirmation
 
 Start with domain scope understanding:
-"I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}}
+
+<display>
+I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}}
 
 **Domain Research Scope:**
 
@@ -53,11 +55,14 @@ Start with domain scope understanding:
 - Multi-source validation for critical domain claims
 - Confidence levels for uncertain domain information
 - Comprehensive domain coverage with industry-specific insights
+</display>
 
 ### 2. Scope Confirmation
 
 Present clear scope confirmation:
-"**Domain Research Scope Confirmation:**
+
+<display>
+**Domain Research Scope Confirmation:**
 
 For **{{research_topic}}**, I will research:
 
@@ -71,6 +76,7 @@ For **{{research_topic}}**, I will research:
 
 **Does this domain research scope and approach align with your goals?**
 [C] Continue - Begin domain research with this scope
+</display>
 
 ### 3. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md

@@ -41,7 +41,9 @@ Conduct industry analysis focusing on market size, growth, and industry dynamics
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly.
 
 Start with industry research approach:
-"Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics.
+
+<display>
+Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics.
 
 **Industry Analysis Focus:**
 
@@ -51,7 +53,8 @@ Start with industry research approach:
 - Industry trends and evolution patterns
 - Economic impact and value creation
 
-**Let me search for current industry insights.**"
+**Let me search for current industry insights.**
+</display>
 
 ### 2. Parallel Industry Research Execution
 
@@ -74,7 +77,8 @@ Search the web: "{{research_topic}} industry trends evolution"
 
 **Collect and analyze findings from all parallel searches:**
 
-"After executing comprehensive parallel web searches, let me analyze and aggregate industry findings:
+<display>
+After executing comprehensive parallel web searches, let me analyze and aggregate industry findings:
 
 **Research Coverage:**
 
@@ -87,7 +91,8 @@ Search the web: "{{research_topic}} industry trends evolution"
 [Identify patterns connecting market dynamics, segmentation, and trends]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
+[Overall confidence levels and research gaps identified]
+</display>
 
 ### 4. Generate Industry Analysis Content
 
@@ -152,7 +157,8 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-"I've completed **industry analysis** for {{research_topic}}.
+<display>
+I've completed **industry analysis** for {{research_topic}}.
 
 **Key Industry Findings:**
 
@@ -164,6 +170,7 @@ _Source: [URL]_
 
 **Ready to proceed to competitive landscape analysis?**
 [C] Continue - Save this to document and proceed to competitive landscape
+</display>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md

@@ -41,7 +41,9 @@ Conduct competitive landscape analysis focusing on key players, market share, an
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different competitive areas simultaneously and thoroughly.
 
 Start with competitive research approach:
-"Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** to understand the competitive ecosystem.
+
+<display>
+Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** to understand the competitive ecosystem.
 
 **Competitive Landscape Focus:**
 
@@ -51,7 +53,8 @@ Start with competitive research approach:
 - Business models and value propositions
 - Entry barriers and competitive dynamics
 
-**Let me search for current competitive insights.**"
+**Let me search for current competitive insights.**
+</display>
 
 ### 2. Parallel Competitive Research Execution
 
@@ -74,7 +77,8 @@ Search the web: "{{research_topic}} entry barriers competitive dynamics"
 
 **Collect and analyze findings from all parallel searches:**
 
-"After executing comprehensive parallel web searches, let me analyze and aggregate competitive findings:
+<display>
+After executing comprehensive parallel web searches, let me analyze and aggregate competitive findings:
 
 **Research Coverage:**
 
@@ -87,7 +91,8 @@ Search the web: "{{research_topic}} entry barriers competitive dynamics"
 [Identify patterns connecting players, strategies, and market dynamics]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
+[Overall confidence levels and research gaps identified]
+</display>
 
 ### 4. Generate Competitive Landscape Content
 
@@ -161,7 +166,8 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-"I've completed **competitive landscape analysis** for {{research_topic}}.
+<display>
+I've completed **competitive landscape analysis** for {{research_topic}}.
 
 **Key Competitive Findings:**
 
@@ -173,6 +179,7 @@ _Source: [URL]_
 
 **Ready to proceed to regulatory focus analysis?**
 [C] Continue - Save this to document and proceed to regulatory focus
+</display>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md

@@ -39,7 +39,9 @@ Conduct focused regulatory and compliance analysis with emphasis on requirements
 ### 1. Begin Regulatory Analysis
 
 Start with regulatory research approach:
-"Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}**.
+
+<display>
+Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}**.
 
 **Regulatory Focus Areas:**
 
@@ -49,7 +51,8 @@ Start with regulatory research approach:
 - Data protection and privacy regulations
 - Environmental and safety requirements
 
-**Let me search for current regulatory requirements.**"
+**Let me search for current regulatory requirements.**
+</display>
 
 ### 2. Web Search for Specific Regulations
 
@@ -136,7 +139,9 @@ _Source: [URL]_
 ### 6. Present Analysis and Continue Option
 
 Show the generated regulatory analysis and present continue option:
-"I've completed **regulatory requirements analysis** for {{research_topic}}.
+
+<display>
+I've completed **regulatory requirements analysis** for {{research_topic}}.
 
 **Key Regulatory Findings:**
 
@@ -148,6 +153,7 @@ Show the generated regulatory analysis and present continue option:
 
 **Ready to proceed to technical trends?**
 [C] Continue - Save this to the document and move to technical trends
+</display>
 
 ### 7. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md

@@ -39,7 +39,9 @@ Conduct comprehensive technical trends analysis using current web data with emph
 ### 1. Begin Technical Trends Analysis
 
 Start with technology research approach:
-"Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current data.
+
+<display>
+Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current data.
 
 **Technical Trends Focus:**
 
@@ -49,7 +51,8 @@ Start with technology research approach:
 - New business models enabled by technology
 - Future technology projections and roadmaps
 
-**Let me search for current technology developments.**"
+**Let me search for current technology developments.**
+</display>
 
 ### 2. Web Search for Emerging Technologies
 
@@ -148,7 +151,9 @@ _Source: [URL]_
 ### 6. Present Analysis and Complete Option
 
 Show the generated technical analysis and present complete option:
-"I've completed **technical trends and innovation analysis** for {{research_topic}}.
+
+<display>
+I've completed **technical trends and innovation analysis** for {{research_topic}}.
 
 **Technical Highlights:**
 
@@ -167,6 +172,7 @@ Show the generated technical analysis and present complete option:
 
 **Ready to proceed to research synthesis and recommendations?**
 [C] Continue - Save this to document and proceed to synthesis
+</display>
 
 ### 7. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md

@@ -339,7 +339,8 @@ _This comprehensive research document serves as an authoritative reference on {{
 
 **Document Completion Presentation:**
 
-"I've completed the **comprehensive research document synthesis** for **{{research_topic}}**, producing an authoritative research document with:
+<display>
+I've completed the **comprehensive research document synthesis** for **{{research_topic}}**, producing an authoritative research document with:
 
 **Document Features:**
 
@@ -368,6 +369,7 @@ _This comprehensive research document serves as an authoritative reference on {{
 
 **Ready to complete this comprehensive research document?**
 [C] Complete Research - Save final comprehensive document
+</display>
 
 ### 6. Handle Final Completion
 

src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md

@@ -39,7 +39,9 @@ Initialize market research by confirming understanding of {{research_topic}} and
 **INITIALIZE - DO NOT RESEARCH YET**
 
 Start with research confirmation:
-"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
+
+<display>
+I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
 
 **My Understanding of Your Research Needs:**
 
@@ -55,7 +57,8 @@ Start with research confirmation:
 - Competitive landscape and positioning
 - Strategic recommendations and implementation guidance
 
-**Does this accurately capture what you're looking for?**"
+**Does this accurately capture what you're looking for?**
+</display>
 
 ### 2. Refine Research Scope
 
@@ -117,7 +120,9 @@ Write initial research scope to document:
 ### 4. Present Confirmation and Continue Option
 
 Show initial scope document and present continue option:
-"I've documented our understanding and initial scope for **{{research_topic}}** market research.
+
+<display>
+I've documented our understanding and initial scope for **{{research_topic}}** market research.
 
 **What I've established:**
 
@@ -131,6 +136,7 @@ Show initial scope document and present continue option:
 **Ready to begin detailed market research?**
 [C] Continue - Confirm scope and proceed to customer insights analysis
 [Modify] Suggest changes to research scope before proceeding
+</display>
 
 ### 5. Handle User Response
 
@@ -138,7 +144,7 @@ Show initial scope document and present continue option:
 
 - Update frontmatter: `stepsCompleted: [1]`
 - Add confirmation note to document: "Scope confirmed by user on {{date}}"
-- Load: `./step-02-customer-insights.md`
+- Load: `./step-02-customer-behavior.md`
 
 #### If 'Modify':
 

src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md

@@ -41,7 +41,9 @@ Conduct customer behavior and segment analysis with emphasis on patterns and dem
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly.
 
 Start with customer behavior research approach:
-"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns.
+
+<display>
+Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns.
 
 **Customer Behavior Focus:**
 
@@ -51,7 +53,8 @@ Start with customer behavior research approach:
 - Behavior drivers and influences
 - Customer interaction patterns and engagement
 
-**Let me search for current customer behavior insights.**"
+**Let me search for current customer behavior insights.**
+</display>
 
 ### 2. Parallel Customer Behavior Research Execution
 
@@ -74,7 +77,8 @@ Search the web: "{{research_topic}} customer behavior drivers"
 
 **Collect and analyze findings from all parallel searches:**
 
-"After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
+<display>
+After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
 
 **Research Coverage:**
 
@@ -88,7 +92,8 @@ Search the web: "{{research_topic}} customer behavior drivers"
 [Identify patterns connecting demographics, psychographics, and behaviors]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
+[Overall confidence levels and research gaps identified]
+</display>
 
 ### 4. Generate Customer Behavior Content
 
@@ -160,7 +165,8 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-"I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
+<display>
+I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
 
 **Key Customer Behavior Findings:**
 
@@ -172,6 +178,7 @@ _Source: [URL]_
 
 **Ready to proceed to customer pain points?**
 [C] Continue - Save this to document and proceed to pain points analysis
+</display>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md

@@ -1,200 +0,0 @@
-# Market Research Step 2: Customer Insights
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without web search verification
-
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ Search the web to verify and supplement your knowledge with current facts
-- 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator
-- 💬 FOCUS on customer behavior and needs analysis
-- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show web search analysis before presenting findings
-- ⚠️ Present [C] continue option after customer insights content generation
-- 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from step-01 are available
-- Focus on customer behavior and needs analysis
-- Web search capabilities with source verification are enabled
-- May need to search for current customer behavior trends
-
-## YOUR TASK:
-
-Conduct comprehensive customer insights analysis with emphasis on behavior patterns and needs.
-
-## CUSTOMER INSIGHTS SEQUENCE:
-
-### 1. Begin Customer Insights Analysis
-
-**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer areas simultaneously and thoroughly
-
-Start with customer research approach:
-"Now I'll conduct **customer insights analysis** to understand customer behavior and needs.
-
-**Customer Insights Focus:**
-
-- Customer behavior patterns and preferences
-- Pain points and challenges
-- Decision-making processes
-- Customer journey mapping
-- Customer satisfaction drivers
-- Demographic and psychographic profiles
-
-**Let me search for current customer insights using parallel web searches for comprehensive coverage.**"
-
-### 2. Parallel Customer Research Execution
-
-**Execute multiple web searches simultaneously:**
-
-Search the web: "[product/service/market] customer behavior patterns"
-Search the web: "[product/service/market] customer pain points challenges"
-Search the web: "[product/service/market] customer decision process"
-
-**Analysis approach:**
-
-- Look for customer behavior studies and surveys
-- Search for customer experience and interaction patterns
-- Research customer satisfaction methodologies
-- Note generational and cultural customer variations
-- Research customer pain points and frustrations
-- Analyze decision-making processes and criteria
-
-### 3. Analyze and Aggregate Results
-
-**Collect and analyze findings from all parallel searches:**
-
-"After executing comprehensive parallel web searches, let me analyze and aggregate the customer insights:
-
-**Research Coverage:**
-
-- Customer behavior patterns and preferences
-- Pain points and challenges
-- Decision-making processes and journey mapping
-
-**Cross-Customer Analysis:**
-[Identify patterns connecting behavior, pain points, and decisions]
-
-**Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
-
-### 4. Generate Customer Insights Content
-
-Prepare customer analysis with web search citations:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Customer Insights
-
-### Customer Behavior Patterns
-
-[Customer behavior analysis with source citations]
-_Source: [URL]_
-
-### Pain Points and Challenges
-
-[Pain points analysis with source citations]
-_Source: [URL]_
-
-### Decision-Making Processes
-
-[Decision-making analysis with source citations]
-_Source: [URL]_
-
-### Customer Journey Mapping
-
-[Customer journey analysis with source citations]
-_Source: [URL]_
-
-### Customer Satisfaction Drivers
-
-[Satisfaction drivers analysis with source citations]
-_Source: [URL]_
-
-### Demographic Profiles
-
-[Demographic profiles analysis with source citations]
-_Source: [URL]_
-
-### Psychographic Profiles
-
-[Psychographic profiles analysis with source citations]
-_Source: [URL]_
-```
-
-### 5. Present Analysis and Continue Option
-
-Show the generated customer insights and present continue option:
-"I've completed the **customer insights analysis** for customer behavior and needs.
-
-**Key Customer Findings:**
-
-- Customer behavior patterns clearly identified
-- Pain points and challenges thoroughly documented
-- Decision-making processes mapped
-- Customer journey insights captured
-- Satisfaction and profile data analyzed
-
-**Ready to proceed to competitive analysis?**
-[C] Continue - Save this to the document and proceed to competitive analysis
-
-### 6. Handle Continue Selection
-
-#### If 'C' (Continue):
-
-- Append the final content to the research document
-- Update frontmatter: `stepsCompleted: [1, 2]`
-- Load: `./step-05-competitive-analysis.md`
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C', append the content directly to the research document using the structure from step 4.
-
-## SUCCESS METRICS:
-
-✅ Customer behavior patterns identified with current citations
-✅ Pain points and challenges clearly documented
-✅ Decision-making processes thoroughly analyzed
-✅ Customer journey insights captured and mapped
-✅ Customer satisfaction drivers identified
-✅ [C] continue option presented and handled correctly
-✅ Content properly appended to document when C selected
-
-## FAILURE MODES:
-
-❌ Relying solely on training data without web verification for current facts
-
-❌ Missing critical customer behavior patterns
-❌ Not identifying key pain points and challenges
-❌ Incomplete customer journey mapping
-❌ Not presenting [C] continue option after content generation
-❌ Appending content without user selecting 'C'
-
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## CUSTOMER RESEARCH PROTOCOLS:
-
-- Search for customer behavior studies and surveys
-- Use market research firm and industry association sources
-- Research customer experience and interaction patterns
-- Note generational and cultural customer variations
-- Research customer satisfaction methodologies
-
-## NEXT STEP:
-
-After user selects 'C' and content is saved to document, load `./step-05-competitive-analysis.md` to focus on competitive landscape analysis.
-
-Remember: Always emphasize current customer data and rigorous source verification!

src/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md

@@ -42,7 +42,9 @@ Conduct customer pain points and needs analysis with emphasis on challenges and
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer pain point areas simultaneously and thoroughly.
 
 Start with customer pain points research approach:
-"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to understand customer challenges.
+
+<display>
+Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to understand customer challenges.
 
 **Customer Pain Points Focus:**
 
@@ -52,7 +54,8 @@ Start with customer pain points research approach:
 - Service and support pain points
 - Customer satisfaction gaps
 
-**Let me search for current customer pain points insights.**"
+**Let me search for current customer pain points insights.**
+</display>
 
 ### 2. Parallel Pain Points Research Execution
 
@@ -75,7 +78,8 @@ Search the web: "{{research_topic}} customer barriers to adoption"
 
 **Collect and analyze findings from all parallel searches:**
 
-"After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings:
+<display>
+After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings:
 
 **Research Coverage:**
 
@@ -88,7 +92,8 @@ Search the web: "{{research_topic}} customer barriers to adoption"
 [Identify patterns connecting different types of pain points]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
+[Overall confidence levels and research gaps identified]
+</display>
 
 ### 4. Generate Customer Pain Points Content
 
@@ -171,7 +176,8 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-"I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges.
+<display>
+I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges.
 
 **Key Pain Points Findings:**
 
@@ -183,6 +189,7 @@ _Source: [URL]_
 
 **Ready to proceed to customer decision processes?**
 [C] Continue - Save this to document and proceed to decision processes analysis
+</display>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md

@@ -42,7 +42,9 @@ Conduct customer decision processes and journey analysis with emphasis on decisi
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer decision areas simultaneously and thoroughly.
 
 Start with customer decisions research approach:
-"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** to understand customer decision-making.
+
+<display>
+Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** to understand customer decision-making.
 
 **Customer Decisions Focus:**
 
@@ -52,7 +54,8 @@ Start with customer decisions research approach:
 - Purchase decision influencers
 - Information gathering patterns
 
-**Let me search for current customer decision insights.**"
+**Let me search for current customer decision insights.**
+</display>
 
 ### 2. Parallel Decisions Research Execution
 
@@ -75,7 +78,8 @@ Search the web: "{{research_topic}} decision influencing factors"
 
 **Collect and analyze findings from all parallel searches:**
 
-"After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings:
+<display>
+After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings:
 
 **Research Coverage:**
 
@@ -88,7 +92,8 @@ Search the web: "{{research_topic}} decision influencing factors"
 [Identify patterns connecting decision factors and journey stages]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
+[Overall confidence levels and research gaps identified]
+</display>
 
 ### 4. Generate Customer Decisions Content
 
@@ -181,7 +186,8 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-"I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making.
+<display>
+I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making.
 
 **Key Decision Findings:**
 
@@ -193,6 +199,7 @@ _Source: [URL]_
 
 **Ready to proceed to competitive analysis?**
 [C] Continue - Save this to document and proceed to competitive analysis
+</display>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md

@@ -36,7 +36,9 @@ Conduct comprehensive competitive analysis with emphasis on market positioning.
 ### 1. Begin Competitive Analysis
 
 Start with competitive research approach:
-"Now I'll conduct **competitive analysis** to understand the competitive landscape.
+
+<display>
+Now I'll conduct **competitive analysis** to understand the competitive landscape.
 
 **Competitive Analysis Focus:**
 
@@ -46,7 +48,8 @@ Start with competitive research approach:
 - Market differentiation opportunities
 - Competitive threats and challenges
 
-**Let me search for current competitive information.**"
+**Let me search for current competitive information.**
+</display>
 
 ### 2. Generate Competitive Analysis Content
 
@@ -98,7 +101,9 @@ _Source: [URL]_
 ### 3. Present Analysis and Complete Option
 
 Show the generated competitive analysis and present complete option:
-"I've completed the **competitive analysis** for the competitive landscape.
+
+<display>
+I've completed the **competitive analysis** for the competitive landscape.
 
 **Key Competitive Findings:**
 
@@ -110,6 +115,7 @@ Show the generated competitive analysis and present complete option:
 
 **Ready to complete the market research?**
 [C] Complete Research - Save final document and conclude
+</display>
 
 ### 4. Handle Complete Selection
 

src/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md

@@ -39,7 +39,9 @@ Produce a comprehensive, authoritative market research document on **{{research_
 ### 1. Begin Strategic Synthesis
 
 Start with strategic synthesis approach:
-"Now I'll complete our market research with **strategic synthesis and recommendations** .
+
+<display>
+Now I'll complete our market research with **strategic synthesis and recommendations** .
 
 **Strategic Synthesis Focus:**
 
@@ -49,7 +51,8 @@ Start with strategic synthesis approach:
 - Risk assessment and mitigation approaches
 - Actionable next steps and implementation guidance
 
-**Let me search for current strategic insights and best practices.**"
+**Let me search for current strategic insights and best practices.**
+</display>
 
 ### 2. Web Search for Market Entry Strategies
 
@@ -356,7 +359,8 @@ _This comprehensive market research document serves as an authoritative market r
 
 **Market Research Document Completion Presentation:**
 
-"I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with:
+<display>
+I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with:
 
 **Document Features:**
 
@@ -384,6 +388,7 @@ _This comprehensive market research document serves as an authoritative market r
 
 **Ready to complete this comprehensive market research document?**
 [C] Complete Research - Save final comprehensive market research document
+</display>
 
 ### 6. Handle Complete Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md

@@ -37,7 +37,9 @@ Confirm technical research scope and approach for **{{research_topic}}** with th
 ### 1. Begin Scope Confirmation
 
 Start with technical scope understanding:
-"I understand you want to conduct **technical research** for **{{research_topic}}** with these goals: {{research_goals}}
+
+<display>
+I understand you want to conduct **technical research** for **{{research_topic}}** with these goals: {{research_goals}}
 
 **Technical Research Scope:**
 
@@ -53,11 +55,14 @@ Start with technical scope understanding:
 - Multi-source validation for critical technical claims
 - Confidence levels for uncertain technical information
 - Comprehensive technical coverage with architecture-specific insights
+</display>
 
 ### 2. Scope Confirmation
 
 Present clear scope confirmation:
-"**Technical Research Scope Confirmation:**
+
+<display>
+**Technical Research Scope Confirmation:**
 
 For **{{research_topic}}**, I will research:
 
@@ -71,6 +76,7 @@ For **{{research_topic}}**, I will research:
 
 **Does this technical research scope and approach align with your goals?**
 [C] Continue - Begin technical research with this scope
+</display>
 
 ### 3. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md

@@ -41,7 +41,9 @@ Conduct technology stack analysis focusing on languages, frameworks, tools, and
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technology stack areas simultaneously and thoroughly.
 
 Start with technology stack research approach:
-"Now I'll conduct **technology stack analysis** for **{{research_topic}}** to understand the technology landscape.
+
+<display>
+Now I'll conduct **technology stack analysis** for **{{research_topic}}** to understand the technology landscape.
 
 **Technology Stack Focus:**
 
@@ -51,7 +53,8 @@ Start with technology stack research approach:
 - Development tools and platforms
 - Cloud infrastructure and deployment platforms
 
-**Let me search for current technology stack insights.**"
+**Let me search for current technology stack insights.**
+</display>
 
 ### 2. Parallel Technology Stack Research Execution
 
@@ -74,7 +77,8 @@ Search the web: "{{research_topic}} cloud infrastructure platforms"
 
 **Collect and analyze findings from all parallel searches:**
 
-"After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings:
+<display>
+After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings:
 
 **Research Coverage:**
 
@@ -87,7 +91,8 @@ Search the web: "{{research_topic}} cloud infrastructure platforms"
 [Identify patterns connecting language choices, frameworks, and platform decisions]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
+[Overall confidence levels and research gaps identified]
+</display>
 
 ### 4. Generate Technology Stack Content
 
@@ -161,7 +166,8 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-"I've completed **technology stack analysis** of the technology landscape for {{research_topic}}.
+<display>
+I've completed **technology stack analysis** of the technology landscape for {{research_topic}}.
 
 **Key Technology Stack Findings:**
 
@@ -173,6 +179,7 @@ _Source: [URL]_
 
 **Ready to proceed to integration patterns analysis?**
 [C] Continue - Save this to document and proceed to integration patterns
+</display>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md

@@ -41,7 +41,9 @@ Conduct integration patterns analysis focusing on APIs, communication protocols,
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different integration areas simultaneously and thoroughly.
 
 Start with integration patterns research approach:
-"Now I'll conduct **integration patterns analysis** for **{{research_topic}}** to understand system integration approaches.
+
+<display>
+Now I'll conduct **integration patterns analysis** for **{{research_topic}}** to understand system integration approaches.
 
 **Integration Patterns Focus:**
 
@@ -51,7 +53,8 @@ Start with integration patterns research approach:
 - Microservices integration patterns
 - Event-driven architectures and messaging
 
-**Let me search for current integration patterns insights.**"
+**Let me search for current integration patterns insights.**
+</display>
 
 ### 2. Parallel Integration Patterns Research Execution
 
@@ -74,7 +77,8 @@ Search the web: "{{research_topic}} microservices integration patterns"
 
 **Collect and analyze findings from all parallel searches:**
 
-"After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings:
+<display>
+After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings:
 
 **Research Coverage:**
 
@@ -87,7 +91,8 @@ Search the web: "{{research_topic}} microservices integration patterns"
 [Identify patterns connecting API choices, communication protocols, and system design]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
+[Overall confidence levels and research gaps identified]
+</display>
 
 ### 4. Generate Integration Patterns Content
 
@@ -170,7 +175,8 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-"I've completed **integration patterns analysis** of system integration approaches for {{research_topic}}.
+<display>
+I've completed **integration patterns analysis** of system integration approaches for {{research_topic}}.
 
 **Key Integration Patterns Findings:**
 
@@ -182,6 +188,7 @@ _Source: [URL]_
 
 **Ready to proceed to architectural patterns analysis?**
 [C] Continue - Save this to document and proceed to architectural patterns
+</display>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md

@@ -39,7 +39,9 @@ Conduct comprehensive architectural patterns analysis with emphasis on design de
 ### 1. Begin Architectural Patterns Analysis
 
 Start with architectural research approach:
-"Now I'll focus on **architectural patterns and design decisions** for effective architecture approaches for [technology/domain].
+
+<display>
+Now I'll focus on **architectural patterns and design decisions** for effective architecture approaches for [technology/domain].
 
 **Architectural Patterns Focus:**
 
@@ -49,7 +51,8 @@ Start with architectural research approach:
 - Integration and communication patterns
 - Security and performance architectural considerations
 
-**Let me search for current architectural patterns and approaches.**"
+**Let me search for current architectural patterns and approaches.**
+</display>
 
 ### 2. Web Search for System Architecture Patterns
 
@@ -137,7 +140,9 @@ _Source: [URL]_
 ### 6. Present Analysis and Continue Option
 
 Show the generated architectural patterns and present continue option:
-"I've completed the **architectural patterns analysis** for effective architecture approaches.
+
+<display>
+I've completed the **architectural patterns analysis** for effective architecture approaches.
 
 **Key Architectural Findings:**
 
@@ -149,6 +154,7 @@ Show the generated architectural patterns and present continue option:
 
 **Ready to proceed to implementation research?**
 [C] Continue - Save this to the document and move to implementation research
+</display>
 
 ### 7. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md

@@ -36,7 +36,9 @@ Conduct comprehensive implementation research with emphasis on practical impleme
 ### 1. Begin Implementation Research
 
 Start with implementation research approach:
-"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis.
+
+<display>
+Now I'll complete our technical research with **implementation approaches and technology adoption** analysis.
 
 **Implementation Research Focus:**
 
@@ -46,7 +48,8 @@ Start with implementation research approach:
 - Team organization and skill requirements
 - Cost optimization and resource management
 
-**Let me search for current implementation and adoption strategies.**"
+**Let me search for current implementation and adoption strategies.**
+</display>
 
 ### 2. Web Search for Technology Adoption
 
@@ -152,7 +155,9 @@ _Source: [URL]_
 ### 6. Present Analysis and Complete Option
 
 Show the generated implementation research and present complete option:
-"I've completed the **implementation research and technology adoption** analysis, finalizing our comprehensive technical research.
+
+<display>
+I've completed the **implementation research and technology adoption** analysis, finalizing our comprehensive technical research.
 
 **Implementation Highlights:**
 
@@ -171,6 +176,7 @@ Show the generated implementation research and present complete option:
 
 **Ready to complete the technical research report?**
 [C] Complete Research - Save final document and conclude
+</display>
 
 ### 7. Handle Complete Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md

@@ -382,7 +382,8 @@ _This comprehensive technical research document serves as an authoritative techn
 
 **Technical Document Completion Presentation:**
 
-"I've completed the **comprehensive technical research document synthesis** for **{{research_topic}}**, producing an authoritative technical research document with:
+<display>
+I've completed the **comprehensive technical research document synthesis** for **{{research_topic}}**, producing an authoritative technical research document with:
 
 **Technical Document Features:**
 
@@ -411,6 +412,7 @@ _This comprehensive technical research document serves as an authoritative techn
 
 **Ready to complete this comprehensive technical research document?**
 [C] Complete Research - Save final comprehensive technical document
+</display>
 
 ### 6. Handle Final Technical Completion
 

src/bmm/workflows/1-analysis/research/workflow.md

@@ -91,7 +91,8 @@ Execute research type discovery and routing:
 
 ### Collaborative Research Discovery
 
-"Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with rigorous source verification, while you bring the domain expertise and research direction.
+<display>
+Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with rigorous source verification, while you bring the domain expertise and research direction.
 
 **Let me help you clarify what you'd like to research.**
 
@@ -104,6 +105,7 @@ For example:
 - 'AI implementation in financial services'
 - 'Sustainable packaging regulations'
 - 'Or anything else you have in mind...'
+</display>
 
 ### Topic Exploration and Clarification
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01-init.md

@@ -121,7 +121,8 @@ Try to discover the following:
 
 **Setup Report to User:**
 
-"Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
+<display>
+Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
 
 **Document Setup:**
 
@@ -141,7 +142,8 @@ Try to discover the following:
 📋 **Note:** This is a **brownfield project**. Your existing project documentation has been loaded. In the next step, I'll ask specifically about what new features or changes you want to add to your existing system.
 {/if}
 
-Do you have any other documents you'd like me to include, or shall we continue to the next step?"
+Do you have any other documents you'd like me to include, or shall we continue to the next step?
+</display>
 
 ### 4. Present MENU OPTIONS
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01b-continue.md

@@ -86,7 +86,9 @@ Review the frontmatter to understand:
 ### 4. Handle Workflow Completion
 
 **If `stepsCompleted` array contains `"step-11-complete.md"`:**
-"Great news! It looks like we've already completed the PRD workflow for {{project_name}}.
+
+<display>
+Great news! It looks like we've already completed the PRD workflow for {{project_name}}.
 
 The final document is ready at `{outputFile}` with all sections completed.
 
@@ -96,12 +98,15 @@ Would you like me to:
 - Suggest next workflow steps (like architecture or epic creation)
 - Start a new PRD revision
 
-What would be most helpful?"
+What would be most helpful?
+</display>
 
 ### 5. Present Current Progress
 
 **If workflow not complete:**
-"Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.
+
+<display>
+Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.
 
 **Current Progress:**
 - Last completed: {last step filename from stepsCompleted array}
@@ -112,11 +117,14 @@ What would be most helpful?"
 - Current PRD document is ready with all completed sections
 - Ready to continue from where we left off
 
-Does this look right, or do you want to make any adjustments before we proceed?"
+Does this look right, or do you want to make any adjustments before we proceed?
+</display>
 
 ### 6. Present MENU OPTIONS
 
-Display: "**Select an Option:** [C] Continue to {next step name}"
+<display>
+**Select an Option:** [C] Continue to {next step name}
+</display>
 
 #### Menu Handling Logic:
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02-discovery.md

@@ -83,20 +83,24 @@ Read the frontmatter from `{outputFile}` to get document counts:
 
 **Announce your understanding:**
 
-"From step 1, I have loaded:
+<display>
+From step 1, I have loaded:
 - Product briefs: {{briefCount}}
 - Research: {{researchCount}}
 - Brainstorming: {{brainstormingCount}}
 - Project docs: {{projectDocsCount}}
 
-{{if projectDocsCount > 0}}This is a brownfield project - I'll focus on understanding what you want to add or change.{{else}}This is a greenfield project - I'll help you define the full product vision.{{/if}}"
+{{if projectDocsCount > 0}}This is a brownfield project - I'll focus on understanding what you want to add or change.{{else}}This is a greenfield project - I'll help you define the full product vision.{{/if}}
+</display>
 
 ### 2. Load Classification Data
 
 **Attempt subprocess data lookup:**
 
 **Project Type Lookup:**
-"Your task: Lookup data in {projectTypesCSV}
+
+<display>
+Your task: Lookup data in {projectTypesCSV}
 
 **Search criteria:**
 - Find row where project_type matches {{detectedProjectType}}
@@ -105,10 +109,13 @@ Read the frontmatter from `{outputFile}` to get document counts:
 Return ONLY the matching row as a YAML-formatted object with these fields:
 project_type, detection_signals
 
-**Do NOT return the entire CSV - only the matching row.**"
+**Do NOT return the entire CSV - only the matching row.**
+</display>
 
 **Domain Complexity Lookup:**
-"Your task: Lookup data in {domainComplexityCSV}
+
+<display>
+Your task: Lookup data in {domainComplexityCSV}
 
 **Search criteria:**
 - Find row where domain matches {{detectedDomain}}
@@ -117,7 +124,8 @@ project_type, detection_signals
 Return ONLY the matching row as a YAML-formatted object with these fields:
 domain, complexity, typical_concerns, compliance_requirements
 
-**Do NOT return the entire CSV - only the matching row.**"
+**Do NOT return the entire CSV - only the matching row.**
+</display>
 
 **Graceful degradation (if Task tool unavailable):**
 - Load the CSV files directly
@@ -147,12 +155,14 @@ As the user describes their product, match against:
 
 Once you have enough understanding, share your classification:
 
-"I'm hearing this as:
+<display>
+I'm hearing this as:
 - **Project Type:** {{detectedType}}
 - **Domain:** {{detectedDomain}}
 - **Complexity:** {{complexityLevel}}
 
-Does this sound right to you?"
+Does this sound right to you?
+</display>
 
 Let the user confirm or refine your classification.
 
@@ -171,7 +181,8 @@ classification:
 
 Present the project classification for review, then display menu:
 
-"Based on our conversation, I've discovered and classified your project.
+<display>
+Based on our conversation, I've discovered and classified your project.
 
 **Here's the classification:**
 
@@ -180,9 +191,12 @@ Present the project classification for review, then display menu:
 **Complexity:** {{complexityLevel}}
 **Project Context:** {{greenfield|brownfield}}
 
-**What would you like to do?**"
+**What would you like to do?**
+</display>
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Product Vision (Step 2b of 13)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Product Vision (Step 2b of 13)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask} with the current classification, process the enhanced insights that come back, ask user if they accept the improvements, if yes update classification then redisplay menu, if no keep original classification then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md

@@ -172,7 +172,9 @@ Present the success criteria content for user review, then display menu:
 - Ask if they'd like to refine further, get other perspectives, or proceed
 - Present menu options naturally as part of the conversation
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to User Journey Mapping (Step 4 of 11)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to User Journey Mapping (Step 4 of 11)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask} with the current success criteria content, process the enhanced success metrics that come back, ask user "Accept these improvements to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md

@@ -152,7 +152,9 @@ Present the user journey content for review, then display menu:
 - Ask if they'd like to refine further, get other perspectives, or proceed
 - Present menu options naturally as part of conversation
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Domain Requirements (Step 5 of 11)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Domain Requirements (Step 5 of 11)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask} with the current journey content, process the enhanced journey insights that come back, ask user "Accept these improvements to the user journeys? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-05-domain.md

@@ -80,9 +80,12 @@ For complex domains, explore what makes this domain special:
 **If complexity is LOW:**
 
 Offer to skip:
-"The domain complexity from our discovery is low. We may not need deep domain-specific requirements. Would you like to:
+
+<display>
+The domain complexity from our discovery is low. We may not need deep domain-specific requirements. Would you like to:
 - [C] Skip this step and move to Innovation
-- [D] Do domain exploration anyway"
+- [D] Do domain exploration anyway
+</display>
 
 **If complexity is MEDIUM or HIGH:**
 
@@ -92,7 +95,8 @@ Proceed with domain exploration.
 
 **Attempt subprocess data lookup:**
 
-"Your task: Lookup data in {domainComplexityCSV}
+<display>
+Your task: Lookup data in {domainComplexityCSV}
 
 **Search criteria:**
 - Find row where domain matches {{domainFromStep02}}
@@ -101,7 +105,8 @@ Proceed with domain exploration.
 Return ONLY the matching row as a YAML-formatted object with these fields:
 domain, complexity, typical_concerns, compliance_requirements
 
-**Do NOT return the entire CSV - only the matching row.**"
+**Do NOT return the entire CSV - only the matching row.**
+</display>
 
 **Graceful degradation (if Task tool unavailable):**
 - Load the CSV file directly
@@ -147,11 +152,15 @@ Acknowledge the domain and explore what makes it complex:
 
 **Check with the user:**
 
-"Are there other domain-specific concerns we should consider? For [this domain], what typically gets overlooked?"
+<display>
+Are there other domain-specific concerns we should consider? For [this domain], what typically gets overlooked?
+</display>
 
 ### N. Present MENU OPTIONS
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue - Save and Proceed to Innovation (Step 6 of 13)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue - Save and Proceed to Innovation (Step 6 of 13)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask}, and when finished redisplay the menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-06-innovation.md

@@ -152,7 +152,9 @@ Present the innovation content for review, then display menu:
 - Ask if they'd like to refine further, get other perspectives, or proceed
 - Present menu options naturally as part of conversation
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Project Type Analysis (Step 7 of 11)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Project Type Analysis (Step 7 of 11)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask} with the current innovation content, process the enhanced innovation insights that come back, ask user "Accept these improvements to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
@@ -172,7 +174,9 @@ If no genuine innovation signals are found after exploration:
 - Note this is fine - many successful products are excellent executions of existing concepts
 - Ask if they'd like to try finding innovative angles or proceed
 
-Display: "**Select:** [A] Advanced Elicitation - Let's try to find innovative angles [C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)"
+<display>
+**Select:** [A] Advanced Elicitation - Let's try to find innovative angles [C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)
+</display>
 
 ### Menu Handling Logic:
 - IF A: Proceed with content generation anyway, then return to menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-07-project-type.md

@@ -55,7 +55,7 @@ Conduct project-type specific discovery using CSV-driven guidance to define tech
 
 **Attempt subprocess data lookup:**
 
-"Your task: Lookup data in {projectTypesCSV}
+Your task: Lookup data in {projectTypesCSV}
 
 **Search criteria:**
 - Find row where project_type matches {{projectTypeFromStep02}}
@@ -64,7 +64,7 @@ Conduct project-type specific discovery using CSV-driven guidance to define tech
 Return ONLY the matching row as a YAML-formatted object with these fields:
 project_type, key_questions, required_sections, skip_sections, innovation_signals
 
-**Do NOT return the entire CSV - only the matching row.**"
+**Do NOT return the entire CSV - only the matching row.**
 
 **Graceful degradation (if Task tool unavailable):**
 - Load the CSV file directly
@@ -161,15 +161,19 @@ When saving to document, append these Level 2 and Level 3 sections:
 
 Present the project-type content for review, then display menu:
 
-"Based on our conversation and best practices for this product type, I've documented the {project_type}-specific requirements for {{project_name}}.
+<display>
+Based on our conversation and best practices for this product type, I've documented the {project_type}-specific requirements for {{project_name}}.
 
 **Here's what I'll add to the document:**
 
 [Show the complete markdown content from section 5]
 
-**What would you like to do?**"
+**What would you like to do?**
+</display>
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Scoping (Step 8 of 11)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Scoping (Step 8 of 11)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask} with the current project-type content, process the enhanced technical insights that come back, ask user "Accept these improvements to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-08-scoping.md

@@ -117,11 +117,14 @@ Create phased development approach:
 Identify and mitigate scoping risks:
 
 **Technical Risks:**
-"Looking at your innovation and domain requirements:
+
+<display>
+Looking at your innovation and domain requirements:
 
 - What's the most technically challenging aspect?
 - Could we simplify the initial implementation?
-- What's the riskiest assumption about technology feasibility?"
+- What's the riskiest assumption about technology feasibility?
+</display>
 
 **Market Risks:**
 
@@ -180,7 +183,9 @@ Present the scoping decisions for review, then display menu:
 - Ask if they'd like to refine further, get other perspectives, or proceed
 - Present menu options naturally as part of conversation
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Functional Requirements (Step 9 of 11)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Functional Requirements (Step 9 of 11)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask} with the current scoping analysis, process the enhanced insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-09-functional.md

@@ -176,9 +176,11 @@ Present the functional requirements for review, then display menu:
 - Ask if they'd like to refine further, get other perspectives, or proceed
 - Present menu options naturally as part of conversation
 
-**What would you like to do?**"
+**What would you like to do?**
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Non-Functional Requirements (Step 10 of 11)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Non-Functional Requirements (Step 10 of 11)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask} with the current FR list, process the enhanced capability coverage that comes back, ask user if they accept the additions, if yes update content then redisplay menu, if no keep original content then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-10-nonfunctional.md

@@ -165,7 +165,9 @@ Present the non-functional requirements for review, then display menu:
 - Ask if they'd like to refine further, get other perspectives, or proceed
 - Present menu options naturally as part of conversation
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Polish Document (Step 11 of 12)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Polish Document (Step 11 of 12)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask} with the current NFR content, process the enhanced quality attribute insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md

@@ -5,7 +5,7 @@ description: 'Optimize and polish the complete PRD document for flow, coherence,
 # File References
 nextStepFile: './step-12-complete.md'
 outputFile: '{planning_artifacts}/prd.md'
-purposeFile: './data/prd-purpose.md'
+purposeFile: '../data/prd-purpose.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
@@ -166,7 +166,9 @@ Present the polished document for review, then display menu:
 - Ask if they'd like to refine further, get other perspectives, or proceed
 - Present menu options naturally as part of conversation
 
-Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Complete PRD (Step 12 of 12)"
+<display>
+**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Complete PRD (Step 12 of 12)
+</display>
 
 #### Menu Handling Logic:
 - IF A: Read fully and follow: {advancedElicitationTask} with the polished document, process the enhanced refinements that come back, ask user "Accept these polish improvements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original polish then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01-discovery.md

@@ -70,11 +70,13 @@ This file defines what makes a great BMAD PRD. Internalize this understanding -
 
 ### 2. Discover PRD to Edit
 
-"**PRD Edit Workflow**
+<display>
+**PRD Edit Workflow**
 
 Which PRD would you like to edit?
 
-Please provide the path to the PRD file you want to edit."
+Please provide the path to the PRD file you want to edit.
+</display>
 
 **Wait for user to provide PRD path.**
 
@@ -97,7 +99,8 @@ ls -t {prd_folder_path}/validation-report-*.md 2>/dev/null | head -1
 **If validation report found:**
 
 Display:
-"**📋 Found Validation Report**
+<display>
+**📋 Found Validation Report**
 
 I found a validation report from {validation_date} in the PRD folder.
 
@@ -105,7 +108,8 @@ This report contains findings from previous validation checks and can help guide
 
 **Would you like to:**
 - **[U] Use validation report** - Load it to guide and prioritize edits
-- **[S] Skip** - Proceed with manual edit discovery"
+- **[S] Skip** - Proceed with manual edit discovery
+</display>
 
 **Wait for user input.**
 
@@ -125,11 +129,13 @@ This report contains findings from previous validation checks and can help guide
 
 ### 5. Ask About Validation Report
 
-"**Do you have a validation report to guide edits?**
+<display>
+**Do you have a validation report to guide edits?**
 
 If you've run the validation workflow on this PRD, I can use that report to guide improvements and prioritize changes.
 
-Validation report path (or type 'none'):"
+Validation report path (or type 'none'):
+</display>
 
 **Wait for user input.**
 
@@ -144,7 +150,8 @@ Validation report path (or type 'none'):"
 
 ### 6. Discover Edit Requirements
 
-"**What would you like to edit in this PRD?**
+<display>
+**What would you like to edit in this PRD?**
 
 Please describe the changes you want to make. For example:
 - Fix specific issues (information density, implementation leakage, etc.)
@@ -154,7 +161,8 @@ Please describe the changes you want to make. For example:
 - General improvements
 - Other changes
 
-**Describe your edit goals:**"
+**Describe your edit goals:**
+</display>
 
 **Wait for user to describe their requirements.**
 
@@ -181,25 +189,31 @@ Analyze the loaded PRD:
 
 **IF validation report provided OR PRD is BMAD Standard/Variant:**
 
-Display: "**Edit Requirements Understood**
+Display:
+<display>
+**Edit Requirements Understood**
 
 **PRD Format:** {classification}
 {If validation report: "**Validation Guide:** Yes - will use validation report findings"}
 **Edit Goals:** {summary of user's requirements}
 
-**Proceeding to deep review and analysis...**"
+**Proceeding to deep review and analysis...**
+</display>
 
 Read fully and follow: next step (step-e-02-review.md)
 
 **IF PRD is Legacy (Non-Standard) AND no validation report:**
 
-Display: "**Format Detected:** Legacy PRD
+Display:
+<display>
+**Format Detected:** Legacy PRD
 
 This PRD does not follow BMAD standard structure (only {count}/6 core sections present).
 
 **Your edit goals:** {user's requirements}
 
-**How would you like to proceed?**"
+**How would you like to proceed?**
+</display>
 
 Present MENU OPTIONS below for user selection
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01b-legacy-conversion.md

@@ -128,7 +128,8 @@ Return conversion assessment with gap analysis and effort estimate."
 
 Display:
 
-"**Legacy PRD Conversion Assessment**
+<display>
+**Legacy PRD Conversion Assessment**
 
 **Current PRD Structure:**
 - Core sections present: {count}/6
@@ -146,7 +147,8 @@ Display:
 **Recommendation:**
 {Based on effort and user goals, recommend best approach}
 
-**How would you like to proceed?**"
+**How would you like to proceed?**
+</display>
 
 ### 4. Present MENU OPTIONS
 
@@ -175,12 +177,15 @@ Store conversion decision for next step:
 - **Edit requirements:** [user's requirements from step e-01]
 - **Gap analysis:** [summary of gaps identified]
 
-Display: "**Conversion Strategy Documented**
+Display:
+<display>
+**Conversion Strategy Documented**
 
 Mode: {conversion mode}
 Edit goals: {summary}
 
-**Proceeding to deep review...**"
+**Proceeding to deep review...**
+</display>
 
 Read fully and follow: {nextStepFile} (step-e-02-review.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-02-review.md

@@ -146,7 +146,8 @@ Return detailed change plan with section breakdown."
 
 Display:
 
-"**Deep Review Complete - Change Plan**
+<display>
+**Deep Review Complete - Change Plan**
 
 **PRD Analysis:**
 {Brief summary of PRD current state}
@@ -175,7 +176,8 @@ Display:
 2. Any sections I should add/remove/reprioritize?
 3. Any concerns before I proceed with edits?
 
-**Review the plan and let me know if you'd like any adjustments.**"
+**Review the plan and let me know if you'd like any adjustments.**
+</display>
 
 ### 5. Get User Confirmation
 
@@ -198,11 +200,14 @@ Store approved change plan for next step:
 - **Priority order:** Sequence to apply changes
 - **User confirmed:** Yes
 
-Display: "**Change Plan Approved**
+Display:
+<display>
+**Change Plan Approved**
 
 {Brief summary of approved plan}
 
-**Proceeding to edit step...**"
+**Proceeding to edit step...**
+</display>
 
 Read fully and follow: {nextStepFile} (step-e-03-edit.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-03-edit.md

@@ -64,13 +64,16 @@ From step e-02, retrieve:
 - **Priority order:** Sequence to apply changes
 - **User requirements:** Edit goals from step e-01
 
-Display: "**Starting PRD Edits**
+Display:
+<display>
+**Starting PRD Edits**
 
 **Change Plan:** {summary}
 **Total Changes:** {count}
 **Estimated Effort:** {effort level}
 
-**Proceeding with edits section by section...**"
+**Proceeding with edits section by section...**
+</display>
 
 ### 2. Attempt Sub-Process Edits (For Complex Changes)
 
@@ -120,9 +123,11 @@ Apply changes and return updated section."
 - Verify changes applied correctly
 
 **Display progress after each section:**
-"**Section Updated:** {section_name}
+<display>
+**Section Updated:** {section_name}
 Changes: {brief summary}
-{More sections remaining...}"
+{More sections remaining...}
+</display>
 
 ### 4. Handle Restructuring (If Needed)
 
@@ -145,9 +150,12 @@ Changes: {brief summary}
 8. Functional Requirements
 9. Non-Functional Requirements
 
-Display: "**PRD Restructured**
+Display:
+<display>
+**PRD Restructured**
 BMAD standard structure applied.
-{Sections added/reordered}"
+{Sections added/reordered}
+</display>
 
 ### 5. Update PRD Frontmatter
 
@@ -194,7 +202,8 @@ editHistory:
 
 Display:
 
-"**PRD Edits Complete**
+<display>
+**PRD Edits Complete**
 
 **Changes Applied:** {count} sections modified
 **PRD Updated:** {prd_file_path}
@@ -206,7 +215,8 @@ Display:
 - Use in downstream workflows (UX, Architecture)
 - Validation (if not yet validated)
 
-**What would you like to do next?**"
+**What would you like to do next?**
+</display>
 
 ### 8. Present MENU OPTIONS
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md

@@ -4,7 +4,7 @@ description: 'Complete & Validate - Present options for next steps including ful
 
 # File references (ONLY variables used in this step)
 prdFile: '{prd_file_path}'
-validationWorkflow: './steps-v/step-v-01-discovery.md'
+validationWorkflow: '../steps-v/step-v-01-discovery.md'
 ---
 
 # Step E-4: Complete & Validate
@@ -80,7 +80,8 @@ From step e-03 change execution, compile:
 
 Display:
 
-"**✓ PRD Edit Complete**
+<display>
+**✓ PRD Edit Complete**
 
 **Updated PRD:** {prd_file_path}
 
@@ -97,7 +98,8 @@ Display:
 - Validation to ensure quality
 - Production use
 
-**What would you like to do next?**"
+**What would you like to do next?**
+</display>
 
 ### 3. Present MENU OPTIONS
 
@@ -116,15 +118,21 @@ Display:
 #### Menu Handling Logic:
 
 - **IF V (Run Full Validation):**
-  - Display: "**Starting Validation Workflow**"
+  - Display:
-  - Display: "This will run all 13 validation checks on the updated PRD."
+    <display>
-  - Display: "Preparing to validate: {prd_file_path}"
+    **Starting Validation Workflow**
-  - Display: "**Proceeding to validation...**"
+
+    This will run all 13 validation checks on the updated PRD.
+
+    Preparing to validate: {prd_file_path}
+
+    **Proceeding to validation...**
+    </display>
   - Read fully and follow: {validationWorkflow} (steps-v/step-v-01-discovery.md)
   - Note: This hands off to the validation workflow which will run its complete 13-step process
 
 - **IF E (Edit More):**
-  - Display: "**Additional Edits**"
+  - <display>**Additional Edits**</display>
   - Ask: "What additional edits would you like to make?"
   - Accept input, then display: "**Returning to edit step...**"
   - Read fully and follow: step-e-03-edit.md again
@@ -134,12 +142,12 @@ Display:
     - Complete list of all changes made
     - Before/after comparison (key improvements)
     - Recommendations for next steps
-  - Display: "**Edit Workflow Complete**"
+  - <display>**Edit Workflow Complete**</display>
   - Exit
 
 - **IF X (Exit):**
   - Display summary
-  - Display: "**Edit Workflow Complete**"
+  - <display>**Edit Workflow Complete**</display>
   - Exit
 
 - **IF Any other:** Help user, then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md

@@ -71,11 +71,14 @@ This file contains the BMAD PRD philosophy, standards, and validation criteria t
 - Use provided path
 
 **If no PRD path provided:**
-"**PRD Validation Workflow**
+
+<display>
+**PRD Validation Workflow**
 
 Which PRD would you like to validate?
 
-Please provide the path to the PRD file you want to validate."
+Please provide the path to the PRD file you want to validate.
+</display>
 
 **Wait for user to provide PRD path.**
 
@@ -112,7 +115,8 @@ For each document listed in `inputDocuments`:
 
 ### 6. Ask About Additional Reference Documents
 
-"**I've loaded the following documents from your PRD frontmatter:**
+<display>
+**I've loaded the following documents from your PRD frontmatter:**
 
 {list loaded documents with file names}
 
@@ -124,7 +128,8 @@ These could include:
 - Standards or compliance documents
 - Competitive analysis or benchmarks
 
-Please provide paths to any additional documents, or type 'none' to proceed."
+Please provide paths to any additional documents, or type 'none' to proceed.
+</display>
 
 **Load any additional documents provided by user.**
 
@@ -161,7 +166,8 @@ validationStatus: IN_PROGRESS
 
 ### 8. Present Discovery Summary
 
-"**Setup Complete!**
+<display>
+**Setup Complete!**
 
 **PRD to Validate:** {prd_path}
 
@@ -173,11 +179,16 @@ validationStatus: IN_PROGRESS
 
 **Validation Report:** {validationReportPath}
 
-**Ready to begin validation.**"
+**Ready to begin validation.**
+</display>
 
 ### 9. Present MENU OPTIONS
 
-Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Format Detection
+Display:
+
+<display>
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Format Detection
+</display>
 
 #### EXECUTION RULES:
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02-format-detection.md

@@ -132,19 +132,27 @@ Append to validation report:
 
 **IF format is BMAD Standard or BMAD Variant:**
 
-Display: "**Format Detected:** {classification}
+Display:
 
-Proceeding to systematic validation checks..."
+<display>
+**Format Detected:** {classification}
+
+Proceeding to systematic validation checks...
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-03-density-validation.md)
 
 **IF format is Non-Standard (< 3 core sections):**
 
-Display: "**Format Detected:** Non-Standard PRD
+Display:
+
+<display>
+**Format Detected:** Non-Standard PRD
 
 This PRD does not follow BMAD standard structure (only {count}/6 core sections present).
 
-You have options:"
+You have options:
+</display>
 
 Present MENU OPTIONS below for user selection
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02b-parity-check.md

@@ -155,7 +155,8 @@ Append to validation report:
 
 Display:
 
-"**Parity Analysis Complete**
+<display>
+**Parity Analysis Complete**
 
 Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to reach BMAD standard is: **{effort level}**
 
@@ -165,7 +166,8 @@ Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to r
 **Recommendation:**
 {recommendation from analysis}
 
-**How would you like to proceed?**"
+**How would you like to proceed?**
+</display>
 
 ### 5. Present MENU OPTIONS
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-03-density-validation.md

@@ -142,11 +142,15 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display: "**Information Density Validation Complete**
+Display:
+
+<display>
+**Information Density Validation Complete**
 
 Severity: {Critical/Warning/Pass}
 
-**Proceeding to next validation check...**"
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-04-brief-coverage-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-04-brief-coverage-validation.md

@@ -72,9 +72,13 @@ Append to validation report:
 **Status:** N/A - No Product Brief was provided as input
 ```
 
-Display: "**Product Brief Coverage: Skipped** (No Product Brief provided)
+Display:
 
-**Proceeding to next validation check...**"
+<display>
+**Product Brief Coverage: Skipped** (No Product Brief provided)
+
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile}
 
@@ -180,11 +184,15 @@ Append to validation report:
 
 ### 6. Display Progress and Auto-Proceed
 
-Display: "**Product Brief Coverage Validation Complete**
+Display:
+
+<display>
+**Product Brief Coverage Validation Complete**
 
 Overall Coverage: {assessment}
 
-**Proceeding to next validation check...**"
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-05-measurability-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-05-measurability-validation.md

@@ -195,11 +195,15 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display: "**Measurability Validation Complete**
+Display:
+
+<display>
+**Measurability Validation Complete**
 
 Total Violations: {count} ({severity})
 
-**Proceeding to next validation check...**"
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-06-traceability-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-06-traceability-validation.md

@@ -183,11 +183,15 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display: "**Traceability Validation Complete**
+Display:
+
+<display>
+**Traceability Validation Complete**
 
 Total Issues: {count} ({severity})
 
-**Proceeding to next validation check...**"
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-07-implementation-leakage-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-07-implementation-leakage-validation.md

@@ -172,11 +172,15 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display: "**Implementation Leakage Validation Complete**
+Display:
+
+<display>
+**Implementation Leakage Validation Complete**
 
 Total Violations: {count} ({severity})
 
-**Proceeding to next validation check...**"
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-08-domain-compliance-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-08-domain-compliance-validation.md

@@ -155,11 +155,15 @@ Append to validation report:
 **Note:** This PRD is for a standard domain without regulatory compliance requirements.
 ```
 
-Display: "**Domain Compliance Validation Skipped**
+Display:
+
+<display>
+**Domain Compliance Validation Skipped**
 
 Domain: {domain} (low complexity)
 
-**Proceeding to next validation check...**"
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile}
 
@@ -206,12 +210,16 @@ Append to validation report:
 
 ### 7. Display Progress and Auto-Proceed
 
-Display: "**Domain Compliance Validation Complete**
+Display:
+
+<display>
+**Domain Compliance Validation Complete**
 
 Domain: {domain} ({complexity})
 Compliance Status: {status}
 
-**Proceeding to next validation check...**"
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-09-project-type-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-09-project-type-validation.md

@@ -227,12 +227,16 @@ Append to validation report:
 
 ### 7. Display Progress and Auto-Proceed
 
-Display: "**Project-Type Compliance Validation Complete**
+Display:
+
+<display>
+**Project-Type Compliance Validation Complete**
 
 Project Type: {projectType}
 Compliance: {score}%
 
-**Proceeding to next validation check...**"
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-10-smart-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md

@@ -173,11 +173,15 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display: "**SMART Requirements Validation Complete**
+Display:
+
+<display>
+**SMART Requirements Validation Complete**
 
 FR Quality: {percentage}% with acceptable scores ({severity})
 
-**Proceeding to next validation check...**"
+**Proceeding to next validation check...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-11-holistic-quality-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md

@@ -226,11 +226,15 @@ Append to validation report:
 
 ### 4. Display Progress and Auto-Proceed
 
-Display: "**Holistic Quality Assessment Complete**
+Display:
+
+<display>
+**Holistic Quality Assessment Complete**
 
 Overall Rating: {rating}/5 - {label}
 
-**Proceeding to final validation checks...**"
+**Proceeding to final validation checks...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-12-completeness-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-12-completeness-validation.md

@@ -206,11 +206,15 @@ Append to validation report:
 
 ### 4. Display Progress and Auto-Proceed
 
-Display: "**Completeness Validation Complete**
+Display:
+
+<display>
+**Completeness Validation Complete**
 
 Overall Completeness: {percentage}% ({severity})
 
-**Proceeding to final step...**"
+**Proceeding to final step...**
+</display>
 
 Without delay, read fully and follow: {nextStepFile} (step-v-13-report-complete.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md

@@ -125,7 +125,8 @@ overallStatus: '{Pass/Warning/Critical based on all findings}'
 
 Display:
 
-"**✓ PRD Validation Complete**
+<display>
+**✓ PRD Validation Complete**
 
 **Overall Status:** {Pass/Warning/Critical}
 
@@ -154,7 +155,8 @@ Display:
 - Warning: "PRD is usable but has issues that should be addressed. Review warnings and improve where needed."
 - Critical: "PRD has significant issues that should be fixed before use. Focus on critical issues above."}
 
-**What would you like to do next?**"
+**What would you like to do next?**
+</display>
 
 ### 5. Present MENU OPTIONS
 
@@ -195,8 +197,12 @@ Display:
   - Return to menu
 
 - **IF X (Exit):**
-  - Display: "**Validation Report Saved:** {validationReportPath}"
+  - Display:
-  - Display: "**Summary:** {overall status} - {recommendation}"
+    <display>
+    **Validation Report Saved:** {validationReportPath}
+
+    **Summary:** {overall status} - {recommendation}
+    </display>
   - PRD Validation complete. Read fully and follow: `_bmad/core/tasks/bmad-help.md` with argument `Validate PRD`.
 
 - **IF Any other:** Help user, then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md

@@ -290,8 +290,8 @@ editWorkflow: './steps-e/step-e-01-discovery.md'
 - ✅ Proper workflow path configuration
 
 **2. External Workflow References:**
-- ✅ Party-mode workflow: Exists at `/src/core/workflows/party-mode/workflow.md`
+- ✅ Party-mode workflow: Exists at `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
-- ✅ Advanced-elicitation task: Exists at `/src/core/workflows/advanced-elicitation/workflow.xml`
+- ✅ Advanced-elicitation task: Exists at `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml`
 
 **3. Directory Structure:**
 - ✅ Complete step architecture (all 3 modes)

src/bmm/workflows/2-plan-workflows/create-prd/workflow.md

@@ -40,30 +40,53 @@ Determine which mode to invoke based on:
 3. **Menu Selection (if unclear):**
 
 If mode cannot be determined from invocation:
-"**PRD Workflow - Select Mode:**
+
+<display>
+**PRD Workflow - Select Mode:**
 
 **[C] Create** - Create a new PRD from scratch
 **[V] Validate** - Validate an existing PRD against BMAD standards
 **[E] Edit** - Improve an existing PRD
 
-Which mode would you like?"
+Which mode would you like?
+</display>
 
 Wait for user selection.
 
 ### Route to Appropriate Workflow
 
 **IF Create Mode:**
-"**Create Mode: Creating a new PRD from scratch.**"
+
+<display>
+**Create Mode: Creating a new PRD from scratch.**
+</display>
+
 Read fully and follow: `{nextStep}` (steps-c/step-01-init.md)
 
 **IF Validate Mode:**
-"**Validate Mode: Validating an existing PRD against BMAD standards.**"
+
-Prompt for PRD path: "Which PRD would you like to validate? Please provide the path to the PRD.md file."
+<display>
+**Validate Mode: Validating an existing PRD against BMAD standards.**
+</display>
+
+Prompt for PRD path:
+
+<display>
+Which PRD would you like to validate? Please provide the path to the PRD.md file.
+</display>
 Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
 
 **IF Edit Mode:**
-"**Edit Mode: Improving an existing PRD.**"
+
-Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
+<display>
+**Edit Mode: Improving an existing PRD.**
+</display>
+
+Prompt for PRD path:
+
+<display>
+Which PRD would you like to edit? Please provide the path to the PRD.md file.
+</display>
 Then read fully and follow: `{editWorkflow}` (steps-e/step-e-01-discovery.md)
 
 ---
@@ -113,13 +136,15 @@ This uses **step-file architecture** for disciplined execution:
 
 **If mode is still unclear, ask user:**
 
-"**PRD Workflow - Select Mode:**
+<display>
+**PRD Workflow - Select Mode:**
 
 **[C] Create** - Create a new PRD from scratch
 **[V] Validate** - Validate an existing PRD against BMAD standards
 **[E] Edit** - Improve an existing PRD
 
-Which mode would you like?"
+Which mode would you like?
+</display>
 
 Wait for user selection.
 
@@ -136,15 +161,37 @@ Load and read full config from {main_config} and resolve:
 ### 3. Route to Appropriate Workflow
 
 **IF mode == create:**
-"**Create Mode: Creating a new PRD from scratch.**"
+
+<display>
+**Create Mode: Creating a new PRD from scratch.**
+</display>
+
 Read fully and follow: `{nextStep}` (steps-c/step-01-init.md)
 
 **IF mode == validate:**
-"**Validate Mode: Validating an existing PRD against BMAD standards.**"
+
-Prompt for PRD path: "Which PRD would you like to validate? Please provide the path to the PRD.md file."
+<display>
+**Validate Mode: Validating an existing PRD against BMAD standards.**
+</display>
+
+Prompt for PRD path:
+
+<display>
+Which PRD would you like to validate? Please provide the path to the PRD.md file.
+</display>
+
 Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
 
 **IF mode == edit:**
-"**Edit Mode: Improving an existing PRD.**"
+
-Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
+<display>
+**Edit Mode: Improving an existing PRD.**
+</display>
+
+Prompt for PRD path:
+
+<display>
+Which PRD would you like to edit? Please provide the path to the PRD.md file.
+</display>
+
 Then read fully and follow: `{editWorkflow}` (steps-e/step-e-01-discovery.md)

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md

@@ -94,7 +94,8 @@ Complete setup and report to user:
 
 **Input Documents Discovered:**
 Report what was found:
-"Welcome {{user_name}}! I've set up your UX design workspace for {{project_name}}.
+<display>
+Welcome {{user_name}}! I've set up your UX design workspace for {{project_name}}.
 
 **Documents Found:**
 
@@ -106,7 +107,8 @@ Report what was found:
 
 Do you have any other documents you'd like me to include, or shall we continue to the next step?
 
-[C] Continue to UX discovery"
+[C] Continue to UX discovery
+</display>
 
 ## NEXT STEP:
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md

@@ -52,7 +52,8 @@ Reload the context documents listed in `inputDocuments`:
 ### 3. Summarize Current Progress
 
 Welcome the user back and provide context:
-"Welcome back {{user_name}}! I'm resuming our UX design collaboration for {{project_name}}.
+<display>
+Welcome back {{user_name}}! I'm resuming our UX design collaboration for {{project_name}}.
 
 **Current Progress:**
 
@@ -66,7 +67,8 @@ Welcome the user back and provide context:
 - Current UX design document is ready with all completed sections
 - Ready to continue from where we left off
 
-Does this look right, or do you want to make any adjustments before we proceed?"
+Does this look right, or do you want to make any adjustments before we proceed?
+</display>
 
 ### 4. Determine Next Step
 
@@ -81,9 +83,11 @@ Based on `lastStep` value, determine which step to load next:
 ### 5. Present Continuation Options
 
 After presenting current progress, ask:
-"Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
+<display>
+Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
 
-[C] Continue to Step {nextStepNumber}"
+[C] Continue to Step {nextStepNumber}
+</display>
 
 ## SUCCESS METRICS:
 
@@ -106,7 +110,8 @@ After presenting current progress, ask:
 ## WORKFLOW ALREADY COMPLETE?
 
 If `lastStep` indicates the final step is completed:
-"Great news! It looks like we've already completed the UX design workflow for {{project_name}}.
+<display>
+Great news! It looks like we've already completed the UX design workflow for {{project_name}}.
 
 The final UX design specification is ready at {output_folder}/ux-design-specification.md with all sections completed through step {finalStepNumber}.
 
@@ -118,7 +123,8 @@ Would you like me to:
 - Suggest next workflow steps (like wireframe generation or architecture)
 - Start a new UX design revision
 
-What would be most helpful?"
+What would be most helpful?
+</display>
 
 ## NEXT STEP:
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md

@@ -51,7 +51,8 @@ Understand the project context, target users, and what makes this product specia
 ### 1. Review Loaded Context
 
 Start by analyzing what we know from the loaded documents:
-"Based on the project documentation we have loaded, let me confirm what I'm understanding about {{project_name}}.
+<display>
+Based on the project documentation we have loaded, let me confirm what I'm understanding about {{project_name}}.
 
 **From the documents:**
 {summary of key insights from loaded PRD, briefs, and other context documents}
@@ -62,12 +63,14 @@ Start by analyzing what we know from the loaded documents:
 **Key Features/Goals:**
 {summary of main features and goals from loaded documents}
 
-Does this match your understanding? Are there any corrections or additions you'd like to make?"
+Does this match your understanding? Are there any corrections or additions you'd like to make?
+</display>
 
 ### 2. Fill Context Gaps (If no documents or gaps exist)
 
 If no documents were loaded or key information is missing:
-"Since we don't have complete documentation, let's start with the essentials:
+<display>
+Since we don't have complete documentation, let's start with the essentials:
 
 **What are you building?** (Describe your product in 1-2 sentences)
 
@@ -75,12 +78,14 @@ If no documents were loaded or key information is missing:
 
 **What makes this special or different?** (What's the unique value proposition?)
 
-**What's the main thing users will do with this?** (Core user action or goal)"
+**What's the main thing users will do with this?** (Core user action or goal)
+</display>
 
 ### 3. Explore User Context Deeper
 
 Dive into user understanding:
-"Let me understand your users better to inform the UX design:
+<display>
+Let me understand your users better to inform the UX design:
 
 **User Context Questions:**
 
@@ -89,12 +94,14 @@ Dive into user understanding:
 - What would make them say 'this is exactly what I needed'?
 - How tech-savvy are your target users?
 - What devices will they use most?
-- When/where will they use this product?"
+- When/where will they use this product?
+</display>
 
 ### 4. Identify UX Design Challenges
 
 Surface the key UX challenges to address:
-"From what we've discussed, I'm seeing some key UX design considerations:
+<display>
+From what we've discussed, I'm seeing some key UX design considerations:
 
 **Design Challenges:**
 
@@ -107,7 +114,8 @@ Surface the key UX challenges to address:
 - [Identify 2-3 areas where great UX could create competitive advantage]
 - [Note any opportunities for innovative UX patterns]
 
-Does this capture the key UX considerations we need to address?"
+Does this capture the key UX considerations we need to address?
+</display>
 
 ### 5. Generate Project Understanding Content
 
@@ -140,14 +148,16 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 6. Present Content and Menu
 
 Show the generated project understanding content and present choices:
-"I've documented our understanding of {{project_name}} from a UX perspective. This will guide all our design decisions moving forward.
+<display>
+I've documented our understanding of {{project_name}} from a UX perspective. This will guide all our design decisions moving forward.
 
 **Here's what I'll add to the document:**
 
 [Show the complete markdown content from step 5]
 
 **What would you like to do?**
-[C] Continue - Save this to the document and move to core experience definition"
+[C] Continue - Save this to the document and move to core experience definition
+</display>
 
 ### 7. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md

@@ -51,7 +51,8 @@ Define the core user experience, platform requirements, and what makes the inter
 ### 1. Define Core User Action
 
 Start by identifying the most important user interaction:
-"Now let's dig into the heart of the user experience for {{project_name}}.
+<display>
+Now let's dig into the heart of the user experience for {{project_name}}.
 
 **Core Experience Questions:**
 
@@ -60,12 +61,14 @@ Start by identifying the most important user interaction:
 - What should be completely effortless for users?
 - If we nail one interaction, everything else follows - what is it?
 
-Think about the core loop or primary action that defines your product's value."
+Think about the core loop or primary action that defines your product's value.
+</display>
 
 ### 2. Explore Platform Requirements
 
 Determine where and how users will interact:
-"Let's define the platform context for {{project_name}}:
+<display>
+Let's define the platform context for {{project_name}}:
 
 **Platform Questions:**
 
@@ -73,34 +76,40 @@ Determine where and how users will interact:
 - Will this be primarily touch-based or mouse/keyboard?
 - Any specific platform requirements or constraints?
 - Do we need to consider offline functionality?
-- Any device-specific capabilities we should leverage?"
+- Any device-specific capabilities we should leverage?
+</display>
 
 ### 3. Identify Effortless Interactions
 
 Surface what should feel magical or completely seamless:
-"**Effortless Experience Design:**
+<display>
+**Effortless Experience Design:**
 
 - What user actions should feel completely natural and require zero thought?
 - Where do users currently struggle with similar products?
 - What interaction, if made effortless, would create delight?
 - What should happen automatically without user intervention?
-- Where can we eliminate steps that competitors require?"
+- Where can we eliminate steps that competitors require?
+</display>
 
 ### 4. Define Critical Success Moments
 
 Identify the moments that determine success or failure:
-"**Critical Success Moments:**
+<display>
+**Critical Success Moments:**
 
 - What's the moment where users realize 'this is better'?
 - When does the user feel successful or accomplished?
 - What interaction, if failed, would ruin the experience?
 - What are the make-or-break user flows?
-- Where does first-time user success happen?"
+- Where does first-time user success happen?
+</display>
 
 ### 5. Synthesize Experience Principles
 
 Extract guiding principles from the conversation:
-"Based on our discussion, I'm hearing these core experience principles for {{project_name}}:
+<display>
+Based on our discussion, I'm hearing these core experience principles for {{project_name}}:
 
 **Experience Principles:**
 
@@ -109,7 +118,8 @@ Extract guiding principles from the conversation:
 - [Principle 3 based on platform considerations]
 - [Principle 4 based on critical success moments]
 
-These principles will guide all our UX decisions. Do these capture what's most important?"
+These principles will guide all our UX decisions. Do these capture what's most important?
+</display>
 
 ### 6. Generate Core Experience Content
 
@@ -146,7 +156,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated core experience content and present choices:
-"I've defined the core user experience for {{project_name}} based on our conversation. This establishes the foundation for all our UX design decisions.
+<display>
+I've defined the core user experience for {{project_name}} based on our conversation. This establishes the foundation for all our UX design decisions.
 
 **Here's what I'll add to the document:**
 
@@ -155,7 +166,8 @@ Show the generated core experience content and present choices:
 **What would you like to do?**
 [A] Advanced Elicitation - Let's refine the core experience definition
 [P] Party Mode - Bring different perspectives on the user experience
-[C] Continue - Save this to the document and move to emotional response definition"
+[C] Continue - Save this to the document and move to emotional response definition
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md

@@ -51,7 +51,8 @@ Define the desired emotional responses users should feel when using the product.
 ### 1. Explore Core Emotional Goals
 
 Start by understanding the emotional objectives:
-"Now let's think about how {{project_name}} should make users feel.
+<display>
+Now let's think about how {{project_name}} should make users feel.
 
 **Emotional Response Questions:**
 
@@ -60,23 +61,27 @@ Start by understanding the emotional objectives:
 - How should users feel after accomplishing their primary goal?
 - What feeling differentiates this from competitors?
 
-Common emotional goals: Empowered and in control? Delighted and surprised? Efficient and productive? Creative and inspired? Calm and focused? Connected and engaged?"
+Common emotional goals: Empowered and in control? Delighted and surprised? Efficient and productive? Creative and inspired? Calm and focused? Connected and engaged?
+</display>
 
 ### 2. Identify Emotional Journey Mapping
 
 Explore feelings at different stages:
-"**Emotional Journey Considerations:**
+<display>
+**Emotional Journey Considerations:**
 
 - How should users feel when they first discover the product?
 - What emotion during the core experience/action?
 - How should they feel after completing their task?
 - What if something goes wrong - what emotional response do we want?
-- How should they feel when returning to use it again?"
+- How should they feel when returning to use it again?
+</display>
 
 ### 3. Define Micro-Emotions
 
 Surface subtle but important emotional states:
-"**Micro-Emotions to Consider:**
+<display>
+**Micro-Emotions to Consider:**
 
 - Confidence vs. Confusion
 - Trust vs. Skepticism
@@ -85,12 +90,14 @@ Surface subtle but important emotional states:
 - Delight vs. Satisfaction
 - Belonging vs. Isolation
 
-Which of these emotional states are most critical for your product's success?"
+Which of these emotional states are most critical for your product's success?
+</display>
 
 ### 4. Connect Emotions to UX Decisions
 
 Link feelings to design implications:
-"**Design Implications:**
+<display>
+**Design Implications:**
 
 - If we want users to feel [emotional state], what UX choices support this?
 - What interactions might create negative emotions we want to avoid?
@@ -101,18 +108,21 @@ Link feelings to design implications:
 
 - [Emotion 1] → [UX design approach]
 - [Emotion 2] → [UX design approach]
-- [Emotion 3] → [UX design approach]"
+- [Emotion 3] → [UX design approach]
+</display>
 
 ### 5. Validate Emotional Goals
 
 Check if emotional goals align with product vision:
-"Let me make sure I understand the emotional vision for {{project_name}}:
+<display>
+Let me make sure I understand the emotional vision for {{project_name}}:
 
 **Primary Emotional Goal:** [Summarize main emotional response]
 **Secondary Feelings:** [List supporting emotional states]
 **Emotions to Avoid:** [List negative emotions to prevent]
 
-Does this capture the emotional experience you want to create? Any adjustments needed?"
+Does this capture the emotional experience you want to create? Any adjustments needed?
+</display>
 
 ### 6. Generate Emotional Response Content
 
@@ -149,7 +159,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated emotional response content and present choices:
-"I've defined the desired emotional responses for {{project_name}}. These emotional goals will guide our design decisions to create the right user experience.
+<display>
+I've defined the desired emotional responses for {{project_name}}. These emotional goals will guide our design decisions to create the right user experience.
 
 **Here's what I'll add to the document:**
 
@@ -158,7 +169,8 @@ Show the generated emotional response content and present choices:
 **What would you like to do?**
 [A] Advanced Elicitation - Let's refine the emotional response definition
 [P] Party Mode - Bring different perspectives on user emotional needs
-[C] Continue - Save this to the document and move to inspiration analysis"
+[C] Continue - Save this to the document and move to inspiration analysis
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md

@@ -51,7 +51,8 @@ Analyze inspiring products and UX patterns to inform design decisions for the cu
 ### 1. Identify User's Favorite Apps
 
 Start by gathering inspiration sources:
-"Let's learn from products your users already love and use regularly.
+<display>
+Let's learn from products your users already love and use regularly.
 
 **Inspiration Questions:**
 
@@ -60,12 +61,14 @@ Start by gathering inspiration sources:
 - What makes the experience compelling or delightful?
 - What keeps users coming back to these apps?
 
-Think about apps in your category or even unrelated products that have great UX."
+Think about apps in your category or even unrelated products that have great UX.
+</display>
 
 ### 2. Analyze UX Patterns and Principles
 
 Break down what makes these apps successful:
-"For each inspiring app, let's analyze their UX success:
+<display>
+For each inspiring app, let's analyze their UX success:
 
 **For [App Name]:**
 
@@ -74,12 +77,14 @@ Break down what makes these apps successful:
 - How do they handle navigation and information hierarchy?
 - What are their most innovative or delightful interactions?
 - What visual design choices support the user experience?
-- How do they handle errors or edge cases?"
+- How do they handle errors or edge cases?
+</display>
 
 ### 3. Extract Transferable Patterns
 
 Identify patterns that could apply to your project:
-"**Transferable UX Patterns:**
+<display>
+**Transferable UX Patterns:**
 Looking across these inspiring apps, I see patterns we could adapt:
 
 **Navigation Patterns:**
@@ -97,24 +102,28 @@ Looking across these inspiring apps, I see patterns we could adapt:
 - [Pattern 1] - supports your [emotional goal]
 - [Pattern 2] - aligns with your [platform requirements]
 
-Which of these patterns resonate most for your product?"
+Which of these patterns resonate most for your product?
+</display>
 
 ### 4. Identify Anti-Patterns to Avoid
 
 Surface what not to do based on analysis:
-"**UX Anti-Patterns to Avoid:**
+<display>
+**UX Anti-Patterns to Avoid:**
 From analyzing both successes and failures in your space, here are patterns to avoid:
 
 - [Anti-pattern 1] - users find this confusing/frustrating
 - [Anti-pattern 2] - this creates unnecessary friction
 - [Anti-pattern 3] - doesn't align with your [emotional goals]
 
-Learning from others' mistakes is as important as learning from their successes."
+Learning from others' mistakes is as important as learning from their successes.
+</display>
 
 ### 5. Define Design Inspiration Strategy
 
 Create a clear strategy for using this inspiration:
-"**Design Inspiration Strategy:**
+<display>
+**Design Inspiration Strategy:**
 
 **What to Adopt:**
 
@@ -131,7 +140,8 @@ Create a clear strategy for using this inspiration:
 - [Specific anti-pattern] - conflicts with [your goals]
 - [Specific anti-pattern] - doesn't fit [your platform]
 
-This strategy will guide our design decisions while keeping {{project_name}} unique."
+This strategy will guide our design decisions while keeping {{project_name}} unique.
+</display>
 
 ### 6. Generate Inspiration Analysis Content
 
@@ -164,7 +174,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated inspiration analysis content and present choices:
-"I've analyzed inspiring UX patterns and products to inform our design strategy for {{project_name}}. This gives us a solid foundation of proven patterns to build upon.
+<display>
+I've analyzed inspiring UX patterns and products to inform our design strategy for {{project_name}}. This gives us a solid foundation of proven patterns to build upon.
 
 **Here's what I'll add to the document:**
 
@@ -173,7 +184,8 @@ Show the generated inspiration analysis content and present choices:
 **What would you like to do?**
 [A] Advanced Elicitation - Let's deepen our UX pattern analysis
 [P] Party Mode - Bring different perspectives on inspiration sources
-[C] Continue - Save this to the document and move to design system choice"
+[C] Continue - Save this to the document and move to design system choice
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md

@@ -51,7 +51,8 @@ Choose appropriate design system approach based on project requirements and cons
 ### 1. Present Design System Options
 
 Educate about design system approaches:
-"For {{project_name}}, we need to choose a design system foundation. Think of design systems like LEGO blocks for UI - they provide proven components and patterns, ensuring consistency and speeding development.
+<display>
+For {{project_name}}, we need to choose a design system foundation. Think of design systems like LEGO blocks for UI - they provide proven components and patterns, ensuring consistency and speeding development.
 
 **Design System Approaches:**
 
@@ -76,12 +77,14 @@ Educate about design system approaches:
 - Moderate learning curve
 - Good balance of speed and uniqueness
 
-Which direction feels right for your project?"
+Which direction feels right for your project?
+</display>
 
 ### 2. Analyze Project Requirements
 
 Guide decision based on project context:
-"**Let's consider your specific needs:**
+<display>
+**Let's consider your specific needs:**
 
 **Based on our previous conversations:**
 
@@ -97,12 +100,14 @@ Guide decision based on project context:
 - Brand guidelines or existing visual identity
 - Team's design expertise
 - Long-term maintenance considerations
-- Integration requirements with existing systems"
+- Integration requirements with existing systems
+</display>
 
 ### 3. Explore Specific Design System Options
 
 Dive deeper into relevant options:
-"**Recommended Options Based on Your Needs:**
+<display>
+**Recommended Options Based on Your Needs:**
 
 **For [Your Platform Type]:**
 
@@ -117,12 +122,14 @@ Dive deeper into relevant options:
 - Customization capabilities
 - Accessibility compliance
 - Performance characteristics
-- Learning curve for your team"
+- Learning curve for your team
+</display>
 
 ### 4. Facilitate Decision Process
 
 Help user make informed choice:
-"**Decision Framework:**
+<display>
+**Decision Framework:**
 
 1. What's most important: Speed, uniqueness, or balance?
 2. How much design expertise does your team have?
@@ -130,12 +137,14 @@ Help user make informed choice:
 4. What's your timeline and budget?
 5. Long-term maintenance needs?
 
-Let's evaluate options based on your answers to these questions."
+Let's evaluate options based on your answers to these questions.
+</display>
 
 ### 5. Finalize Design System Choice
 
 Confirm and document the decision:
-"Based on our analysis, I recommend [Design System Choice] for {{project_name}}.
+<display>
+Based on our analysis, I recommend [Design System Choice] for {{project_name}}.
 
 **Rationale:**
 
@@ -149,7 +158,8 @@ Confirm and document the decision:
 - Define component strategy for custom components needed
 - Establish design tokens and patterns
 
-Does this design system choice feel right to you?"
+Does this design system choice feel right to you?
+</display>
 
 ### 6. Generate Design System Content
 
@@ -182,7 +192,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated design system content and present choices:
-"I've documented our design system choice for {{project_name}}. This foundation will ensure consistency and speed up development.
+<display>
+I've documented our design system choice for {{project_name}}. This foundation will ensure consistency and speed up development.
 
 **Here's what I'll add to the document:**
 
@@ -192,6 +203,7 @@ Show the generated design system content and present choices:
 [A] Advanced Elicitation - Let's refine our design system decision
 [P] Party Mode - Bring technical perspectives on design systems
 [C] Continue - Save this to the document and move to defining experience
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md

@@ -51,7 +51,8 @@ Define the core interaction that, if nailed, makes everything else follow in the
 ### 1. Identify the Defining Experience
 
 Focus on the core interaction:
-"Every successful product has a defining experience - the core interaction that, if we nail it, everything else follows.
+<display>
+Every successful product has a defining experience - the core interaction that, if we nail it, everything else follows.
 
 **Think about these famous examples:**
 
@@ -63,12 +64,14 @@ Focus on the core interaction:
 **For {{project_name}}:**
 What's the core action that users will describe to their friends?
 What's the interaction that makes users feel successful?
-If we get ONE thing perfectly right, what should it be?"
+If we get ONE thing perfectly right, what should it be?
+</display>
 
 ### 2. Explore the User's Mental Model
 
 Understand how users think about the core task:
-"**User Mental Model Questions:**
+<display>
+**User Mental Model Questions:**
 
 - How do users currently solve this problem?
 - What mental model do they bring to this task?
@@ -79,12 +82,14 @@ Understand how users think about the core task:
 
 - What do users love/hate about existing approaches?
 - What shortcuts or workarounds do they use?
-- What makes existing solutions feel magical or terrible?"
+- What makes existing solutions feel magical or terrible?
+</display>
 
 ### 3. Define Success Criteria for Core Experience
 
 Establish what makes the core interaction successful:
-"**Core Experience Success Criteria:**
+<display>
+**Core Experience Success Criteria:**
 
 - What makes users say 'this just works'?
 - When do they feel smart or accomplished?
@@ -96,12 +101,14 @@ Establish what makes the core interaction successful:
 
 - [Success indicator 1]
 - [Success indicator 2]
-- [Success indicator 3]"
+- [Success indicator 3]
+</display>
 
 ### 4. Identify Novel vs. Established Patterns
 
 Determine if we need to innovate or can use proven patterns:
-"**Pattern Analysis:**
+<display>
+**Pattern Analysis:**
 Looking at your core experience, does this:
 
 - Use established UX patterns that users already understand?
@@ -118,12 +125,14 @@ Looking at your core experience, does this:
 
 - Which proven patterns should we adopt?
 - How can we innovate within familiar patterns?
-- What's our unique twist on established interactions?"
+- What's our unique twist on established interactions?
+</display>
 
 ### 5. Define Experience Mechanics
 
 Break down the core interaction into details:
-"**Core Experience Mechanics:**
+<display>
+**Core Experience Mechanics:**
 Let's design the step-by-step flow for [defining experience]:
 
 **1. Initiation:**
@@ -147,7 +156,8 @@ Let's design the step-by-step flow for [defining experience]:
 
 - How do users know they're done?
 - What's the successful outcome?
-- What's next?"
+- What's next?
+</display>
 
 ### 6. Generate Defining Experience Content
 
@@ -184,7 +194,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated defining experience content and present choices:
-"I've defined the core experience for {{project_name}} - the interaction that will make users love this product.
+<display>
+I've defined the core experience for {{project_name}} - the interaction that will make users love this product.
 
 **Here's what I'll add to the document:**
 
@@ -194,6 +205,7 @@ Show the generated defining experience content and present choices:
 [A] Advanced Elicitation - Let's refine the core experience definition
 [P] Party Mode - Bring different perspectives on the defining interaction
 [C] Continue - Save this to the document and move to visual foundation
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md

@@ -51,24 +51,29 @@ Establish the visual design foundation including color themes, typography, and s
 ### 1. Brand Guidelines Assessment
 
 Check for existing brand requirements:
-"Do you have existing brand guidelines or a specific color palette I should follow? (y/n)
+<display>
+Do you have existing brand guidelines or a specific color palette I should follow? (y/n)
 
 If yes, I'll extract and document your brand colors and create semantic color mappings.
-If no, I'll generate theme options based on your project's personality and emotional goals from our earlier discussion."
+If no, I'll generate theme options based on your project's personality and emotional goals from our earlier discussion.
+</display>
 
 ### 2. Generate Color Theme Options (If no brand guidelines)
 
 Create visual exploration opportunities:
-"If no existing brand guidelines, I'll create a color theme visualizer to help you explore options.
+<display>
+If no existing brand guidelines, I'll create a color theme visualizer to help you explore options.
 
 🎨 I can generate comprehensive HTML color theme visualizers with multiple theme options, complete UI examples, and the ability to see how colors work in real interface contexts.
 
-This will help you make an informed decision about the visual direction for {{project_name}}."
+This will help you make an informed decision about the visual direction for {{project_name}}.
+</display>
 
 ### 3. Define Typography System
 
 Establish the typographic foundation:
-"**Typography Questions:**
+<display>
+**Typography Questions:**
 
 - What should the overall tone feel like? (Professional, friendly, modern, classic?)
 - How much text content will users read? (Headings only? Long-form content?)
@@ -80,12 +85,14 @@ Establish the typographic foundation:
 - Choose primary and secondary typefaces
 - Establish type scale (h1, h2, h3, body, etc.)
 - Define line heights and spacing relationships
-- Consider readability and accessibility"
+- Consider readability and accessibility
+</display>
 
 ### 4. Establish Spacing and Layout Foundation
 
 Define the structural foundation:
-"**Spacing and Layout Foundation:**
+<display>
+**Spacing and Layout Foundation:**
 
 - How should the overall layout feel? (Dense and efficient? Airy and spacious?)
 - What spacing unit should we use? (4px, 8px, 12px base?)
@@ -96,12 +103,14 @@ Define the structural foundation:
 
 - [Layout principle 1 based on product type]
 - [Layout principle 2 based on user needs]
-- [Layout principle 3 based on platform requirements]"
+- [Layout principle 3 based on platform requirements]
+</display>
 
 ### 5. Create Visual Foundation Strategy
 
 Synthesize all visual decisions:
-"**Visual Foundation Strategy:**
+<display>
+**Visual Foundation Strategy:**
 
 **Color System:**
 
@@ -121,7 +130,8 @@ Synthesize all visual decisions:
 - Grid system approach
 - Component spacing relationships
 
-This foundation will ensure consistency across all our design decisions."
+This foundation will ensure consistency across all our design decisions.
+</display>
 
 ### 6. Generate Visual Foundation Content
 
@@ -154,7 +164,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated visual foundation content and present choices:
-"I've established the visual design foundation for {{project_name}}. This provides the building blocks for consistent, beautiful design.
+<display>
+I've established the visual design foundation for {{project_name}}. This provides the building blocks for consistent, beautiful design.
 
 **Here's what I'll add to the document:**
 
@@ -164,6 +175,7 @@ Show the generated visual foundation content and present choices:
 [A] Advanced Elicitation - Let's refine our visual foundation
 [P] Party Mode - Bring design perspectives on visual choices
 [C] Continue - Save this to the document and move to design directions
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md

@@ -51,7 +51,8 @@ Generate comprehensive design direction mockups showing different visual approac
 ### 1. Generate Design Direction Variations
 
 Create diverse visual explorations:
-"I'll generate 6-8 different design direction variations exploring:
+<display>
+I'll generate 6-8 different design direction variations exploring:
 
 - Different layout approaches and information hierarchy
 - Various interaction patterns and visual weights
@@ -59,12 +60,14 @@ Create diverse visual explorations:
 - Different density and spacing approaches
 - Various navigation and component arrangements
 
-Each mockup will show a complete vision for {{project_name}} with all our design decisions applied."
+Each mockup will show a complete vision for {{project_name}} with all our design decisions applied.
+</display>
 
 ### 2. Create HTML Design Direction Showcase
 
 Generate interactive visual exploration:
-"🎨 Design Direction Mockups Generated!
+<display>
+🎨 Design Direction Mockups Generated!
 
 I'm creating a comprehensive HTML design direction showcase at `{planning_artifacts}/ux-design-directions.html`
 
@@ -76,12 +79,14 @@ I'm creating a comprehensive HTML design direction showcase at `{planning_artifa
 - Complete UI examples with real content
 - Responsive behavior demonstrations
 
-Each mockup represents a complete visual direction for your app's look and feel."
+Each mockup represents a complete visual direction for your app's look and feel.
+</display>
 
 ### 3. Present Design Exploration Framework
 
 Guide evaluation criteria:
-"As you explore the design directions, look for:
+<display>
+As you explore the design directions, look for:
 
 ✅ **Layout Intuitiveness** - Which information hierarchy matches your priorities?
 ✅ **Interaction Style** - Which interaction style fits your core experience?
@@ -90,12 +95,14 @@ Guide evaluation criteria:
 ✅ **Component Usage** - How well do the components support your user journeys?
 ✅ **Brand Alignment** - Which direction best supports your emotional goals?
 
-Take your time exploring - this is a crucial decision that will guide all our design work!"
+Take your time exploring - this is a crucial decision that will guide all our design work!
+</display>
 
 ### 4. Facilitate Design Direction Selection
 
 Help user choose or combine elements:
-"After exploring all the design directions:
+<display>
+After exploring all the design directions:
 
 **Which approach resonates most with you?**
 
@@ -109,19 +116,22 @@ Help user choose or combine elements:
 - Which layout feels most intuitive for your users?
 - Which visual weight matches your brand personality?
 - Which interaction style supports your core experience?
-- Are there elements from different directions you'd like to combine?"
+- Are there elements from different directions you'd like to combine?
+</display>
 
 ### 5. Document Design Direction Decision
 
 Capture the chosen approach:
-"Based on your exploration, I'm understanding your design direction preference:
+<display>
+Based on your exploration, I'm understanding your design direction preference:
 
 **Chosen Direction:** [Direction number or combination]
 **Key Elements:** [Specific elements you liked]
 **Modifications Needed:** [Any changes requested]
 **Rationale:** [Why this direction works for your product]
 
-This will become our design foundation moving forward. Are we ready to lock this in, or do you want to explore variations?"
+This will become our design foundation moving forward. Are we ready to lock this in, or do you want to explore variations?
+</display>
 
 ### 6. Generate Design Direction Content
 
@@ -154,7 +164,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated design direction content and present choices:
-"I've documented our design direction decision for {{project_name}}. This visual approach will guide all our detailed design work.
+<display>
+I've documented our design direction decision for {{project_name}}. This visual approach will guide all our detailed design work.
 
 **Here's what I'll add to the document:**
 
@@ -164,6 +175,7 @@ Show the generated design direction content and present choices:
 [A] Advanced Elicitation - Let's refine our design direction
 [P] Party Mode - Bring different perspectives on visual choices
 [C] Continue - Save this to the document and move to user journey flows
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md

@@ -51,7 +51,8 @@ Design detailed user journey flows for critical user interactions.
 ### 1. Load PRD User Journeys as Foundation
 
 Start with user journeys already defined in the PRD:
-"Great! Since we have the PRD available, let's build on the user journeys already documented there.
+<display>
+Great! Since we have the PRD available, let's build on the user journeys already documented there.
 
 **Existing User Journeys from PRD:**
 I've already loaded these user journeys from your PRD:
@@ -66,14 +67,16 @@ Looking at the PRD journeys, I need to design detailed interaction flows for:
 - [Critical journey 2 identified from PRD narratives]
 - [Critical journey 3 identified from PRD narratives]
 
-The PRD gave us the stories - now we design the mechanics!"
+The PRD gave us the stories - now we design the mechanics!
+</display>
 
 ### 2. Design Each Journey Flow
 
 For each critical journey, design detailed flow:
 
 **For [Journey Name]:**
-"Let's design the flow for users accomplishing [journey goal].
+<display>
+Let's design the flow for users accomplishing [journey goal].
 
 **Flow Design Questions:**
 
@@ -83,12 +86,14 @@ For each critical journey, design detailed flow:
 - How do they know they're progressing successfully?
 - What does success look like for this journey?
 - Where might they get confused or stuck?
-- How do they recover from errors?"
+- How do they recover from errors?
+</display>
 
 ### 3. Create Flow Diagrams
 
 Visualize each journey with Mermaid diagrams:
-"I'll create detailed flow diagrams for each journey showing:
+<display>
+I'll create detailed flow diagrams for each journey showing:
 
 **[Journey Name] Flow:**
 
@@ -98,12 +103,14 @@ Visualize each journey with Mermaid diagrams:
 - Error recovery mechanisms
 - Progressive disclosure of information
 
-Each diagram will map the complete user experience from start to finish."
+Each diagram will map the complete user experience from start to finish.
+</display>
 
 ### 4. Optimize for Efficiency and Delight
 
 Refine flows for optimal user experience:
-"**Flow Optimization:**
+<display>
+**Flow Optimization:**
 For each journey, let's ensure we're:
 
 - Minimizing steps to value (getting users to success quickly)
@@ -116,12 +123,14 @@ For each journey, let's ensure we're:
 
 - [Optimization 1 for journey efficiency]
 - [Optimization 2 for user delight]
-- [Optimization 3 for error handling]"
+- [Optimization 3 for error handling]
+</display>
 
 ### 5. Document Journey Patterns
 
 Extract reusable patterns across journeys:
-"**Journey Patterns:**
+<display>
+**Journey Patterns:**
 Across these flows, I'm seeing some common patterns we can standardize:
 
 **Navigation Patterns:**
@@ -139,7 +148,8 @@ Across these flows, I'm seeing some common patterns we can standardize:
 - [Feedback pattern 1]
 - [Feedback pattern 2]
 
-These patterns will ensure consistency across all user experiences."
+These patterns will ensure consistency across all user experiences.
+</display>
 
 ### 6. Generate User Journey Content
 
@@ -172,7 +182,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated user journey content and present choices:
-"I've designed detailed user journey flows for {{project_name}}. These flows will guide the detailed design of each user interaction.
+<display>
+I've designed detailed user journey flows for {{project_name}}. These flows will guide the detailed design of each user interaction.
 
 **Here's what I'll add to the document:**
 
@@ -182,6 +193,7 @@ Show the generated user journey content and present choices:
 [A] Advanced Elicitation - Let's refine our user journey designs
 [P] Party Mode - Bring different perspectives on user flows
 [C] Continue - Save this to the document and move to component strategy
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md

@@ -51,7 +51,8 @@ Define component library strategy and design custom components not covered by th
 ### 1. Analyze Design System Coverage
 
 Review what components are available vs. needed:
-"Based on our chosen design system [design system from step 6], let's identify what components are already available and what we need to create custom.
+<display>
+Based on our chosen design system [design system from step 6], let's identify what components are already available and what we need to create custom.
 
 **Available from Design System:**
 [List of components available in chosen design system]
@@ -66,14 +67,16 @@ Looking at our user journeys and design direction, we need:
 **Gap Analysis:**
 
 - [Gap 1 - needed but not available]
-- [Gap 2 - needed but not available]"
+- [Gap 2 - needed but not available]
+</display>
 
 ### 2. Design Custom Components
 
 For each custom component needed, design thoroughly:
 
 **For each custom component:**
-"**[Component Name] Design:**
+<display>
+**[Component Name] Design:**
 
 **Purpose:** What does this component do for users?
 **Content:** What information or data does it display?
@@ -82,7 +85,8 @@ For each custom component needed, design thoroughly:
 **Variants:** Are there different sizes or styles needed?
 **Accessibility:** What ARIA labels and keyboard support needed?
 
-Let's walk through each custom component systematically."
+Let's walk through each custom component systematically.
+</display>
 
 ### 3. Document Component Specifications
 
@@ -106,7 +110,8 @@ Create detailed specifications for each component:
 ### 4. Define Component Strategy
 
 Establish overall component library approach:
-"**Component Strategy:**
+<display>
+**Component Strategy:**
 
 **Foundation Components:** (from design system)
 
@@ -123,12 +128,14 @@ Establish overall component library approach:
 - Build custom components using design system tokens
 - Ensure consistency with established patterns
 - Follow accessibility best practices
-- Create reusable patterns for common use cases"
+- Create reusable patterns for common use cases
+</display>
 
 ### 5. Plan Implementation Roadmap
 
 Define how and when to build components:
-"**Implementation Roadmap:**
+<display>
+**Implementation Roadmap:**
 
 **Phase 1 - Core Components:**
 
@@ -145,7 +152,8 @@ Define how and when to build components:
 - [Component 5] - optimizes [user journey]
 - [Component 6] - adds [special feature]
 
-This roadmap helps prioritize development based on user journey criticality."
+This roadmap helps prioritize development based on user journey criticality.
+</display>
 
 ### 6. Generate Component Strategy Content
 
@@ -178,7 +186,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated component strategy content and present choices:
-"I've defined the component strategy for {{project_name}}. This balances using proven design system components with custom components for your unique needs.
+<display>
+I've defined the component strategy for {{project_name}}. This balances using proven design system components with custom components for your unique needs.
 
 **Here's what I'll add to the document:**
 
@@ -188,6 +197,7 @@ Show the generated component strategy content and present choices:
 [A] Advanced Elicitation - Let's refine our component strategy
 [P] Party Mode - Bring technical perspectives on component design
 [C] Continue - Save this to the document and move to UX patterns
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md

@@ -51,7 +51,8 @@ Establish UX consistency patterns for common situations like buttons, forms, nav
 ### 1. Identify Pattern Categories
 
 Determine which patterns need definition for your product:
-"Let's establish consistency patterns for how {{project_name}} behaves in common situations.
+<display>
+Let's establish consistency patterns for how {{project_name}} behaves in common situations.
 
 **Pattern Categories to Define:**
 
@@ -63,14 +64,16 @@ Determine which patterns need definition for your product:
 - Empty states and loading states
 - Search and filtering patterns
 
-Which categories are most critical for your product? We can go through each thoroughly or focus on the most important ones."
+Which categories are most critical for your product? We can go through each thoroughly or focus on the most important ones.
+</display>
 
 ### 2. Define Critical Patterns First
 
 Focus on patterns most relevant to your product:
 
 **For [Critical Pattern Category]:**
-"**[Pattern Type] Patterns:**
+<display>
+**[Pattern Type] Patterns:**
 What should users see/do when they need to [pattern action]?
 
 **Considerations:**
@@ -86,7 +89,8 @@ What should users see/do when they need to [pattern action]?
 - [Example 1 for this pattern type]
 - [Example 2 for this pattern type]
 
-How should {{project_name}} handle [pattern type] interactions?"
+How should {{project_name}} handle [pattern type] interactions?
+</display>
 
 ### 3. Establish Pattern Guidelines
 
@@ -108,7 +112,8 @@ Document specific design decisions:
 ### 4. Design System Integration
 
 Ensure patterns work with chosen design system:
-"**Integration with [Design System]:**
+<display>
+**Integration with [Design System]:**
 
 - How do these patterns complement our design system components?
 - What customizations are needed?
@@ -118,7 +123,8 @@ Ensure patterns work with chosen design system:
 
 - [Custom rule 1]
 - [Custom rule 2]
-- [Custom rule 3]"
+- [Custom rule 3]
+</display>
 
 ### 5. Create Pattern Documentation
 
@@ -167,7 +173,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated UX patterns content and present choices:
-"I've established UX consistency patterns for {{project_name}}. These patterns ensure users have a consistent, predictable experience across all interactions.
+<display>
+I've established UX consistency patterns for {{project_name}}. These patterns ensure users have a consistent, predictable experience across all interactions.
 
 **Here's what I'll add to the document:**
 
@@ -177,6 +184,7 @@ Show the generated UX patterns content and present choices:
 [A] Advanced Elicitation - Let's refine our UX patterns
 [P] Party Mode - Bring different perspectives on consistency patterns
 [C] Continue - Save this to the document and move to responsive design
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md

@@ -51,7 +51,8 @@ Define responsive design strategy and accessibility requirements for the product
 ### 1. Define Responsive Strategy
 
 Establish how the design adapts across devices:
-"Let's define how {{project_name}} adapts across different screen sizes and devices.
+<display>
+Let's define how {{project_name}} adapts across different screen sizes and devices.
 
 **Responsive Design Questions:**
 
@@ -71,12 +72,14 @@ Establish how the design adapts across devices:
 
 - Bottom navigation or hamburger menu?
 - How do layouts collapse on small screens?
-- What's the most critical information to show mobile-first?"
+- What's the most critical information to show mobile-first?
+</display>
 
 ### 2. Establish Breakpoint Strategy
 
 Define when and how layouts change:
-"**Breakpoint Strategy:**
+<display>
+**Breakpoint Strategy:**
 We need to define screen size breakpoints where layouts adapt.
 
 **Common Breakpoints:**
@@ -89,12 +92,14 @@ We need to define screen size breakpoints where layouts adapt.
 
 - Use standard breakpoints or custom ones?
 - Focus on mobile-first or desktop-first design?
-- Have specific breakpoints for your key use cases?"
+- Have specific breakpoints for your key use cases?
+</display>
 
 ### 3. Design Accessibility Strategy
 
 Define accessibility requirements and compliance level:
-"**Accessibility Strategy:**
+<display>
+**Accessibility Strategy:**
 What level of WCAG compliance does {{project_name}} need?
 
 **WCAG Levels:**
@@ -113,12 +118,14 @@ What level of WCAG compliance does {{project_name}} need?
 - Keyboard navigation support
 - Screen reader compatibility
 - Touch target sizes (minimum 44x44px)
-- Focus indicators and skip links"
+- Focus indicators and skip links
+</display>
 
 ### 4. Define Testing Strategy
 
 Plan how to ensure responsive design and accessibility:
-"**Testing Strategy:**
+<display>
+**Testing Strategy:**
 
 **Responsive Testing:**
 
@@ -137,12 +144,14 @@ Plan how to ensure responsive design and accessibility:
 
 - Include users with disabilities in testing
 - Test with diverse assistive technologies
-- Validate with actual target devices"
+- Validate with actual target devices
+</display>
 
 ### 5. Document Implementation Guidelines
 
 Create specific guidelines for developers:
-"**Implementation Guidelines:**
+<display>
+**Implementation Guidelines:**
 
 **Responsive Development:**
 
@@ -157,7 +166,8 @@ Create specific guidelines for developers:
 - ARIA labels and roles
 - Keyboard navigation implementation
 - Focus management and skip links
-- High contrast mode support"
+- High contrast mode support
+</display>
 
 ### 6. Generate Responsive & Accessibility Content
 
@@ -194,7 +204,8 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### 7. Present Content and Menu
 
 Show the generated responsive and accessibility content and present choices:
-"I've defined the responsive design and accessibility strategy for {{project_name}}. This ensures your product works beautifully across all devices and is accessible to all users.
+<display>
+I've defined the responsive design and accessibility strategy for {{project_name}}. This ensures your product works beautifully across all devices and is accessible to all users.
 
 **Here's what I'll add to the document:**
 
@@ -204,6 +215,7 @@ Show the generated responsive and accessibility content and present choices:
 [A] Advanced Elicitation - Let's refine our responsive/accessibility strategy
 [P] Party Mode - Bring different perspectives on inclusive design
 [C] Continue - Save this to the document and complete the workflow
+</display>
 
 ### 8. Handle Menu Selection
 

src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md

@@ -44,7 +44,8 @@ Complete the UX design workflow, update status files, and suggest next steps for
 ### 1. Announce Workflow Completion
 
 Inform user that the UX design is complete:
-"🎉 **UX Design Complete, {{user_name}}!**
+<display>
+🎉 **UX Design Complete, {{user_name}}!**
 
 I've successfully collaborated with you to create a comprehensive UX design specification for {{project_name}}.
 
@@ -69,7 +70,8 @@ I've successfully collaborated with you to create a comprehensive UX design spec
 - Color themes visualizer: `{planning_artifacts}/ux-color-themes.html`
 - Design directions mockups: `{planning_artifacts}/ux-design-directions.html`
 
-This specification is now ready to guide visual design, implementation, and development."
+This specification is now ready to guide visual design, implementation, and development.
+</display>
 
 ### 2. Workflow Status Update
 

src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md

@@ -54,14 +54,16 @@ To discover, inventory, and organize all project documents, identifying duplicat
 
 ### 1. Initialize Document Discovery
 
-"Beginning **Document Discovery** to inventory all project files.
+<display>
+Beginning **Document Discovery** to inventory all project files.
 
 I will:
 
 1. Search for all required documents (PRD, Architecture, Epics, UX)
 2. Group sharded documents together
 3. Identify any duplicates (whole + sharded versions)
-4. Present findings for your confirmation"
+4. Present findings for your confirmation
+</display>
 
 ### 2. Document Search Patterns
 
@@ -133,7 +135,8 @@ Initialize {outputFile} with {templateFile}.
 ### 6. Present Findings and Get Confirmation
 
 Display findings and ask:
-"**Document Discovery Complete**
+<display>
+**Document Discovery Complete**
 
 [Show organized file list]
 
@@ -147,11 +150,14 @@ Display findings and ask:
 - If duplicates exist: Please remove/rename one version
 - Confirm which documents to use for assessment
 
-**Ready to proceed?** [C] Continue after resolving issues"
+**Ready to proceed?** [C] Continue after resolving issues
+</display>
 
 ### 7. Present MENU OPTIONS
 
-Display: **Select an Option:** [C] Continue to File Validation
+<display>
+**Select an Option:** [C] Continue to File Validation
+</display>
 
 #### EXECUTION RULES:
 

src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md

@@ -54,7 +54,8 @@ To fully read and analyze the PRD document (whole or sharded) to extract all Fun
 
 ### 1. Initialize PRD Analysis
 
-"Beginning **PRD Analysis** to extract all requirements.
+<display>
+Beginning **PRD Analysis** to extract all requirements.
 
 I will:
 
@@ -62,7 +63,8 @@ I will:
 2. Read it completely and thoroughly
 3. Extract ALL Functional Requirements (FRs)
 4. Extract ALL Non-Functional Requirements (NFRs)
-5. Document findings for coverage validation"
+5. Document findings for coverage validation
+</display>
 
 ### 2. Load and Read PRD
 

src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-03-epic-coverage-validation.md

@@ -53,14 +53,16 @@ To validate that all Functional Requirements from the PRD are captured in the ep
 
 ### 1. Initialize Coverage Validation
 
-"Beginning **Epic Coverage Validation**.
+<display>
+Beginning **Epic Coverage Validation**.
 
 I will:
 
 1. Load the epics and stories document
 2. Extract FR coverage information
 3. Compare against PRD FRs from previous step
-4. Identify any FRs not covered in epics"
+4. Identify any FRs not covered in epics
+</display>
 
 ### 2. Load Epics Document
 

src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-04-ux-alignment.md

@@ -53,13 +53,15 @@ To check if UX documentation exists and validate that it aligns with PRD require
 
 ### 1. Initialize UX Validation
 
-"Beginning **UX Alignment** validation.
+<display>
+Beginning **UX Alignment** validation.
 
 I will:
 
 1. Check if UX documentation exists
 2. If UX exists: validate alignment with PRD and Architecture
-3. If no UX: determine if UX is implied and document warning"
+3. If no UX: determine if UX is implied and document warning
+</display>
 
 ### 2. Search for UX Documentation
 

src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-05-epic-quality-review.md

@@ -55,7 +55,8 @@ To validate epics and stories against the best practices defined in create-epics
 
 ### 1. Initialize Best Practices Validation
 
-"Beginning **Epic Quality Review** against create-epics-and-stories standards.
+<display>
+Beginning **Epic Quality Review** against create-epics-and-stories standards.
 
 I will rigorously validate:
 
@@ -64,7 +65,8 @@ I will rigorously validate:
 - Story dependencies (no forward references)
 - Proper story sizing and completeness
 
-Any deviation from best practices will be flagged as a defect."
+Any deviation from best practices will be flagged as a defect.
+</display>
 
 ### 2. Epic Structure Validation
 

src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md

@@ -52,14 +52,16 @@ To provide a comprehensive summary of all findings and give the report a final p
 
 ### 1. Initialize Final Assessment
 
-"Completing **Final Assessment**.
+<display>
+Completing **Final Assessment**.
 
 I will now:
 
 1. Review all findings from previous steps
 2. Provide a comprehensive summary
 3. Add specific recommendations
-4. Determine overall readiness status"
+4. Determine overall readiness status
+</display>
 
 ### 2. Review Previous Findings
 
@@ -105,11 +107,13 @@ This assessment identified [X] issues across [Y] categories. Address the critica
 ### 5. Present Completion
 
 Display:
-"**Implementation Readiness Assessment Complete**
+<display>
+**Implementation Readiness Assessment Complete**
 
 Report generated: {outputFile}
 
-The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations."
+The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations.
+</display>
 
 ## WORKFLOW COMPLETE
 

src/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md

@@ -108,7 +108,8 @@ Complete setup and report to user:
 
 **Input Documents Discovered:**
 Report what was found:
-"Welcome {{user_name}}! I've set up your Architecture workspace for {{project_name}}.
+<display>
+Welcome {{user_name}}! I've set up your Architecture workspace for {{project_name}}.
 
 **Documents Found:**
 
@@ -123,6 +124,7 @@ Report what was found:
 Ready to begin architectural decision making. Do you have any other documents you'd like me to include?
 
 [C] Continue to project context analysis
+</display>
 
 ## SUCCESS METRICS:
 

src/bmm/workflows/3-solutioning/create-architecture/steps/step-01b-continue.md

@@ -55,7 +55,8 @@ Read the existing architecture document completely and analyze:
 
 Show the user their current progress:
 
-"Welcome back {{user_name}}! I found your Architecture work for {{project_name}}.
+<display>
+Welcome back {{user_name}}! I found your Architecture work for {{project_name}}.
 
 **Current Progress:**
 
@@ -77,7 +78,7 @@ Show the user their current progress:
 [C] Continue to next logical step
 [O] Overview of all remaining steps
 [X] Start over (will overwrite existing work)
-"
+</display>
 
 ### 3. Handle User Choice
 

src/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md

@@ -94,7 +94,8 @@ Calculate and present project complexity:
 
 Present your analysis back to user for validation:
 
-"I'm reviewing your project documentation for {{project_name}}.
+<display>
+I'm reviewing your project documentation for {{project_name}}.
 
 {if_epics_loaded}I see {{epic_count}} epics with {{story_count}} total stories.{/if_epics_loaded}
 {if_no_epics}I found {{fr_count}} functional requirements organized into {{fr_category_list}}.{/if_no_epics}
@@ -116,7 +117,8 @@ Present your analysis back to user for validation:
 
 This analysis will help me guide you through the architectural decisions needed to ensure AI agents implement this consistently.
 
-Does this match your understanding of the project scope and requirements?"
+Does this match your understanding of the project scope and requirements?
+</display>
 
 ### 4. Generate Project Context Content
 
@@ -155,7 +157,8 @@ Prepare the content to append to the document:
 
 Show the generated content and present choices:
 
-"I've drafted the Project Context Analysis based on your requirements. This sets the foundation for our architectural decisions.
+<display>
+I've drafted the Project Context Analysis based on your requirements. This sets the foundation for our architectural decisions.
 
 **Here's what I'll add to the document:**
 
@@ -164,7 +167,8 @@ Show the generated content and present choices:
 **What would you like to do?**
 [A] Advanced Elicitation - Let's dive deeper into architectural implications
 [P] Party Mode - Bring different perspectives to analyze requirements
-[C] Continue - Save this analysis and begin architectural decisions"
+[C] Continue - Save this analysis and begin architectural decisions
+</display>
 
 ### 6. Handle Menu Selection