155 changed files with 5833 additions and 5120 deletions
--- a/.claude/skills/changelog-social.skill
+++ b/.claude/skills/changelog-social.skill
--- a/.claude/skills/changelog-social/SKILL.md
+++ b/.claude/skills/changelog-social/SKILL.md
@ -1,178 +0,0 @@
 ---
 name: bmad-os-changelog-social
 description: Generate social media announcements for Discord, Twitter, and LinkedIn from the latest changelog entry. Use when user asks to create release announcements, social posts, or share changelog updates. Reads CHANGELOG.md in current working directory. Reference examples/ for tone and format.
 disable-model-invocation: true
 ---
 # Changelog Social
 Generate engaging social media announcements from changelog entries.
 ## Workflow
 ### Step 1: Extract Changelog Entry
 Read `./CHANGELOG.md` and extract the latest version entry. The changelog follows this format:
 ```markdown
 ## [VERSION]
 ### 🎁 Features
 * **Title** — Description
 ### 🐛 Bug Fixes
 * **Title** — Description
 ### 📚 Documentation
 * **Title** — Description
 ### 🔧 Maintenance
 * **Title** — Description
 ```
 Parse:
 - **Version number** (e.g., `6.0.0-Beta.5`)
 - **Features** - New functionality, enhancements
 - **Bug Fixes** - Fixes users will care about
 - **Documentation** - New or improved docs
 - **Maintenance** - Dependency updates, tooling improvements
 ### Step 2: Get Git Contributors
 Use git log to find contributors since the previous version. Get commits between the current version tag and the previous one:
 ```bash
 # Find the previous version tag first
 git tag --sort=-version:refname | head -5
 # Get commits between versions with PR numbers and authors
 git log <previous-tag>..<current-tag> --pretty=format:"%h|%s|%an" --grep="#"
 ```
 Extract PR numbers from commit messages that contain `#` followed by digits. Compile unique contributors.
 ### Step 3: Generate Discord Announcement
 **Limit: 2,000 characters per message.** Split into multiple messages if needed.
 Use this template style:
 ```markdown
 🚀 **BMad vVERSION RELEASED!**
 🎉 [Brief hype sentence]
 🪥 **KEY HIGHLIGHT** - [One-line summary]
 🎯 **CATEGORY NAME**
 • Feature one - brief description
 • Feature two - brief description
 • Coming soon: Future teaser
 🔧 **ANOTHER CATEGORY**
 • Fix or feature
 • Another item
 📚 **DOCS OR OTHER**
 • Item
 • Item with link
 🌟 **COMMUNITY PHILOSOPHY** (optional - include for major releases)
 • Everything is FREE - No paywalls
 • Knowledge shared, not sold
 📊 **STATS**
 X commits | Y PRs merged | Z files changed
 🙏 **CONTRIBUTORS**
@username1 (X PRs!), @username2 (Y PRs!)
@username3, @username4, username5 + dependabot 🛡️
 Community-driven FTW! 🌟
 📦 **INSTALL:**
 `npx bmad-method@VERSION install`
 ⭐ **SUPPORT US:**
 🌟 GitHub: github.com/bmad-code-org/BMAD-METHOD/
 📺 YouTube: youtube.com/@BMadCode
 ☕ Donate: buymeacoffee.com/bmad
 🔥 **Next version tease!**
 ```
 **Content Strategy:**
 - Focus on **user impact** - what's better for them?
 - Highlight **annoying bugs fixed** that frustrated users
 - Show **new capabilities** that enable workflows
 - Keep it **punchy** - use emojis and short bullets
 - Add **personality** - excitement, humor, gratitude
 ### Step 4: Generate Twitter Post
 **Limit: 25,000 characters per tweet (Premium).** With Premium, use a single comprehensive post matching the Discord style (minus Discord-specific formatting). Aim for 1,500-3,000 characters for better engagement.
 **Threads are optional** — only use for truly massive releases where you want multiple engagement points.
 See `examples/twitter-example.md` for the single-post Premium format.
 ## Content Selection Guidelines
 **Include:**
 - New features that change workflows
 - Bug fixes for annoying/blocking issues
 - Documentation that helps users
 - Performance improvements
 - New agents or workflows
 - Breaking changes (call out clearly)
 **Skip/Minimize:**
 - Internal refactoring
 - Dependency updates (unless user-facing)
 - Test improvements
 - Minor style fixes
 **Emphasize:**
 - "Finally fixed" issues
 - "Faster" operations
 - "Easier" workflows
 - "Now supports" capabilities
 ## Examples
 Reference example posts in `examples/` for tone and formatting guidance:
 - **discord-example.md** — Full Discord announcement with emojis, sections, contributor shout-outs
 - **twitter-example.md** — Twitter thread format (5 tweets max for major releases)
 - **linkedin-example.md** — Professional post for major/minor releases with significant features
 **When to use LinkedIn:**
 - Major version releases (e.g., v6.0.0 Beta, v7.0.0)
 - Minor releases with exceptional new features
 - Community milestone announcements
 Read the appropriate example file before generating to match the established style and voice.
 ## Output Format
 **CRITICAL: ALWAYS write to files** - Create files in `_bmad-output/social/` directory:
 1. `{repo-name}-discord-{version}.md` - Discord announcement
 2. `{repo-name}-twitter-{version}.md` - Twitter post
 3. `{repo-name}-linkedin-{version}.md` - LinkedIn post (if applicable)
 Also present a preview in the chat:
 ```markdown
 ## Discord Announcement
 [paste Discord content here]
 ## Twitter Post
 [paste Twitter content here]
 ```
 Files created:
 - `_bmad-output/social/{filename}`
 Offer to make adjustments if the user wants different emphasis, tone, or content.
--- a/.claude/skills/changelog-social/examples/discord-example.md
+++ b/.claude/skills/changelog-social/examples/discord-example.md
@ -1,53 +0,0 @@
 🚀 **BMad v6.0.0-alpha.23 RELEASED!**
 🎉 Huge update - almost beta!
 🪟 **WINDOWS INSTALLER FIXED** - Menu arrows issue should be fixed! CRLF & ESM problems resolved.
 🎯 **PRD WORKFLOWS IMPROVED**
 • Validation & Edit workflows added!
 • PRD Cohesion check ensures document flows beautifully
 • Coming soon: Use of subprocess optimization (context saved!)
 • Coming soon: Final format polish step in all workflows - Human consumption OR hyper-optimized LLM condensed initially!
 🔧 **WORKFLOW CREATOR & VALIDATOR**
 • Subprocess support for advanced optimization
 • Path violation checks ensure integrity
 • Beyond error checking - offers optimization & flow suggestions!
 📚 **NEW DOCS SITE** - docs.bmad-method.org
 • Diataxis framework: Tutorials, How-To, Explanations, References
 • Current docs still being revised
 • Tutorials, blogs & explainers coming soon!
 💡 **BRAINSTORMING REVOLUTION**
 • 100+ idea goal (quantity-first!)
 • Anti-bias protocol (pivot every 10 ideas)
 • Chain-of-thought + simulated temperature prompts
 • Coming soon: SubProcessing (on-the-fly sub agents)
 🌟 **COMMUNITY PHILOSOPHY**
 • Everything is FREE - No paywalls, no gated content
 • Knowledge shared, not sold
 • No premium tiers - full access to our ideas
 📊 **27 commits | 217 links converted | 42+ docs created**
 🙏 **17 Community PR Authors in this release!**
@lum (6 PRs!), @q00 (3 PRs!), @phil (2 PRs!)
@mike, @alex, @ramiz, @sjennings + dependabot 🛡️
 Community-driven FTW! 🌟
 📦 **INSTALL ALPHA:**
 `npx bmad-method install`
 ⭐ **SUPPORT US:**
 🌟 GitHub: github.com/bmad-code-org/BMAD-METHOD/
 📺 YouTube: youtube.com/@BMadCode
 🎤 **SPEAKING & MEDIA**
 Available for conferences, podcasts, media appearances!
 Topics: AI-Native Organizations (Any Industry), BMad Method
 DM on Discord for inquiries!
 🔥 **V6 Beta is DAYS away!** January 22nd ETA - new features such as xyz and abc bug fixes!
--- a/.claude/skills/changelog-social/examples/linkedin-example.md
+++ b/.claude/skills/changelog-social/examples/linkedin-example.md
@ -1,49 +0,0 @@
 🚀 **Announcing BMad Method v6.0.0 Beta - AI-Native Agile Development Framework**
 I'm excited to share that BMad Method, the open-source AI-driven agile development framework, is entering Beta! After 27 alpha releases and countless community contributions, we're approaching a major milestone.
 **What's New in v6.0.0-alpha.23**
 🪟 **Windows Compatibility Fixed**
 We've resolved the installer issues that affected Windows users. The menu arrows problem, CRLF handling, and ESM compatibility are all resolved.
 🎯 **Enhanced PRD Workflows**
 Our Product Requirements Document workflows now include validation and editing capabilities, with a new cohesion check that ensures your documents flow beautifully. Subprocess optimization is coming soon to save even more context.
 🔧 **Workflow Creator & Validator**
 New tools for creating and validating workflows with subprocess support, path violation checks, and optimization suggestions that go beyond simple error checking.
 📚 **New Documentation Platform**
 We've launched docs.bmad-method.org using the Diataxis framework - providing clear separation between tutorials, how-to guides, explanations, and references. Our documentation is being continuously revised and expanded.
 💡 **Brainstorming Revolution**
 Our brainstorming workflows now use research-backed techniques: 100+ idea goals, anti-bias protocols, chain-of-thought reasoning, and simulated temperature prompts for higher divergence.
 **Our Philosophy**
 Everything in BMad Method is FREE. No paywalls, no gated content, no premium tiers. We believe knowledge should be shared, not sold. This is community-driven development at its finest.
 **The Stats**
 - 27 commits in this release
 - 217 documentation links converted
 - 42+ new documents created
 - 17 community PR authors contributed
 **Get Started**
 ```
 npx bmad-method@alpha install
 ```
 **Learn More**
 - GitHub: github.com/bmad-code-org/BMAD-METHOD
 - YouTube: youtube.com/@BMadCode
 - Docs: docs.bmad-method.org
 **What's Next?**
 Beta is just days away with an ETA of January 22nd. We're also available for conferences, podcasts, and media appearances to discuss AI-Native Organizations and the BMad Method.
 Have you tried BMad Method yet? I'd love to hear about your experience in the comments!
 #AI #SoftwareDevelopment #Agile #OpenSource #DevTools #LLM #AgentEngineering
--- a/.claude/skills/changelog-social/examples/twitter-example.md
+++ b/.claude/skills/changelog-social/examples/twitter-example.md
@ -1,55 +0,0 @@
 🚀 **BMad v6.0.0-alpha.23 RELEASED!**
 Huge update - we're almost at Beta! 🎉
 🪟 **WINDOWS INSTALLER FIXED** - Menu arrows issue should be fixed! CRLF & ESM problems resolved.
 🎯 **PRD WORKFLOWS IMPROVED**
 • Validation & Edit workflows added!
 • PRD Cohesion check ensures document flows beautifully
 • Coming soon: Subprocess optimization (context saved!)
 • Coming soon: Final format polish step in all workflows
 🔧 **WORKFLOW CREATOR & VALIDATOR**
 • Subprocess support for advanced optimization
 • Path violation checks ensure integrity
 • Beyond error checking - offers optimization & flow suggestions!
 📚 **NEW DOCS SITE** - docs.bmad-method.org
 • Diataxis framework: Tutorials, How-To, Explanations, References
 • Current docs still being revised
 • Tutorials, blogs & explainers coming soon!
 💡 **BRAINSTORMING REVOLUTION**
 • 100+ idea goal (quantity-first!)
 • Anti-bias protocol (pivot every 10 ideas)
 • Chain-of-thought + simulated temperature prompts
 • Coming soon: SubProcessing (on-the-fly sub agents)
 🌟 **COMMUNITY PHILOSOPHY**
 • Everything is FREE - No paywalls, no gated content
 • Knowledge shared, not sold
 • No premium tiers - full access to our ideas
 📊 **27 commits | 217 links converted | 42+ docs created**
 🙏 **17 Community PR Authors in this release!**
@lum (6 PRs!), @q00 (3 PRs!), @phil (2 PRs!)
@mike, @alex, @ramiz, @sjennings + dependabot 🛡️
 Community-driven FTW! 🌟
 📦 **INSTALL ALPHA:**
 `npx bmad-method install`
 ⭐ **SUPPORT US:**
 🌟 GitHub: github.com/bmad-code-org/BMAD-METHOD/
 📺 YouTube: youtube.com/@BMadCode
 🎤 **SPEAKING & MEDIA**
 Available for conferences, podcasts, media appearances!
 Topics: AI-Native Organizations (Any Industry), BMad Method
 DM on Discord for inquiries!
 🔥 **V6 Beta is DAYS away!** January 22nd ETA!
 #AI #DevTools #Agile #OpenSource #LLM #AgentEngineering
--- a/.claude/skills/draft-changelog/SKILL.md
+++ b/.claude/skills/draft-changelog/SKILL.md
@ -1,7 +0,0 @@
 ---
 name: bmad-os-draft-changelog
 description: Analyzes changes since last release and updates CHANGELOG.md ONLY. Does NOT trigger releases.
 disable-model-invocation: true
 ---
 Read `prompts/instructions.md` and execute.
--- a/.claude/skills/draft-changelog/prompts/instructions.md
+++ b/.claude/skills/draft-changelog/prompts/instructions.md
@ -1,82 +0,0 @@
 # Draft Changelog Execution
 ## ⚠️ IMPORTANT - READ FIRST
 **This skill ONLY updates CHANGELOG.md. That is its entire purpose.**
 - **DO** update CHANGELOG.md with the new version entry
 - **DO** present the draft for user review before editing
 - **DO NOT** trigger any GitHub release workflows
 - **DO NOT** run any other skills or workflows automatically
 - **DO NOT** make any commits
 After the changelog is complete, you may suggest the user can run `/release-module` if they want to proceed with the actual release — but NEVER trigger it yourself.
 ## Input
 Project path (or run from project root)
 ## Step 1: Identify Current State
 - Get the latest released tag
 - Get current version
 - Verify there are commits since the last release
 ## Step 2: Launch Explore Agent
 Use `thoroughness: "very thorough"` to analyze all changes since the last release tag.
 **Key: For each merge commit, look up the merged PR/issue that was closed.**
 - Use `gh pr view` or git commit body to find the PR number
 - Read the PR description and comments to understand full context
 - Don't rely solely on commit merge messages - they lack context
 **Analyze:**
 1. **All merges/commits** since the last tag
 2. **For each merge, read the original PR/issue** that was closed
 3. **Files changed** with statistics
 4. **Categorize changes:**
   - 🎁 **Features** - New functionality, new agents, new workflows
   - 🐛 **Bug Fixes** - Fixed bugs, corrected issues
   - ♻️ **Refactoring** - Code improvements, reorganization
   - 📚 **Documentation** - Docs updates, README changes
   - 🔧 **Maintenance** - Dependency updates, tooling, infrastructure
   - 💥 **Breaking Changes** - Changes that may affect users
 **Provide:**
 - Comprehensive summary of ALL changes with PR context
 - Categorization of each change
 - Identification of breaking changes
 - Significance assessment (major/minor/trivial)
 ## Step 3: Generate Draft Changelog
 Format:
 ```markdown
 ## v0.X.X - [Date]
 * [Change 1 - categorized by type]
 * [Change 2]
 ```
 Guidelines:
 - Present tense ("Fix bug" not "Fixed bug")
 - Most significant changes first
 - Group related changes
 - Clear, concise language
 - For breaking changes, clearly indicate impact
 ## Step 4: Present Draft & Update CHANGELOG.md
 Show the draft with current version, last tag, commit count, and options to edit/retry.
 When user accepts:
 1. Update CHANGELOG.md with the new entry (insert at top, after `# Changelog` header)
 2. STOP. That's it. You're done.
 You may optionally suggest: *"When ready, you can run `/release-module` to create the actual release."*
 **DO NOT:**
 - Trigger any GitHub workflows
 - Run any other skills
 - Make any commits
 - Do anything beyond updating CHANGELOG.md
--- a/.claude/skills/gh-triage/README.md
+++ b/.claude/skills/gh-triage/README.md
@ -1,14 +0,0 @@
 # gh-triage
 Fetches all GitHub issues via gh CLI and uses AI agents to deeply analyze, cluster, and prioritize issues.
 ## Usage
 Run from within any BMad Method repository to triage issues.
 ## What It Does
 1. Fetches all open issues via `gh issue list`
 2. Splits issues into batches
 3. Launches parallel agents to analyze each batch
 4. Generates comprehensive triage report to `_bmad-output/triage-reports/`
--- a/.claude/skills/gh-triage/SKILL.md
+++ b/.claude/skills/gh-triage/SKILL.md
@ -1,12 +0,0 @@
 ---
 name: bmad-os-gh-triage
 description: Fetch all GitHub issues via gh CLI and use AI agents to deeply analyze, cluster, and prioritize issues
 license: MIT
 disable-model-invocation: true
 metadata:
  author: bmad-code-org
  version: "3.0.0"
 compatibility: Requires gh CLI, git repository, and BMad Method with Task tool support
 ---
 Read `prompts/instructions.md` and execute.
--- a/.claude/skills/gh-triage/prompts/agent-prompt.md
+++ b/.claude/skills/gh-triage/prompts/agent-prompt.md
@ -1,60 +0,0 @@
 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.
--- a/.claude/skills/gh-triage/prompts/instructions.md
+++ b/.claude/skills/gh-triage/prompts/instructions.md
@ -1,74 +0,0 @@
 # 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
 ### Step 1: Fetch Issues
 Use `gh issue list --json number,title,body,labels` to fetch all open issues.
 ### 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 prompt from `prompts/agent-prompt.md`
 ### 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`
 ## Report Format
 ### 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.
 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.
--- a/.claude/skills/release-module/README.md
+++ b/.claude/skills/release-module/README.md
@ -1,24 +0,0 @@
 # release-module
 Automates the complete release process for npm modules.
 ## Usage
 Run from project root or pass project path:
 ```
 bmad-utility-skills:release-module
 ```
 ## Prerequisite
 First run `draft-changelog` to analyze changes and create a draft changelog.
 ## What It Does
 1. Gets and confirms changelog entry
 2. Confirms version bump type (patch/minor/major)
 3. Updates CHANGELOG.md
 4. Bumps version with `npm version`
 5. Pushes git tag
 6. Publishes to npm
 7. Creates GitHub release
--- a/.claude/skills/release-module/SKILL.md
+++ b/.claude/skills/release-module/SKILL.md
@ -1,7 +0,0 @@
 ---
 name: bmad-os-release-module
 description: Automates the complete release process for npm modules - version bump, changelog, git tag, npm publish, GitHub release
 disable-model-invocation: true
 ---
 Read `prompts/instructions.md` and execute.
--- a/.claude/skills/release-module/prompts/instructions.md
+++ b/.claude/skills/release-module/prompts/instructions.md
@ -1,53 +0,0 @@
 # Release BMad Module Execution
 ## Input
 Project path (or run from project root)
 ## Execution Steps
 ### Step 1: Get Current State
 - Verify git working tree is clean
 - Get latest tag and current version
 - Check for unpushed commits
 ### Step 2: Get Changelog Entry
 Ask the user for the changelog entry (from draft-changelog skill or manual).
 ### Step 3: Confirm Changelog
 Show project name, current version, proposed next version, and changelog. Get confirmation.
 ### Step 4: Confirm Version Bump Type
 Ask what type of bump: patch, minor, major, prerelease, or custom.
 ### Step 5: Update CHANGELOG.md
 Insert new entry at top, commit, and push.
 ### Step 6: Bump Version
 Run `npm version` to update package.json, create commit, and create tag.
 ### Step 7: Push Tag
 Push the new version tag to GitHub.
 ### Step 8: Publish to npm
 Publish the package.
 ### Step 9: Create GitHub Release
 Create release with changelog notes using `gh release create`.
 ## Error Handling
 Stop immediately on any step failure. Inform user and suggest fix.
 ## Important Notes
 - Wait for user confirmation before destructive operations
 - Push changelog commit before version bump
 - Use explicit directory paths in commands
--- a/.github/ISSUE_TEMPLATE/bug-report.yaml
+++ b/.github/ISSUE_TEMPLATE/bug-report.yaml
@ -1,124 +0,0 @@
 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
--- a/.github/ISSUE_TEMPLATE/documentation.yaml
+++ b/.github/ISSUE_TEMPLATE/documentation.yaml
@ -1,55 +0,0 @@
 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
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
--- a/.github/workflows/quality.yaml
+++ b/.github/workflows/quality.yaml
@ -113,6 +113,3 @@ jobs:
      - name: Test agent compilation components
        run: npm run test:install
      - name: Validate file references
        run: npm run validate:refs
--- a/.gitignore
+++ b/.gitignore
@ -50,7 +50,7 @@ _bmad-output
 .qwen
 .rovodev
 .kilocodemodes
-.claude/commands
+.claude
 .codex
 .github/chatmodes
 .github/agents
--- a/.npmrc
+++ b/.npmrc
@ -1,5 +1 @@
-# Prevent peer dependency warnings during installation
+registry=https://registry.npmjs.org
 legacy-peer-deps=true
 # Improve install performance
 prefer-offline=true
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@ -58,7 +58,8 @@
    "tmpl",
    "Trae",
    "Unsharded",
-    "VNET"
+    "VNET",
    "webskip"
  ],
  "json.schemas": [
    {
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@ -1,111 +1,5 @@
 # Changelog
 ## [6.0.0-Beta.7]
 **Release: February 4, 2026**
 ### 🌟 Key Highlights
 1. **Direct Workflow Invocation** — Agent workflows can now be run directly via slash commands instead of only through agent orchestration
 2. **Installer Workflow Support** — Installer now picks up `workflow-*.md` files, enabling multiple workflow files per directory
 ### 🎁 Features
 * **Slash Command Workflow Access** — Research and PRD workflows now accessible via direct slash commands: `/domain-research`, `/market-research`, `/technical-research`, `/create-prd`, `/edit-prd`, `/validate-prd` (bd620e38, 731bee26)
 * **Version Checking** — CLI now checks npm for newer versions and displays a warning banner when updates are available (d37ee7f2)
 ### ♻️ Refactoring
 * **Workflow File Splitting** — Split monolithic `workflow.md` files into specific `workflow-*.md` files for individual workflow invocation (bd620e38)
 * **Installer Multi-Workflow Support** — Installer manifest generator now supports `workflow-*.md` pattern, allowing multiple workflow files per directory (731bee26)
 * **Internal Skill Renaming** — Renamed internal project skills to use `bmad-os-` prefix for consistent naming (5276d58b)
 ---
 ## [6.0.0-Beta.6]
 **Release: February 4, 2026**
 ### 🌟 Key Highlights
 1. **Cross-File Reference Validator**: Comprehensive tool to detect broken file references, preventing 59 known bugs (~25% of historical issues)
 2. **New AutocompleteMultiselect Prompt**: Searchable multi-select with improved tool/IDE selection UX
 3. **Critical Installer Fixes**: Windows CRLF parsing, Gemini CLI TOML support, file extension preservation
 4. **Codebase Cleanup**: Removed dead Excalidraw/flattener artifacts (-3,798 lines)
 ### 🎁 Features
 * **Cross-File Reference Validator** — Validates ~483 references across ~217 source files, detecting absolute path leaks and broken references (PR #1494)
 * **AutocompleteMultiselect Prompt** — Upgraded `@clack/prompts` to v1.0.0 with custom searchable multiselect, Tab-to-fill-placeholder behavior, and improved tool/IDE selection UX (PR #1514)
 * **OT Domains** — Added `process_control` and `building_automation` domains with high complexity ratings (PR #1510)
 * **Documentation Reference Pages** — Added `docs/reference/agents.md`, `commands.md`, and `testing.md` (PR #1525)
 ### 🐛 Bug Fixes
 * **Critical Installer Fixes** — Fixed CRLF line ending parsing on Windows, Gemini CLI TOML support, file extension preservation, Codex task generation, Windows path handling, and CSV parsing (PR #1492)
 * **Double Tool Questioning** — Removed redundant tool questioning during installation (df176d42)
 * **QA Agent Rename** — Renamed Quinn agent to `qa` for naming consistency (PR #1508)
 * **Documentation Organization** — Fixed documentation ordering and links, hide BMGD pages from main LLM docs (PR #1525)
 ### ♻️ Refactoring
 * **Excalidraw/Flattener Removal** — Removed dead artifacts no longer supported beyond beta: Excalidraw workflows, flattener tool, and 12+ diagram creation workflows (-3,798 lines) (f699a368)
 * **Centralized Constants** — Centralized `BMAD_FOLDER_NAME` to reduce hardcoded strings (PR #1492)
 * **Cross-Platform Paths** — Fixed path separator inconsistencies in agent IDs (PR #1492)
 ### 📚 Documentation
 * **BMGD Diataxis Refactor** — Refactored BMGD documentation using Diataxis principles for better organization (PR #1502)
 * **Generate Project Context** — Restored `generate-project-context` workflow for brownfield project analysis (PR #1491)
 ### 🔧 Maintenance
 * **Dependency Updates** — Upgraded `@clack/prompts` from v0.11.0 to v1.0.0 and added `@clack/core` (PR #1514)
 * **CI Integration** — Added `validate:refs` to CI quality workflow with warning annotations (PR #1494)
 ---
 ## [6.0.0-Beta.5]
 ### 🎁 Features
 * **Add generate-project-context workflow** — New 3-step workflow for project context generation, integrated with quick-flow-solo-dev agent
 * **Shard market research customer analysis** — Refactor monolithic customer insights into 4-step detailed customer behavior analysis workflow
 ### 🐛 Bug Fixes
 * **Fix npm install peer dependency issues** — Add `.npmrc` with `legacy-peer-deps=true`, update Starlight to 0.37.5, and add `--legacy-peer-deps` flag to module installer (PR #1476)
 * **Fix leaked source paths in PRD validation report** — Replace absolute `/src/core/` paths with `{project-root}/_bmad/core/` (#1481)
 * **Fix orphaned market research customer analysis** — Connect step-01-init to step-02-customer-behavior to complete workflow sharding (#1486)
 * **Fix duplicate 2-letter brainstorming code** — Change BS to BSP to resolve conflict with cis Brainstorming module
 * **Fix tech writer sidecar functionality** — Enable proper sidecar operation (#1487)
 * **Fix relative paths in workflow steps** — Correct paths in step-11-polish (#1497) and step-e-04-complete (#1498)
 * **Fix party-mode workflow file extension** — Correct extension in workflow.xml (#1499)
 * **Fix generated slash commands** — Add `disable-model-invocation` to all generated commands (#1501)
 * **Fix agent scan and help CSV files** — Correct module-help.csv entries
 * **Fix HELP_STEP placeholder replacement** — Fix placeholder not replaced in compiled agents, fix hardcoded path, fix single quote (#1437)
 ### 📚 Documentation
 * **Add exact slash commands to Getting Started guide** — Provide precise command examples for users (#1505)
 * **Remove .claude/commands from version control** — Commands are generated, not tracked (#1506)
 ### 🔧 Maintenance
 * **Update Starlight to 0.37.5** — Latest version with peer dependency compatibility
 * **Add GitHub issue templates** — New bug-report.yaml and documentation.yaml templates
 ---
 ## [6.0.0-Beta.4]
 ### 🐛 Bug Fixes
 - **Activation steps formatting fix**: Fixed missing opening quote that caused infrequent menu rendering issues
 - **Custom module installation fix**: Added missing yaml require in manifest.js to fix custom module installation
 ---
 ## [6.0.0-Beta.3]
 ### 🌟 Key Highlights
@ -1266,6 +1160,7 @@ Located in `src/modules/bmb/workflows/agent/data/`:
 - **Workflow Vendoring**: Web bundler performs automatic cross-module dependency vendoring
 - **BMGD Module Extraction**: Game development split into standalone 4-phase structure
 - **Enhanced Dependency Resolution**: Better handling of web_bundle: false workflows
 - **Advanced Elicitation Fix**: Added missing CSV files to workflow bundles
 - **Claude Code Fix**: Resolved README slash command installation regression
--- a/README.md
+++ b/README.md
@ -66,7 +66,7 @@ Every step tells you what's next. Optional phases (brainstorming, research, UX d
 BMad Method extends with official modules for specialized domains. Modules are available during installation and can be added to your project at any time. After the V6 beta period these will also be available as Plugins and Granular Skills.
 | Module                                | GitHub                                                                                                                            | NPM                                                                                                                | Purpose                                                           |
-| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
+| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- |
 | **BMad Method (BMM)**                 | [bmad-code-org/BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD)                                                         | [bmad-method](https://www.npmjs.com/package/bmad-method)                                           | Core framework with 34+ workflows across 4 development phases     |
 | **BMad Builder (BMB)**                | [bmad-code-org/bmad-builder](https://github.com/bmad-code-org/bmad-builder)                                                       | [bmad-builder](https://www.npmjs.com/package/bmad-builder)                                         | Create custom BMad agents, workflows, and domain-specific modules |
 | **Test Architect (TEA)** 🆕           | [bmad-code-org/tea](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)                                    | [tea](https://www.npmjs.com/package/bmad-method-test-architecture-enterprise)                      | Risk-based test strategy, automation, and release gates (8 workflows) |
@ -116,7 +116,6 @@ BMad provides two testing options to fit your needs:
 ### For v4 Users
 - **[v4 Documentation](https://github.com/bmad-code-org/BMAD-METHOD/tree/V4/docs)**
 - If you need to install V4, you can do this with  `npx bmad-method@4.44.3 install` - similar for any past version.
 ## Community
--- a/docs/bmgd/bmgd-logo.png
+++ b/docs/bmgd/bmgd-logo.png
--- a/docs/bmgd/game-types.md
+++ b/docs/bmgd/game-types.md
@ -1,375 +0,0 @@
 ---
 title: "Game Types Reference"
 draft: true
 ---
 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 |
--- a/docs/bmgd/index.md
+++ b/docs/bmgd/index.md
@ -1,113 +0,0 @@
 ---
 title: "BMGD Quick Guide"
 description: Quick reference for BMad Game Dev Studio
 draft: true
 ---
 ![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)
--- a/docs/bmgd/quick-flow-workflows.md
+++ b/docs/bmgd/quick-flow-workflows.md
@ -1,161 +0,0 @@
 ---
 title: "Quick Flow Workflows"
 draft: true
 ---
 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
--- a/docs/bmgd/workflow.jpg
+++ b/docs/bmgd/workflow.jpg
--- a/docs/reference/agents.md
+++ b/docs/reference/agents.md
@ -1,22 +0,0 @@
 ---
 title: Agents
 ---
 This page lists the default BMM (Agile suite) agents that install with BMAD Method, along with their menu triggers and primary workflows.
 Notes:
 - Triggers are the short menu codes (e.g., `CP`) and fuzzy matches shown in each agent menu.
 - Slash commands are generated separately. See `docs/reference/commands.md` for the slash command list and where they are defined.
 - QA (Quinn) is the lightweight test automation agent in BMM. The full Test Architect (TEA) lives in its own module.
 | Agent                       | Triggers                           | Primary workflows                                                                                   |
 | --------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------- |
 | Analyst (Mary)              | `BP`, `RS`, `CB`, `DP`             | Brainstorm Project, Research, Create Brief, Document Project                                        |
 | Product Manager (John)      | `CP`, `VP`, `EP`, `CE`, `IR`, `CC` | Create/Validate/Edit PRD, Create Epics and Stories, Implementation Readiness, Correct Course        |
 | Architect (Winston)         | `CA`, `IR`                         | Create Architecture, Implementation Readiness                                                       |
 | Scrum Master (Bob)          | `SP`, `CS`, `ER`, `CC`             | Sprint Planning, Create Story, Epic Retrospective, Correct Course                                   |
 | Developer (Amelia)          | `DS`, `CR`                         | Dev Story, Code Review                                                                              |
 | QA Engineer (Quinn)         | `QA`                               | Automate (generate tests for existing features)                                                     |
 | Quick Flow Solo Dev (Barry) | `QS`, `QD`, `CR`                   | Quick Spec, Quick Dev, Code Review                                                                  |
 | UX Designer (Sally)         | `CU`                               | Create UX Design                                                                                    |
 | Technical Writer (Paige)    | `DP`, `WD`, `US`, `MG`, `VD`, `EC` | Document Project, Write Document, Update Standards, Mermaid Generate, Validate Doc, Explain Concept |
--- a/docs/reference/commands.md
+++ b/docs/reference/commands.md
@ -1,34 +0,0 @@
 ---
 title: Commands
 description: How BMAD commands are generated and where to find them.
 ---
 # Commands
 BMAD slash commands are generated by the installer for your IDE and **reflect the modules you have installed**.  
 That means the authoritative list lives **in your project**, not in a static docs page.
 ## How to Discover Commands (Recommended)
 - Type `/bmad` in your IDE and use autocomplete to browse agents/workflows.
 - Run `/bmad-help` to get guided next steps and context-aware recommendations.
 ## Where Commands Are Generated
 The installer writes command files into your project (example paths for Claude Code):
 - `.claude/commands/bmad/<module>/agents/`
 - `.claude/commands/bmad/<module>/workflows/`
 These folders are the **canonical, project-specific command list**.
 ## Common Commands
 - `/bmad-help` - Interactive help and next-step guidance
 - `/bmad:<module>:agents:<agent>` - Load an agent (e.g. `/bmad:bmm:agents:dev`)
 - `/bmad:<module>:workflows:<workflow>` - Run a workflow (e.g. `/bmad:bmm:workflows:create-prd`)
 ## Why This Page Is Short
 BMAD is modular, so the exact commands vary by install.  
 Use your IDE's autocomplete or the generated command folders above to see *everything* available.
--- a/docs/reference/testing.md
+++ b/docs/reference/testing.md
@ -1,21 +0,0 @@
 ---
 title: Testing Options
 ---
 # Testing Options
 BMad provides a built-in QA agent for quick test automation and a separate Test Architect (TEA) module for advanced testing.
 ## Built-in QA (Quinn)
 Use the built-in QA agent for fast, straightforward test coverage:
 - Trigger: `QA` or `bmad-bmm-qa-automate`
 - Best for: small projects, quick coverage, standard patterns
 ## Test Architect (TEA) Module
 TEA is a standalone module with advanced testing workflows (test design, ATDD, automate, review, trace, NFR assessment).
 - Documentation: <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/>
 - Install: `npx bmad-method@alpha install` and select the TEA module
--- a/docs/reference/workflow-map.md
+++ b/docs/reference/workflow-map.md
@ -58,7 +58,7 @@ Build it, one story at a time.
 | `correct-course`  | Handle significant mid-sprint changes  | Updated plan or re-routing    |
 | `retrospective`   | Review after epic completion           | Lessons learned               |
-**Quinn (QA Agent):** Built-in QA agent for test automation. Trigger with `QA` or `bmad-bmm-qa-automate`. Generates standard API and E2E tests using your project's test framework. Beginner-friendly, no configuration needed. For advanced test strategy, install [Test Architect (TEA)](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) module.
+**Quinn (QA Agent):** Built-in QA agent for test automation. Trigger with `QA` or `bmad-bmm-automate`. Generates standard API and E2E tests using your project's test framework. Beginner-friendly, no configuration needed. For advanced test strategy, install [Test Architect (TEA)](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) module.
 ## Quick Flow (Parallel Track)
--- a/docs/tutorials/getting-started.md
+++ b/docs/tutorials/getting-started.md
@ -65,11 +65,7 @@ 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`) 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` on most platforms) 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.
@ -82,29 +78,29 @@ Work through phases 1-3. **Use fresh chats for each workflow.**
 ### Phase 1: Analysis (Optional)
 All workflows in this phase are optional:
- **brainstorming** (`/bmad-brainstorming`) — Guided ideation
+- **brainstorming** — Guided ideation
- **research** (`/bmad-bmm-research`) — Market and technical research
+- **research** — Market and technical research
- **create-product-brief** (`/bmad-bmm-create-product-brief`) — Recommended foundation document
+- **create-product-brief** — Recommended foundation document
 ### Phase 2: Planning (Required)
 **For BMad Method and Enterprise tracks:**
-1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat
+1. Load the **PM agent** in a new chat
-2. Run the `prd` workflow (`/bmad-bmm-create-prd`)
+2. Run the `prd` workflow
 3. Output: `PRD.md`
 **For Quick Flow track:**
- Use the `quick-spec` workflow (`/bmad-bmm-quick-spec`) instead of PRD, then skip to implementation
+- Use the `quick-spec` workflow instead of PRD, then skip to implementation
 :::note[UX Design (Optional)]
-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.
+If your project has a user interface, load the **UX-Designer agent** and run the UX design workflow after creating your PRD.
 :::
 ### Phase 3: Solutioning (BMad Method/Enterprise)
 **Create Architecture**
-1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat
+1. Load the **Architect agent** in a new chat
-2. Run `create-architecture` (`/bmad-bmm-create-architecture`)
+2. Run `create-architecture`
 3. Output: Architecture document with technical decisions
 **Create Epics and Stories**
@ -113,13 +109,13 @@ If your project has a user interface, load the **UX-Designer agent** (`/bmad-age
 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** (`/bmad-agent-bmm-pm`) in a new chat
+1. Load the **PM agent** in a new chat
-2. Run `create-epics-and-stories` (`/bmad-bmm-create-epics-and-stories`)
+2. Run `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** (`/bmad-agent-bmm-architect`) in a new chat
+1. Load the **Architect agent** in a new chat
-2. Run `check-implementation-readiness` (`/bmad-bmm-check-implementation-readiness`)
+2. Run `check-implementation-readiness`
 3. Validates cohesion across all planning documents
 ## Step 2: Build Your Project
@ -128,19 +124,19 @@ Once planning is complete, move to implementation. **Each workflow should run in
 ### Initialize Sprint Planning
-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.
+Load the **SM agent** and run `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       | Command                    | Purpose                            |
+| Step | Agent | Workflow       | Purpose                            |
-| ---- | ----- | -------------- | -------------------------- | ---------------------------------- |
+| ---- | ----- | -------------- | ---------------------------------- |
-| 1    | SM    | `create-story` | `/bmad-bmm-create-story`  | Create story file from epic        |
+| 1    | SM    | `create-story` | Create story file from epic        |
-| 2    | DEV   | `dev-story`    | `/bmad-bmm-dev-story`     | Implement the story                |
+| 2    | DEV   | `dev-story`    | Implement the story                |
-| 3    | DEV   | `code-review`  | `/bmad-bmm-code-review`   | Quality validation *(recommended)* |
+| 3    | DEV   | `code-review`  | Quality validation *(recommended)* |
-After completing all stories in an epic, load the **SM agent** (`/bmad-agent-bmm-sm`) and run `retrospective` (`/bmad-bmm-retrospective`).
+After completing all stories in an epic, load the **SM agent** and run `retrospective`.
 ## What You've Accomplished
@ -166,17 +162,17 @@ your-project/
 ## Quick Reference
-| Workflow                         | Command                                    | Agent     | Purpose                              |
+| Workflow                         | Agent     | Purpose                              |
-| -------------------------------- | ------------------------------------------ | --------- | ------------------------------------ |
+| -------------------------------- | --------- | ------------------------------------ |
-| `help`                           | `/bmad-help`                               | Any       | Get guidance on what to do next      |
+| `help`                           | Any       | Get guidance on what to do next      |
-| `prd`                            | `/bmad-bmm-create-prd`                     | PM        | Create Product Requirements Document |
+| `prd`                            | PM        | Create Product Requirements Document |
-| `create-architecture`            | `/bmad-bmm-create-architecture`            | Architect | Create architecture document         |
+| `create-architecture`            | Architect | Create architecture document         |
-| `create-epics-and-stories`       | `/bmad-bmm-create-epics-and-stories`       | PM        | Break down PRD into epics            |
+| `create-epics-and-stories`       | PM        | Break down PRD into epics            |
-| `check-implementation-readiness` | `/bmad-bmm-check-implementation-readiness` | Architect | Validate planning cohesion           |
+| `check-implementation-readiness` | Architect | Validate planning cohesion           |
-| `sprint-planning`                | `/bmad-bmm-sprint-planning`                | SM        | Initialize sprint tracking           |
+| `sprint-planning`                | SM        | Initialize sprint tracking           |
-| `create-story`                   | `/bmad-bmm-create-story`                   | SM        | Create a story file                  |
+| `create-story`                   | SM        | Create a story file                  |
-| `dev-story`                      | `/bmad-bmm-dev-story`                      | DEV       | Implement a story                    |
+| `dev-story`                      | DEV       | Implement a story                    |
-| `code-review`                    | `/bmad-bmm-code-review`                    | DEV       | Review implemented code              |
+| `code-review`                    | DEV       | Review implemented code              |
 ## Common Questions
@ -184,10 +180,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 (`/bmad-bmm-correct-course`) for handling scope changes.
+Yes. The SM agent has a `correct-course` workflow for handling scope changes.
 **What if I want to brainstorm first?**
-Load the Analyst agent (`/bmad-agent-bmm-analyst`) and run `brainstorming` (`/bmad-brainstorming`) before starting your PRD.
+Load the Analyst agent and run `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.
@ -196,14 +192,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` (`/bmad-help`) to see what to do next
+- **Stuck?** — Run `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` (`/bmad-help`) when stuck** — It detects your progress and suggests next steps
+- **Use `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.
--- a/package-lock.json
+++ b/package-lock.json
--- a/package.json
+++ b/package.json
@ -1,7 +1,7 @@
 {
  "$schema": "https://json.schemastore.org/package.json",
  "name": "bmad-method",
-  "version": "6.0.0-Beta.6",
+  "version": "6.0.0-Beta.3",
  "description": "Breakthrough Method of Agile AI-driven Development",
  "keywords": [
    "agile",
@ -39,7 +39,7 @@
    "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0",
    "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix",
    "lint:md": "markdownlint-cli2 \"**/*.md\"",
-    "prepare": "command -v husky >/dev/null 2>&1 && husky || exit 0",
+    "prepare": "husky",
    "rebundle": "node tools/cli/bundlers/bundle-web.js rebundle",
    "release:major": "gh workflow run \"Manual Release\" -f version_bump=major",
    "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor",
@ -49,7 +49,6 @@
    "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",
    "test:install": "node test/test-installation-components.js",
    "test:schemas": "node test/test-agent-schema.js",
    "validate:refs": "node tools/validate-file-refs.js",
    "validate:schemas": "node tools/validate-agent-schema.js"
  },
  "lint-staged": {
@ -69,8 +68,7 @@
    ]
  },
  "dependencies": {
-    "@clack/core": "^1.0.0",
+    "@clack/prompts": "^0.11.0",
    "@clack/prompts": "^1.0.0",
    "@kayvan/markdown-tree-parser": "^1.6.1",
    "boxen": "^5.1.2",
    "chalk": "^4.1.2",
@ -83,7 +81,6 @@
    "ignore": "^7.0.5",
    "js-yaml": "^4.1.0",
    "ora": "^5.4.1",
    "picocolors": "^1.1.1",
    "semver": "^7.6.3",
    "wrap-ansi": "^7.0.0",
    "xml2js": "^0.6.2",
@ -91,7 +88,7 @@
  },
  "devDependencies": {
    "@astrojs/sitemap": "^3.6.0",
-    "@astrojs/starlight": "^0.37.5",
+    "@astrojs/starlight": "^0.37.0",
    "@eslint/js": "^9.33.0",
    "archiver": "^7.0.1",
    "astro": "^5.16.0",
@ -102,7 +99,7 @@
    "eslint-plugin-unicorn": "^60.0.0",
    "eslint-plugin-yml": "^1.18.0",
    "husky": "^9.1.7",
-    "jest": "^30.2.0",
+    "jest": "^30.0.4",
    "lint-staged": "^16.1.1",
    "markdownlint-cli2": "^0.19.1",
    "prettier": "^3.7.4",
--- a/src/bmm/agents/analyst.agent.yaml
+++ b/src/bmm/agents/analyst.agent.yaml
@ -1,3 +1,5 @@
 # Business Analyst Agent Definition
 agent:
  metadata:
    id: "_bmad/bmm/agents/analyst.md"
@ -21,17 +23,9 @@ agent:
      data: "{project-root}/_bmad/bmm/data/project-context-template.md"
      description: "[BP] Brainstorm Project: Expert Guided Facilitation through a single or multiple techniques with a final report"
-    - trigger: MR or fuzzy match on market-research
+    - trigger: RS or fuzzy match on research
-      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md"
+      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow.md"
-      description: "[MR] Market Research: Market analysis, competitive landscape, customer needs and trends"
+      description: "[RS] Research: Choose from or specify market, domain, competitive analysis, or technical research"
    - trigger: DR or fuzzy match on domain-research
      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md"
      description: "[DR] Domain Research: Industry domain deep dive, subject matter expertise and terminology"
    - trigger: TR or fuzzy match on technical-research
      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md"
      description: "[TR] Technical Research: Technical feasibility, architecture options and implementation approaches"
    - trigger: CB or fuzzy match on product-brief
      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
--- a/src/bmm/agents/dev.agent.yaml
+++ b/src/bmm/agents/dev.agent.yaml
@ -1,6 +1,7 @@
 # Dev Implementation Agent Definition (v6)
 agent:
  webskip: true
  metadata:
    id: "_bmad/bmm/agents/dev.md"
    name: Amelia
--- a/src/bmm/agents/pm.agent.yaml
+++ b/src/bmm/agents/pm.agent.yaml
@ -1,3 +1,6 @@
 # Product Manager Agent Definition
 # This file defines the PM agent for the BMAD BMM module
 agent:
  metadata:
    id: "_bmad/bmm/agents/pm.md"
@ -19,15 +22,15 @@ agent:
  menu:
    - trigger: CP or fuzzy match on create-prd
-      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md"
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md"
      description: "[CP] Create PRD: Expert led facilitation to produce your Product Requirements Document"
    - trigger: VP or fuzzy match on validate-prd
-      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md"
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md"
      description: "[VP] Validate PRD: Validate a Product Requirements Document is comprehensive, lean, well organized and cohesive"
    - trigger: EP or fuzzy match on edit-prd
-      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md"
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md"
      description: "[EP] Edit PRD: Update an existing Product Requirements Document"
    - trigger: CE or fuzzy match on epics-stories
--- a/src/bmm/agents/quick-flow-solo-dev.agent.yaml
+++ b/src/bmm/agents/quick-flow-solo-dev.agent.yaml
@ -16,11 +16,12 @@ agent:
    principles: |
      - Planning and execution are two sides of the same coin.
      - Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't.
      - If `**/project-context.md` exists, follow it. If absent, proceed without.
  menu:
-    - trigger: QS or fuzzy match on quick-spec
+    - trigger: TS or fuzzy match on tech-spec
      exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md"
-      description: "[QS] Quick Spec: Architect a quick but complete technical spec with implementation-ready stories/specs"
+      description: "[TS] Tech 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"
--- a/src/bmm/agents/quinn.agent.yaml
+++ b/src/bmm/agents/quinn.agent.yaml
@ -1,6 +1,6 @@
 agent:
  metadata:
-    id: "_bmad/bmm/agents/qa"
+    id: "_bmad/bmm/agents/quinn"
    name: Quinn
    title: QA Engineer
    icon: 🧪
@ -27,7 +27,7 @@ agent:
    - Focus on realistic user scenarios
  menu:
-    - trigger: QA or fuzzy match on qa-automate
+    - trigger: QA
      workflow: "{project-root}/_bmad/bmm/workflows/qa/automate/workflow.yaml"
      description: "[QA] Automate - Generate tests for existing features (simplified)"
@ -54,4 +54,4 @@ agent:
        For comprehensive test strategy, risk-based planning, quality gates, and enterprise features,
        install the Test Architect (TEA) module: https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/
-        Ready to generate some tests? Just say `QA` or `bmad-bmm-qa-automate`!
+        Ready to generate some tests? Just say `QA` or `bmad-bmm-automate`!
--- a/src/bmm/agents/tech-writer/tech-writer.agent.yaml
+++ b/src/bmm/agents/tech-writer/tech-writer.agent.yaml
@ -7,7 +7,7 @@ agent:
    title: Technical Writer
    icon: 📚
    module: bmm
-    hasSidecar: true
+    hasSidecar: false
  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: US or fuzzy match on update-standards
+    - trigger: WD or fuzzy match on write-document
      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."
--- a/src/bmm/module-help.csv
+++ b/src/bmm/module-help.csv
@ -1,31 +1,32 @@
 module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
-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,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,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,Write Document,WD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,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,,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,,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,,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,,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-market-research.md,bmad-bmm-market-research,false,analyst,Create Mode,"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-domain-research.md,bmad-bmm-domain-research,false,analyst,Create Mode,"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-technical-research.md,bmad-bmm-technical-research,false,analyst,Create Mode,"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-product-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
+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,2-planning,Create PRD,CP,10,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
+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,Validate PRD,VP,20,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.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 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,Edit PRD,EP,25,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md,bmad-bmm-edit-prd,false,pm,Edit Mode,"Improve and enhance an existing PRD",planning_artifacts,"updated 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,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",
 bmm,3-solutioning,Validate Epics and Stories,VE,40,_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md,bmad-bmm-create-epics-and-stories,false,pm,Validate Mode,"Validates epics and stories completeness",planning_artifacts,"epics validation report",
 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,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,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,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,qa,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",
--- a/src/bmm/workflows/1-analysis/create-product-brief/workflow.md
+++ b/src/bmm/workflows/1-analysis/create-product-brief/workflow.md
@ -1,6 +1,7 @@
 ---
 name: create-product-brief
 description: Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
 web_bundle: true
 ---
 # Product Brief Workflow
--- a/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md
+++ b/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md
@ -138,7 +138,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-behavior.md`
+- Load: `./step-02-customer-insights.md`
 #### If 'Modify':
--- a/src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md
+++ b/src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md
@ -0,0 +1,200 @@
 # 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!
--- a/src/bmm/workflows/1-analysis/research/workflow-domain-research.md
+++ b/src/bmm/workflows/1-analysis/research/workflow-domain-research.md
@ -1,54 +0,0 @@
 ---
 name: domain-research
 description: Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.
 ---
 # Domain Research Workflow
 **Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
 **Your Role:** You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
 ## PREREQUISITE
 **⛔ Web search required.** If unavailable, abort and tell the user.
 ## CONFIGURATION
 Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as a system-generated value
 ## QUICK TOPIC DISCOVERY
 "Welcome {{user_name}}! Let's get started with your **domain/industry research**.
 **What domain, industry, or sector do you want to research?**
 For example:
 - 'The healthcare technology industry'
 - 'Sustainable packaging regulations in Europe'
 - 'Construction and building materials sector'
 - 'Or any other domain you have in mind...'"
 ### Topic Clarification
 Based on the user's topic, briefly clarify:
 1. **Core Domain**: "What specific aspect of [domain] are you most interested in?"
 2. **Research Goals**: "What do you hope to achieve with this research?"
 3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
 ## ROUTE TO DOMAIN RESEARCH STEPS
 After gathering the topic and goals:
 1. Set `research_type = "domain"`
 2. Set `research_topic = [discovered topic from discussion]`
 3. Set `research_goals = [discovered goals from discussion]`
 4. Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
 5. Load: `./domain-steps/step-01-init.md` with topic context
 **Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for domain research.
 **✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**
--- a/src/bmm/workflows/1-analysis/research/workflow-market-research.md
+++ b/src/bmm/workflows/1-analysis/research/workflow-market-research.md
@ -1,54 +0,0 @@
 ---
 name: market-research
 description: Conduct market research covering market size, growth, competition, and customer insights using current web data and verified sources.
 ---
 # Market Research Workflow
 **Goal:** Conduct comprehensive market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
 **Your Role:** You are a market research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
 ## PREREQUISITE
 **⛔ Web search required.** If unavailable, abort and tell the user.
 ## CONFIGURATION
 Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as a system-generated value
 ## QUICK TOPIC DISCOVERY
 "Welcome {{user_name}}! Let's get started with your **market research**.
 **What topic, problem, or area do you want to research?**
 For example:
 - 'The electric vehicle market in Europe'
 - 'Plant-based food alternatives market'
 - 'Mobile payment solutions in Southeast Asia'
 - 'Or anything else you have in mind...'"
 ### Topic Clarification
 Based on the user's topic, briefly clarify:
 1. **Core Topic**: "What exactly about [topic] are you most interested in?"
 2. **Research Goals**: "What do you hope to achieve with this research?"
 3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
 ## ROUTE TO MARKET RESEARCH STEPS
 After gathering the topic and goals:
 1. Set `research_type = "market"`
 2. Set `research_topic = [discovered topic from discussion]`
 3. Set `research_goals = [discovered goals from discussion]`
 4. Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
 5. Load: `./market-steps/step-01-init.md` with topic context
 **Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for market research.
 **✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**
--- a/src/bmm/workflows/1-analysis/research/workflow-technical-research.md
+++ b/src/bmm/workflows/1-analysis/research/workflow-technical-research.md
@ -1,54 +0,0 @@
 ---
 name: technical-research
 description: Conduct technical research covering technology evaluation, architecture decisions, and implementation approaches using current web data and verified sources.
 ---
 # Technical Research Workflow
 **Goal:** Conduct comprehensive technical research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
 **Your Role:** You are a technical research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
 ## PREREQUISITE
 **⛔ Web search required.** If unavailable, abort and tell the user.
 ## CONFIGURATION
 Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as a system-generated value
 ## QUICK TOPIC DISCOVERY
 "Welcome {{user_name}}! Let's get started with your **technical research**.
 **What technology, tool, or technical area do you want to research?**
 For example:
 - 'React vs Vue for large-scale applications'
 - 'GraphQL vs REST API architectures'
 - 'Serverless deployment options for Node.js'
 - 'Or any other technical topic you have in mind...'"
 ### Topic Clarification
 Based on the user's topic, briefly clarify:
 1. **Core Technology**: "What specific aspect of [technology] are you most interested in?"
 2. **Research Goals**: "What do you hope to achieve with this research?"
 3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
 ## ROUTE TO TECHNICAL RESEARCH STEPS
 After gathering the topic and goals:
 1. Set `research_type = "technical"`
 2. Set `research_topic = [discovered topic from discussion]`
 3. Set `research_goals = [discovered goals from discussion]`
 4. Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
 5. Load: `./technical-steps/step-01-init.md` with topic context
 **Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for technical research.
 **✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**
--- a/src/bmm/workflows/1-analysis/research/workflow.md
+++ b/src/bmm/workflows/1-analysis/research/workflow.md
@ -0,0 +1,173 @@
 ---
 name: research
 description: Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.
 web_bundle: true
 ---
 # Research Workflow
 **Goal:** Conduct comprehensive, exhaustive research across multiple domains using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
 **Document Standards:**
 - **Comprehensive Coverage**: Exhaustive research with no critical gaps
 - **Source Verification**: Every factual claim backed by web sources with URL citations
 - **Document Length**: As long as needed to fully cover the research topic
 - **Professional Structure**: Compelling narrative introduction, detailed TOC, and comprehensive summary
 - **Authoritative Sources**: Multiple independent sources for all critical claims
 **Your Role:** You are a research facilitator and web data analyst working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
 **Final Deliverable**: A complete research document that serves as an authoritative reference on the research topic with:
 - Compelling narrative introduction
 - Comprehensive table of contents
 - Detailed research sections with proper citations
 - Executive summary and conclusions
 ## WORKFLOW ARCHITECTURE
 This uses **micro-file architecture** with **routing-based discovery**:
 - Each research type has its own step folder
 - Step 01 discovers research type and routes to appropriate sub-workflow
 - Sequential progression within each research type
 - Document state tracked in output frontmatter
 ## INITIALIZATION
 ### Configuration Loading
 Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `project_name`, `output_folder`, , `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as a system-generated value
 ### Paths
 - `installed_path` = `{project-root}/_bmad/bmm/workflows/1-analysis/research`
 - `template_path` = `{installed_path}/research.template.md`
 - `default_output_file` = `{planning_artifacts}/research/{{research_type}}-{{topic}}-research-{{date}}.md` (dynamic based on research type)
 ## PREREQUISITE
 **⛔ Web search required.** If unavailable, abort and tell the user.
 ## RESEARCH BEHAVIOR
 ### Web Research Standards
 - **Current Data Only**: Search the web to verify and supplement your knowledge with current facts
 - **Source Verification**: Require citations for all factual claims
 - **Anti-Hallucination Protocol**: Never present information without verified sources
 - **Multiple Sources**: Require at least 2 independent sources for critical claims
 - **Conflict Resolution**: Present conflicting views and note discrepancies
 - **Confidence Levels**: Flag uncertain data with [High/Medium/Low Confidence]
 ### Source Quality Standards
 - **Distinguish Clearly**: Facts (from sources) vs Analysis (interpretation) vs Speculation
 - **URL Citation**: Always include source URLs when presenting web search data
 - **Critical Claims**: Market size, growth rates, competitive data need verification
 - **Fact Checking**: Apply fact-checking to critical data points
 ## Implementation Instructions
 Execute research type discovery and routing:
 ### Research Type Discovery
 **Your Role:** You are a research facilitator and web data analyst working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
 **Research Standards:**
 - **Anti-Hallucination Protocol**: Never present information without verified sources
 - **Current Data Only**: Search the web to verify and supplement your knowledge with current facts
 - **Source Citation**: Always include URLs for factual claims from web searches
 - **Multiple Sources**: Require 2+ independent sources for critical claims
 - **Conflict Resolution**: Present conflicting views and note discrepancies
 - **Confidence Levels**: Flag uncertain data with [High/Medium/Low Confidence]
 ### 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.
 **Let me help you clarify what you'd like to research.**
 **First, tell me: What specific topic, problem, or area do you want to research?**
 For example:
 - 'The electric vehicle market in Europe'
 - 'Cloud migration strategies for healthcare'
 - 'AI implementation in financial services'
 - 'Sustainable packaging regulations'
 - 'Or anything else you have in mind...'
 ### Topic Exploration and Clarification
 Based on the user's initial topic, explore and refine the research scope:
 #### Topic Clarification Questions:
 1. **Core Topic**: "What exactly about [topic] are you most interested in?"
 2. **Research Goals**: "What do you hope to achieve with this research?"
 3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
 4. **Timeline**: "Are you looking at current state, historical context, or future trends?"
 5. **Application**: "How will you use this research? (product development, strategy, academic, etc.)"
 #### Context Building:
 - **Initial Input**: User provides topic or research interest
 - **Collaborative Refinement**: Work together to clarify scope and objectives
 - **Goal Alignment**: Ensure research direction matches user needs
 - **Research Boundaries**: Establish clear focus areas and deliverables
 ### Research Type Identification
 After understanding the research topic and goals, identify the most appropriate research approach:
 **Research Type Options:**
 1. **Market Research** - Market size, growth, competition, customer insights
   _Best for: Understanding market dynamics, customer behavior, competitive landscape_
 2. **Domain Research** - Industry analysis, regulations, technology trends in specific domain
   _Best for: Understanding industry context, regulatory environment, ecosystem_
 3. **Technical Research** - Technology evaluation, architecture decisions, implementation approaches
   _Best for: Technical feasibility, technology selection, implementation strategies_
 **Recommendation**: Based on [topic] and [goals], I recommend [suggested research type] because [specific rationale].
 **What type of research would work best for your needs?**
 ### Research Type Routing
 <critical>Based on user selection, route to appropriate sub-workflow with the discovered topic using the following IF block sets of instructions. YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`</critical>
 #### If Market Research:
 - Set `research_type = "market"`
 - Set `research_topic = [discovered topic from discussion]`
 - Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
 - Load: `./market-steps/step-01-init.md` with topic context
 #### If Domain Research:
 - Set `research_type = "domain"`
 - Set `research_topic = [discovered topic from discussion]`
 - Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
 - Load: `./domain-steps/step-01-init.md` with topic context
 #### If Technical Research:
 - Set `research_type = "technical"`
 - Set `research_topic = [discovered topic from discussion]`
 - Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
 - Load: `./technical-steps/step-01-init.md` with topic context
 **Important**: The discovered topic from the collaborative discussion should be passed to the research initialization steps, so they don't need to ask "What do you want to research?" again - they can focus on refining the scope for their specific research type.
 **Note:** All research workflows require web search for current data and source verification.
--- a/src/bmm/workflows/2-plan-workflows/create-prd/data/domain-complexity.csv
+++ b/src/bmm/workflows/2-plan-workflows/create-prd/data/domain-complexity.csv
@ -9,7 +9,5 @@ scientific,"research,algorithm,simulation,modeling,computational,analysis,data s
 legaltech,"legal,law,contract,compliance,litigation,patent,attorney,court",high,"Legal ethics;Bar regulations;Data retention;Attorney-client privilege;Court system integration","Legal practice rules;Ethics requirements;Court filing systems;Document standards;Confidentiality","domain-research","legal technology ethics {date};law practice management software requirements;court filing system standards;attorney client privilege technology","ethics_compliance;data_retention;confidentiality_measures;court_integration"
 insuretech,"insurance,claims,underwriting,actuarial,policy,risk,premium",high,"Insurance regulations;Actuarial standards;Data privacy;Fraud detection;State compliance","Insurance regulations by state;Actuarial methods;Risk modeling;Claims processing;Regulatory reporting","domain-research","insurance software regulations {date};actuarial standards software;insurance fraud detection;state insurance compliance","regulatory_requirements;risk_modeling;fraud_detection;reporting_compliance"
 energy,"energy,utility,grid,solar,wind,power,electricity,oil,gas",high,"Grid compliance;NERC standards;Environmental regulations;Safety requirements;Real-time operations","Energy regulations;Grid standards;Environmental compliance;Safety protocols;SCADA systems","domain-research","energy sector software compliance {date};NERC CIP standards;smart grid requirements;renewable energy software standards","grid_compliance;safety_protocols;environmental_compliance;operational_requirements"
 process_control,"industrial automation,process control,PLC,SCADA,DCS,HMI,operational technology,OT,control system,cyberphysical,MES,historian,instrumentation,I&C,P&ID",high,"Functional safety;OT cybersecurity;Real-time control requirements;Legacy system integration;Process safety and hazard analysis;Environmental compliance and permitting;Engineering authority and PE requirements","Functional safety standards;OT security frameworks;Industrial protocols;Process control architecture;Plant reliability and maintainability","domain-research + technical-model","IEC 62443 OT cybersecurity requirements {date};functional safety software requirements {date};industrial process control architecture;ISA-95 manufacturing integration","functional_safety;ot_security;process_requirements;engineering_authority"
 building_automation,"building automation,BAS,BMS,HVAC,smart building,lighting control,fire alarm,fire protection,fire suppression,life safety,elevator,access control,DDC,energy management,sequence of operations,commissioning",high,"Life safety codes;Building energy standards;Multi-trade coordination and interoperability;Commissioning and ongoing operational performance;Indoor environmental quality and occupant comfort;Engineering authority and PE requirements","Building automation protocols;HVAC and mechanical controls;Fire alarm, fire protection, and life safety design;Commissioning process and sequence of operations;Building codes and energy standards","domain-research","smart building software architecture {date};BACnet integration best practices;building automation cybersecurity {date};ASHRAE building standards","life_safety;energy_compliance;commissioning_requirements;engineering_authority"
 gaming,"game,player,gameplay,level,character,multiplayer,quest",redirect,"REDIRECT TO GAME WORKFLOWS","Game design","game-brief","NA","NA"
 general,"",low,"Standard requirements;Basic security;User experience;Performance","General software practices","continue","software development best practices {date}","standard_requirements"
--- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md
+++ b/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'
--- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md
+++ b/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
--- a/src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md
+++ b/src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md
@ -0,0 +1,433 @@
 ---
 validationTarget: 'PRD Workflow Structure'
 validationDate: '2026-01-08'
 inputDocuments: []
 validationStepsCompleted: ['discovery', 'frontmatter-validation', 'content-validation', 'documentation-validation', 'integration-validation', 'corrections-applied']
 validationStatus: COMPLETE - PRODUCTION READY
 ---
 # PRD Workflow Validation Report
 **Workflow Being Validated:** /Users/brianmadison/dev/BMAD-METHOD/src/bmm/workflows/2-plan-workflows/create-prd
 **Validation Date:** 2026-01-08
 **Validator:** BMAD Workflow Validation System
 ---
 ## Executive Summary
 This validation report assesses the PRD workflow structure against BMAD workflow standards. The PRD workflow is a tri-modal workflow system with Create, Validate, and Edit phases.
 ---
 ## 1. File Structure & Size Analysis
 ### Folder Structure
 ```
 prd/
 ├── workflow.md (main workflow file)
 ├── steps-c/ (Create steps - 12 files)
 ├── steps-v/ (Validation steps - 13 files)
 ├── steps-e/ (Edit steps - 5 files)
 ├── data/
 │   └── prd-purpose.md
 └── templates/
    └── prd-template.md
 ```
 **✅ Structure Status**: PASS - All required folders present
 ### File Size Analysis
 #### Steps-C (Create Steps) - 12 files
 | File                     | Lines | Status              |
 | ------------------------ | ----- | ------------------- |
 | step-01-init.md          | 191   | ⚠️ Approaching limit |
 | step-01b-continue.md     | 153   | ✅ Good              |
 | step-02-discovery.md     | 197   | ⚠️ Approaching limit |
 | step-03-success.md       | 226   | ⚠️ Approaching limit |
 | step-04-journeys.md      | 213   | ⚠️ Approaching limit |
 | step-05-domain.md        | 193   | ⚠️ Approaching limit |
 | step-06-innovation.md    | 226   | ⚠️ Approaching limit |
 | step-07-project-type.md  | 225   | ⚠️ Approaching limit |
 | step-08-scoping.md       | 228   | ⚠️ Approaching limit |
 | step-09-functional.md    | 231   | ⚠️ Approaching limit |
 | step-10-nonfunctional.md | 242   | ⚠️ Approaching limit |
 | step-11-polish.md        | 217   | ⚠️ Approaching limit |
 | step-12-complete.md      | 185   | ✅ Good              |
 #### Steps-V (Validation Steps) - 13 files
 | File                                           | Lines | Status              |
 | ---------------------------------------------- | ----- | ------------------- |
 | step-v-01-discovery.md                         | 217   | ⚠️ Approaching limit |
 | step-v-02-format-detection.md                  | 191   | ⚠️ Approaching limit |
 | step-v-02b-parity-check.md                     | 209   | ⚠️ Approaching limit |
 | step-v-03-density-validation.md                | 174   | ✅ Good              |
 | step-v-04-brief-coverage-validation.md         | 214   | ⚠️ Approaching limit |
 | step-v-05-measurability-validation.md          | 228   | ⚠️ Approaching limit |
 | step-v-06-traceability-validation.md           | 217   | ⚠️ Approaching limit |
 | step-v-07-implementation-leakage-validation.md | 205   | ⚠️ Approaching limit |
 | step-v-08-domain-compliance-validation.md      | 243   | ⚠️ Approaching limit |
 | step-v-09-project-type-validation.md           | 263   | ❌ Exceeds limit     |
 | step-v-10-smart-validation.md                  | 209   | ⚠️ Approaching limit |
 | step-v-11-holistic-quality-validation.md       | 264   | ❌ Exceeds limit     |
 | step-v-12-completeness-validation.md           | 242   | ⚠️ Approaching limit |
 | step-v-13-report-complete.md                   | 231   | ⚠️ Approaching limit |
 #### Steps-E (Edit Steps) - 5 files
 | File                            | Lines | Status              |
 | ------------------------------- | ----- | ------------------- |
 | step-e-01-discovery.md          | 206   | ⚠️ Approaching limit |
 | step-e-01b-legacy-conversion.md | 208   | ⚠️ Approaching limit |
 | step-e-02-review.md             | 249   | ⚠️ Approaching limit |
 | step-e-03-edit.md               | 253   | ❌ Exceeds limit     |
 | step-e-04-complete.md           | 168   | ✅ Good              |
 #### Data & Templates
 | File                      | Lines | Status              |
 | ------------------------- | ----- | ------------------- |
 | data/prd-purpose.md       | 197   | ⚠️ Approaching limit |
 | templates/prd-template.md | 10    | ✅ Good              |
 | workflow.md               | 114   | ✅ Good              |
 ### File Size Statistics
 - **Total Files**: 32 markdown files
 - **✅ Good (<200 lines)**: 6 files (18.8%)
 - **⚠️ Approaching limit (200-250)**: 23 files (71.9%)
 - **❌ Exceeds limit (>250)**: 3 files (9.4%)
 - **Average lines per file**: 213.3 lines
 ### ⚠️ Recommendations
 1. **Files Exceeding 250-line limit**:
   - `step-v-09-project-type-validation.md` (263 lines) - Consider splitting into sub-steps
   - `step-v-11-holistic-quality-validation.md` (264 lines) - Consider splitting into sub-steps
   - `step-e-03-edit.md` (253 lines) - Consider splitting into sub-steps
 2. **Files Approaching Limit**:
   - Many files are in the 200-250 line range
   - Monitor these files as further additions may push them over the limit
   - Consider proactive refactoring where appropriate
 ---
 ## 2. Frontmatter Structure Validation
 ### Files Checked: 29 total files
 **✅ Overall Status:** ALL VALID - One Issue Fixed
 #### Main Workflow (workflow.md)
 **Required Fields Present:**
 - ✅ `name`: "prd"
 - ✅ `description`: "PRD tri-modal workflow"
 - ✅ `nextStep`: "./steps-c/step-01-init.md"
 - ✅ `validateWorkflow`: "./steps-v/step-v-01-discovery.md"
 - ✅ `editWorkflow`: "./steps-e/step-e-01-discovery.md" (FIXED - was assess-workflow.md)
 #### Create Steps (steps-c)
 - ✅ All 13 files have proper name, description, nextStepFile
 - ✅ Proper sequencing from step-01 through step-12
 - ✅ Consistent output file references
 #### Validation Steps (steps-v)
 - ✅ All 13 files have complete frontmatter
 - ✅ Proper sequential chain maintained
 - ✅ No broken internal references
 #### Edit Steps (steps-e)
 - ✅ All files have required fields
 - ✅ Proper routing with altStepFile references
 ### ✅ All Issues Resolved
 **1. Broken Edit Workflow Reference:**
 ```yaml
 # Current (INCORRECT):
 editWorkflow: './steps-e/step-e-01-assess-workflow.md'
 # Should be:
 editWorkflow: './steps-e/step-e-01-discovery.md'
 ```
 **2. Step Numbering Gap:**
 - Original `step-11-complete.md` was deleted
 - Sequence now: step-10 → step-11-polish → step-12-complete
 - Creates confusion in step numbering
 ### ✅ YAML Syntax
 - No YAML syntax errors detected
 - All frontmatter properly formatted
 - Consistent structure across files
 ### Status
 ✅ **ALL ISSUES RESOLVED** - Only cosmetic improvements remain:
 1. **✅ FIXED**: Edit workflow path corrected in workflow.md
 2. **⚠️ OPTIONAL**: Address step numbering gap for clarity
 3. **⚠️ OPTIONAL**: Rename step-01b-continue.md to step-01a-continue.md for consistency
 ---
 ## 3. Step File Content Validation
 ### Content Quality Assessment: 4.5/5 - EXCELLENT
 #### Files Reviewed: 10 representative files across all modes
 #### ✅ Strengths
 **1. Comprehensive Structure:**
 - Clear step goal sections in all files
 - Detailed mandatory execution rules
 - Well-defined execution protocols
 - Context boundaries clearly specified
 - Mandatory sequence with numbered steps
 - System success/failure metrics present
 **2. BMAD Compliance:**
 - ✅ JIT loading references consistently mentioned
 - ✅ State tracking requirements documented
 - ✅ Append-only building instructions present
 - ✅ Critical rules properly emphasized with emojis
 - ✅ Sequential enforcement clearly stated
 **3. Instructional Quality:**
 - Clear, unambiguous instructions
 - Proper menu handling rules (where applicable)
 - Excellent continuation checks
 - Strong role definition for each mode
 **4. Role Clarity:**
 - Create Mode: "Product-focused PM facilitator"
 - Validate Mode: "Validation Architect and Quality Assurance Specialist"
 - Edit Mode: "PRD improvement specialist"
 #### ⚠️ Minor Improvement Opportunities
 **1. Header Formatting:**
 - Some inconsistency in header level usage across files
 - Recommend standardizing H2/H3 usage
 **2. Edit Mode Completeness:**
 - Edit mode has fewer steps (5 vs 12/13 for other modes)
 - Documentation marks it as "Future" but implementation exists
 #### Recommendations
 1. **LOW PRIORITY**: Standardize header formatting across all step files
 2. **LOW PRIORITY**: Complete remaining edit mode steps for parity
 3. **MAINTAIN**: Current excellent quality standards
 ---
 ## 4. Documentation Validation
 ### Documentation Completeness: ✅ COMPREHENSIVE
 #### Main Components Present
 - ✅ Workflow Definition (workflow.md)
 - ✅ Purpose Document (data/prd-purpose.md)
 - ✅ Template (templates/prd-template.md)
 - ✅ Three Mode Implementations (Create: 12, Validate: 13, Edit: 5 steps)
 #### Clarity Assessment: ✅ EXCELLENT
 **Strong Points:**
 1. Clear mode determination (commands, flags, menu selection)
 2. Detailed routing instructions for each mode
 3. Comprehensive workflow architecture explanation
 4. Well-defined critical rules with visual emphasis
 5. Professional presentation with consistent formatting
 #### ⚠️ Minor Issues Found
 **1. Step Count Mismatch:**
 - workflow.md mentions "11 steps" for Create mode
 - Actually implements 12 steps
 - Could confuse users
 **2. Edit Mode Status:**
 - workflow.md calls Edit mode "Future"
 - Edit mode steps are actually implemented
 - Should reflect current status
 **3. Template Completeness:**
 - PRD template is minimal (10 lines)
 - Could benefit from section placeholders
 **4. Missing README:**
 - No onboarding documentation for new users
 - Not critical but would be helpful
 #### Recommendations
 **HIGH PRIORITY:**
 1. Fix step count reference to match implementation (12 steps)
 2. Update edit mode documentation to "Implemented"
 **MEDIUM PRIORITY:**
 3. Enhance PRD template with section structure
 4. Add quick-start README for new users
 **LOW PRIORITY:**
 5. Add troubleshooting section
 6. Document external dependencies (domain-complexity.csv, project-types.csv)
 ---
 ## 5. Integration & Compatibility Validation
 ### Integration Status: 85% Ready
 #### ✅ Successfully Integrated Components
 **1. Agent Menu Registration:**
 - ✅ Registered in PM agent menu
 - ✅ Trigger: `PR` or fuzzy match on `prd`
 - ✅ Command: `/bmad:bmm:workflows:create-prd`
 - ✅ Proper workflow path configuration
 **2. External Workflow References:**
 - ✅ Party-mode workflow: Exists at `/src/core/workflows/party-mode/workflow.md`
 - ✅ Advanced-elicitation task: Exists at `/src/core/workflows/advanced-elicitation/workflow.xml`
 **3. Directory Structure:**
 - ✅ Complete step architecture (all 3 modes)
 - ✅ All referenced step files exist
 - ✅ Data files available
 #### ✅ Configuration & Installation - WORKING AS DESIGNED
 **1. BMM Config Reference:**
 - Path: `{project-root}/_bmad/bmm/config.yaml`
 - **Status:** ✅ Correct installation-time placeholder
 - Resolves to actual config during workflow installation
 - **Note:** This is expected behavior, not an issue
 **2. Planning Artifacts Folder:**
 - Reference: `{planning_artifacts}/prd.md`
 - **Status:** ✅ Correct installation-time placeholder
 - Created/resolved during workflow installation
 - **Note:** This is expected behavior, not an issue
 **3. Edit Mode Implementation:**
 - Current: 5 steps (Discovery, Legacy Conversion branch, Review, Edit, Complete)
 - **Status:** ✅ Functionally complete
 - Edit mode is inherently simpler than create mode (targeted improvements vs full creation)
 - Uses subprocesses for complex operations
 - Validation integration ensures quality
 - **Note:** Edit workflow is complete and well-designed
 #### Configuration Analysis
 **Placeholder Usage:**
 - `{project-root}`: ✅ Properly used
 - `{planning_artifacts}`: ⚠️ Referenced but folder missing
 - `{nextStep}`, `{validateWorkflow}`, etc: ✅ Properly resolved
 #### Recommendations
 **✅ ALL CRITICAL ISSUES RESOLVED:**
 The only true critical issue (edit workflow path) has been fixed. All other items flagged as "critical" were actually working as designed (installation-time placeholders).
 **LOW PRIORITY:**
 3. Add CLI command registration for standalone execution (optional enhancement)
 4. Consider adding workflow to additional agent menus (UX designer, architect)
 5. Create standalone execution documentation (nice-to-have)
 6. Address step numbering gap if desired (cosmetic)
 ---
 ## 6. Executive Summary & Overall Assessment
 ### Overall Validation Status: ✅ PRODUCTION-READY
 #### Validation Scores by Category
 | Category                   | Status      | Score  | Notes                                         |
 | -------------------------- | ----------- | ------ | --------------------------------------------- |
 | **File Structure & Size**  | ⚠️ WARNINGS  | 7/10   | 3 files exceed 250-line limit, 23 approaching |
 | **Frontmatter Validation** | ✅ PASS      | 9/10   | One broken path reference                     |
 | **Step Content Quality**   | ✅ EXCELLENT | 9.5/10 | High-quality instructional design             |
 | **Documentation**          | ✅ EXCELLENT | 9/10   | Comprehensive, minor inconsistencies          |
 | **Integration**            | ✅ PASS      | 9/10   | All paths correct (one issue fixed)           |
 | **BMAD Compliance**        | ✅ EXCELLENT | 9.5/10 | Strong adherence to standards                 |
 **Overall Score: 9.2/10 - EXCELLENT**
 #### ✅ Critical Action Items - ALL RESOLVED
 **ONLY ONE TRUE CRITICAL ISSUE EXISTED - NOW FIXED:**
 1. **✅ FIXED: Edit Workflow Path**
   - File: `workflow.md` ✓ RESOLVED
   - Changed from: `./steps-e/step-e-01-assess-workflow.md`
   - Changed to: `./steps-e/step-e-01-discovery.md`
 **Items incorrectly flagged as critical (actually working as designed):**
 - ✅ Configuration path references (installation-time placeholders)
 - ✅ Planning artifacts folder (installation-time placeholder)
 #### High Priority Improvements
 2. **⚠️ Split Large Step Files** (>250 lines):
   - `step-v-09-project-type-validation.md` (263 lines)
   - `step-v-11-holistic-quality-validation.md` (264 lines)
   - `step-e-03-edit.md` (253 lines)
 3. **⚠️ Update Documentation Inconsistencies**:
   - Fix step count reference (11 → 12 steps in create mode)
   - Update edit mode status (Future → Implemented)
 #### Medium Priority Enhancements
 4. **Enhance PRD Template** (currently minimal at 10 lines)
 5. **Add quick-start README** for new users
 6. **Address step numbering gap** (cosmetic - missing step-11-complete.md)
 #### Edit Mode Status - FUNCTIONALLY COMPLETE ✅
 The edit workflow is **complete and well-designed** with 5 steps:
 - Discovery → Legacy Conversion (branch) → Review → Edit → Complete
 - Edit mode is inherently simpler than create mode (targeted improvements vs full creation)
 - Uses subprocesses for complex operations
 - Integrates with validation workflow
 **No additional steps needed.**
 ### Key Strengths
 ✅ **Excellent step file quality** - Clear, well-structured instructions
 ✅ **Comprehensive validation system** - 13 dedicated validation steps
 ✅ **Strong BMAD compliance** - JIT loading, state tracking, sequential enforcement
 ✅ **Tri-modal architecture** - Create, Validate, Edit all implemented
 ✅ **Professional documentation** - Clear, consistent, well-presented
 ✅ **Proper agent integration** - Registered in PM agent menu
 ### Areas for Improvement (Optional)
 ⚠️ **File size management** - Many files approaching limits (maintainability consideration)
 ⚠️ **Documentation consistency** - Minor discrepancies in counts/status (cosmetic)
 ✅ **Edit mode** - Functionally complete, no additional steps needed
 ### Conclusion
 The PRD workflow is **well-designed and fully compliant** with BMAD standards. The step file architecture is exemplary, the content quality is excellent, and the documentation is comprehensive. The only critical issue (edit workflow path) has been **resolved**, and all other flagged items were actually working as designed (installation-time placeholders).
 **Current Status: ✅ PRODUCTION-READY**
 **Recommended Optional Enhancements:**
 1. Split the 3 files exceeding 250-line limit (maintainability)
 2. Update documentation inconsistencies (step counts, edit mode status)
 3. Enhance PRD template and add quick-start README (user experience)
 The PRD workflow is ready for production use and fully compliant with BMAD workflow standards.
 ---
 **Validation Completed:** 2026-01-08
 **Validation Method:** Systematic subprocess analysis with maximum context coverage
 **Validator:** BMAD Workflow Validation System (Wendy - Workflow Building Master)
--- a/src/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md
+++ b/src/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md
@ -1,63 +0,0 @@
 ---
 name: create-prd
 description: Create a comprehensive PRD (Product Requirements Document) through structured workflow facilitation
 main_config: '{project-root}/_bmad/bmm/config.yaml'
 nextStep: './steps-c/step-01-init.md'
 ---
 # PRD Create Workflow
 **Goal:** Create comprehensive PRDs through structured workflow facilitation.
 **Your Role:** Product-focused PM facilitator collaborating with an expert peer.
 You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
 ## WORKFLOW ARCHITECTURE
 This uses **step-file architecture** for disciplined execution:
 ### Core Principles
 - **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
 - **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
 - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
 - **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
 - **Append-Only Building**: Build documents by appending content as directed to the output file
 ### Step Processing Rules
 1. **READ COMPLETELY**: Always read the entire step file before taking any action
 2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
 3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
 4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
 5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
 6. **LOAD NEXT**: When directed, read fully and follow the next step file
 ### Critical Rules (NO EXCEPTIONS)
 - 🛑 **NEVER** load multiple step files simultaneously
 - 📖 **ALWAYS** read entire step file before execution
 - 🚫 **NEVER** skip steps or optimize the sequence
 - 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
 - 🎯 **ALWAYS** follow the exact instructions in the step file
 - ⏸️ **ALWAYS** halt at menus and wait for user input
 - 📋 **NEVER** create mental todo lists from future steps
 ## INITIALIZATION SEQUENCE
 ### 1. Configuration Loading
 Load and read full config from {main_config} and resolve:
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
 ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
 ### 2. Route to Create Workflow
 "**Create Mode: Creating a new PRD from scratch.**"
 Read fully and follow: `{nextStep}` (steps-c/step-01-init.md)
--- a/src/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md
+++ b/src/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md
@ -1,65 +0,0 @@
 ---
 name: edit-prd
 description: Edit and improve an existing PRD - enhance clarity, completeness, and quality
 main_config: '{project-root}/_bmad/bmm/config.yaml'
 editWorkflow: './steps-e/step-e-01-discovery.md'
 ---
 # PRD Edit Workflow
 **Goal:** Edit and improve existing PRDs through structured enhancement workflow.
 **Your Role:** PRD improvement specialist.
 You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
 ## WORKFLOW ARCHITECTURE
 This uses **step-file architecture** for disciplined execution:
 ### Core Principles
 - **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
 - **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
 - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
 - **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
 - **Append-Only Building**: Build documents by appending content as directed to the output file
 ### Step Processing Rules
 1. **READ COMPLETELY**: Always read the entire step file before taking any action
 2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
 3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
 4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
 5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
 6. **LOAD NEXT**: When directed, read fully and follow the next step file
 ### Critical Rules (NO EXCEPTIONS)
 - 🛑 **NEVER** load multiple step files simultaneously
 - 📖 **ALWAYS** read entire step file before execution
 - 🚫 **NEVER** skip steps or optimize the sequence
 - 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
 - 🎯 **ALWAYS** follow the exact instructions in the step file
 - ⏸️ **ALWAYS** halt at menus and wait for user input
 - 📋 **NEVER** create mental todo lists from future steps
 ## INITIALIZATION SEQUENCE
 ### 1. Configuration Loading
 Load and read full config from {main_config} and resolve:
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
 ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
 ### 2. Route to Edit Workflow
 "**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."
 Then read fully and follow: `{editWorkflow}` (steps-e/step-e-01-discovery.md)
--- a/src/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md
+++ b/src/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md
@ -1,65 +0,0 @@
 ---
 name: validate-prd
 description: Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality
 main_config: '{project-root}/_bmad/bmm/config.yaml'
 validateWorkflow: './steps-v/step-v-01-discovery.md'
 ---
 # PRD Validate Workflow
 **Goal:** Validate existing PRDs against BMAD standards through comprehensive review.
 **Your Role:** Validation Architect and Quality Assurance Specialist.
 You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
 ## WORKFLOW ARCHITECTURE
 This uses **step-file architecture** for disciplined execution:
 ### Core Principles
 - **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
 - **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
 - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
 - **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
 - **Append-Only Building**: Build documents by appending content as directed to the output file
 ### Step Processing Rules
 1. **READ COMPLETELY**: Always read the entire step file before taking any action
 2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
 3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
 4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
 5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
 6. **LOAD NEXT**: When directed, read fully and follow the next step file
 ### Critical Rules (NO EXCEPTIONS)
 - 🛑 **NEVER** load multiple step files simultaneously
 - 📖 **ALWAYS** read entire step file before execution
 - 🚫 **NEVER** skip steps or optimize the sequence
 - 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
 - 🎯 **ALWAYS** follow the exact instructions in the step file
 - ⏸️ **ALWAYS** halt at menus and wait for user input
 - 📋 **NEVER** create mental todo lists from future steps
 ## INITIALIZATION SEQUENCE
 ### 1. Configuration Loading
 Load and read full config from {main_config} and resolve:
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
 ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
 ### 2. Route to Validate Workflow
 "**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."
 Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
--- a/src/bmm/workflows/2-plan-workflows/create-prd/workflow.md
+++ b/src/bmm/workflows/2-plan-workflows/create-prd/workflow.md
@ -0,0 +1,150 @@
 ---
 name: create-prd
 description: PRD tri-modal workflow - Create, Validate, or Edit comprehensive PRDs
 main_config: '{project-root}/_bmad/bmm/config.yaml'
 nextStep: './steps-c/step-01-init.md'
 validateWorkflow: './steps-v/step-v-01-discovery.md'
 editWorkflow: './steps-e/step-e-01-discovery.md'
 web_bundle: true
 ---
 # PRD Workflow (Tri-Modal)
 **Goal:** Create, Validate, or Edit comprehensive PRDs through structured workflows.
 **Your Role:**
 - **Create Mode:** Product-focused PM facilitator collaborating with an expert peer
 - **Validate Mode:** Validation Architect and Quality Assurance Specialist
 - **Edit Mode:** PRD improvement specialist
 You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
 ---
 ## MODE DETERMINATION
 ### Detect Workflow Mode
 Determine which mode to invoke based on:
 1. **Command/Invocation:**
   - "create prd" or "new prd" → Create mode
   - "validate prd" or "check prd" → Validate mode
   - "edit prd" or "improve prd" → Edit mode
 2. **Context Detection:**
   - If invoked with -c flag → Create mode
   - If invoked with -v flag → Validate mode
   - If invoked with -e flag → Edit mode
 3. **Menu Selection (if unclear):**
 If mode cannot be determined from invocation:
 "**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?"
 Wait for user selection.
 ### Route to Appropriate Workflow
 **IF Create Mode:**
 "**Create Mode: Creating a new PRD from scratch.**"
 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."
 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."
 Then read fully and follow: `{editWorkflow}` (steps-e/step-e-01-discovery.md)
 ---
 ## WORKFLOW ARCHITECTURE
 This uses **step-file architecture** for disciplined execution:
 ### Core Principles
 - **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
 - **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
 - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
 - **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
 - **Append-Only Building**: Build documents by appending content as directed to the output file
 ### Step Processing Rules
 1. **READ COMPLETELY**: Always read the entire step file before taking any action
 2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
 3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
 4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
 5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
 6. **LOAD NEXT**: When directed, read fully and follow the next step file
 ### Critical Rules (NO EXCEPTIONS)
 - 🛑 **NEVER** load multiple step files simultaneously
 - 📖 **ALWAYS** read entire step file before execution
 - 🚫 **NEVER** skip steps or optimize the sequence
 - 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
 - 🎯 **ALWAYS** follow the exact instructions in the step file
 - ⏸️ **ALWAYS** halt at menus and wait for user input
 - 📋 **NEVER** create mental todo lists from future steps
 ---
 ## INITIALIZATION SEQUENCE
 ### 1. Mode Determination
 **Check if mode was specified in the command invocation:**
 - If user invoked with "create prd" or "new prd" or "build prd" or "-c" or "--create" → Set mode to **create**
 - If user invoked with "validate prd" or "review prd" or "check prd" or "-v" or "--validate" → Set mode to **validate**
 - If user invoked with "edit prd" or "modify prd" or "improve prd" or "-e" or "--edit" → Set mode to **edit**
 **If mode is still unclear, ask user:**
 "**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?"
 Wait for user selection.
 ### 2. Configuration Loading
 Load and read full config from {main_config} and resolve:
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
 ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
 ### 3. Route to Appropriate Workflow
 **IF mode == create:**
 "**Create Mode: Creating a new PRD from scratch.**"
 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."
 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."
 Then read fully and follow: `{editWorkflow}` (steps-e/step-e-01-discovery.md)
--- a/src/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md
+++ b/src/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md
@ -1,6 +1,7 @@
 ---
 name: create-ux-design
 description: Work with a peer UX Design expert to plan your applications UX patterns, look and feel.
 web_bundle: true
 ---
 # Create UX Design Workflow
--- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md
+++ b/src/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md
@ -1,6 +1,7 @@
 ---
 name: check-implementation-readiness
 description: 'Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.'
 web_bundle: false
 ---
 # Implementation Readiness
--- a/src/bmm/workflows/3-solutioning/create-architecture/data/domain-complexity.csv
+++ b/src/bmm/workflows/3-solutioning/create-architecture/data/domain-complexity.csv
@ -8,6 +8,4 @@ productivity,"productivity,workflow,tasks,management,business,tools",medium,stan
 media,"content,media,video,audio,streaming,broadcast",high,advanced,"CDN architecture, video encoding, streaming protocols, content delivery"
 iot,"IoT,sensors,devices,embedded,smart,connected",high,advanced,"device communication, real-time data processing, edge computing, security"
 government,"government,civic,public,admin,policy,regulation",high,enhanced,"accessibility standards, security clearance, data privacy, audit trails"
 process_control,"industrial automation,process control,PLC,SCADA,DCS,HMI,operational technology,control system,cyberphysical,MES,instrumentation,I&C,P&ID",high,advanced,"industrial process control architecture, SCADA system design, OT cybersecurity architecture, real-time control systems"
 building_automation,"building automation,BAS,BMS,HVAC,smart building,fire alarm,fire protection,fire suppression,life safety,elevator,DDC,access control,sequence of operations,commissioning",high,advanced,"building automation architecture, BACnet integration patterns, smart building design, building management system security"
 gaming,"game,gaming,multiplayer,real-time,interactive,entertainment",high,advanced,"real-time multiplayer, game engine architecture, matchmaking, leaderboards"
--- a/src/bmm/workflows/3-solutioning/create-architecture/workflow.md
+++ b/src/bmm/workflows/3-solutioning/create-architecture/workflow.md
@ -1,6 +1,7 @@
 ---
 name: create-architecture
 description: Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.
 web_bundle: true
 ---
 # Architecture Workflow
--- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md
+++ b/src/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md
@ -1,6 +1,7 @@
 ---
 name: create-epics-and-stories
 description: 'Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.'
 web_bundle: true
 ---
 # Create Epics and Stories
--- a/src/bmm/workflows/4-implementation/code-review/workflow.yaml
+++ b/src/bmm/workflows/4-implementation/code-review/workflow.yaml
@ -46,3 +46,6 @@ input_file_patterns:
    sharded_index: "{planning_artifacts}/*epic*/index.md"
    sharded_single: "{planning_artifacts}/*epic*/epic-{{epic_num}}.md"
    load_strategy: "SELECTIVE_LOAD"
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/4-implementation/correct-course/workflow.yaml
+++ b/src/bmm/workflows/4-implementation/correct-course/workflow.yaml
@ -54,3 +54,7 @@ instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 checklist: "{installed_path}/checklist.md"
 default_output_file: "{planning_artifacts}/sprint-change-proposal-{date}.md"
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/4-implementation/create-story/workflow.yaml
+++ b/src/bmm/workflows/4-implementation/create-story/workflow.yaml
@ -55,3 +55,7 @@ input_file_patterns:
    whole: "{planning_artifacts}/*epic*.md"
    sharded: "{planning_artifacts}/*epic*/*.md"
    load_strategy: "SELECTIVE_LOAD" # Only load needed epic
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/4-implementation/dev-story/workflow.yaml
+++ b/src/bmm/workflows/4-implementation/dev-story/workflow.yaml
@ -21,3 +21,7 @@ story_file: "" # Explicit story path; auto-discovered if empty
 implementation_artifacts: "{config_source}:implementation_artifacts"
 sprint_status: "{implementation_artifacts}/sprint-status.yaml"
 project_context: "**/project-context.md"
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/4-implementation/retrospective/workflow.yaml
+++ b/src/bmm/workflows/4-implementation/retrospective/workflow.yaml
@ -53,3 +53,6 @@ input_file_patterns:
 sprint_status_file: "{implementation_artifacts}/sprint-status.yaml"
 story_directory: "{implementation_artifacts}"
 retrospectives_folder: "{implementation_artifacts}"
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
+++ b/src/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
@ -49,3 +49,7 @@ input_file_patterns:
 # Output configuration
 default_output_file: "{status_file}"
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/4-implementation/sprint-status/workflow.yaml
+++ b/src/bmm/workflows/4-implementation/sprint-status/workflow.yaml
@ -28,3 +28,9 @@ input_file_patterns:
    description: "Sprint status file generated by sprint-planning"
    whole: "{implementation_artifacts}/sprint-status.yaml"
    load_strategy: "FULL_LOAD"
 # Standalone so IDE commands get generated
 standalone: true
 # No web bundle needed
 web_bundle: false
--- a/src/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md
+++ b/src/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md
@ -2,6 +2,7 @@
 name: quick-spec
 description: Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.
 main_config: '{project-root}/_bmad/bmm/config.yaml'
 web_bundle: true
 # Checkpoint handler paths
 advanced_elicitation: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
--- a/src/bmm/workflows/document-project/workflow.yaml
+++ b/src/bmm/workflows/document-project/workflow.yaml
@ -20,3 +20,11 @@ validation: "{installed_path}/checklist.md"
 # Required data files - CRITICAL for project type detection and documentation requirements
 documentation_requirements_csv: "{installed_path}/documentation-requirements.csv"
 # Output configuration - Multiple files generated in output folder
 # Primary output: {output_folder}/project-documentation/
 # Additional files generated by sub-workflows based on project structure
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/excalidraw-diagrams/_shared/excalidraw-library.json
+++ b/src/bmm/workflows/excalidraw-diagrams/_shared/excalidraw-library.json
@ -0,0 +1,90 @@
 {
  "type": "excalidrawlib",
  "version": 2,
  "library": [
    {
      "id": "start-end-circle",
      "status": "published",
      "elements": [
        {
          "type": "ellipse",
          "width": 120,
          "height": 60,
          "strokeColor": "#1976d2",
          "backgroundColor": "#e3f2fd",
          "fillStyle": "solid",
          "strokeWidth": 2,
          "roughness": 0
        }
      ]
    },
    {
      "id": "process-rectangle",
      "status": "published",
      "elements": [
        {
          "type": "rectangle",
          "width": 160,
          "height": 80,
          "strokeColor": "#1976d2",
          "backgroundColor": "#e3f2fd",
          "fillStyle": "solid",
          "strokeWidth": 2,
          "roughness": 0,
          "roundness": {
            "type": 3,
            "value": 8
          }
        }
      ]
    },
    {
      "id": "decision-diamond",
      "status": "published",
      "elements": [
        {
          "type": "diamond",
          "width": 140,
          "height": 100,
          "strokeColor": "#f57c00",
          "backgroundColor": "#fff3e0",
          "fillStyle": "solid",
          "strokeWidth": 2,
          "roughness": 0
        }
      ]
    },
    {
      "id": "data-store",
      "status": "published",
      "elements": [
        {
          "type": "rectangle",
          "width": 140,
          "height": 80,
          "strokeColor": "#388e3c",
          "backgroundColor": "#e8f5e9",
          "fillStyle": "solid",
          "strokeWidth": 2,
          "roughness": 0
        }
      ]
    },
    {
      "id": "external-entity",
      "status": "published",
      "elements": [
        {
          "type": "rectangle",
          "width": 120,
          "height": 80,
          "strokeColor": "#7b1fa2",
          "backgroundColor": "#f3e5f5",
          "fillStyle": "solid",
          "strokeWidth": 3,
          "roughness": 0
        }
      ]
    }
  ]
 }
--- a/src/bmm/workflows/excalidraw-diagrams/_shared/excalidraw-templates.yaml
+++ b/src/bmm/workflows/excalidraw-diagrams/_shared/excalidraw-templates.yaml
@ -0,0 +1,127 @@
 flowchart:
  viewport:
    x: 0
    y: 0
    zoom: 1
  grid:
    size: 20
  spacing:
    vertical: 100
    horizontal: 180
  elements:
    start:
      type: ellipse
      width: 120
      height: 60
      label: "Start"
    process:
      type: rectangle
      width: 160
      height: 80
      roundness: 8
    decision:
      type: diamond
      width: 140
      height: 100
    end:
      type: ellipse
      width: 120
      height: 60
      label: "End"
 diagram:
  viewport:
    x: 0
    y: 0
    zoom: 1
  grid:
    size: 20
  spacing:
    vertical: 120
    horizontal: 200
  elements:
    component:
      type: rectangle
      width: 180
      height: 100
      roundness: 8
    database:
      type: rectangle
      width: 140
      height: 80
    service:
      type: rectangle
      width: 160
      height: 90
      roundness: 12
    external:
      type: rectangle
      width: 140
      height: 80
 wireframe:
  viewport:
    x: 0
    y: 0
    zoom: 0.8
  grid:
    size: 20
  spacing:
    vertical: 40
    horizontal: 40
  elements:
    container:
      type: rectangle
      width: 800
      height: 600
      strokeStyle: solid
      strokeWidth: 2
    header:
      type: rectangle
      width: 800
      height: 80
    button:
      type: rectangle
      width: 120
      height: 40
      roundness: 4
    input:
      type: rectangle
      width: 300
      height: 40
      roundness: 4
    text:
      type: text
      fontSize: 16
 dataflow:
  viewport:
    x: 0
    y: 0
    zoom: 1
  grid:
    size: 20
  spacing:
    vertical: 120
    horizontal: 200
  elements:
    process:
      type: ellipse
      width: 140
      height: 80
      label: "Process"
    datastore:
      type: rectangle
      width: 140
      height: 80
      label: "Data Store"
    external:
      type: rectangle
      width: 120
      height: 80
      strokeWidth: 3
      label: "External Entity"
    dataflow:
      type: arrow
      strokeWidth: 2
      label: "Data Flow"
--- a/src/bmm/workflows/excalidraw-diagrams/create-dataflow/checklist.md
+++ b/src/bmm/workflows/excalidraw-diagrams/create-dataflow/checklist.md
@ -0,0 +1,39 @@
 # Create Data Flow Diagram - Validation Checklist
 ## DFD Notation
 - [ ] Processes shown as circles/ellipses
 - [ ] Data stores shown as parallel lines or rectangles
 - [ ] External entities shown as rectangles
 - [ ] Data flows shown as labeled arrows
 - [ ] Follows standard DFD notation
 ## Structure
 - [ ] All processes numbered correctly
 - [ ] All data flows labeled with data names
 - [ ] All data stores named appropriately
 - [ ] External entities clearly identified
 ## Completeness
 - [ ] All inputs and outputs accounted for
 - [ ] No orphaned processes (unconnected)
 - [ ] Data conservation maintained
 - [ ] Level appropriate (context/level 0/level 1)
 ## Layout
 - [ ] Logical flow direction (left to right, top to bottom)
 - [ ] No crossing data flows where avoidable
 - [ ] Balanced layout
 - [ ] Grid alignment maintained
 ## Technical Quality
 - [ ] All elements properly grouped
 - [ ] Arrows have proper bindings
 - [ ] Text readable and properly sized
 - [ ] No elements with `isDeleted: true`
 - [ ] JSON is valid
 - [ ] File saved to correct location
--- a/src/bmm/workflows/excalidraw-diagrams/create-dataflow/instructions.md
+++ b/src/bmm/workflows/excalidraw-diagrams/create-dataflow/instructions.md
@ -0,0 +1,130 @@
 # Create Data Flow Diagram - Workflow Instructions
 ```xml
 <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>This workflow creates data flow diagrams (DFD) in Excalidraw format.</critical>
 <workflow>
  <step n="0" goal="Contextual Analysis">
    <action>Review user's request and extract: DFD level, processes, data stores, external entities</action>
    <check if="ALL requirements clear"><action>Skip to Step 4</action></check>
  </step>
  <step n="1" goal="Identify DFD Level" elicit="true">
    <action>Ask: "What level of DFD do you need?"</action>
    <action>Present options:
      1. Context Diagram (Level 0) - Single process showing system boundaries
      2. Level 1 DFD - Major processes and data flows
      3. Level 2 DFD - Detailed sub-processes
      4. Custom - Specify your requirements
    </action>
    <action>WAIT for selection</action>
  </step>
  <step n="2" goal="Gather Requirements" elicit="true">
    <action>Ask: "Describe the processes, data stores, and external entities in your system"</action>
    <action>WAIT for user description</action>
    <action>Summarize what will be included and confirm with user</action>
  </step>
  <step n="3" goal="Theme Setup" elicit="true">
    <action>Check for existing theme.json, ask to use if exists</action>
    <check if="no existing theme">
      <action>Ask: "Choose a DFD color scheme:"</action>
      <action>Present numbered options:
        1. Standard DFD
           - Process: #e3f2fd (light blue)
           - Data Store: #e8f5e9 (light green)
           - External Entity: #f3e5f5 (light purple)
           - Border: #1976d2 (blue)
        2. Colorful DFD
           - Process: #fff9c4 (light yellow)
           - Data Store: #c5e1a5 (light lime)
           - External Entity: #ffccbc (light coral)
           - Border: #f57c00 (orange)
        3. Minimal DFD
           - Process: #f5f5f5 (light gray)
           - Data Store: #eeeeee (gray)
           - External Entity: #e0e0e0 (medium gray)
           - Border: #616161 (dark gray)
        4. Custom - Define your own colors
      </action>
      <action>WAIT for selection</action>
      <action>Create theme.json based on selection</action>
    </check>
  </step>
  <step n="4" goal="Plan DFD Structure">
    <action>List all processes with numbers (1.0, 2.0, etc.)</action>
    <action>List all data stores (D1, D2, etc.)</action>
    <action>List all external entities</action>
    <action>Map all data flows with labels</action>
    <action>Show planned structure, confirm with user</action>
  </step>
  <step n="5" goal="Load Resources">
    <action>Load {{templates}} and extract `dataflow` section</action>
    <action>Load {{library}}</action>
    <action>Load theme.json</action>
    <action>Load {{helpers}}</action>
  </step>
  <step n="6" goal="Build DFD Elements">
    <critical>Follow standard DFD notation from {{helpers}}</critical>
    <substep>Build Order:
      1. External entities (rectangles, bold border)
      2. Processes (circles/ellipses with numbers)
      3. Data stores (parallel lines or rectangles)
      4. Data flows (labeled arrows)
    </substep>
    <substep>DFD Rules:
      - Processes: Numbered (1.0, 2.0), verb phrases
      - Data stores: Named (D1, D2), noun phrases
      - External entities: Named, noun phrases
      - Data flows: Labeled with data names, arrows show direction
      - No direct flow between external entities
      - No direct flow between data stores
    </substep>
    <substep>Layout:
      - External entities at edges
      - Processes in center
      - Data stores between processes
      - Minimize crossing flows
      - Left-to-right or top-to-bottom flow
    </substep>
  </step>
  <step n="7" goal="Optimize and Save">
    <action>Verify DFD rules compliance</action>
    <action>Strip unused elements and elements with isDeleted: true</action>
    <action>Save to {{default_output_file}}</action>
  </step>
  <step n="8" goal="Validate JSON Syntax">
    <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{default_output_file}}', 'utf8')); console.log('✓ Valid JSON')"</action>
    <check if="validation fails (exit code 1)">
      <action>Read the error message carefully - it shows the syntax error and position</action>
      <action>Open the file and navigate to the error location</action>
      <action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>
      <action>Save the file</action>
      <action>Re-run validation with the same command</action>
      <action>Repeat until validation passes</action>
    </check>
    <action>Once validation passes, confirm with user</action>
  </step>
  <step n="9" goal="Validate Content">
    <invoke-task>Validate against {{validation}}</invoke-task>
  </step>
 </workflow>
 ```
--- a/src/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml
+++ b/src/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml
@ -0,0 +1,27 @@
 name: create-excalidraw-dataflow
 description: "Create data flow diagrams (DFD) in Excalidraw format"
 author: "BMad"
 # Config values
 config_source: "{project-root}/_bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 # Workflow components
 installed_path: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow"
 shared_path: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/_shared"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Core Excalidraw resources (universal knowledge)
 helpers: "{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md"
 json_validation: "{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md"
 # Domain-specific resources (technical diagrams)
 templates: "{shared_path}/excalidraw-templates.yaml"
 library: "{shared_path}/excalidraw-library.json"
 # Output file (respects user's configured output_folder)
 default_output_file: "{output_folder}/excalidraw-diagrams/dataflow-{timestamp}.excalidraw"
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/excalidraw-diagrams/create-diagram/checklist.md
+++ b/src/bmm/workflows/excalidraw-diagrams/create-diagram/checklist.md
@ -0,0 +1,43 @@
 # Create Diagram - Validation Checklist
 ## Element Structure
 - [ ] All components with labels have matching `groupIds`
 - [ ] All text elements have `containerId` pointing to parent component
 - [ ] Text width calculated properly (no cutoff)
 - [ ] Text alignment appropriate for diagram type
 ## Layout and Alignment
 - [ ] All elements snapped to 20px grid
 - [ ] Component spacing consistent (40px/60px)
 - [ ] Hierarchical alignment maintained
 - [ ] No overlapping elements
 ## Connections
 - [ ] All arrows have `startBinding` and `endBinding`
 - [ ] `boundElements` array updated on connected components
 - [ ] Arrow routing avoids overlaps
 - [ ] Relationship types clearly indicated
 ## Notation and Standards
 - [ ] Follows specified notation standard (UML/ERD/etc)
 - [ ] Symbols used correctly
 - [ ] Cardinality/multiplicity shown where needed
 - [ ] Labels and annotations clear
 ## Theme and Styling
 - [ ] Theme colors applied consistently
 - [ ] Component types visually distinguishable
 - [ ] Text is readable
 - [ ] Professional appearance
 ## Output Quality
 - [ ] Element count under 80
 - [ ] No elements with `isDeleted: true`
 - [ ] JSON is valid
 - [ ] File saved to correct location
--- a/src/bmm/workflows/excalidraw-diagrams/create-diagram/instructions.md
+++ b/src/bmm/workflows/excalidraw-diagrams/create-diagram/instructions.md
@ -0,0 +1,141 @@
 # Create Diagram - Workflow Instructions
 ```xml
 <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>This workflow creates system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format.</critical>
 <workflow>
  <step n="0" goal="Contextual Analysis">
    <action>Review user's request and extract: diagram type, components/entities, relationships, notation preferences</action>
    <check if="ALL requirements clear"><action>Skip to Step 5</action></check>
    <check if="SOME requirements clear"><action>Only ask about missing info in Steps 1-2</action></check>
  </step>
  <step n="1" goal="Identify Diagram Type" elicit="true">
    <action>Ask: "What type of technical diagram do you need?"</action>
    <action>Present options:
      1. System Architecture
      2. Entity-Relationship Diagram (ERD)
      3. UML Class Diagram
      4. UML Sequence Diagram
      5. UML Use Case Diagram
      6. Network Diagram
      7. Other
    </action>
    <action>WAIT for selection</action>
  </step>
  <step n="2" goal="Gather Requirements" elicit="true">
    <action>Ask: "Describe the components/entities and their relationships"</action>
    <action>Ask: "What notation standard? (Standard/Simplified/Strict UML-ERD)"</action>
    <action>WAIT for user input</action>
    <action>Summarize what will be included and confirm with user</action>
  </step>
  <step n="3" goal="Check for Existing Theme" elicit="true">
    <action>Check if theme.json exists at output location</action>
    <check if="exists"><action>Ask to use it, load if yes, else proceed to Step 4</action></check>
    <check if="not exists"><action>Proceed to Step 4</action></check>
  </step>
  <step n="4" goal="Create Theme" elicit="true">
    <action>Ask: "Choose a color scheme for your diagram:"</action>
    <action>Present numbered options:
      1. Professional
         - Component: #e3f2fd (light blue)
         - Database: #e8f5e9 (light green)
         - Service: #fff3e0 (light orange)
         - Border: #1976d2 (blue)
      2. Colorful
         - Component: #e1bee7 (light purple)
         - Database: #c5e1a5 (light lime)
         - Service: #ffccbc (light coral)
         - Border: #7b1fa2 (purple)
      3. Minimal
         - Component: #f5f5f5 (light gray)
         - Database: #eeeeee (gray)
         - Service: #e0e0e0 (medium gray)
         - Border: #616161 (dark gray)
      4. Custom - Define your own colors
    </action>
    <action>WAIT for selection</action>
    <action>Create theme.json based on selection</action>
    <action>Show preview and confirm</action>
  </step>
  <step n="5" goal="Plan Diagram Structure">
    <action>List all components/entities</action>
    <action>Map all relationships</action>
    <action>Show planned layout</action>
    <action>Ask: "Structure looks correct? (yes/no)"</action>
    <check if="no"><action>Adjust and repeat</action></check>
  </step>
  <step n="6" goal="Load Resources">
    <action>Load {{templates}} and extract `diagram` section</action>
    <action>Load {{library}}</action>
    <action>Load theme.json and merge with template</action>
    <action>Load {{helpers}} for guidelines</action>
  </step>
  <step n="7" goal="Build Diagram Elements">
    <critical>Follow {{helpers}} for proper element creation</critical>
    <substep>For Each Component:
      - Generate unique IDs (component-id, text-id, group-id)
      - Create shape with groupIds
      - Calculate text width
      - Create text with containerId and matching groupIds
      - Add boundElements
    </substep>
    <substep>For Each Connection:
      - Determine arrow type (straight/elbow)
      - Create with startBinding and endBinding
      - Update boundElements on both components
    </substep>
    <substep>Build Order by Type:
      - Architecture: Services → Databases → Connections → Labels
      - ERD: Entities → Attributes → Relationships → Cardinality
      - UML Class: Classes → Attributes → Methods → Relationships
      - UML Sequence: Actors → Lifelines → Messages → Returns
      - UML Use Case: Actors → Use Cases → Relationships
    </substep>
    <substep>Alignment:
      - Snap to 20px grid
      - Space: 40px between components, 60px between sections
    </substep>
  </step>
  <step n="8" goal="Optimize and Save">
    <action>Strip unused elements and elements with isDeleted: true</action>
    <action>Save to {{default_output_file}}</action>
  </step>
  <step n="9" goal="Validate JSON Syntax">
    <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{default_output_file}}', 'utf8')); console.log('✓ Valid JSON')"</action>
    <check if="validation fails (exit code 1)">
      <action>Read the error message carefully - it shows the syntax error and position</action>
      <action>Open the file and navigate to the error location</action>
      <action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>
      <action>Save the file</action>
      <action>Re-run validation with the same command</action>
      <action>Repeat until validation passes</action>
    </check>
    <action>Once validation passes, confirm: "Diagram created at {{default_output_file}}. Open to view?"</action>
  </step>
  <step n="10" goal="Validate Content">
    <invoke-task>Validate against {{validation}} using {_bmad}/core/tasks/validate-workflow.xml</invoke-task>
  </step>
 </workflow>
 ```
--- a/src/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml
+++ b/src/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml
@ -0,0 +1,27 @@
 name: create-excalidraw-diagram
 description: "Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format"
 author: "BMad"
 # Config values
 config_source: "{project-root}/_bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 # Workflow components
 installed_path: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-diagram"
 shared_path: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/_shared"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Core Excalidraw resources (universal knowledge)
 helpers: "{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md"
 json_validation: "{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md"
 # Domain-specific resources (technical diagrams)
 templates: "{shared_path}/excalidraw-templates.yaml"
 library: "{shared_path}/excalidraw-library.json"
 # Output file (respects user's configured output_folder)
 default_output_file: "{output_folder}/excalidraw-diagrams/diagram-{timestamp}.excalidraw"
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/excalidraw-diagrams/create-flowchart/checklist.md
+++ b/src/bmm/workflows/excalidraw-diagrams/create-flowchart/checklist.md
@ -0,0 +1,49 @@
 # Create Flowchart - Validation Checklist
 ## Element Structure
 - [ ] All shapes with labels have matching `groupIds`
 - [ ] All text elements have `containerId` pointing to parent shape
 - [ ] Text width calculated properly (no cutoff)
 - [ ] Text alignment set (`textAlign` + `verticalAlign`)
 ## Layout and Alignment
 - [ ] All elements snapped to 20px grid
 - [ ] Consistent spacing between elements (60px minimum)
 - [ ] Vertical alignment maintained for flow direction
 - [ ] No overlapping elements
 ## Connections
 - [ ] All arrows have `startBinding` and `endBinding`
 - [ ] `boundElements` array updated on connected shapes
 - [ ] Arrow types appropriate (straight for forward, elbow for backward/upward)
 - [ ] Gap set to 10 for all bindings
 ## Theme and Styling
 - [ ] Theme colors applied consistently
 - [ ] All shapes use theme primary fill color
 - [ ] All borders use theme accent color
 - [ ] Text color is readable (#1e1e1e)
 ## Composition
 - [ ] Element count under 50
 - [ ] Library components referenced where possible
 - [ ] No duplicate element definitions
 ## Output Quality
 - [ ] No elements with `isDeleted: true`
 - [ ] JSON is valid
 - [ ] File saved to correct location
 ## Functional Requirements
 - [ ] Start point clearly marked
 - [ ] End point clearly marked
 - [ ] All process steps labeled
 - [ ] Decision points use diamond shapes
 - [ ] Flow direction is clear and logical
--- a/src/bmm/workflows/excalidraw-diagrams/create-flowchart/instructions.md
+++ b/src/bmm/workflows/excalidraw-diagrams/create-flowchart/instructions.md
@ -0,0 +1,241 @@
 # Create Flowchart - Workflow Instructions
 ```xml
 <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>This workflow creates a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows.</critical>
 <workflow>
  <step n="0" goal="Contextual Analysis (Smart Elicitation)">
    <critical>Before asking any questions, analyze what the user has already told you</critical>
    <action>Review the user's initial request and conversation history</action>
    <action>Extract any mentioned: flowchart type, complexity, decision points, save location</action>
    <check if="ALL requirements are clear from context">
      <action>Summarize your understanding</action>
      <action>Skip directly to Step 4 (Plan Flowchart Layout)</action>
    </check>
    <check if="SOME requirements are clear">
      <action>Note what you already know</action>
      <action>Only ask about missing information in Step 1</action>
    </check>
    <check if="requirements are unclear or minimal">
      <action>Proceed with full elicitation in Step 1</action>
    </check>
  </step>
  <step n="1" goal="Gather Requirements" elicit="true">
    <action>Ask Question 1: "What type of process flow do you need to visualize?"</action>
    <action>Present numbered options:
      1. Business Process Flow - Document business workflows, approval processes, or operational procedures
      2. Algorithm/Logic Flow - Visualize code logic, decision trees, or computational processes
      3. User Journey Flow - Map user interactions, navigation paths, or experience flows
      4. Data Processing Pipeline - Show data transformation, ETL processes, or processing stages
      5. Other - Describe your specific flowchart needs
    </action>
    <action>WAIT for user selection (1-5)</action>
    <action>Ask Question 2: "How many main steps are in this flow?"</action>
    <action>Present numbered options:
      1. Simple (3-5 steps) - Quick process with few decision points
      2. Medium (6-10 steps) - Standard workflow with some branching
      3. Complex (11-20 steps) - Detailed process with multiple decision points
      4. Very Complex (20+ steps) - Comprehensive workflow requiring careful layout
    </action>
    <action>WAIT for user selection (1-4)</action>
    <action>Store selection in {{complexity}}</action>
    <action>Ask Question 3: "Does your flow include decision points (yes/no branches)?"</action>
    <action>Present numbered options:
      1. No decisions - Linear flow from start to end
      2. Few decisions (1-2) - Simple branching with yes/no paths
      3. Multiple decisions (3-5) - Several conditional branches
      4. Complex decisions (6+) - Extensive branching logic
    </action>
    <action>WAIT for user selection (1-4)</action>
    <action>Store selection in {{decision_points}}</action>
    <action>Ask Question 4: "Where should the flowchart be saved?"</action>
    <action>Present numbered options:
      1. Default location - docs/flowcharts/[auto-generated-name].excalidraw
      2. Custom path - Specify your own file path
      3. Project root - Save in main project directory
      4. Specific folder - Choose from existing folders
    </action>
    <action>WAIT for user selection (1-4)</action>
    <check if="selection is 2 or 4">
      <action>Ask for specific path</action>
      <action>WAIT for user input</action>
    </check>
    <action>Store final path in {{default_output_file}}</action>
  </step>
  <step n="2" goal="Check for Existing Theme" elicit="true">
    <action>Check if theme.json exists at output location</action>
    <check if="theme.json exists">
      <action>Ask: "Found existing theme. Use it? (yes/no)"</action>
      <action>WAIT for user response</action>
      <check if="user says yes">
        <action>Load and use existing theme</action>
        <action>Skip to Step 4</action>
      </check>
      <check if="user says no">
        <action>Proceed to Step 3</action>
      </check>
    </check>
    <check if="theme.json does not exist">
      <action>Proceed to Step 3</action>
    </check>
  </step>
  <step n="3" goal="Create Theme" elicit="true">
    <action>Ask: "Let's create a theme for your flowchart. Choose a color scheme:"</action>
    <action>Present numbered options:
      1. Professional Blue
         - Primary Fill: #e3f2fd (light blue)
         - Accent/Border: #1976d2 (blue)
         - Decision: #fff3e0 (light orange)
         - Text: #1e1e1e (dark gray)
      2. Success Green
         - Primary Fill: #e8f5e9 (light green)
         - Accent/Border: #388e3c (green)
         - Decision: #fff9c4 (light yellow)
         - Text: #1e1e1e (dark gray)
      3. Neutral Gray
         - Primary Fill: #f5f5f5 (light gray)
         - Accent/Border: #616161 (gray)
         - Decision: #e0e0e0 (medium gray)
         - Text: #1e1e1e (dark gray)
      4. Warm Orange
         - Primary Fill: #fff3e0 (light orange)
         - Accent/Border: #f57c00 (orange)
         - Decision: #ffe0b2 (peach)
         - Text: #1e1e1e (dark gray)
      5. Custom Colors - Define your own color palette
    </action>
    <action>WAIT for user selection (1-5)</action>
    <action>Store selection in {{theme_choice}}</action>
    <check if="selection is 5 (Custom)">
      <action>Ask: "Primary fill color (hex code)?"</action>
      <action>WAIT for user input</action>
      <action>Store in {{custom_colors.primary_fill}}</action>
      <action>Ask: "Accent/border color (hex code)?"</action>
      <action>WAIT for user input</action>
      <action>Store in {{custom_colors.accent}}</action>
      <action>Ask: "Decision color (hex code)?"</action>
      <action>WAIT for user input</action>
      <action>Store in {{custom_colors.decision}}</action>
    </check>
    <action>Create theme.json with selected colors</action>
    <action>Show theme preview with all colors</action>
    <action>Ask: "Theme looks good?"</action>
    <action>Present numbered options:
      1. Yes, use this theme - Proceed with theme
      2. No, adjust colors - Modify color selections
      3. Start over - Choose different preset
    </action>
    <action>WAIT for selection (1-3)</action>
    <check if="selection is 2 or 3">
      <action>Repeat Step 3</action>
    </check>
  </step>
  <step n="4" goal="Plan Flowchart Layout">
    <action>List all steps and decision points based on gathered requirements</action>
    <action>Show user the planned structure</action>
    <action>Ask: "Structure looks correct? (yes/no)"</action>
    <action>WAIT for user response</action>
    <check if="user says no">
      <action>Adjust structure based on feedback</action>
      <action>Repeat this step</action>
    </check>
  </step>
  <step n="5" goal="Load Template and Resources">
    <action>Load {{templates}} file</action>
    <action>Extract `flowchart` section from YAML</action>
    <action>Load {{library}} file</action>
    <action>Load theme.json and merge colors with template</action>
    <action>Load {{helpers}} for element creation guidelines</action>
  </step>
  <step n="6" goal="Build Flowchart Elements">
    <critical>Follow guidelines from {{helpers}} for proper element creation</critical>
    <action>Build ONE section at a time following these rules:</action>
    <substep>For Each Shape with Label:
      1. Generate unique IDs (shape-id, text-id, group-id)
      2. Create shape with groupIds: [group-id]
      3. Calculate text width: (text.length × fontSize × 0.6) + 20, round to nearest 10
      4. Create text element with:
         - containerId: shape-id
         - groupIds: [group-id] (SAME as shape)
         - textAlign: "center"
         - verticalAlign: "middle"
         - width: calculated width
      5. Add boundElements to shape referencing text
    </substep>
    <substep>For Each Arrow:
      1. Determine arrow type needed:
         - Straight: For forward flow (left-to-right, top-to-bottom)
         - Elbow: For upward flow, backward flow, or complex routing
      2. Create arrow with startBinding and endBinding
      3. Set startBinding.elementId to source shape ID
      4. Set endBinding.elementId to target shape ID
      5. Set gap: 10 for both bindings
      6. If elbow arrow, add intermediate points for direction changes
      7. Update boundElements on both connected shapes
    </substep>
    <substep>Alignment:
      - Snap all x, y to 20px grid
      - Align shapes vertically (same x for vertical flow)
      - Space elements: 60px between shapes
    </substep>
    <substep>Build Order:
      1. Start point (circle) with label
      2. Each process step (rectangle) with label
      3. Each decision point (diamond) with label
      4. End point (circle) with label
      5. Connect all with bound arrows
    </substep>
  </step>
  <step n="7" goal="Optimize and Save">
    <action>Strip unused elements and elements with isDeleted: true</action>
    <action>Save to {{default_output_file}}</action>
  </step>
  <step n="8" goal="Validate JSON Syntax">
    <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{default_output_file}}', 'utf8')); console.log('✓ Valid JSON')"</action>
    <check if="validation fails (exit code 1)">
      <action>Read the error message carefully - it shows the syntax error and position</action>
      <action>Open the file and navigate to the error location</action>
      <action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>
      <action>Save the file</action>
      <action>Re-run validation with the same command</action>
      <action>Repeat until validation passes</action>
    </check>
    <action>Once validation passes, confirm with user: "Flowchart created at {{default_output_file}}. Open to view?"</action>
  </step>
  <step n="9" goal="Validate Content">
    <invoke-task>Validate against checklist at {{validation}} using {_bmad}/core/tasks/validate-workflow.xml</invoke-task>
  </step>
 </workflow>
 ```
--- a/src/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
+++ b/src/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
@ -0,0 +1,27 @@
 name: create-excalidraw-flowchart
 description: "Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows"
 author: "BMad"
 # Config values
 config_source: "{project-root}/_bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 # Workflow components
 installed_path: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart"
 shared_path: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/_shared"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Core Excalidraw resources (universal knowledge)
 helpers: "{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md"
 json_validation: "{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md"
 # Domain-specific resources (technical diagrams)
 templates: "{shared_path}/excalidraw-templates.yaml"
 library: "{shared_path}/excalidraw-library.json"
 # Output file (respects user's configured output_folder)
 default_output_file: "{output_folder}/excalidraw-diagrams/flowchart-{timestamp}.excalidraw"
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/excalidraw-diagrams/create-wireframe/checklist.md
+++ b/src/bmm/workflows/excalidraw-diagrams/create-wireframe/checklist.md
@ -0,0 +1,38 @@
 # Create Wireframe - Validation Checklist
 ## Layout Structure
 - [ ] Screen dimensions appropriate for device type
 - [ ] Grid alignment (20px) maintained
 - [ ] Consistent spacing between UI elements
 - [ ] Proper hierarchy (header, content, footer)
 ## UI Elements
 - [ ] All interactive elements clearly marked
 - [ ] Buttons, inputs, and controls properly sized
 - [ ] Text labels readable and appropriately sized
 - [ ] Navigation elements clearly indicated
 ## Fidelity
 - [ ] Matches requested fidelity level (low/medium/high)
 - [ ] Appropriate level of detail
 - [ ] Placeholder content used where needed
 - [ ] No unnecessary decoration for low-fidelity
 ## Annotations
 - [ ] Key interactions annotated
 - [ ] Flow indicators present if multi-screen
 - [ ] Important notes included
 - [ ] Element purposes clear
 ## Technical Quality
 - [ ] All elements properly grouped
 - [ ] Text elements have containerId
 - [ ] Snapped to grid
 - [ ] No elements with `isDeleted: true`
 - [ ] JSON is valid
 - [ ] File saved to correct location
--- a/src/bmm/workflows/excalidraw-diagrams/create-wireframe/instructions.md
+++ b/src/bmm/workflows/excalidraw-diagrams/create-wireframe/instructions.md
@ -0,0 +1,133 @@
 # Create Wireframe - Workflow Instructions
 ```xml
 <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>This workflow creates website or app wireframes in Excalidraw format.</critical>
 <workflow>
  <step n="0" goal="Contextual Analysis">
    <action>Review user's request and extract: wireframe type, fidelity level, screen count, device type, save location</action>
    <check if="ALL requirements clear"><action>Skip to Step 5</action></check>
  </step>
  <step n="1" goal="Identify Wireframe Type" elicit="true">
    <action>Ask: "What type of wireframe do you need?"</action>
    <action>Present options:
      1. Website (Desktop)
      2. Mobile App (iOS/Android)
      3. Web App (Responsive)
      4. Tablet App
      5. Multi-platform
    </action>
    <action>WAIT for selection</action>
  </step>
  <step n="2" goal="Gather Requirements" elicit="true">
    <action>Ask fidelity level (Low/Medium/High)</action>
    <action>Ask screen count (Single/Few 2-3/Multiple 4-6/Many 7+)</action>
    <action>Ask device dimensions or use standard</action>
    <action>Ask save location</action>
  </step>
  <step n="3" goal="Check Theme" elicit="true">
    <action>Check for existing theme.json, ask to use if exists</action>
  </step>
  <step n="4" goal="Create Theme" elicit="true">
    <action>Ask: "Choose a wireframe style:"</action>
    <action>Present numbered options:
      1. Classic Wireframe
         - Background: #ffffff (white)
         - Container: #f5f5f5 (light gray)
         - Border: #9e9e9e (gray)
         - Text: #424242 (dark gray)
      2. High Contrast
         - Background: #ffffff (white)
         - Container: #eeeeee (light gray)
         - Border: #212121 (black)
         - Text: #000000 (black)
      3. Blueprint Style
         - Background: #1a237e (dark blue)
         - Container: #3949ab (blue)
         - Border: #7986cb (light blue)
         - Text: #ffffff (white)
      4. Custom - Define your own colors
    </action>
    <action>WAIT for selection</action>
    <action>Create theme.json based on selection</action>
    <action>Confirm with user</action>
  </step>
  <step n="5" goal="Plan Wireframe Structure">
    <action>List all screens and their purposes</action>
    <action>Map navigation flow between screens</action>
    <action>Identify key UI elements for each screen</action>
    <action>Show planned structure, confirm with user</action>
  </step>
  <step n="6" goal="Load Resources">
    <action>Load {{templates}} and extract `wireframe` section</action>
    <action>Load {{library}}</action>
    <action>Load theme.json</action>
    <action>Load {{helpers}}</action>
  </step>
  <step n="7" goal="Build Wireframe Elements">
    <critical>Follow {{helpers}} for proper element creation</critical>
    <substep>For Each Screen:
      - Create container/frame
      - Add header section
      - Add content areas
      - Add navigation elements
      - Add interactive elements (buttons, inputs)
      - Add labels and annotations
    </substep>
    <substep>Build Order:
      1. Screen containers
      2. Layout sections (header, content, footer)
      3. Navigation elements
      4. Content blocks
      5. Interactive elements
      6. Labels and annotations
      7. Flow indicators (if multi-screen)
    </substep>
    <substep>Fidelity Guidelines:
      - Low: Basic shapes, minimal detail, placeholder text
      - Medium: More defined elements, some styling, representative content
      - High: Detailed elements, realistic sizing, actual content examples
    </substep>
  </step>
  <step n="8" goal="Optimize and Save">
    <action>Strip unused elements and elements with isDeleted: true</action>
    <action>Save to {{default_output_file}}</action>
  </step>
  <step n="9" goal="Validate JSON Syntax">
    <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{default_output_file}}', 'utf8')); console.log('✓ Valid JSON')"</action>
    <check if="validation fails (exit code 1)">
      <action>Read the error message carefully - it shows the syntax error and position</action>
      <action>Open the file and navigate to the error location</action>
      <action>Fix the syntax error (add missing comma, bracket, or quote as indicated)</action>
      <action>Save the file</action>
      <action>Re-run validation with the same command</action>
      <action>Repeat until validation passes</action>
    </check>
    <action>Once validation passes, confirm with user</action>
  </step>
  <step n="10" goal="Validate Content">
    <invoke-task>Validate against {{validation}}</invoke-task>
  </step>
 </workflow>
 ```
--- a/src/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml
+++ b/src/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml
@ -0,0 +1,27 @@
 name: create-excalidraw-wireframe
 description: "Create website or app wireframes in Excalidraw format"
 author: "BMad"
 # Config values
 config_source: "{project-root}/_bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 # Workflow components
 installed_path: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe"
 shared_path: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/_shared"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 # Core Excalidraw resources (universal knowledge)
 helpers: "{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md"
 json_validation: "{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md"
 # Domain-specific resources (technical diagrams)
 templates: "{shared_path}/excalidraw-templates.yaml"
 library: "{shared_path}/excalidraw-library.json"
 # Output file (respects user's configured output_folder)
 default_output_file: "{output_folder}/excalidraw-diagrams/wireframe-{timestamp}.excalidraw"
 standalone: true
 web_bundle: false
--- a/src/bmm/workflows/generate-project-context/project-context-template.md
+++ b/src/bmm/workflows/generate-project-context/project-context-template.md
@ -1,21 +0,0 @@
 ---
 project_name: '{{project_name}}'
 user_name: '{{user_name}}'
 date: '{{date}}'
 sections_completed: ['technology_stack']
 existing_patterns_found: { { number_of_patterns_discovered } }
 ---
 # Project Context for AI Agents
 _This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._
 ---
 ## Technology Stack & Versions
 _Documented after discovery phase_
 ## Critical Implementation Rules
 _Documented after discovery phase_
--- a/src/bmm/workflows/generate-project-context/steps/step-01-discover.md
+++ b/src/bmm/workflows/generate-project-context/steps/step-01-discover.md
@ -1,184 +0,0 @@
 # Step 1: Context Discovery & Initialization
 ## MANDATORY EXECUTION RULES (READ FIRST):
 - 🛑 NEVER generate content without user input
 - ✅ ALWAYS treat this as collaborative discovery between technical peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on discovering existing project context and technology stack
 - 🎯 IDENTIFY critical implementation rules that AI agents need
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 ## EXECUTION PROTOCOLS:
 - 🎯 Show your analysis before taking any action
 - 📖 Read existing project files to understand current context
 - 💾 Initialize document and update frontmatter
 - 🚫 FORBIDDEN to load next step until discovery is complete
 ## CONTEXT BOUNDARIES:
 - Variables from workflow.md are available in memory
 - Focus on existing project files and architecture decisions
 - Look for patterns, conventions, and unique requirements
 - Prioritize rules that prevent implementation mistakes
 ## YOUR TASK:
 Discover the project's technology stack, existing patterns, and critical implementation rules that AI agents must follow when writing code.
 ## DISCOVERY SEQUENCE:
 ### 1. Check for Existing Project Context
 First, check if project context already exists:
 - Look for file at `{project_knowledge}/project-context.md or {project-root}/**/project-context.md`
 - If exists: Read complete file to understand existing rules
 - Present to user: "Found existing project context with {number_of_sections} sections. Would you like to update this or create a new one?"
 ### 2. Discover Project Technology Stack
 Load and analyze project files to identify technologies:
 **Architecture Document:**
 - Look for `{planning_artifacts}/architecture.md`
 - Extract technology choices with specific versions
 - Note architectural decisions that affect implementation
 **Package Files:**
 - Check for `package.json`, `requirements.txt`, `Cargo.toml`, etc.
 - Extract exact versions of all dependencies
 - Note development vs production dependencies
 **Configuration Files:**
 - Look for project language specific configs ( example: `tsconfig.json`)
 - Build tool configs (webpack, vite, next.config.js, etc.)
 - Linting and formatting configs (.eslintrc, .prettierrc, etc.)
 - Testing configurations (jest.config.js, vitest.config.ts, etc.)
 ### 3. Identify Existing Code Patterns
 Search through existing codebase for patterns:
 **Naming Conventions:**
 - File naming patterns (PascalCase, kebab-case, etc.)
 - Component/function naming conventions
 - Variable naming patterns
 - Test file naming patterns
 **Code Organization:**
 - How components are structured
 - Where utilities and helpers are placed
 - How services are organized
 - Test organization patterns
 **Documentation Patterns:**
 - Comment styles and conventions
 - Documentation requirements
 - README and API doc patterns
 ### 4. Extract Critical Implementation Rules
 Look for rules that AI agents might miss:
 **Language-Specific Rules:**
 - TypeScript strict mode requirements
 - Import/export conventions
 - Async/await vs Promise usage patterns
 - Error handling patterns specific to the language
 **Framework-Specific Rules:**
 - React hooks usage patterns
 - API route conventions
 - Middleware usage patterns
 - State management patterns
 **Testing Rules:**
 - Test structure requirements
 - Mock usage conventions
 - Integration vs unit test boundaries
 - Coverage requirements
 **Development Workflow Rules:**
 - Branch naming conventions
 - Commit message patterns
 - PR review requirements
 - Deployment procedures
 ### 5. Initialize Project Context Document
 Based on discovery, create or update the context document:
 #### A. Fresh Document Setup (if no existing context)
 Copy template from `{installed_path}/project-context-template.md` to `{output_folder}/project-context.md`
 Initialize frontmatter fields.
 #### B. Existing Document Update
 Load existing context and prepare for updates
 Set frontmatter `sections_completed` to track what will be updated
 ### 6. Present Discovery Summary
 Report findings to user:
 "Welcome {{user_name}}! I've analyzed your project for {{project_name}} to discover the context that AI agents need.
 **Technology Stack Discovered:**
 {{list_of_technologies_with_versions}}
 **Existing Patterns Found:**
 - {{number_of_patterns}} implementation patterns
 - {{number_of_conventions}} coding conventions
 - {{number_of_rules}} critical rules
 **Key Areas for Context Rules:**
 - {{area_1}} (e.g., TypeScript configuration)
 - {{area_2}} (e.g., Testing patterns)
 - {{area_3}} (e.g., Code organization)
 {if_existing_context}
 **Existing Context:** Found {{sections}} sections already defined. We can update or add to these.
 {/if_existing_context}
 Ready to create/update your project context. This will help AI agents implement code consistently with your project's standards.
 [C] Continue to context generation"
 ## SUCCESS METRICS:
 ✅ Existing project context properly detected and handled
 ✅ Technology stack accurately identified with versions
 ✅ Critical implementation patterns discovered
 ✅ Project context document properly initialized
 ✅ Discovery findings clearly presented to user
 ✅ User ready to proceed with context generation
 ## FAILURE MODES:
 ❌ Not checking for existing project context before creating new one
 ❌ Missing critical technology versions or configurations
 ❌ Overlooking important coding patterns or conventions
 ❌ Not initializing frontmatter properly
 ❌ Not presenting clear discovery summary to user
 ## NEXT STEP:
 After user selects [C] to continue, load `./step-02-generate.md` to collaboratively generate the specific project context rules.
 Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and discovery is confirmed and the initial file has been written as directed in this discovery step!
--- a/src/bmm/workflows/generate-project-context/steps/step-02-generate.md
+++ b/src/bmm/workflows/generate-project-context/steps/step-02-generate.md
@ -1,318 +0,0 @@
 # Step 2: Context Rules Generation
 ## MANDATORY EXECUTION RULES (READ FIRST):
 - 🛑 NEVER generate content without user input
 - ✅ ALWAYS treat this as collaborative discovery between technical peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on unobvious rules that AI agents need to be reminded of
 - 🎯 KEEP CONTENT LEAN - optimize for LLM context efficiency
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 ## EXECUTION PROTOCOLS:
 - 🎯 Show your analysis before taking any action
 - 📝 Focus on specific, actionable rules rather than general advice
 - ⚠️ Present A/P/C menu after each major rule category
 - 💾 ONLY save when user chooses C (Continue)
 - 📖 Update frontmatter with completed sections
 - 🚫 FORBIDDEN to load next step until all sections are complete
 ## COLLABORATION MENUS (A/P/C):
 This step will generate content and present choices for each rule category:
 - **A (Advanced Elicitation)**: Use discovery protocols to explore nuanced implementation rules
 - **P (Party Mode)**: Bring multiple perspectives to identify critical edge cases
 - **C (Continue)**: Save the current rules and proceed to next category
 ## PROTOCOL INTEGRATION:
 - When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 ## CONTEXT BOUNDARIES:
 - Discovery results from step-1 are available
 - Technology stack and existing patterns are identified
 - Focus on rules that prevent implementation mistakes
 - Prioritize unobvious details that AI agents might miss
 ## YOUR TASK:
 Collaboratively generate specific, critical rules that AI agents must follow when implementing code in this project.
 ## CONTEXT GENERATION SEQUENCE:
 ### 1. Technology Stack & Versions
 Document the exact technology stack from discovery:
 **Core Technologies:**
 Based on user skill level, present findings:
 **Expert Mode:**
 "Technology stack from your architecture and package files:
 {{exact_technologies_with_versions}}
 Any critical version constraints I should document for agents?"
 **Intermediate Mode:**
 "I found your technology stack:
 **Core Technologies:**
 {{main_technologies_with_versions}}
 **Key Dependencies:**
 {{important_dependencies_with_versions}}
 Are there any version constraints or compatibility notes agents should know about?"
 **Beginner Mode:**
 "Here are the technologies you're using:
 **Main Technologies:**
 {{friendly_description_of_tech_stack}}
 **Important Notes:**
 {{key_things_agents_need_to_know_about_versions}}
 Should I document any special version rules or compatibility requirements?"
 ### 2. Language-Specific Rules
 Focus on unobvious language patterns agents might miss:
 **TypeScript/JavaScript Rules:**
 "Based on your codebase, I notice some specific patterns:
 **Configuration Requirements:**
 {{typescript_config_rules}}
 **Import/Export Patterns:**
 {{import_export_conventions}}
 **Error Handling Patterns:**
 {{error_handling_requirements}}
 Are these patterns correct? Any other language-specific rules agents should follow?"
 **Python/Ruby/Other Language Rules:**
 Adapt to the actual language in use with similar focused questions.
 ### 3. Framework-Specific Rules
 Document framework-specific patterns:
 **React Rules (if applicable):**
 "For React development, I see these patterns:
 **Hooks Usage:**
 {{hooks_usage_patterns}}
 **Component Structure:**
 {{component_organization_rules}}
 **State Management:**
 {{state_management_patterns}}
 **Performance Rules:**
 {{performance_optimization_requirements}}
 Should I add any other React-specific rules?"
 **Other Framework Rules:**
 Adapt for Vue, Angular, Next.js, Express, etc.
 ### 4. Testing Rules
 Focus on testing patterns that ensure consistency:
 **Test Structure Rules:**
 "Your testing setup shows these patterns:
 **Test Organization:**
 {{test_file_organization}}
 **Mock Usage:**
 {{mock_patterns_and_conventions}}
 **Test Coverage Requirements:**
 {{coverage_expectations}}
 **Integration vs Unit Test Rules:**
 {{test_boundary_patterns}}
 Are there testing rules agents should always follow?"
 ### 5. Code Quality & Style Rules
 Document critical style and quality rules:
 **Linting/Formatting:**
 "Your code style configuration requires:
 **ESLint/Prettier Rules:**
 {{specific_linting_rules}}
 **Code Organization:**
 {{file_and_folder_structure_rules}}
 **Naming Conventions:**
 {{naming_patterns_agents_must_follow}}
 **Documentation Requirements:**
 {{comment_and_documentation_patterns}}
 Any additional code quality rules?"
 ### 6. Development Workflow Rules
 Document workflow patterns that affect implementation:
 **Git/Repository Rules:**
 "Your project uses these patterns:
 **Branch Naming:**
 {{branch_naming_conventions}}
 **Commit Message Format:**
 {{commit_message_patterns}}
 **PR Requirements:**
 {{pull_request_checklist}}
 **Deployment Patterns:**
 {{deployment_considerations}}
 Should I document any other workflow rules?"
 ### 7. Critical Don't-Miss Rules
 Identify rules that prevent common mistakes:
 **Anti-Patterns to Avoid:**
 "Based on your codebase, here are critical things agents must NOT do:
 {{critical_anti_patterns_with_examples}}
 **Edge Cases:**
 {{specific_edge_cases_agents_should_handle}}
 **Security Rules:**
 {{security_considerations_agents_must_follow}}
 **Performance Gotchas:**
 {{performance_patterns_to_avoid}}
 Are there other 'gotchas' agents should know about?"
 ### 8. Generate Context Content
 For each category, prepare lean content for the project context file:
 #### Content Structure:
 ```markdown
 ## Technology Stack & Versions
 {{concise_technology_list_with_exact_versions}}
 ## Critical Implementation Rules
 ### Language-Specific Rules
 {{bullet_points_of_critical_language_rules}}
 ### Framework-Specific Rules
 {{bullet_points_of_framework_patterns}}
 ### Testing Rules
 {{bullet_points_of_testing_requirements}}
 ### Code Quality & Style Rules
 {{bullet_points_of_style_and_quality_rules}}
 ### Development Workflow Rules
 {{bullet_points_of_workflow_patterns}}
 ### Critical Don't-Miss Rules
 {{bullet_points_of_anti_patterns_and_edge_cases}}
 ```
 ### 9. Present Content and Menu
 After each category, show the generated rules and present choices:
 "I've drafted the {{category_name}} rules for your project context.
 **Here's what I'll add:**
 [Show the complete markdown content for this category]
 **What would you like to do?**
 [A] Advanced Elicitation - Explore nuanced rules for this category
 [P] Party Mode - Review from different implementation perspectives
 [C] Continue - Save these rules and move to next category"
 ### 10. Handle Menu Selection
 #### If 'A' (Advanced Elicitation):
 - Execute advanced-elicitation.xml with current category rules
 - Process enhanced rules that come back
 - Ask user: "Accept these enhanced rules for {{category}}? (y/n)"
 - If yes: Update content, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
 #### If 'P' (Party Mode):
 - Execute party-mode workflow with category rules context
 - Process collaborative insights on implementation patterns
 - Ask user: "Accept these changes to {{category}} rules? (y/n)"
 - If yes: Update content, then return to A/P/C menu
 - If no: Keep original content, then return to A/P/C menu
 #### If 'C' (Continue):
 - Save the current category content to project context file
 - Update frontmatter: `sections_completed: [...]`
 - Proceed to next category or step-03 if complete
 ## APPEND TO PROJECT CONTEXT:
 When user selects 'C' for a category, append the content directly to `{output_folder}/project-context.md` using the structure from step 8.
 ## SUCCESS METRICS:
 ✅ All critical technology versions accurately documented
 ✅ Language-specific rules cover unobvious patterns
 ✅ Framework rules capture project-specific conventions
 ✅ Testing rules ensure consistent test quality
 ✅ Code quality rules maintain project standards
 ✅ Workflow rules prevent implementation conflicts
 ✅ Content is lean and optimized for LLM context
 ✅ A/P/C menu presented and handled correctly for each category
 ## FAILURE MODES:
 ❌ Including obvious rules that agents already know
 ❌ Making content too verbose for LLM context efficiency
 ❌ Missing critical anti-patterns or edge cases
 ❌ Not getting user validation for each rule category
 ❌ Not documenting exact versions and configurations
 ❌ Not presenting A/P/C menu after content generation
 ## NEXT STEP:
 After completing all rule categories and user selects 'C' for the final category, load `./step-03-complete.md` to finalize the project context file.
 Remember: Do NOT proceed to step-03 until all categories are complete and user explicitly selects 'C' for each!
--- a/src/bmm/workflows/generate-project-context/steps/step-03-complete.md
+++ b/src/bmm/workflows/generate-project-context/steps/step-03-complete.md
@ -1,278 +0,0 @@
 # Step 3: Context Completion & Finalization
 ## MANDATORY EXECUTION RULES (READ FIRST):
 - 🛑 NEVER generate content without user input
 - ✅ ALWAYS treat this as collaborative completion between technical peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on finalizing a lean, LLM-optimized project context
 - 🎯 ENSURE all critical rules are captured and actionable
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 ## EXECUTION PROTOCOLS:
 - 🎯 Show your analysis before taking any action
 - 📝 Review and optimize content for LLM context efficiency
 - 📖 Update frontmatter with completion status
 - 🚫 NO MORE STEPS - this is the final step
 ## CONTEXT BOUNDARIES:
 - All rule categories from step-2 are complete
 - Technology stack and versions are documented
 - Focus on final review, optimization, and completion
 - Ensure the context file is ready for AI agent consumption
 ## YOUR TASK:
 Complete the project context file, optimize it for LLM efficiency, and provide guidance for usage and maintenance.
 ## COMPLETION SEQUENCE:
 ### 1. Review Complete Context File
 Read the entire project context file and analyze:
 **Content Analysis:**
 - Total length and readability for LLMs
 - Clarity and specificity of rules
 - Coverage of all critical areas
 - Actionability of each rule
 **Structure Analysis:**
 - Logical organization of sections
 - Consistency of formatting
 - Absence of redundant or obvious information
 - Optimization for quick scanning
 ### 2. Optimize for LLM Context
 Ensure the file is lean and efficient:
 **Content Optimization:**
 - Remove any redundant rules or obvious information
 - Combine related rules into concise bullet points
 - Use specific, actionable language
 - Ensure each rule provides unique value
 **Formatting Optimization:**
 - Use consistent markdown formatting
 - Implement clear section hierarchy
 - Ensure scannability with strategic use of bolding
 - Maintain readability while maximizing information density
 ### 3. Final Content Structure
 Ensure the final structure follows this optimized format:
 ```markdown
 # Project Context for AI Agents
 _This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._
 ---
 ## Technology Stack & Versions
 {{concise_technology_list}}
 ## Critical Implementation Rules
 ### Language-Specific Rules
 {{specific_language_rules}}
 ### Framework-Specific Rules
 {{framework_patterns}}
 ### Testing Rules
 {{testing_requirements}}
 ### Code Quality & Style Rules
 {{style_and_quality_patterns}}
 ### Development Workflow Rules
 {{workflow_patterns}}
 ### Critical Don't-Miss Rules
 {{anti_patterns_and_edge_cases}}
 ---
 ## Usage Guidelines
 **For AI Agents:**
 - Read this file before implementing any code
 - Follow ALL rules exactly as documented
 - When in doubt, prefer the more restrictive option
 - Update this file if new patterns emerge
 **For Humans:**
 - Keep this file lean and focused on agent needs
 - Update when technology stack changes
 - Review quarterly for outdated rules
 - Remove rules that become obvious over time
 Last Updated: {{date}}
 ```
 ### 4. Present Completion Summary
 Based on user skill level, present the completion:
 **Expert Mode:**
 "Project context complete. Optimized for LLM consumption with {{rule_count}} critical rules across {{section_count}} sections.
 File saved to: `{output_folder}/project-context.md`
 Ready for AI agent integration."
 **Intermediate Mode:**
 "Your project context is complete and optimized for AI agents!
 **What we created:**
 - {{rule_count}} critical implementation rules
 - Technology stack with exact versions
 - Framework-specific patterns and conventions
 - Testing and quality guidelines
 - Workflow and anti-pattern rules
 **Key benefits:**
 - AI agents will implement consistently with your standards
 - Reduced context switching and implementation errors
 - Clear guidance for unobvious project requirements
 **Next steps:**
 - AI agents should read this file before implementing
 - Update as your project evolves
 - Review periodically for optimization"
 **Beginner Mode:**
 "Excellent! Your project context guide is ready! 🎉
 **What this does:**
 Think of this as a 'rules of the road' guide for AI agents working on your project. It ensures they all follow the same patterns and avoid common mistakes.
 **What's included:**
 - Exact technology versions to use
 - Critical coding rules they might miss
 - Testing and quality standards
 - Workflow patterns to follow
 **How AI agents use it:**
 They read this file before writing any code, ensuring everything they create follows your project's standards perfectly.
 Your project context is saved and ready to help agents implement consistently!"
 ### 5. Final File Updates
 Update the project context file with completion information:
 **Frontmatter Update:**
 ```yaml
 ---
 project_name: '{{project_name}}'
 user_name: '{{user_name}}'
 date: '{{date}}'
 sections_completed:
  ['technology_stack', 'language_rules', 'framework_rules', 'testing_rules', 'quality_rules', 'workflow_rules', 'anti_patterns']
 status: 'complete'
 rule_count: { { total_rules } }
 optimized_for_llm: true
 ---
 ```
 **Add Usage Section:**
 Append the usage guidelines from step 3 to complete the document.
 ### 6. Completion Validation
 Final checks before completion:
 **Content Validation:**
 ✅ All critical technology versions documented
 ✅ Language-specific rules are specific and actionable
 ✅ Framework rules cover project conventions
 ✅ Testing rules ensure consistency
 ✅ Code quality rules maintain standards
 ✅ Workflow rules prevent conflicts
 ✅ Anti-pattern rules prevent common mistakes
 **Format Validation:**
 ✅ Content is lean and optimized for LLMs
 ✅ Structure is logical and scannable
 ✅ No redundant or obvious information
 ✅ Consistent formatting throughout
 ### 7. Completion Message
 Present final completion to user:
 "✅ **Project Context Generation Complete!**
 Your optimized project context file is ready at:
 `{output_folder}/project-context.md`
 **📊 Context Summary:**
 - {{rule_count}} critical rules for AI agents
 - {{section_count}} comprehensive sections
 - Optimized for LLM context efficiency
 - Ready for immediate agent integration
 **🎯 Key Benefits:**
 - Consistent implementation across all AI agents
 - Reduced common mistakes and edge cases
 - Clear guidance for project-specific patterns
 - Minimal LLM context usage
 **📋 Next Steps:**
 1. AI agents will automatically read this file when implementing
 2. Update this file when your technology stack or patterns evolve
 3. Review quarterly to optimize and remove outdated rules
 Your project context will help ensure high-quality, consistent implementation across all development work. Great work capturing your project's critical implementation requirements!"
 ## SUCCESS METRICS:
 ✅ Complete project context file with all critical rules
 ✅ Content optimized for LLM context efficiency
 ✅ All technology versions and patterns documented
 ✅ File structure is logical and scannable
 ✅ Usage guidelines included for agents and humans
 ✅ Frontmatter properly updated with completion status
 ✅ User provided with clear next steps and benefits
 ## FAILURE MODES:
 ❌ Final content is too verbose for LLM consumption
 ❌ Missing critical implementation rules or patterns
 ❌ Not optimizing content for agent readability
 ❌ Not providing clear usage guidelines
 ❌ Frontmatter not properly updated
 ❌ Not validating file completion before ending
 ## WORKFLOW COMPLETE:
 This is the final step of the Generate Project Context workflow. The user now has a comprehensive, optimized project context file that will ensure consistent, high-quality implementation across all AI agents working on the project.
 The project context file serves as the critical "rules of the road" that agents need to implement code consistently with the project's standards and patterns.
--- a/src/bmm/workflows/generate-project-context/workflow.md
+++ b/src/bmm/workflows/generate-project-context/workflow.md
@ -1,49 +0,0 @@
 ---
 name: generate-project-context
 description: Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.
 ---
 # Generate Project Context Workflow
 **Goal:** Create a concise, optimized `project-context.md` file containing critical rules, patterns, and guidelines that AI agents must follow when implementing code. This file focuses on unobvious details that LLMs need to be reminded of.
 **Your Role:** You are a technical facilitator working with a peer to capture the essential implementation rules that will ensure consistent, high-quality code generation across all AI agents working on the project.
 ---
 ## WORKFLOW ARCHITECTURE
 This uses **micro-file architecture** for disciplined execution:
 - Each step is a self-contained file with embedded rules
 - Sequential progression with user control at each step
 - Document state tracked in frontmatter
 - Focus on lean, LLM-optimized content generation
 - You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation.
 ---
 ## INITIALIZATION
 ### Configuration Loading
 Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 ### Paths
 - `installed_path` = `{project-root}/_bmad/bmm/workflows/generate-project-context`
 - `template_path` = `{installed_path}/project-context-template.md`
 - `output_file` = `{output_folder}/project-context.md`
 ---
 ## EXECUTION
 Load and execute `steps/step-01-discover.md` to begin the workflow.
 **Note:** Input document discovery and initialization protocols are handled in step-01-discover.md.
--- a/src/bmm/workflows/qa/automate/workflow.yaml
+++ b/src/bmm/workflows/qa/automate/workflow.yaml
@ -45,3 +45,5 @@ execution_hints:
  interactive: false
  autonomous: true
  iterative: false
 web_bundle: false
--- a/src/core/module-help.csv
+++ b/src/core/module-help.csv
@ -1,9 +1,9 @@
 module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs
-core,anytime,Brainstorming,BSP,,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,,"Generate diverse ideas through interactive techniques. Use early in ideation phase or when stuck generating ideas.",{output_folder}/brainstorming/brainstorming-session-{{date}}.md,,
+core,,Brainstorming,BS,20,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,,Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods,{output_folder}/brainstorming/brainstorming-session-{{date}}.md,,
-core,anytime,Party Mode,PM,,_bmad/core/workflows/party-mode/workflow.md,bmad-party-mode,false,party-mode facilitator,,"Orchestrate multi-agent discussions. Use when you need multiple agent perspectives or want agents to collaborate.",,
+core,,Party Mode,PM,30,_bmad/core/workflows/party-mode/workflow.md,bmad-party-mode,false,party-mode facilitator,,Orchestrates group discussions between all installed BMAD agents enabling natural multi-agent conversations,,
-core,anytime,bmad-help,BH,,_bmad/core/tasks/help.md,bmad-help,false,,,"Get unstuck by showing what workflow steps come next or answering BMad Method questions.",,
+core,,bmad-help,BH,40,_bmad/core/tasks/help.md,bmad-help,false,,,Get unstuck by showing what workflow steps come next or answering questions about what to do in the BMad Method,,
-core,anytime,Index Docs,ID,,_bmad/core/tasks/index-docs.xml,bmad-index-docs,false,,,"Create lightweight index for quick LLM scanning. Use when LLM needs to understand available docs without loading everything.",,
+core,,Index Docs,ID,50,_bmad/core/tasks/index-docs.xml,bmad-index-docs,false,,,Generates or updates an index.md of all documents in the specified directory,,
-core,anytime,Shard Document,SD,,_bmad/core/tasks/shard-doc.xml,bmad-shard-doc,false,,,"Split large documents into smaller files by sections. Use when doc becomes too large (>500 lines) to manage effectively.",,
+core,,Shard Document,SD,70,_bmad/core/tasks/shard-doc.xml,bmad-shard-doc,false,,,Splits large markdown documents into smaller organized files based on level 2 sections,,
-core,anytime,Editorial Review - Prose,EP,,_bmad/core/tasks/editorial-review-prose.xml,bmad-editorial-review-prose,false,,,"Review prose for clarity, tone, and communication issues. Use after drafting to polish written content.",report located with target document,"three-column markdown table with suggested fixes",
+core,,Editorial Review - Prose,EP,80,_bmad/core/tasks/editorial-review-prose.xml,bmad-editorial-review-prose,false,,,Clinical copy-editor that reviews text for communication issues,,"three-column markdown table with suggested fixes",
-core,anytime,Editorial Review - Structure,ES,,_bmad/core/tasks/editorial-review-structure.xml,bmad-editorial-review-structure,false,,,"Propose cuts, reorganization, and simplification while preserving comprehension. Use when doc produced from multiple subprocesses or needs structural improvement.",report located with target document,
+core,,Editorial Review - Structure,ES,90,_bmad/core/tasks/editorial-review-structure.xml,bmad-editorial-review-structure,false,,,Structural editor that proposes cuts reorganization and simplification while preserving comprehension,,
-core,anytime,Adversarial Review (General),AR,,_bmad/core/tasks/review-adversarial-general.xml,bmad-review-adversarial-general,false,,,"Review content critically to find issues and weaknesses. Use for quality assurance or before finalizing deliverables. Code Review in other modules run this automatically, but its useful also for document reviews",,
+core,,Adversarial Review (General),AR,100,_bmad/core/tasks/review-adversarial-general.xml,bmad-review-adversarial-general,false,,,Cynically review content and produce findings,,
--- a/src/core/resources/excalidraw/README.md
+++ b/src/core/resources/excalidraw/README.md
@ -0,0 +1,160 @@
 # Core Excalidraw Resources
 Universal knowledge for creating Excalidraw diagrams. All agents that create Excalidraw files should reference these resources.
 ## Purpose
 Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (domain-specific application).
 **Core = "How to create Excalidraw elements"**
 - How to group shapes with text labels
 - How to calculate text width
 - How to create arrows with proper bindings
 - How to validate JSON syntax
 - Base structure and primitives
 **Agents = "What diagrams to create"**
 - Frame Expert (BMM): Technical flowcharts, architecture diagrams, wireframes
 - Presentation Master (CIS): Pitch decks, creative visuals, Rube Goldberg machines
 - Tech Writer (BMM): Documentation diagrams, concept explanations
 ## Files in This Directory
 ### excalidraw-helpers.md
 **Universal element creation patterns**
 - Text width calculation
 - Element grouping rules (shapes + labels)
 - Grid alignment
 - Arrow creation (straight, elbow)
 - Theme application
 - Validation checklist
 - Optimization rules
 **Agents reference this to:**
 - Create properly grouped shapes
 - Calculate text dimensions
 - Connect elements with arrows
 - Ensure valid structure
 ### validate-json-instructions.md
 **Universal JSON validation process**
 - How to validate Excalidraw JSON
 - Common errors and fixes
 - Workflow integration
 - Error recovery
 **Agents reference this to:**
 - Validate files after creation
 - Fix syntax errors
 - Ensure files can be opened in Excalidraw
 ### library-loader.md (Future)
 **How to load external .excalidrawlib files**
 - Programmatic library loading
 - Community library integration
 - Custom library management
 **Status:** To be developed when implementing external library support.
 ## How Agents Use These Resources
 ### Example: Frame Expert (Technical Diagrams)
 ```yaml
 # workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
 helpers: '{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md'
 json_validation: '{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md'
 ```
 **Domain-specific additions:**
 ```yaml
 # workflows/excalidraw-diagrams/_shared/flowchart-templates.yaml
 flowchart:
  start_node:
    type: ellipse
    width: 120
    height: 60
  process_box:
    type: rectangle
    width: 160
    height: 80
  decision_diamond:
    type: diamond
    width: 140
    height: 100
 ```
 ### Example: Presentation Master (Creative Visuals)
 ```yaml
 # workflows/create-visual-metaphor/workflow.yaml
 helpers: '{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md'
 json_validation: '{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md'
 ```
 **Domain-specific additions:**
 ```yaml
 # workflows/_shared/creative-templates.yaml
 rube_goldberg:
  whimsical_connector:
    type: arrow
    strokeStyle: dashed
    roughness: 2
  playful_box:
    type: rectangle
    roundness: 12
 ```
 ## What Doesn't Belong in Core
 **Domain-Specific Elements:**
 - Flowchart-specific templates (belongs in Frame Expert)
 - Pitch deck layouts (belongs in Presentation Master)
 - Documentation-specific styles (belongs in Tech Writer)
 **Agent Workflows:**
 - How to create a flowchart (Frame Expert workflow)
 - How to create a pitch deck (Presentation Master workflow)
 - Step-by-step diagram creation (agent-specific)
 **Theming:**
 - Currently in agent workflows
 - **Future:** Will be refactored to core as user-configurable themes
 ## Architecture Principle
 **Single Source of Truth:**
 - Core holds universal knowledge
 - Agents reference core, don't duplicate
 - Updates to core benefit all agents
 - Agents specialize with domain knowledge
 **DRY (Don't Repeat Yourself):**
 - Element creation logic: ONCE in core
 - Text width calculation: ONCE in core
 - Validation process: ONCE in core
 - Arrow binding patterns: ONCE in core
 ## Future Enhancements
 1. **External Library Loader** - Load .excalidrawlib files from libraries.excalidraw.com
 2. **Theme Management** - User-configurable color themes saved in core
 3. **Component Library** - Shared reusable components across agents
 4. **Layout Algorithms** - Auto-layout helpers for positioning elements
--- a/src/core/resources/excalidraw/excalidraw-helpers.md
+++ b/src/core/resources/excalidraw/excalidraw-helpers.md
@ -0,0 +1,127 @@
 # Excalidraw Element Creation Guidelines
 ## Text Width Calculation
 For text elements inside shapes (labels):
 ```
 text_width = (text.length × fontSize × 0.6) + 20
 ```
 Round to nearest 10 for grid alignment.
 ## Element Grouping Rules
 **CRITICAL:** When creating shapes with labels:
 1. Generate unique IDs:
   - `shape-id` for the shape
   - `text-id` for the text
   - `group-id` for the group
 2. Shape element must have:
   - `groupIds: [group-id]`
   - `boundElements: [{type: "text", id: text-id}]`
 3. Text element must have:
   - `containerId: shape-id`
   - `groupIds: [group-id]` (SAME as shape)
   - `textAlign: "center"`
   - `verticalAlign: "middle"`
   - `width: calculated_width`
 ## Grid Alignment
 - Snap all `x`, `y` coordinates to 20px grid
 - Formula: `Math.round(value / 20) * 20`
 - Spacing between elements: 60px minimum
 ## Arrow Creation
 ### Straight Arrows
 Use for forward flow (left-to-right, top-to-bottom):
 ```json
 {
  "type": "arrow",
  "startBinding": {
    "elementId": "source-shape-id",
    "focus": 0,
    "gap": 10
  },
  "endBinding": {
    "elementId": "target-shape-id",
    "focus": 0,
    "gap": 10
  },
  "points": [[0, 0], [distance_x, distance_y]]
 }
 ```
 ### Elbow Arrows
 Use for upward flow, backward flow, or complex routing:
 ```json
 {
  "type": "arrow",
  "startBinding": {...},
  "endBinding": {...},
  "points": [
    [0, 0],
    [intermediate_x, 0],
    [intermediate_x, intermediate_y],
    [final_x, final_y]
  ],
  "elbowed": true
 }
 ```
 ### Update Connected Shapes
 After creating arrow, update `boundElements` on both connected shapes:
 ```json
 {
  "id": "shape-id",
  "boundElements": [
    { "type": "text", "id": "text-id" },
    { "type": "arrow", "id": "arrow-id" }
  ]
 }
 ```
 ## Theme Application
 Theme colors should be applied consistently:
 - **Shapes**: `backgroundColor` from theme primary fill
 - **Borders**: `strokeColor` from theme accent
 - **Text**: `strokeColor` = "#1e1e1e" (dark text)
 - **Arrows**: `strokeColor` from theme accent
 ## Validation Checklist
 Before saving, verify:
 - [ ] All shapes with labels have matching `groupIds`
 - [ ] All text elements have `containerId` pointing to parent shape
 - [ ] Text width calculated properly (no cutoff)
 - [ ] Text alignment set (`textAlign` + `verticalAlign`)
 - [ ] All elements snapped to 20px grid
 - [ ] All arrows have `startBinding` and `endBinding`
 - [ ] `boundElements` array updated on connected shapes
 - [ ] Theme colors applied consistently
 - [ ] No metadata or history in final output
 - [ ] All IDs are unique
 ## Optimization
 Remove from final output:
 - `appState` object
 - `files` object (unless images used)
 - All elements with `isDeleted: true`
 - Unused library items
 - Version history
--- a/src/core/resources/excalidraw/library-loader.md
+++ b/src/core/resources/excalidraw/library-loader.md
@ -0,0 +1,50 @@
 # External Library Loader
 **Status:** Placeholder for future implementation
 ## Purpose
 Load external .excalidrawlib files from <https://libraries.excalidraw.com> or custom sources.
 ## Planned Capabilities
 - Load libraries by URL
 - Load libraries from local files
 - Merge multiple libraries
 - Filter library components
 - Cache loaded libraries
 ## API Reference
 Will document how to use:
 - `importLibrary(url)` - Load library from URL
 - `loadSceneOrLibraryFromBlob()` - Load from file
 - `mergeLibraryItems()` - Combine libraries
 ## Usage Example
 ```yaml
 # Future workflow.yaml structure
 libraries:
  - url: 'https://libraries.excalidraw.com/libraries/...'
    filter: ['aws', 'cloud']
  - path: '{project-root}/_data/custom-library.excalidrawlib'
 ```
 ## Implementation Notes
 This will be developed when agents need to leverage the extensive library ecosystem available at <https://libraries.excalidraw.com>.
 Hundreds of pre-built component libraries exist for:
 - AWS/Cloud icons
 - UI/UX components
 - Business diagrams
 - Mind map shapes
 - Floor plans
 - And much more...
 ## User Configuration
 Future: Users will be able to configure favorite libraries in their BMAD config for automatic loading.
--- a/src/core/resources/excalidraw/validate-json-instructions.md
+++ b/src/core/resources/excalidraw/validate-json-instructions.md
@ -0,0 +1,79 @@
 # JSON Validation Instructions
 ## Purpose
 Validate Excalidraw JSON files after saving to catch syntax errors (missing commas, brackets, quotes).
 ## How to Validate
 Use Node.js built-in JSON parsing to validate the file:
 ```bash
 node -e "JSON.parse(require('fs').readFileSync('FILE_PATH', 'utf8')); console.log('✓ Valid JSON')"
 ```
 Replace `FILE_PATH` with the actual file path.
 ## Exit Codes
 - Exit code 0 = Valid JSON
 - Exit code 1 = Invalid JSON (syntax error)
 ## Error Output
 If invalid, Node.js will output:
 - Error message with description
 - Position in file where error occurred
 - Line and column information (if available)
 ## Common Errors and Fixes
 ### Missing Comma
 ```
 SyntaxError: Expected ',' or '}' after property value
 ```
 **Fix:** Add comma after the property value
 ### Missing Bracket/Brace
 ```
 SyntaxError: Unexpected end of JSON input
 ```
 **Fix:** Add missing closing bracket `]` or brace `}`
 ### Extra Comma (Trailing)
 ```
 SyntaxError: Unexpected token ,
 ```
 **Fix:** Remove the trailing comma before `]` or `}`
 ### Missing Quote
 ```
 SyntaxError: Unexpected token
 ```
 **Fix:** Add missing quote around string value
 ## Workflow Integration
 After saving an Excalidraw file, run validation:
 1. Save the file
 2. Run: `node -e "JSON.parse(require('fs').readFileSync('{{save_location}}', 'utf8')); console.log('✓ Valid JSON')"`
 3. If validation fails:
   - Read the error message for line/position
   - Open the file at that location
   - Fix the syntax error
   - Save and re-validate
 4. Repeat until validation passes
 ## Critical Rule
 **NEVER delete the file due to validation errors - always fix the syntax error at the reported location.**
--- a/src/core/tasks/editorial-review-prose.xml
+++ b/src/core/tasks/editorial-review-prose.xml
@ -1,6 +1,7 @@
 <task id="_bmad/core/tasks/editorial-review-prose.xml"
  name="Editorial Review - Prose"
-  description="Clinical copy-editor that reviews text for communication issues">
+  description="Clinical copy-editor that reviews text for communication issues"
  standalone="true">
  <objective>Review text for communication issues that impede comprehension and output suggested fixes in a three-column table</objective>
@ -61,8 +62,7 @@
    </step>
    <step n="3" title="Editorial Review" critical="true">
-      <action if="style_guide provided">Consult style_guide now and note its key requirements—these override default principles for this
+      <action if="style_guide provided">Consult style_guide now and note its key requirements—these override default principles for this review</action>
        review</action>
      <action>Review all prose sections (skip code blocks, frontmatter, structural markup)</action>
      <action>Identify communication issues that impede comprehension</action>
      <action>For each issue, determine the minimal fix that achieves clarity</action>
@ -85,10 +85,8 @@
      <example title="Correct output format">
 | Original Text | Revised Text | Changes |
 |---------------|--------------|---------|
-        | The system will processes data and it handles errors. | The system processes data and handles errors. | Fixed subject-verb
+| The system will processes data and it handles errors. | The system processes data and handles errors. | Fixed subject-verb agreement ("will processes" to "processes"); removed redundant "it" |
-        agreement ("will processes" to "processes"); removed redundant "it" |
+| Users can chose from options (lines 12, 45, 78) | Users can choose from options | Fixed spelling: "chose" to "choose" (appears in 3 locations) |
        | Users can chose from options (lines 12, 45, 78) | Users can choose from options | Fixed spelling: "chose" to "choose" (appears in
        3 locations) |
      </example>
    </step>
  </flow>
--- a/src/core/tasks/editorial-review-structure.xml
+++ b/src/core/tasks/editorial-review-structure.xml
@ -4,7 +4,8 @@
 <task id="_bmad/core/tasks/editorial-review-structure.xml"
  name="Editorial Review - Structure"
  description="Structural editor that proposes cuts, reorganization,
-    and simplification while preserving comprehension">
+    and simplification while preserving comprehension"
  standalone="true">
  <objective>Review document structure and propose substantive changes
    to improve clarity and flow-run this BEFORE copy editing</objective>
  <inputs>
@ -131,8 +132,7 @@
      <action>Note reader_type and which principles apply (human-reader-principles or llm-reader-principles)</action>
    </step>
    <step n="3" title="Structural Analysis" critical="true">
-      <action if="style_guide provided">Consult style_guide now and note its key requirements—these override default principles for this
+      <action if="style_guide provided">Consult style_guide now and note its key requirements—these override default principles for this analysis</action>
        analysis</action>
      <action>Map the document structure: list each major section with its word count</action>
      <action>Evaluate structure against the selected model's primary rules
        (e.g., 'Does recommendation come first?' for Pyramid)</action>
--- a/src/core/tasks/help.md
+++ b/src/core/tasks/help.md
@ -1,11 +1,12 @@
 ---
 name: help
 description: Get unstuck by showing what workflow steps come next or answering questions about what to do
 standalone: true
 ---
 # Task: BMAD Help
-## ROUTING RULES
+## KEY RULES
 - **Empty `phase` = anytime** — Universal tools work regardless of workflow state
 - **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order (naming varies by module)
@ -14,26 +15,6 @@ description: Get unstuck by showing what workflow steps come next or answering q
 - **`required=true` blocks progress** — Required workflows must complete before proceeding to later phases
 - **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns, fuzzy-match found files to workflow rows
 ## DISPLAY RULES
 ### Command-Based Workflows
 When `command` field has a value:
 - Show the command prefixed with `/` (e.g., `/bmad-bmm-create-prd`)
 ### Agent-Based Workflows
 When `command` field is empty:
 - User loads agent first via `/agent-command`
 - Then invokes by referencing the `code` field or describing the `name` field
 - Do NOT show a slash command — show the code value and agent load instruction instead
 Example presentation for empty command:
 ```
 Explain Concept (EC)
 Load: /tech-writer, then ask to "EC about [topic]"
 Agent: Tech Writer
 Description: Create clear technical explanations with examples...
 ```
 ## MODULE DETECTION
 - **Empty `module` column** → universal tools (work across all modules)
@ -44,10 +25,10 @@ Detect the active module from conversation context, recent workflows, or user qu
 ## INPUT ANALYSIS
 Determine what was just completed:
- Explicit completion stated by user
+- Did someone state they completed something? Proceed as if that was the input.
- Workflow completed in current conversation
+- Was a workflow just completed in this conversation? Proceed as if that was the input.
- Artifacts found matching `outputs` patterns
+- Search resolved artifact locations for files; fuzzy-match to workflow `outputs` patterns.
- If `index.md` exists, read it for additional context
+- If an `index.md` exists, read it for additional context.
 - If still unclear, ask: "What workflow did you most recently complete?"
 ## EXECUTION
@ -56,27 +37,26 @@ Determine what was just completed:
 2. **Resolve output locations** — Scan each folder under `_bmad/` (except `_config`) for `config.yaml`. For each workflow row, resolve its `output-location` variables against that module's config so artifact paths can be searched.
-3. **Detect active module** — Use MODULE DETECTION above
+3. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
-4. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
+4. **Detect active module** — Use MODULE DETECTION above to determine which module the user is working in.
-5. **Present recommendations** — Show next steps based on:
+5. **Present recommendations** — Show next steps based on completed workflows, phase/sequence ordering (KEY RULES), and artifact detection. Format per the following
-   - Completed workflows detected
+
-   - Phase/sequence ordering (ROUTING RULES)
+## RECOMMENDED OUTPUT FORMAT
   - Artifact presence
   **Optional items first** — List optional workflows until a required step is reached
   **Required items next** — List the next required workflow
-
+   For each item show:
   For each item, apply DISPLAY RULES above and include:
   - Workflow **name**
-   - **Command** OR **Code + Agent load instruction** (per DISPLAY RULES)
+   - **Command** (prefixed with `/`, e.g., `/bmad:example:build-prototype`)
   - **Agent** title and display name from the CSV (e.g., "🎨 Alex (Designer)")
   - Brief **description**
-6. **Additional guidance to convey**:
+   ### Additional response output guidance to convey:
   - Run each workflow in a **fresh context window**
   - Load the agent using (`/` + `agent-command`), or run the workflow command directly
   - For **validation workflows**: recommend using a different high-quality LLM if available
   - For conversational requests: match the user's tone while presenting clearly
-7. Return to the calling process after presenting recommendations.
+6. Return to the calling process after presenting recommendations.
--- a/src/core/tasks/index-docs.xml
+++ b/src/core/tasks/index-docs.xml
@ -1,5 +1,5 @@
 <task id="_bmad/core/tasks/index-docs" name="Index Docs"
-  description="Generates or updates an index.md of all documents in the specified directory">
+  description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
  <llm critical="true">
    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
    <i>DO NOT skip steps or change the sequence</i>
--- a/Show More
+++ b/Show More