.github/workflows/publish.yaml

@@ -37,22 +37,14 @@ permissions:
 
 jobs:
   publish:
-    if: github.repository == 'bmad-code-org/BMAD-METHOD' && (github.event_name != 'workflow_dispatch' || github.ref == 'refs/heads/main')
+    if: github.event_name != 'workflow_dispatch' || github.ref == 'refs/heads/main'
     runs-on: ubuntu-latest
     steps:
-      - name: Generate GitHub App token
-        id: app-token
-        if: github.event_name == 'workflow_dispatch' && inputs.channel == 'latest'
-        uses: actions/create-github-app-token@v2
-        with:
-          app-id: ${{ secrets.RELEASE_APP_ID }}
-          private-key: ${{ secrets.RELEASE_APP_PRIVATE_KEY }}
-
       - name: Checkout
         uses: actions/checkout@v4
         with:
           fetch-depth: 0
-          token: ${{ steps.app-token.outputs.token || secrets.GITHUB_TOKEN }}
+          token: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Setup Node
         uses: actions/setup-node@v4

.github/workflows/quality.yaml

@@ -7,7 +7,7 @@ name: Quality & Validation
 # - Schema validation (YAML structure)
 # - Agent schema tests (fixture-based validation)
 # - Installation component tests (compilation)
-# Keep this workflow aligned with `npm run quality` in `package.json`.
+# - Bundle validation (web bundle integrity)
 
 "on":
   pull_request:

.gitignore

@@ -20,10 +20,6 @@ build/*.txt
 # Environment variables
 .env
 
-# Python
-__pycache__/
-.pytest_cache/
-
 # System files
 .DS_Store
 Thumbs.db

AGENTS.md

@@ -1,9 +0,0 @@
-# BMAD-METHOD
-
-Open source framework for structured, agent-assisted software delivery.
-
-## Rules
-
-- Use Conventional Commits for every commit.
-- Before pushing, run `npm ci && npm run quality` on `HEAD` in the exact checkout you are about to push.
-  `quality` mirrors the checks in `.github/workflows/quality.yaml`.

CHANGELOG.md

@@ -1,42 +1,5 @@
 # Changelog
 
-## [6.1.0] - 2026-03-12
-
-### Highlights
-
-* Whiteport Design Studio (WDS) module enabled in the installer
-* Support @next installation channel (`npx bmad-method@next install`) — get the latest tip of main instead of waiting for the next stable published version
-* Everything now installs as a skill — all workflows, agents, and tasks converted to markdown with SKILL.md entrypoints (not yet optimized skills, but unified format)
-* An experimental preview of the new Quick Dev is available, which will become the main Phase 4 development tool
-* Edge Case Hunter added as a parallel code review layer in Phase 4, improving code quality by exhaustively tracing branching paths and boundary conditions (#1791)
-* Documentation now available in Chinese (zh-CN) with complete translation (#1822, #1795)
-
-### 💥 Breaking Changes
-
-* Convert entire BMAD method to skills-based architecture with unified skill manifests (#1834)
-* Convert all core workflows from YAML+instructions to single workflow.md format
-* Migrate all remaining platforms to native Agent Skills format (#1841)
-* Remove legacy YAML/XML workflow engine plumbing (#1864)
-
-### 🎁 Features
-
-* Add Pi coding agent as supported platform (#1854)
-* Add unified skill scanner decoupled from legacy collectors (#1859)
-* Add continuous delivery workflows for npm publishing with trusted OIDC publishing (#1872)
-
-### ♻️ Refactoring
-
-* Update terminology from "commands" to "skills" across all documentation (#1850)
-
-### 🐛 Bug Fixes
-
-* Fix code review removing mandatory minimum issue count that caused infinite review loops (#1913)
-* Fix silent loss of brainstorming ideas in PRD by adding reconciliation step (#1914)
-* Reduce npm tarball from 533 to 348 files (91% size reduction, 6.2 MB → 555 KB) via .npmignore (#1900)
-* Fix party-mode skill conversion review findings (#1919)
-
----
-
 ## [6.0.4]
 
 ### 🎁 Features

README_CN.md

@@ -20,7 +20,7 @@
 - **派对模式** — 将多个智能体角色带入一个会话进行协作和讨论
 - **完整生命周期** — 从想法开始（头脑风暴）到部署发布
 
-[在 **docs.bmad-method.org** 了解更多](https://docs.bmad-method.org)
+[在 **docs.bmad-method.org** 了解更多](http://docs.bmad-method.org)
 
 ---
 
@@ -28,7 +28,7 @@
 
 **V6 已到来，我们才刚刚开始！** BMad 方法正在快速发展，包括跨平台智能体团队和子智能体集成、技能架构、BMad Builder v1、开发循环自动化等优化，以及更多正在开发中的功能。
 
-**[📍 查看完整路线图 →](https://docs.bmad-method.org/roadmap/)**
+**[📍 查看完整路线图 →](http://docs.bmad-method.org/roadmap/)**
 
 ---
 
@@ -40,7 +40,7 @@
 npx bmad-method install
 ```
 
-> 想要最新的预发布版本？使用 `npx bmad-method@next install`。相比默认安装，可能会有更多变更。
+> 如果你获得的是过时的测试版，请使用：`npx bmad-method@6.0.1 install`
 
 按照安装程序提示操作，然后在项目文件夹中打开你的 AI IDE（Claude Code、Cursor 等）。
 
@@ -50,7 +50,7 @@ npx bmad-method install
 npx bmad-method install --directory /path/to/project --modules bmm --tools claude-code --yes
 ```
 
-[查看所有安装选项](https://docs.bmad-method.org/how-to/non-interactive-installation/)
+[查看所有安装选项](http://docs.bmad-method.org/how-to/non-interactive-installation/)
 
 > **不确定该做什么？** 运行 `bmad-help` — 它会准确告诉你下一步做什么以及什么是可选的。你也可以问诸如 `bmad-help 我刚刚完成了架构设计，接下来该做什么？` 之类的问题。
 
@@ -62,17 +62,17 @@ BMad 方法通过官方模块扩展到专业领域。可在安装期间或之后
 | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
 | **[BMad Method (BMM)](https://github.com/bmad-code-org/BMAD-METHOD)**                                             | 包含 34+ 工作流的核心框架                         |
 | **[BMad Builder (BMB)](https://github.com/bmad-code-org/bmad-builder)**                                           | 创建自定义 BMad 智能体和工作流                     |
-| **[Test Architect (TEA)](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)**             | 基于风险的测试策略和自动化                         |
+| **[Test Architect (TEA)](https://github.com/bmad-code-org/tea)**                                                  | 基于风险的测试策略和自动化                         |
 | **[Game Dev Studio (BMGD)](https://github.com/bmad-code-org/bmad-module-game-dev-studio)**                        | 游戏开发工作流（Unity、Unreal、Godot）             |
 | **[Creative Intelligence Suite (CIS)](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | 创新、头脑风暴、设计思维                           |
 
 ## 文档
 
-[BMad 方法文档站点](https://docs.bmad-method.org) — 教程、指南、概念和参考
+[BMad 方法文档站点](http://docs.bmad-method.org) — 教程、指南、概念和参考
 
 **快速链接：**
-- [入门教程](https://docs.bmad-method.org/tutorials/getting-started/)
-- [从先前版本升级](https://docs.bmad-method.org/how-to/upgrade-to-v6/)
+- [入门教程](http://docs.bmad-method.org/tutorials/getting-started/)
+- [从先前版本升级](http://docs.bmad-method.org/how-to/upgrade-to-v6/)
 - [测试架构师文档](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/)
 
 

docs/how-to/get-answers-about-bmad.md

@@ -42,6 +42,8 @@ BMad-Help responds with:
 - What the first required task is
 - What the rest of the process looks like
 
+---
+
 ## When to Use This Guide
 
 Use this section when:

docs/how-to/project-context.md

@@ -5,7 +5,7 @@ sidebar:
   order: 7
 ---
 
-Use the `project-context.md` file to ensure AI agents follow your project's technical preferences and implementation rules throughout all workflows. To make sure this is always available, you can also add the line `Important project context and conventions are located in [path to project context]/project-context.md` to your tools context or always rules file (such as `AGENTS.md`)
+Use the `project-context.md` file to ensure AI agents follow your project's technical preferences and implementation rules throughout all workflows.
 
 :::note[Prerequisites]
 - BMad Method installed
@@ -114,11 +114,20 @@ A `project-context.md` file that:
 
 ## Tips
 
-:::tip[Best Practices]
-- **Focus on the unobvious** — Document patterns agents might miss (e.g., "Use JSDoc on every public class"), not universal practices like "use meaningful variable names."
-- **Keep it lean** — This file is loaded by every implementation workflow. Long files waste context. Exclude content that only applies to narrow scope or specific stories.
-- **Update as needed** — Edit manually when patterns change, or re-generate after significant architecture changes.
-- Works for Quick Flow and full BMad Method projects alike.
+:::tip[Focus on the Unobvious]
+Document patterns agents might miss such as "Use JSDoc style comments on every public class, function and variable", not universal practices like "use meaningful variable names" which LLMs know at this point.
+:::
+
+:::tip[Keep It Lean]
+This file is loaded by every implementation workflow. Long files waste context. Do not include content that only applies to narrow scope or specific stories or features.
+:::
+
+:::tip[Update as Needed]
+Edit manually when patterns change, or re-generate after significant architecture changes.
+:::
+
+:::tip[Works for All Project Types]
+Just as useful for Quick Flow as for full BMad Method projects.
 :::
 
 ## Next Steps

docs/reference/commands.md

@@ -105,21 +105,32 @@ See [Workflow Map](./workflow-map.md) for the complete workflow reference organi
 
 Tasks and tools are standalone operations that do not require an agent or workflow context.
 
-**BMad-Help: Your Intelligent Guide**
+#### BMad-Help: Your Intelligent Guide
 
-`bmad-help` is your primary interface for discovering what to do next. It inspects your project, understands natural language queries, and recommends the next required or optional step based on your installed modules.
+**`bmad-help`** is your primary interface for discovering what to do next. It's not just a lookup tool — it's an intelligent assistant that:
+
+- **Inspects your project** to see what's already been done
+- **Understands natural language queries** — ask questions in plain English
+- **Varies by installed modules** — shows options based on what you have
+- **Auto-invokes after workflows** — every workflow ends with clear next steps
+- **Recommends the first required task** — no guessing where to start
+
+**Examples:**
 
-:::note[Example]
 ```
 bmad-help
 bmad-help I have a SaaS idea and know all the features. Where do I start?
 bmad-help What are my options for UX design?
+bmad-help I'm stuck on the PRD workflow
 ```
-:::
 
-**Other Core Tasks and Tools**
+#### Other Tasks and Tools
 
-The core module includes 11 built-in tools — reviews, compression, brainstorming, document management, and more. See [Core Tools](./core-tools.md) for the complete reference.
+| Example skill | Purpose |
+| --- | --- |
+| `bmad-shard-doc` | Split a large markdown file into smaller sections |
+| `bmad-index-docs` | Index project documentation |
+| `bmad-editorial-review-prose` | Review document prose quality |
 
 ## Naming Convention
 

docs/reference/core-tools.md

@@ -1,293 +0,0 @@
----
-title: Core Tools
-description: Reference for all built-in tasks and workflows available in every BMad installation without additional modules.
-sidebar:
-  order: 2
----
-
-Every BMad installation includes a set of core skills that can be used in conjunction with any anything you are doing — standalone tasks and workflows that work across all projects, all modules, and all phases. These are always available regardless of which optional modules you install.
-
-:::tip[Quick Path]
-Run any core tool by typing its skill name (e.g., `bmad-help`) in your IDE. No agent session required.
-:::
-
-## Overview
-
-| Tool | Type | Purpose |
-| --- | --- | --- |
-| [`bmad-help`](#bmad-help) | Task | Get context-aware guidance on what to do next |
-| [`bmad-brainstorming`](#bmad-brainstorming) | Workflow | Facilitate interactive brainstorming sessions |
-| [`bmad-party-mode`](#bmad-party-mode) | Workflow | Orchestrate multi-agent group discussions |
-| [`bmad-distillator`](#bmad-distillator) | Task | Lossless LLM-optimized compression of documents |
-| [`bmad-advanced-elicitation`](#bmad-advanced-elicitation) | Task | Push LLM output through iterative refinement methods |
-| [`bmad-review-adversarial-general`](#bmad-review-adversarial-general) | Task | Cynical review that finds what's missing and what's wrong |
-| [`bmad-review-edge-case-hunter`](#bmad-review-edge-case-hunter) | Task | Exhaustive branching-path analysis for unhandled edge cases |
-| [`bmad-editorial-review-prose`](#bmad-editorial-review-prose) | Task | Clinical copy-editing for communication clarity |
-| [`bmad-editorial-review-structure`](#bmad-editorial-review-structure) | Task | Structural editing — cuts, merges, and reorganization |
-| [`bmad-shard-doc`](#bmad-shard-doc) | Task | Split large markdown files into organized sections |
-| [`bmad-index-docs`](#bmad-index-docs) | Task | Generate or update an index of all docs in a folder |
-
-## bmad-help
-
-**Your intelligent guide to what comes next.** — Inspects your project state, detects what's been done, and recommends the next required or optional step.
-
-**Use it when:**
-
-- You finished a workflow and want to know what's next
-- You're new to BMad and need orientation
-- You're stuck and want context-aware advice
-- You installed new modules and want to see what's available
-
-**How it works:**
-
-1. Scans your project for existing artifacts (PRD, architecture, stories, etc.)
-2. Detects which modules are installed and their available workflows
-3. Recommends next steps in priority order — required steps first, then optional
-4. Presents each recommendation with the skill command and a brief description
-
-**Input:** Optional query in natural language (e.g., `bmad-help I have a SaaS idea, where do I start?`)
-
-**Output:** Prioritized list of recommended next steps with skill commands
-
-## bmad-brainstorming
-
-**Generate diverse ideas through interactive creative techniques.** — A facilitated brainstorming session that loads proven ideation methods from a technique library and guides you toward 100+ ideas before organizing.
-
-**Use it when:**
-
-- You're starting a new project and need to explore the problem space
-- You're stuck generating ideas and need structured creativity
-- You want to use proven ideation frameworks (SCAMPER, reverse brainstorming, etc.)
-
-**How it works:**
-
-1. Sets up a brainstorming session with your topic
-2. Loads creative techniques from a method library
-3. Guides you through technique after technique, generating ideas
-4. Applies anti-bias protocol — shifts creative domain every 10 ideas to prevent clustering
-5. Produces an append-only session document with all ideas organized by technique
-
-**Input:** Brainstorming topic or problem statement, optional context file
-
-**Output:** `brainstorming-session-{date}.md` with all generated ideas
-
-:::note[Quantity Target]
-The magic happens in ideas 50–100. The workflow encourages generating 100+ ideas before organization.
-:::
-
-## bmad-party-mode
-
-**Orchestrate multi-agent group discussions.** — Loads all installed BMad agents and facilitates a natural conversation where each agent contributes from their unique expertise and personality.
-
-**Use it when:**
-
-- You need multiple expert perspectives on a decision
-- You want agents to challenge each other's assumptions
-- You're exploring a complex topic that spans multiple domains
-
-**How it works:**
-
-1. Loads the agent manifest with all installed agent personalities
-2. Analyzes your topic to select 2–3 most relevant agents
-3. Agents take turns contributing, with natural cross-talk and disagreements
-4. Rotates agent participation to ensure diverse perspectives over time
-5. Exit with `goodbye`, `end party`, or `quit`
-
-**Input:** Discussion topic or question, along with specification of personas you would like to participate (optional)
-
-**Output:** Real-time multi-agent conversation with maintained agent personalities
-
-## bmad-distillator
-
-**Lossless LLM-optimized compression of source documents.** — Produces dense, token-efficient distillates that preserve all information for downstream LLM consumption. Verifiable through round-trip reconstruction.
-
-**Use it when:**
-
-- A document is too large for an LLM's context window
-- You need token-efficient versions of research, specs, or planning artifacts
-- You want to verify no information is lost during compression
-- Agents will need to frequently reference and find information in it
-
-**How it works:**
-
-1. **Analyze** — Reads source documents, identifies information density and structure
-2. **Compress** — Converts prose to dense bullet-point format, strips decorative formatting
-3. **Verify** — Checks completeness to ensure all original information is preserved
-4. **Validate** (optional) — Round-trip reconstruction test proves lossless compression
-
-**Input:**
-
-- `source_documents` (required) — File paths, folder paths, or glob patterns
-- `downstream_consumer` (optional) — What consumes this (e.g., "PRD creation")
-- `token_budget` (optional) — Approximate target size
-- `--validate` (flag) — Run round-trip reconstruction test
-
-**Output:** Distillate markdown file(s) with compression ratio report (e.g., "3.2:1")
-
-## bmad-advanced-elicitation
-
-**Push LLM output through iterative refinement methods.** — Selects from a library of elicitation techniques to systematically improve content through multiple passes.
-
-**Use it when:**
-
-- LLM output feels shallow or generic
-- You want to explore a topic from multiple analytical angles
-- You're refining a critical document and want deeper thinking
-
-**How it works:**
-
-1. Loads method registry with 5+ elicitation techniques
-2. Selects 5 best-fit methods based on content type and complexity
-3. Presents an interactive menu — pick a method, reshuffle, or list all
-4. Applies the selected method to enhance the content
-5. Re-presents options for iterative improvement until you select "Proceed"
-
-**Input:** Content section to enhance
-
-**Output:** Enhanced version of the content with improvements applied
-
-## bmad-review-adversarial-general
-
-**Cynical review that assumes problems exist and searches for them.** — Takes a skeptical, jaded reviewer perspective with zero patience for sloppy work. Looks for what's missing, not just what's wrong.
-
-**Use it when:**
-
-- You need quality assurance before finalizing a deliverable
-- You want to stress-test a spec, story, or document
-- You want to find gaps in coverage that optimistic reviews miss
-
-**How it works:**
-
-1. Reads the content with a cynical, critical perspective
-2. Identifies issues across completeness, correctness, and quality
-3. Searches specifically for what's missing — not just what's present and wrong
-4. Must find a minimum of 10 issues or re-analyzes deeper
-
-**Input:**
-
-- `content` (required) — Diff, spec, story, doc, or any artifact
-- `also_consider` (optional) — Additional areas to keep in mind
-
-**Output:** Markdown list of 10+ findings with descriptions
-
-## bmad-review-edge-case-hunter
-
-**Walk every branching path and boundary condition, report only unhandled cases.** — Pure path-tracing methodology that mechanically derives edge classes. Orthogonal to adversarial review — method-driven, not attitude-driven.
-
-**Use it when:**
-
-- You want exhaustive edge case coverage for code or logic
-- You need a complement to adversarial review (different methodology, different findings)
-- You're reviewing a diff or function for boundary conditions
-
-**How it works:**
-
-1. Enumerates all branching paths in the content
-2. Derives edge classes mechanically: missing else/default, unguarded inputs, off-by-one, arithmetic overflow, implicit type coercion, race conditions, timeout gaps
-3. Tests each path against existing guards
-4. Reports only unhandled paths — silently discards handled ones
-
-**Input:**
-
-- `content` (required) — Diff, full file, or function
-- `also_consider` (optional) — Additional areas to keep in mind
-
-**Output:** JSON array of findings, each with `location`, `trigger_condition`, `guard_snippet`, and `potential_consequence`
-
-:::note[Complementary Reviews]
-Run both `bmad-review-adversarial-general` and `bmad-review-edge-case-hunter` together for orthogonal coverage. The adversarial review catches quality and completeness issues; the edge case hunter catches unhandled paths.
-:::
-
-## bmad-editorial-review-prose
-
-**Clinical copy-editing focused on communication clarity.** — Reviews text for issues that impede comprehension. Applies Microsoft Writing Style Guide baseline. Preserves author voice.
-
-**Use it when:**
-
-- You've drafted a document and want to polish the writing
-- You need to ensure clarity for a specific audience
-- You want communication fixes without style opinion changes
-
-**How it works:**
-
-1. Reads the content, skipping code blocks and frontmatter
-2. Identifies communication issues (not style preferences)
-3. Deduplicates same issues across multiple locations
-4. Produces a three-column fix table
-
-**Input:**
-
-- `content` (required) — Markdown, plain text, or XML
-- `style_guide` (optional) — Project-specific style guide
-- `reader_type` (optional) — `humans` (default) for clarity/flow, or `llm` for precision/consistency
-
-**Output:** Three-column markdown table: Original Text | Revised Text | Changes
-
-## bmad-editorial-review-structure
-
-**Structural editing — proposes cuts, merges, moves, and condensing.** — Reviews document organization and proposes substantive changes to improve clarity and flow before copy editing.
-
-**Use it when:**
-
-- A document was produced from multiple subprocesses and needs structural coherence
-- You want to reduce document length while preserving comprehension
-- You need to identify scope violations or buried critical information
-
-**How it works:**
-
-1. Analyzes document against 5 structure models (Tutorial, Reference, Explanation, Prompt, Strategic)
-2. Identifies redundancies, scope violations, and buried information
-3. Produces prioritized recommendations: CUT, MERGE, MOVE, CONDENSE, QUESTION, PRESERVE
-4. Estimates total reduction in words and percentage
-
-**Input:**
-
-- `content` (required) — Document to review
-- `purpose` (optional) — Intended purpose (e.g., "quickstart tutorial")
-- `target_audience` (optional) — Who reads this
-- `reader_type` (optional) — `humans` or `llm`
-- `length_target` (optional) — Target reduction (e.g., "30% shorter")
-
-**Output:** Document summary, prioritized recommendation list, and estimated reduction
-
-## bmad-shard-doc
-
-**Split large markdown files into organized section files.** — Uses level-2 headers as split points to create a folder of self-contained section files with an index.
-
-**Use it when:**
-
-- A markdown document has grown too large to manage effectively (500+ lines)
-- You want to break a monolithic doc into navigable sections
-- You need separate files for parallel editing or LLM context management
-
-**How it works:**
-
-1. Validates the source file exists and is markdown
-2. Splits on level-2 (`##`) headers into numbered section files
-3. Creates an `index.md` with section manifest and links
-4. Prompts you to delete, archive, or keep the original
-
-**Input:** Source markdown file path, optional destination folder
-
-**Output:** Folder with `index.md` and `01-{section}.md`, `02-{section}.md`, etc.
-
-## bmad-index-docs
-
-**Generate or update an index of all documents in a folder.** — Scans a directory, reads each file to understand its purpose, and produces an organized `index.md` with links and descriptions.
-
-**Use it when:**
-
-- You need a lightweight index for quick LLM scanning of available docs
-- A documentation folder has grown and needs an organized table of contents
-- You want an auto-generated overview that stays current
-
-**How it works:**
-
-1. Scans the target directory for all non-hidden files
-2. Reads each file to understand its actual purpose
-3. Groups files by type, purpose, or subdirectory
-4. Generates concise descriptions (3–10 words each)
-
-**Input:** Target folder path
-
-**Output:** `index.md` with organized file listings, relative links, and brief descriptions

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "6.1.0",
+  "version": "6.0.4",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "6.1.0",
+      "version": "6.0.4",
       "license": "MIT",
       "dependencies": {
         "@clack/core": "^1.0.0",

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.1.0",
+  "version": "6.0.4",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -39,7 +39,6 @@
     "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",
-    "quality": "npm run format:check && npm run lint && npm run lint:md && npm run docs:build && npm run validate:schemas && npm run test:schemas && npm run test:install && npm run validate:refs",
     "rebundle": "node tools/cli/bundlers/bundle-web.js rebundle",
     "test": "npm run test:schemas && npm run test:refs && npm run test:install && npm run validate:schemas && npm run lint && npm run lint:md && npm run format:check",
     "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",

src/bmm/agents/analyst.agent.yaml

@@ -18,26 +18,26 @@ agent:
 
   menu:
     - trigger: BP or fuzzy match on brainstorm-project
-      exec: "skill:bmad-brainstorming"
+      exec: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
       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
-      exec: "skill:bmad-market-research"
+      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md"
       description: "[MR] Market Research: Market analysis, competitive landscape, customer needs and trends"
 
     - trigger: DR or fuzzy match on domain-research
-      exec: "skill:bmad-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: "skill:bmad-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: "skill:bmad-create-product-brief"
+      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
       description: "[CB] Create Brief: A guided experience to nail down your product idea into an executive brief"
 
     - trigger: DP or fuzzy match on document-project
-      exec: "skill:bmad-document-project"
+      exec: "{project-root}/_bmad/bmm/workflows/document-project/workflow.md"
       description: "[DP] Document Project: Analyze an existing project to produce useful documentation for both human and LLM"

src/bmm/agents/architect.agent.yaml

@@ -21,9 +21,9 @@ agent:
 
   menu:
     - trigger: CA or fuzzy match on create-architecture
-      exec: "skill:bmad-create-architecture"
+      exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md"
       description: "[CA] Create Architecture: Guided Workflow to document technical decisions to keep implementation on track"
 
     - trigger: IR or fuzzy match on implementation-readiness
-      exec: "skill:bmad-check-implementation-readiness"
+      exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
       description: "[IR] Implementation Readiness: Ensure the PRD, UX, and Architecture and Epics and Stories List are all aligned"

src/bmm/agents/dev.agent.yaml

@@ -30,9 +30,9 @@ agent:
 
   menu:
     - trigger: DS or fuzzy match on dev-story
-      exec: "skill:bmad-dev-story"
+      exec: "{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.md"
       description: "[DS] Dev Story: Write the next or specified stories tests and code."
 
     - trigger: CR or fuzzy match on code-review
-      exec: "skill:bmad-code-review"
+      exec: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.md"
       description: "[CR] Code Review: Initiate a comprehensive code review across multiple quality facets. For best results, use a fresh context and a different quality LLM if available"

src/bmm/agents/pm.agent.yaml

@@ -20,25 +20,25 @@ agent:
 
   menu:
     - trigger: CP or fuzzy match on create-prd
-      exec: "skill:bmad-create-prd"
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md"
       description: "[CP] Create PRD: Expert led facilitation to produce your Product Requirements Document"
 
     - trigger: VP or fuzzy match on validate-prd
-      exec: "skill:bmad-validate-prd"
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.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: "skill:bmad-edit-prd"
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md"
       description: "[EP] Edit PRD: Update an existing Product Requirements Document"
 
     - trigger: CE or fuzzy match on epics-stories
-      exec: "skill:bmad-create-epics-and-stories"
+      exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
       description: "[CE] Create Epics and Stories: Create the Epics and Stories Listing, these are the specs that will drive development"
 
     - trigger: IR or fuzzy match on implementation-readiness
-      exec: "skill:bmad-check-implementation-readiness"
+      exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
       description: "[IR] Implementation Readiness: Ensure the PRD, UX, and Architecture and Epics and Stories List are all aligned"
 
     - trigger: CC or fuzzy match on correct-course
-      exec: "skill:bmad-correct-course"
+      exec: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.md"
       description: "[CC] Course Correction: Use this so we can determine how to proceed if major need for change is discovered mid implementation"

src/bmm/agents/qa.agent.yaml

@@ -29,7 +29,7 @@ agent:
 
   menu:
     - trigger: QA or fuzzy match on qa-automate
-      exec: "skill:bmad-qa-generate-e2e-tests"
+      exec: "{project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.md"
       description: "[QA] Automate - Generate tests for existing features (simplified)"
 
   prompts:

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

@@ -20,11 +20,11 @@ agent:
 
   menu:
     - trigger: QS or fuzzy match on quick-spec
-      exec: "skill:bmad-quick-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"
 
     - trigger: QD or fuzzy match on quick-dev
-      exec: "skill:bmad-quick-dev"
+      exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md"
       description: "[QD] Quick-flow Develop: Implement a story tech spec end-to-end (Core of Quick Flow)"
 
     - trigger: QQ or fuzzy match on bmad-quick-dev-new-preview
@@ -32,5 +32,5 @@ agent:
       description: "[QQ] Quick Dev New (Preview): Unified quick flow — clarify intent, plan, implement, review, present (experimental)"
 
     - trigger: CR or fuzzy match on code-review
-      exec: "skill:bmad-code-review"
+      exec: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.md"
       description: "[CR] Code Review: Initiate a comprehensive code review across multiple quality facets. For best results, use a fresh context and a different quality LLM if available"

src/bmm/agents/sm.agent.yaml

@@ -20,18 +20,18 @@ agent:
 
   menu:
     - trigger: SP or fuzzy match on sprint-planning
-      exec: "skill:bmad-sprint-planning"
+      exec: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.md"
       description: "[SP] Sprint Planning: Generate or update the record that will sequence the tasks to complete the full project that the dev agent will follow"
 
     - trigger: CS or fuzzy match on create-story
-      exec: "skill:bmad-create-story"
+      exec: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.md"
       description: "[CS] Context Story: Prepare a story with all required context for implementation for the developer agent"
 
     - trigger: ER or fuzzy match on epic-retrospective
-      exec: "skill:bmad-retrospective"
+      exec: "{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.md"
       data: "{project-root}/_bmad/_config/agent-manifest.csv"
       description: "[ER] Epic Retrospective: Party Mode review of all work completed across an epic."
 
     - trigger: CC or fuzzy match on correct-course
-      exec: "skill:bmad-correct-course"
+      exec: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.md"
       description: "[CC] Course Correction: Use this so we can determine how to proceed if major need for change is discovered mid implementation"

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

@@ -22,7 +22,7 @@ agent:
 
   menu:
     - trigger: DP or fuzzy match on document-project
-      exec: "skill:bmad-document-project"
+      exec: "{project-root}/_bmad/bmm/workflows/document-project/workflow.md"
       description: "[DP] Document Project: Generate comprehensive project documentation (brownfield analysis, architecture scanning)"
 
     - trigger: WD or fuzzy match on write-document

src/bmm/agents/ux-designer.agent.yaml

@@ -23,5 +23,5 @@ agent:
 
   menu:
     - trigger: CU or fuzzy match on ux-design
-      exec: "skill:bmad-create-ux-design"
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
       description: "[CU] Create UX: Guidance through realizing the plan for your UX to inform architecture and implementation. Provides more details than what was discovered in the PRD"

src/bmm/module-help.csv

@@ -1,32 +1,32 @@
 module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
-bmm,anytime,Document Project,DP,,skill:bmad-document-project,bmad-bmm-document-project,false,analyst,Create Mode,"Analyze an existing project to produce useful documentation",project-knowledge,*,
-bmm,anytime,Generate Project Context,GPC,,skill:bmad-generate-project-context,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,QS,,skill:bmad-quick-spec,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,,skill:bmad-quick-dev,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,Document Project,DP,,_bmad/bmm/workflows/document-project/workflow.md,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,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,,_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 New Preview,QQ,,skill:bmad-quick-dev-new-preview,bmad-bmm-quick-dev-new-preview,false,quick-flow-solo-dev,Create Mode,"Unified quick flow (experimental): clarify intent plan implement review and present in a single workflow",implementation_artifacts,"tech spec implementation",
-bmm,anytime,Correct Course,CC,,skill:bmad-correct-course,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.md,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,skill:bmad-brainstorming,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,skill:bmad-market-research,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,Domain Research,DR,21,skill:bmad-domain-research,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,Technical Research,TR,22,skill:bmad-technical-research,bmad-bmm-technical-research,false,analyst,Create Mode,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project_knowledge","research documents",
-bmm,1-analysis,Create Brief,CB,30,skill:bmad-create-product-brief,bmad-bmm-create-product-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,skill:bmad-create-prd,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
-bmm,2-planning,Validate PRD,VP,20,skill:bmad-validate-prd,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,Edit PRD,EP,25,skill:bmad-edit-prd,bmad-bmm-edit-prd,false,pm,Edit Mode,"Improve and enhance an existing PRD",planning_artifacts,"updated prd",
-bmm,2-planning,Create UX,CU,30,skill:bmad-create-ux-design,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,3-solutioning,Create Architecture,CA,10,skill:bmad-create-architecture,bmad-bmm-create-architecture,true,architect,Create Mode,"Guided Workflow to document technical decisions",planning_artifacts,architecture,
-bmm,3-solutioning,Create Epics and Stories,CE,30,skill:bmad-create-epics-and-stories,bmad-bmm-create-epics-and-stories,true,pm,Create Mode,"Create the Epics and Stories Listing",planning_artifacts,"epics and stories",
-bmm,3-solutioning,Check Implementation Readiness,IR,70,skill:bmad-check-implementation-readiness,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,skill:bmad-sprint-planning,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,skill:bmad-sprint-status,bmad-bmm-sprint-status,false,sm,Create Mode,"Anytime: Summarize sprint status and route to next workflow",,,
-bmm,4-implementation,Validate Story,VS,35,skill:bmad-create-story,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,skill:bmad-create-story,bmad-bmm-create-story,true,sm,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story,
-bmm,4-implementation,Dev Story,DS,40,skill:bmad-dev-story,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,skill:bmad-code-review,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,skill:bmad-qa-generate-e2e-tests,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,skill:bmad-retrospective,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,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,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,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,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,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,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,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,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,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,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,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.md,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.md,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.md,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.md,bmad-bmm-create-story,true,sm,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story,
+bmm,4-implementation,Dev Story,DS,40,_bmad/bmm/workflows/4-implementation/dev-story/workflow.md,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.md,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-generate-e2e-tests/workflow.md,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.md,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,

src/bmm/workflows/1-analysis/bmad-create-product-brief/SKILL.md

@@ -1,6 +0,0 @@
----
-name: bmad-create-product-brief
-description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

src/bmm/workflows/1-analysis/bmad-product-brief-preview/SKILL.md

@@ -1,88 +0,0 @@
----
-name: bmad-product-brief-preview
-description: Create or update product briefs through guided or autonomous discovery. Use when the user requests to 'create a product brief', 'help me create a project brief', or 'update my product brief'.
-argument-hint: "[optional --create, --edit, --optimize, --distillate, --inputs, --headless] [brief idea]"
----
-
-# Create Product Brief
-
-## Overview
-
-This skill helps you create compelling product briefs through collaborative discovery, intelligent artifact analysis, and web research. Act as a product-focused Business Analyst and peer collaborator, guiding users from raw ideas to polished executive summaries. Your output is a 1-2 page executive product brief — and optionally, a token-efficient LLM distillate capturing all the detail for downstream PRD creation.
-
-The user is the domain expert. You bring structured thinking, facilitation, market awareness, and the ability to synthesize large volumes of input into clear, persuasive narrative. Work together as equals.
-
-**Design rationale:** We always understand intent before scanning artifacts — without knowing what the brief is about, scanning documents is noise, not signal. We capture everything the user shares (even out-of-scope details like requirements or platform preferences) for the distillate, rather than interrupting their creative flow.
-
-## Activation Mode Detection
-
-Check activation context immediately:
-
-1. **Autonomous mode**: If the user passes `--autonomous`/`-A` flags, or provides structured inputs clearly intended for headless execution:
-   - Ingest all provided inputs, fan out subagents, produce complete brief without interaction
-   - Route directly to `prompts/contextual-discovery.md` with `{mode}=autonomous`
-
-2. **Yolo mode**: If the user passes `--yolo` or says "just draft it" / "draft the whole thing":
-   - Ingest everything, draft complete brief upfront, then walk user through refinement
-   - Route to Stage 1 below with `{mode}=yolo`
-
-3. **Guided mode** (default): Conversational discovery with soft gates
-   - Route to Stage 1 below with `{mode}=guided`
-
-## On Activation
-
-1. Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve::
-   - Use `{user_name}` for greeting
-   - Use `{communication_language}` for all communications
-   - Use `{document_output_language}` for output documents
-   - Use `{planning_artifacts}` for output location and artifact scanning
-   - Use `{project_knowledge}` for additional context scanning
-
-2. **Greet user** as `{user_name}`, speaking in `{communication_language}`. Be warm but efficient — dream builder energy.
-
-3. **Stage 1: Understand Intent** (handled here in SKILL.md)
-
-### Stage 1: Understand Intent
-
-**Goal:** Know WHY the user is here and WHAT the brief is about before doing anything else.
-
-**Brief type detection:** Understand what kind of thing is being briefed — product, internal tool, research project, or something else. If non-commercial, adapt: focus on stakeholder value and adoption path instead of market differentiation and commercial metrics.
-
-**Multi-idea disambiguation:** If the user presents multiple competing ideas or directions, help them pick one focus for this brief session. Note that others can be briefed separately.
-
-**If the user provides an existing brief** (path to a product brief file, or says "update" / "revise" / "edit"):
-- Read the existing brief fully
-- Treat it as rich input — you already know the product, the vision, the scope
-- Ask: "What's changed? What do you want to update or improve?"
-- The rest of the workflow proceeds normally — contextual discovery may pull in new research, elicitation focuses on gaps or changes, and draft-and-review produces an updated version
-
-**If the user already provided context** when launching the skill (description, docs, brain dump):
-- Acknowledge what you received — but **DO NOT read document files yet**. Note their paths for Stage 2's subagents to scan contextually. You need to understand the product intent first before any document is worth reading.
-- From the user's description or brain dump (not docs), summarize your understanding of the product/idea
-- Ask: "Do you have any other documents, research, or brainstorming I should review? Anything else to add before I dig in?"
-
-**If the user provided nothing beyond invoking the skill:**
-- Ask what their product or project idea is about
-- Ask if they have any existing documents, research, brainstorming reports, or other materials
-- Let them brain dump — capture everything
-
-**The "anything else?" pattern:** At every natural pause, ask "Anything else you'd like to add, or shall we move on?" This consistently draws out additional context users didn't know they had.
-
-**Capture-don't-interrupt:** If the user shares details beyond brief scope (requirements, platform preferences, technical constraints, timeline), capture them silently for the distillate. Don't redirect or stop their flow.
-
-**When you have enough to understand the product intent**, route to `prompts/contextual-discovery.md` with the current mode.
-
-## Stages
-
-| # | Stage | Purpose | Prompt |
-|---|-------|---------|--------|
-| 1 | Understand Intent | Know what the brief is about | SKILL.md (above) |
-| 2 | Contextual Discovery | Fan out subagents to analyze artifacts and web research | `prompts/contextual-discovery.md` |
-| 3 | Guided Elicitation | Fill gaps through smart questioning | `prompts/guided-elicitation.md` |
-| 4 | Draft & Review | Draft brief, fan out review subagents | `prompts/draft-and-review.md` |
-| 5 | Finalize | Polish, output, offer distillate | `prompts/finalize.md` |
-
-## External Skills
-
-This workflow uses:
-- `bmad-init` — Configuration loading (module: bmm)

src/bmm/workflows/1-analysis/bmad-product-brief-preview/agents/artifact-analyzer.md

@@ -1,60 +0,0 @@
-# Artifact Analyzer
-
-You are a research analyst. Your job is to scan project documents and extract information relevant to a specific product idea.
-
-## Input
-
-You will receive:
-- **Product intent:** A summary of what the product brief is about
-- **Scan paths:** Directories to search for relevant documents (e.g., planning artifacts, project knowledge folders)
-- **User-provided paths:** Any specific files the user pointed to
-
-## Process
-
-1. **Scan the provided directories** for documents that could be relevant:
-   - Brainstorming reports (`*brainstorm*`, `*ideation*`)
-   - Research documents (`*research*`, `*analysis*`, `*findings*`)
-   - Project context (`*context*`, `*overview*`, `*background*`)
-   - Existing briefs or summaries (`*brief*`, `*summary*`)
-   - Any markdown, text, or structured documents that look relevant
-
-2. **For sharded documents** (a folder with `index.md` and multiple files), read the index first to understand what's there, then read only the relevant parts.
-
-3. **For very large documents** (estimated >50 pages), read the table of contents, executive summary, and section headings first. Read only sections directly relevant to the stated product intent. Note which sections were skimmed vs read fully.
-
-4. **Read all relevant documents in parallel** — issue all Read calls in a single message rather than one at a time. Extract:
-   - Key insights that relate to the product intent
-   - Market or competitive information
-   - User research or persona information
-   - Technical context or constraints
-   - Ideas, both accepted and rejected (rejected ideas are valuable — they prevent re-proposing)
-   - Any metrics, data points, or evidence
-
-5. **Ignore documents that aren't relevant** to the stated product intent. Don't waste tokens on unrelated content.
-
-## Output
-
-Return ONLY the following JSON object. No preamble, no commentary. Maximum 8 bullets per section.
-
-```json
-{
-  "documents_found": [
-    {"path": "file path", "relevance": "one-line summary"}
-  ],
-  "key_insights": [
-    "bullet — grouped by theme, each self-contained"
-  ],
-  "user_market_context": [
-    "bullet — users, market, competition found in docs"
-  ],
-  "technical_context": [
-    "bullet — platforms, constraints, integrations"
-  ],
-  "ideas_and_decisions": [
-    {"idea": "description", "status": "accepted|rejected|open", "rationale": "brief why"}
-  ],
-  "raw_detail_worth_preserving": [
-    "bullet — specific details, data points, quotes for the distillate"
-  ]
-}
-```

src/bmm/workflows/1-analysis/bmad-product-brief-preview/agents/opportunity-reviewer.md

@@ -1,44 +0,0 @@
-# Opportunity Reviewer
-
-You are a strategic advisor reviewing a product brief draft. Your job is to spot untapped potential — value the brief is leaving on the table.
-
-## Input
-
-You will receive the complete draft product brief.
-
-## Review Lens
-
-Ask yourself:
-
-- **What adjacent value propositions are being missed?** Are there related problems this solution naturally addresses?
-- **What market angles are underemphasized?** Is the positioning leaving opportunities unexplored?
-- **What partnerships or integrations could multiply impact?** Who would benefit from aligning with this product?
-- **What's the network effect or viral potential?** Is there a growth flywheel the brief doesn't describe?
-- **What's underemphasized?** Which strengths deserve more spotlight?
-- **What user segments are overlooked?** Could this serve audiences not yet mentioned?
-- **What's the bigger story?** If you zoom out, is there a more compelling narrative?
-- **What would an investor want to hear more about?** What would make someone lean forward?
-
-## Output
-
-Return ONLY the following JSON object. No preamble, no commentary. Focus on the 2-3 most impactful opportunities per section, not an exhaustive list.
-
-```json
-{
-  "untapped_value": [
-    {"opportunity": "adjacent problem or value prop", "rationale": "why it matters"}
-  ],
-  "positioning_opportunities": [
-    {"angle": "market angle or narrative", "impact": "how it strengthens the brief"}
-  ],
-  "growth_and_scale": [
-    "bullet — network effects, viral loops, expansion paths"
-  ],
-  "strategic_partnerships": [
-    {"partner_type": "who", "value": "why this alliance matters"}
-  ],
-  "underemphasized_strengths": [
-    {"strength": "what's underplayed", "suggestion": "how to elevate it"}
-  ]
-}
-```

src/bmm/workflows/1-analysis/bmad-product-brief-preview/agents/skeptic-reviewer.md

@@ -1,44 +0,0 @@
-# Skeptic Reviewer
-
-You are a critical analyst reviewing a product brief draft. Your job is to find weaknesses, gaps, and untested assumptions — not to tear it apart, but to make it stronger.
-
-## Input
-
-You will receive the complete draft product brief.
-
-## Review Lens
-
-Ask yourself:
-
-- **What's missing?** Are there sections that feel thin or glossed over?
-- **What assumptions are untested?** Where does the brief assert things without evidence?
-- **What could go wrong?** What risks aren't acknowledged?
-- **Where is it vague?** Which claims need more specificity?
-- **Does the problem statement hold up?** Is this a real, significant problem or a nice-to-have?
-- **Are the differentiators actually defensible?** Could a competitor replicate them easily?
-- **Do the success metrics make sense?** Are they measurable and meaningful?
-- **Is the MVP scope realistic?** Too ambitious? Too timid?
-
-## Output
-
-Return ONLY the following JSON object. No preamble, no commentary. Maximum 5 items per section. Prioritize — lead with the most impactful issues.
-
-```json
-{
-  "critical_gaps": [
-    {"issue": "what's missing", "impact": "why it matters", "suggestion": "how to fix"}
-  ],
-  "untested_assumptions": [
-    {"assumption": "what's asserted", "risk": "what could go wrong"}
-  ],
-  "unacknowledged_risks": [
-    {"risk": "potential failure mode", "severity": "high|medium|low"}
-  ],
-  "vague_areas": [
-    {"section": "where", "issue": "what's vague", "suggestion": "how to sharpen"}
-  ],
-  "suggested_improvements": [
-    "actionable suggestion"
-  ]
-}
-```

src/bmm/workflows/1-analysis/bmad-product-brief-preview/agents/web-researcher.md

@@ -1,49 +0,0 @@
-# Web Researcher
-
-You are a market research analyst. Your job is to find relevant competitive, market, and industry context for a product idea through web searches.
-
-## Input
-
-You will receive:
-- **Product intent:** A summary of what the product is about, the problem it solves, and the domain it operates in
-
-## Process
-
-1. **Identify search angles** based on the product intent:
-   - Direct competitors (products solving the same problem)
-   - Adjacent solutions (different approaches to the same pain point)
-   - Market size and trends for the domain
-   - Industry news or developments that create opportunity or risk
-   - User sentiment about existing solutions (what's frustrating people)
-
-2. **Execute 3-5 targeted web searches** — quality over quantity. Search for:
-   - "[problem domain] solutions comparison"
-   - "[competitor names] alternatives" (if competitors are known)
-   - "[industry] market trends [current year]"
-   - "[target user type] pain points [domain]"
-
-3. **Synthesize findings** — don't just list links. Extract the signal.
-
-## Output
-
-Return ONLY the following JSON object. No preamble, no commentary. Maximum 5 bullets per section.
-
-```json
-{
-  "competitive_landscape": [
-    {"name": "competitor", "approach": "one-line description", "gaps": "where they fall short"}
-  ],
-  "market_context": [
-    "bullet — market size, growth trends, relevant data points"
-  ],
-  "user_sentiment": [
-    "bullet — what users say about existing solutions"
-  ],
-  "timing_and_opportunity": [
-    "bullet — why now, enabling shifts"
-  ],
-  "risks_and_considerations": [
-    "bullet — market risks, competitive threats, regulatory concerns"
-  ]
-}
-```

src/bmm/workflows/1-analysis/bmad-product-brief-preview/bmad-manifest.json

@@ -1,17 +0,0 @@
-{
-  "module-code": "bmm",
-  "replaces-skill": "bmad-create-product-brief",
-  "capabilities": [
-    {
-      "name": "create-brief",
-      "menu-code": "CB",
-      "description": "Produces executive product brief and optional LLM distillate for PRD input.",
-      "supports-headless": true,
-      "phase-name": "1-analysis",
-      "after": ["brainstorming, perform-research"],
-      "before": ["create-prd"],
-      "is-required": true,
-      "output-location": "{planning_artifacts}"
-    }
-  ]
-}

src/bmm/workflows/1-analysis/bmad-product-brief-preview/prompts/contextual-discovery.md

@@ -1,57 +0,0 @@
-**Language:** Use `{communication_language}` for all output.
-**Output Language:** Use `{document_output_language}` for documents.
-**Output Location:** `{planning_artifacts}`
-
-# Stage 2: Contextual Discovery
-
-**Goal:** Armed with the user's stated intent, intelligently gather and synthesize all available context — documents, project knowledge, and web research — so later stages work from a rich, relevant foundation.
-
-## Subagent Fan-Out
-
-Now that you know what the brief is about, fan out subagents in parallel to gather context. Each subagent receives the product intent summary so it knows what's relevant.
-
-**Launch in parallel:**
-
-1. **Artifact Analyzer** (`agents/artifact-analyzer.md`) — Scans `{planning_artifacts}` and `{project_knowledge}` for relevant documents. Also scans any specific paths the user provided. Returns structured synthesis of what it found.
-
-2. **Web Researcher** (`agents/web-researcher.md`) — Searches for competitive landscape, market context, trends, and relevant industry data. Returns structured findings scoped to the product domain.
-
-### Graceful Degradation
-
-If subagents are unavailable or fail:
-- Read only the most relevant 1-2 documents in the main context and summarize (don't full-read everything — limit context impact in degraded mode)
-- Do a few targeted web searches inline
-- Never block the workflow because a subagent feature is unavailable
-
-## Synthesis
-
-Once subagent results return (or inline scanning completes):
-
-1. **Merge findings** with what the user already told you
-2. **Identify gaps** — what do you still need to know to write a solid brief?
-3. **Note surprises** — anything from research that contradicts or enriches the user's assumptions?
-
-## Mode-Specific Behavior
-
-**Guided mode:**
-- Present a concise summary of what you found: "Here's what I learned from your documents and web research..."
-- Highlight anything surprising or worth discussing
-- Share the gaps you've identified
-- Ask: "Anything else you'd like to add, or shall we move on to filling in the details?"
-- Route to `prompts/guided-elicitation.md`
-
-**Yolo mode:**
-- Absorb all findings silently
-- Skip directly to `prompts/draft-and-review.md` — you have enough to draft
-- The user will refine later
-
-**Headless mode:**
-- Absorb all findings
-- Skip directly to `prompts/draft-and-review.md`
-- No interaction
-
-## Stage Complete
-
-This stage is complete when subagent results (or inline scanning fallback) have returned and findings are merged with user context. Route per mode:
-- **Guided** → `prompts/guided-elicitation.md`
-- **Yolo / Headless** → `prompts/draft-and-review.md`

src/bmm/workflows/1-analysis/bmad-product-brief-preview/prompts/draft-and-review.md

@@ -1,86 +0,0 @@
-**Language:** Use `{communication_language}` for all output.
-**Output Language:** Use `{document_output_language}` for documents.
-**Output Location:** `{planning_artifacts}`
-
-# Stage 4: Draft & Review
-
-**Goal:** Produce the executive product brief and run it through multiple review lenses to catch blind spots before the user sees the final version.
-
-## Step 1: Draft the Executive Brief
-
-Use `resources/brief-template.md` as a guide — adapt structure to fit the product's story.
-
-**Writing principles:**
-- **Executive audience** — persuasive, clear, concise. 1-2 pages.
-- **Lead with the problem** — make the reader feel the pain before presenting the solution
-- **Concrete over abstract** — specific examples, real scenarios, measurable outcomes
-- **Confident voice** — this is a pitch, not a hedge
-- Write in `{document_output_language}`
-
-**Create the output document at:** `{planning_artifacts}/product-brief-{project_name}.md`
-
-Include YAML frontmatter:
-```yaml
----
-title: "Product Brief: {project_name}"
-status: "draft"
-created: "{timestamp}"
-updated: "{timestamp}"
-inputs: [list of input files used]
----
-```
-
-## Step 2: Fan Out Review Subagents
-
-Before showing the draft to the user, run it through multiple review lenses in parallel.
-
-**Launch in parallel:**
-
-1. **Skeptic Reviewer** (`agents/skeptic-reviewer.md`) — "What's missing? What assumptions are untested? What could go wrong? Where is the brief vague or hand-wavy?"
-
-2. **Opportunity Reviewer** (`agents/opportunity-reviewer.md`) — "What adjacent value propositions are being missed? What market angles or partnerships could strengthen this? What's underemphasized?"
-
-3. **Contextual Reviewer** — You (the main agent) pick the most useful third lens based on THIS specific product. Choose the lens that addresses the SINGLE BIGGEST RISK that the skeptic and opportunity reviewers won't naturally catch. Examples:
-   - For healthtech: "Regulatory and compliance risk reviewer"
-   - For devtools: "Developer experience and adoption friction critic"
-   - For marketplace: "Network effects and chicken-and-egg problem analyst"
-   - For enterprise: "Procurement and organizational change management reviewer"
-   - **When domain is unclear, default to:** "Go-to-market and launch risk reviewer" — examines distribution, pricing, and first-customer acquisition. Almost always valuable, frequently missed.
-   Describe the lens, run the review yourself inline.
-
-### Graceful Degradation
-
-If subagents are unavailable:
-- Perform all three review passes yourself, sequentially
-- Apply each lens deliberately — don't blend them into one generic review
-- The quality of review matters more than the parallelism
-
-## Step 3: Integrate Review Insights
-
-After all reviews complete:
-
-1. **Triage findings** — group by theme, remove duplicates
-2. **Apply non-controversial improvements** directly to the draft (obvious gaps, unclear language, missing specifics)
-3. **Flag substantive suggestions** that need user input (strategic choices, scope questions, market positioning decisions)
-
-## Step 4: Present to User
-
-**Headless mode:** Skip to `prompts/finalize.md` — no user interaction. Save the improved draft directly.
-
-**Yolo and Guided modes:**
-
-Present the draft brief to the user. Then share the reviewer insights:
-
-"Here's your product brief draft. Before we finalize, my review panel surfaced some things worth considering:
-
-**[Grouped reviewer findings — only the substantive ones that need user input]**
-
-What do you think? Any changes you'd like to make?"
-
-Present reviewer findings with brief rationale, then offer: "Want me to dig into any of these, or are you ready to make your revisions?"
-
-**Iterate** as long as the user wants to refine. Use the "anything else, or are we happy with this?" soft gate.
-
-## Stage Complete
-
-This stage is complete when: (a) the draft has been reviewed by all three lenses and improvements integrated, AND either (autonomous) save and route directly, or (guided/yolo) the user is satisfied. Route to `prompts/finalize.md`.

src/bmm/workflows/1-analysis/bmad-product-brief-preview/prompts/finalize.md

@@ -1,75 +0,0 @@
-**Language:** Use `{communication_language}` for all output.
-**Output Language:** Use `{document_output_language}` for documents.
-**Output Location:** `{planning_artifacts}`
-
-# Stage 5: Finalize
-
-**Goal:** Save the polished brief, offer the LLM distillate, and point the user forward.
-
-## Step 1: Polish and Save
-
-Update the product brief document at `{planning_artifacts}/product-brief-{project_name}.md`:
-- Update frontmatter `status` to `"complete"`
-- Update `updated` timestamp
-- Ensure formatting is clean and consistent
-- Confirm the document reads well as a standalone 1-2 page executive summary
-
-## Step 2: Offer the Distillate
-
-Throughout the discovery process, you likely captured detail that doesn't belong in a 1-2 page executive summary but is valuable for downstream work — requirements hints, platform preferences, rejected ideas, technical constraints, detailed user scenarios, competitive deep-dives, etc.
-
-**Ask the user:**
-"Your product brief is complete. During our conversation, I captured additional detail that goes beyond the executive summary — things like [mention 2-3 specific examples of overflow you captured]. Would you like me to create a detail pack for PRD creation? It distills all that extra context into a concise, structured format optimized for the next phase."
-
-**If yes, create the distillate** at `{planning_artifacts}/product-brief-{project_name}-distillate.md`:
-
-```yaml
----
-title: "Product Brief Distillate: {project_name}"
-type: llm-distillate
-source: "product-brief-{project_name}.md"
-created: "{timestamp}"
-purpose: "Token-efficient context for downstream PRD creation"
----
-```
-
-**Distillate content principles:**
-- Dense bullet points, not prose
-- Each bullet carries enough context to be understood standalone (don't assume the reader has the full brief loaded)
-- Group by theme, not by when it was mentioned
-- Include:
-  - **Rejected ideas** — so downstream workflows don't re-propose them, with brief rationale
-  - **Requirements hints** — anything the user mentioned that sounds like a requirement
-  - **Technical context** — platforms, integrations, constraints, preferences
-  - **Detailed user scenarios** — richer than what fits in the exec summary
-  - **Competitive intelligence** — specifics from web research worth preserving
-  - **Open questions** — things surfaced but not resolved during discovery
-  - **Scope signals** — what the user indicated is in/out/maybe for MVP
-- Token-conscious: be concise, but give enough context per bullet so an LLM reading this later understands WHY each point matters
-
-**Headless mode:** Always create the distillate automatically — unless the session was too brief to capture meaningful overflow (in that case, note this in the completion output instead of creating an empty file).
-
-## Step 3: Present Completion
-
-"Your product brief for {project_name} is complete!
-
-**Executive Brief:** `{planning_artifacts}/product-brief-{project_name}.md`
-[If distillate created:] **Detail Pack:** `{planning_artifacts}/product-brief-{project_name}-distillate.md`
-
-**Recommended next step:** Use the product brief (and detail pack) as input for PRD creation — tell your assistant 'create a PRD' and point it to these files."
-[If distillate created:] "The detail pack contains all the overflow context (requirements hints, rejected ideas, technical constraints) specifically structured for the PRD workflow to consume."
-
-**Headless mode:** Output the file paths as structured JSON and exit:
-```json
-{
-  "status": "complete",
-  "brief": "{planning_artifacts}/product-brief-{project_name}.md",
-  "distillate": "{path or null}",
-  "confidence": "high|medium|low",
-  "open_questions": ["any unresolved items"]
-}
-```
-
-## Stage Complete
-
-This is the terminal stage. After delivering the completion message and file paths, the workflow is done. If the user requests further revisions, loop back to `prompts/draft-and-review.md`. Otherwise, exit.

src/bmm/workflows/1-analysis/bmad-product-brief-preview/prompts/guided-elicitation.md

@@ -1,70 +0,0 @@
-**Language:** Use `{communication_language}` for all output.
-**Output Language:** Use `{document_output_language}` for documents.
-
-# Stage 3: Guided Elicitation
-
-**Goal:** Fill the gaps in what you know. By now you have the user's brain dump, artifact analysis, and web research. This stage is about smart, targeted questioning — not rote section-by-section interrogation.
-
-**Skip this stage entirely in Yolo and Autonomous modes** — go directly to `prompts/draft-and-review.md`.
-
-## Approach
-
-You are NOT walking through a rigid questionnaire. You're having a conversation that covers the substance of a great product brief. The topics below are your mental checklist, not a script. Adapt to:
-- What you already know (don't re-ask what's been covered)
-- What the user is excited about (follow their energy)
-- What's genuinely unclear (focus questions where they matter)
-
-## Topics to Cover (flexibly, conversationally)
-
-### Vision & Problem
-- What core problem does this solve? For whom?
-- How do people solve this today? What's frustrating about current approaches?
-- What would success look like for the people this helps?
-- What's the insight or angle that makes this approach different?
-
-### Users & Value
-- Who experiences this problem most acutely?
-- Are there different user types with different needs?
-- What's the "aha moment" — when does a user realize this is what they needed?
-- How does this fit into their existing workflow or life?
-
-### Market & Differentiation
-- What competitive or alternative solutions exist? (Leverage web research findings)
-- What's the unfair advantage or defensible moat?
-- Why is now the right time for this?
-
-### Success & Scope
-- How will you know this is working? What metrics matter?
-- What's the minimum viable version that creates real value?
-- What's explicitly NOT in scope for the first version?
-- If this is wildly successful, what does it become in 2-3 years?
-
-## The Flow
-
-For each topic area where you have gaps:
-
-1. **Lead with what you know** — "Based on your input and my research, it sounds like [X]. Is that right?"
-2. **Ask the gap question** — targeted, specific, not generic
-3. **Reflect and confirm** — paraphrase what you heard
-4. **"Anything else on this, or shall we move on?"** — the soft gate
-
-If the user is giving you detail beyond brief scope (requirements, architecture, platform details, timelines), **capture it silently** for the distillate. Acknowledge it briefly ("Good detail, I'll capture that") but don't derail the conversation.
-
-## When to Move On
-
-When you have enough substance to draft a compelling 1-2 page executive brief covering:
-- Clear problem and who it affects
-- Proposed solution and what makes it different
-- Target users (at least primary)
-- Some sense of success criteria or business objectives
-- MVP-level scope thinking
-
-You don't need perfection — you need enough to draft well. Missing details can be surfaced during the review stage.
-
-If the user is providing complete, confident answers and you have solid coverage across all four topic areas after fewer than 3-4 exchanges, proactively offer to draft early.
-
-**Transition:** "I think I have a solid picture. Ready for me to draft the brief, or is there anything else you'd like to add?"
-
-## Stage Complete
-
-This stage is complete when sufficient substance exists to draft a compelling brief and the user confirms readiness. Route to `prompts/draft-and-review.md`.

src/bmm/workflows/1-analysis/bmad-product-brief-preview/resources/brief-template.md

@@ -1,60 +0,0 @@
-# Product Brief Template
-
-This is a flexible guide for the executive product brief — adapt it to serve the product's story. Merge sections, add new ones, reorder as needed. The product determines the structure, not the template.
-
-## Sensible Default Structure
-
-```markdown
-# Product Brief: {Product Name}
-
-## Executive Summary
-
-[2-3 paragraph narrative: What is this? What problem does it solve? Why does it matter? Why now?
-This should be compelling enough to stand alone — if someone reads only this section, they should understand the vision.]
-
-## The Problem
-
-[What pain exists? Who feels it? How are they coping today? What's the cost of the status quo?
-Be specific — real scenarios, real frustrations, real consequences.]
-
-## The Solution
-
-[What are we building? How does it solve the problem?
-Focus on the experience and outcome, not the implementation.]
-
-## What Makes This Different
-
-[Key differentiators. Why this approach vs alternatives? What's the unfair advantage?
-Be honest — if the moat is execution speed, say so. Don't fabricate technical moats.]
-
-## Who This Serves
-
-[Primary users — vivid but brief. Who are they, what do they need, what does success look like for them?
-Secondary users if relevant.]
-
-## Success Criteria
-
-[How do we know this is working? What metrics matter?
-Mix of user success signals and business objectives. Be measurable.]
-
-## Scope
-
-[What's in for the first version? What's explicitly out?
-Keep this tight — it's a boundary document, not a feature list.]
-
-## Vision
-
-[Where does this go if it succeeds? What does it become in 2-3 years?
-Inspiring but grounded.]
-```
-
-## Adaptation Guidelines
-
-- **For B2B products:** Consider adding a "Buyer vs User" section if they're different people
-- **For platforms/marketplaces:** Consider a "Network Effects" or "Ecosystem" section
-- **For technical products:** May need a brief "Technical Approach" section (keep it high-level)
-- **For regulated industries:** Consider a "Compliance & Regulatory" section
-- **If scope is well-defined:** Merge "Scope" and "Vision" into "Roadmap Thinking"
-- **If the problem is well-known:** Shorten "The Problem" and expand "What Makes This Different"
-
-The brief should be 1-2 pages. If it's longer, you're putting in too much detail — that's what the distillate is for.

src/bmm/workflows/1-analysis/create-product-brief/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+canonicalId: bmad-create-product-brief
+type: workflow
+description: "Create product brief through collaborative discovery"

src/bmm/workflows/1-analysis/create-product-brief/product-brief.template.md

@@ -1,8 +1,8 @@
 ---
 stepsCompleted: []
 inputDocuments: []
-date: {{system-date}}
-author: {{user_name}}
+date: { system-date }
+author: { user }
 ---
 
 # Product Brief: {{project_name}}

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

@@ -1,6 +1,13 @@
 ---
+name: 'step-01-init'
+description: 'Initialize the product brief workflow by detecting continuation state and setting up the document'
+
 # File References
+nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+
+# Template References
+productBriefTemplate: '../product-brief.template.md'
 ---
 
 # Step 1: Product Brief Initialization
@@ -66,7 +73,7 @@ If the document exists and has frontmatter with `stepsCompleted`:
 
 **Continuation Protocol:**
 
-- **STOP immediately** and load `./step-01b-continue.md`
+- **STOP immediately** and load `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md`
 - Do not proceed with any initialization tasks
 - Let step-01b handle all continuation logic
 - This is an auto-proceed situation - no user choice needed
@@ -81,7 +88,7 @@ load context documents using smart discovery. Documents can be in the following
 - {planning_artifacts}/**
 - {output_folder}/**
 - {product_knowledge}/**
-- {project-root}/docs/**
+- docs/**
 
 Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
 
@@ -105,7 +112,7 @@ Try to discover the following:
 
 **Document Setup:**
 
-- Copy the template from `../product-brief.template.md` to `{outputFile}`, and update the frontmatter fields
+- Copy the template from `{productBriefTemplate}` to `{outputFile}`, and update the frontmatter fields
 
 #### C. Present Initialization Results
 
@@ -134,7 +141,7 @@ Display: "**Proceeding to product vision discovery...**"
 
 #### Menu Handling Logic:
 
-- After setup report is presented, without delay, read fully and follow: ./step-02-vision.md
+- After setup report is presented, without delay, read fully and follow: {nextStepFile}
 
 #### EXECUTION RULES:
 
@@ -143,7 +150,7 @@ Display: "**Proceeding to product vision discovery...**"
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then read fully and follow: `./step-02-vision.md` to begin product vision discovery.
+ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then read fully and follow: `{nextStepFile}` to begin product vision discovery.
 
 ---
 

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

@@ -1,4 +1,7 @@
 ---
+name: 'step-01b-continue'
+description: 'Resume the product brief workflow from where it was left off, ensuring smooth continuation'
+
 # File References
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 ---
@@ -92,9 +95,9 @@ Does this look right, or do you want to make any adjustments before we proceed?"
 **Next Step Logic:**
 Based on `lastStep` value, determine which step to load next:
 
-- If `lastStep = 1` → Load `./step-02-vision.md`
-- If `lastStep = 2` → Load `./step-03-users.md`
-- If `lastStep = 3` → Load `./step-04-metrics.md`
+- If `lastStep = 1` → Load `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md`
+- If `lastStep = 2` → Load `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md`
+- If `lastStep = 3` → Load `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md`
 - Continue this pattern for all steps
 - If `lastStep = 6` → Workflow already complete
 

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

@@ -1,9 +1,13 @@
 ---
+name: 'step-02-vision'
+description: 'Discover and define the core product vision, problem statement, and unique value proposition'
+
 # File References
+nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
-advancedElicitationTask: 'skill:bmad-advanced-elicitation'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
 ---
 
@@ -22,7 +26,6 @@ Conduct comprehensive product vision discovery to define the core problem, solut
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -155,7 +158,7 @@ Prepare the following structure for document append:
 
 - IF A: Read fully and follow: {advancedElicitationTask} with current vision content to dive deeper and refine
 - IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to positioning and differentiation
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then read fully and follow: ./step-03-users.md
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
 
 #### EXECUTION RULES:
@@ -167,7 +170,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then read fully and follow: `./step-03-users.md` to begin target user discovery.
+ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin target user discovery.
 
 ---
 

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

@@ -1,9 +1,13 @@
 ---
+name: 'step-03-users'
+description: 'Define target users with rich personas and map their key interactions with the product'
+
 # File References
+nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
-advancedElicitationTask: 'skill:bmad-advanced-elicitation'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
 ---
 
@@ -22,7 +26,6 @@ Define target users with rich personas and map their key interactions with the p
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -158,7 +161,7 @@ Prepare the following structure for document append:
 
 - IF A: Read fully and follow: {advancedElicitationTask} with current user content to dive deeper into personas and journeys
 - IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate user understanding
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then read fully and follow: ./step-04-metrics.md
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
 
 #### EXECUTION RULES:
@@ -170,7 +173,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then read fully and follow: `./step-04-metrics.md` to begin success metrics definition.
+ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin success metrics definition.
 
 ---
 

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

@@ -1,9 +1,13 @@
 ---
+name: 'step-04-metrics'
+description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators'
+
 # File References
+nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
-advancedElicitationTask: 'skill:bmad-advanced-elicitation'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
 ---
 
@@ -22,7 +26,6 @@ Define comprehensive success metrics that include user success, business objecti
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -161,7 +164,7 @@ Prepare the following structure for document append:
 
 - IF A: Read fully and follow: {advancedElicitationTask} with current metrics content to dive deeper into success metric insights
 - IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate comprehensive metrics
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then read fully and follow: ./step-05-scope.md
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
 
 #### EXECUTION RULES:
@@ -173,7 +176,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then read fully and follow: `./step-05-scope.md` to begin MVP scope definition.
+ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin MVP scope definition.
 
 ---
 

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

@@ -1,9 +1,13 @@
 ---
+name: 'step-05-scope'
+description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep'
+
 # File References
+nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md'
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
-advancedElicitationTask: 'skill:bmad-advanced-elicitation'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
 ---
 
@@ -22,7 +26,6 @@ Define MVP scope with clear boundaries and outline future vision through collabo
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -175,7 +178,7 @@ Prepare the following structure for document append:
 
 - IF A: Read fully and follow: {advancedElicitationTask} with current scope content to optimize scope definition
 - IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate MVP scope
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then read fully and follow: ./step-06-complete.md
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
 
 #### EXECUTION RULES:
@@ -187,7 +190,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then read fully and follow: `./step-06-complete.md` to complete the product brief workflow.
+ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to complete the product brief workflow.
 
 ---
 

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

@@ -1,4 +1,7 @@
 ---
+name: 'step-06-complete'
+description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'
+
 # File References
 outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 ---

src/bmm/workflows/1-analysis/create-product-brief/workflow.md

@@ -1,3 +1,8 @@
+---
+name: create-product-brief
+description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
+---
+
 # Product Brief Workflow
 
 **Goal:** Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
@@ -47,9 +52,6 @@ Load and read full 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`
 
-✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
-✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
-
 ### 2. First Step EXECUTION
 
-Read fully and follow: `./steps/step-01-init.md` to begin the workflow.
+Read fully and follow: `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.

src/bmm/workflows/1-analysis/research/bmad-domain-research/SKILL.md

@@ -1,6 +0,0 @@
----
-name: bmad-domain-research
-description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

src/bmm/workflows/1-analysis/research/bmad-domain-research/research.template.md

@@ -1,29 +0,0 @@
----
-stepsCompleted: []
-inputDocuments: []
-workflowType: 'research'
-lastStep: 1
-research_type: '{{research_type}}'
-research_topic: '{{research_topic}}'
-research_goals: '{{research_goals}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
-web_research_enabled: true
-source_verification: true
----
-
-# Research Report: {{research_type}}
-
-**Date:** {{date}}
-**Author:** {{user_name}}
-**Research Type:** {{research_type}}
-
----
-
-## Research Overview
-
-[Research overview and methodology will be appended here]
-
----
-
-<!-- Content will be appended sequentially through research workflow steps -->

src/bmm/workflows/1-analysis/research/bmad-market-research/SKILL.md

@@ -1,6 +0,0 @@
----
-name: bmad-market-research
-description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".'
----
-
-Follow the instructions in [workflow.md](workflow.md).

src/bmm/workflows/1-analysis/research/bmad-market-research/research.template.md

@@ -1,29 +0,0 @@
----
-stepsCompleted: []
-inputDocuments: []
-workflowType: 'research'
-lastStep: 1
-research_type: '{{research_type}}'
-research_topic: '{{research_topic}}'
-research_goals: '{{research_goals}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
-web_research_enabled: true
-source_verification: true
----
-
-# Research Report: {{research_type}}
-
-**Date:** {{date}}
-**Author:** {{user_name}}
-**Research Type:** {{research_type}}
-
----
-
-## Research Overview
-
-[Research overview and methodology will be appended here]
-
----
-
-<!-- Content will be appended sequentially through research workflow steps -->

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

@@ -1,184 +0,0 @@
-# Market Research Step 1: Market Research Initialization
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate research content in init step
-- ✅ ALWAYS confirm understanding of user's research goals
-- 📋 YOU ARE A MARKET RESEARCH FACILITATOR, not content generator
-- 💬 FOCUS on clarifying scope and approach
-- 🔍 NO WEB RESEARCH in init - that's for later steps
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Confirm research understanding before proceeding
-- ⚠️ Present [C] continue option after scope clarification
-- 💾 Write initial scope document immediately
-- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from main workflow discovery are available
-- Research type = "market" is already set
-- **Research topic = "{{research_topic}}"** - discovered from initial discussion
-- **Research goals = "{{research_goals}}"** - captured from initial discussion
-- Focus on market research scope clarification
-- Web search capabilities are enabled for later steps
-
-## YOUR TASK:
-
-Initialize market research by confirming understanding of {{research_topic}} and establishing clear research scope.
-
-## MARKET RESEARCH INITIALIZATION:
-
-### 1. Confirm Research Understanding
-
-**INITIALIZE - DO NOT RESEARCH YET**
-
-Start with research confirmation:
-"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
-
-**My Understanding of Your Research Needs:**
-
-- **Research Topic**: {{research_topic}}
-- **Research Goals**: {{research_goals}}
-- **Research Type**: Market Research
-- **Approach**: Comprehensive market analysis with source verification
-
-**Market Research Areas We'll Cover:**
-
-- Market size, growth dynamics, and trends
-- Customer insights and behavior analysis
-- Competitive landscape and positioning
-- Strategic recommendations and implementation guidance
-
-**Does this accurately capture what you're looking for?**"
-
-### 2. Refine Research Scope
-
-Gather any clarifications needed:
-
-#### Scope Clarification Questions:
-
-- "Are there specific customer segments or aspects of {{research_topic}} we should prioritize?"
-- "Should we focus on specific geographic regions or global market?"
-- "Is this for market entry, expansion, product development, or other business purpose?"
-- "Any competitors or market segments you specifically want us to analyze?"
-
-### 3. Document Initial Scope
-
-**WRITE IMMEDIATELY TO DOCUMENT**
-
-Write initial research scope to document:
-
-```markdown
-# Market Research: {{research_topic}}
-
-## Research Initialization
-
-### Research Understanding Confirmed
-
-**Topic**: {{research_topic}}
-**Goals**: {{research_goals}}
-**Research Type**: Market Research
-**Date**: {{date}}
-
-### Research Scope
-
-**Market Analysis Focus Areas:**
-
-- Market size, growth projections, and dynamics
-- Customer segments, behavior patterns, and insights
-- Competitive landscape and positioning analysis
-- Strategic recommendations and implementation guidance
-
-**Research Methodology:**
-
-- Current web data with source verification
-- Multiple independent sources for critical claims
-- Confidence level assessment for uncertain data
-- Comprehensive coverage with no critical gaps
-
-### Next Steps
-
-**Research Workflow:**
-
-1. ✅ Initialization and scope setting (current step)
-2. Customer Insights and Behavior Analysis
-3. Competitive Landscape Analysis
-4. Strategic Synthesis and Recommendations
-
-**Research Status**: Scope confirmed, ready to proceed with detailed market analysis
-```
-
-### 4. Present Confirmation and Continue Option
-
-Show initial scope document and present continue option:
-"I've documented our understanding and initial scope for **{{research_topic}}** market research.
-
-**What I've established:**
-
-- Research topic and goals confirmed
-- Market analysis focus areas defined
-- Research methodology verification
-- Clear workflow progression
-
-**Document Status:** Initial scope written to research file for your review
-
-**Ready to begin detailed market research?**
-[C] Continue - Confirm scope and proceed to customer insights analysis
-[Modify] Suggest changes to research scope before proceeding
-
-**HALT — wait for user response before proceeding.**
-
-### 5. Handle User Response
-
-#### If 'C' (Continue):
-
-- Update frontmatter: `stepsCompleted: [1]`
-- Add confirmation note to document: "Scope confirmed by user on {{date}}"
-- Load: `./step-02-customer-behavior.md`
-
-#### If 'Modify':
-
-- Gather user changes to scope
-- Update document with modifications
-- Re-present updated scope for confirmation
-
-## SUCCESS METRICS:
-
-✅ Research topic and goals accurately understood
-✅ Market research scope clearly defined
-✅ Initial scope document written immediately
-✅ User opportunity to review and modify scope
-✅ [C] continue option presented and handled correctly
-✅ Document properly updated with scope confirmation
-
-## FAILURE MODES:
-
-❌ Not confirming understanding of research topic and goals
-❌ Generating research content instead of just scope clarification
-❌ Not writing initial scope document to file
-❌ Not providing opportunity for user to modify scope
-❌ Proceeding to next step without user confirmation
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research 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
-
-## INITIALIZATION PRINCIPLES:
-
-This step ensures:
-
-- Clear mutual understanding of research objectives
-- Well-defined research scope and approach
-- Immediate documentation for user review
-- User control over research direction before detailed work begins
-
-## NEXT STEP:
-
-After user confirmation and scope finalization, load `./step-02-customer-behavior.md` to begin detailed market research with customer insights analysis.
-
-Remember: Init steps confirm understanding and scope, not generate research content!

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

@@ -1,239 +0,0 @@
-# Market Research Step 2: Customer Behavior and Segments
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without web search verification
-- ✅ Search the web to verify and supplement your knowledge with current facts
-- 📋 YOU ARE A CUSTOMER BEHAVIOR ANALYST, not content generator
-- 💬 FOCUS on customer behavior patterns and demographic analysis
-- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
-- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ 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 behavior content generation
-- 📝 WRITE CUSTOMER BEHAVIOR ANALYSIS TO DOCUMENT IMMEDIATELY
-- 💾 ONLY proceed 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 patterns and demographic analysis
-- Web search capabilities with source verification are enabled
-- Previous step confirmed research scope and goals
-- **Research topic = "{{research_topic}}"** - established from initial discussion
-- **Research goals = "{{research_goals}}"** - established from initial discussion
-
-## YOUR TASK:
-
-Conduct customer behavior and segment analysis with emphasis on patterns and demographics.
-
-## CUSTOMER BEHAVIOR ANALYSIS SEQUENCE:
-
-### 1. Begin Customer Behavior Analysis
-
-**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly.
-
-Start with customer behavior research approach:
-"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns.
-
-**Customer Behavior Focus:**
-
-- Customer behavior patterns and preferences
-- Demographic profiles and segmentation
-- Psychographic characteristics and values
-- Behavior drivers and influences
-- Customer interaction patterns and engagement
-
-**Let me search for current customer behavior insights.**"
-
-### 2. Parallel Customer Behavior Research Execution
-
-**Execute multiple web searches simultaneously:**
-
-Search the web: "{{research_topic}} customer behavior patterns"
-Search the web: "{{research_topic}} customer demographics"
-Search the web: "{{research_topic}} psychographic profiles"
-Search the web: "{{research_topic}} customer behavior drivers"
-
-**Analysis approach:**
-
-- Look for customer behavior studies and research reports
-- Search for demographic segmentation and analysis
-- Research psychographic profiling and value systems
-- Analyze behavior drivers and influencing factors
-- Study customer interaction and engagement patterns
-
-### 3. Analyze and Aggregate Results
-
-**Collect and analyze findings from all parallel searches:**
-
-"After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
-
-**Research Coverage:**
-
-- Customer behavior patterns and preferences
-- Demographic profiles and segmentation
-- Psychographic characteristics and values
-- Behavior drivers and influences
-- Customer interaction patterns and engagement
-
-**Cross-Behavior Analysis:**
-[Identify patterns connecting demographics, psychographics, and behaviors]
-
-**Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
-
-### 4. Generate Customer Behavior Content
-
-**WRITE IMMEDIATELY TO DOCUMENT**
-
-Prepare customer behavior analysis with web search citations:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Customer Behavior and Segments
-
-### Customer Behavior Patterns
-
-[Customer behavior patterns analysis with source citations]
-_Behavior Drivers: [Key motivations and patterns from web search]_
-_Interaction Preferences: [Customer engagement and interaction patterns]_
-_Decision Habits: [How customers typically make decisions]_
-_Source: [URL]_
-
-### Demographic Segmentation
-
-[Demographic analysis with source citations]
-_Age Demographics: [Age groups and preferences]_
-_Income Levels: [Income segments and purchasing behavior]_
-_Geographic Distribution: [Regional/city differences]_
-_Education Levels: [Education impact on behavior]_
-_Source: [URL]_
-
-### Psychographic Profiles
-
-[Psychographic analysis with source citations]
-_Values and Beliefs: [Core values driving customer behavior]_
-_Lifestyle Preferences: [Lifestyle choices and behaviors]_
-_Attitudes and Opinions: [Customer attitudes toward products/services]_
-_Personality Traits: [Personality influences on behavior]_
-_Source: [URL]_
-
-### Customer Segment Profiles
-
-[Detailed customer segment profiles with source citations]
-_Segment 1: [Detailed profile including demographics, psychographics, behavior]_
-_Segment 2: [Detailed profile including demographics, psychographics, behavior]_
-_Segment 3: [Detailed profile including demographics, psychographics, behavior]_
-_Source: [URL]_
-
-### Behavior Drivers and Influences
-
-[Behavior drivers analysis with source citations]
-_Emotional Drivers: [Emotional factors influencing behavior]_
-_Rational Drivers: [Logical decision factors]_
-_Social Influences: [Social and peer influences]_
-_Economic Influences: [Economic factors affecting behavior]_
-_Source: [URL]_
-
-### Customer Interaction Patterns
-
-[Customer interaction analysis with source citations]
-_Research and Discovery: [How customers find and research options]_
-_Purchase Decision Process: [Steps in purchase decision making]_
-_Post-Purchase Behavior: [After-purchase engagement patterns]_
-_Loyalty and Retention: [Factors driving customer loyalty]_
-_Source: [URL]_
-```
-
-### 5. Present Analysis and Continue Option
-
-**Show analysis and present continue option:**
-
-"I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
-
-**Key Customer Behavior Findings:**
-
-- Customer behavior patterns clearly identified with drivers
-- Demographic segmentation thoroughly analyzed
-- Psychographic profiles mapped and documented
-- Customer interaction patterns captured
-- Multiple sources verified for critical insights
-
-**Ready to proceed to customer pain points?**
-[C] Continue - Save this to document and proceed to pain points analysis
-
-**HALT — wait for user response before proceeding.**
-
-### 6. Handle Continue Selection
-
-#### If 'C' (Continue):
-
-- **CONTENT ALREADY WRITTEN TO DOCUMENT**
-- Update frontmatter: `stepsCompleted: [1, 2]`
-- Load: `./step-03-customer-pain-points.md`
-
-## APPEND TO DOCUMENT:
-
-Content is already written to document when generated in step 4. No additional append needed.
-
-## SUCCESS METRICS:
-
-✅ Customer behavior patterns identified with current citations
-✅ Demographic segmentation thoroughly analyzed
-✅ Psychographic profiles clearly documented
-✅ Customer interaction patterns captured
-✅ Multiple sources verified for critical insights
-✅ Content written immediately to document
-✅ [C] continue option presented and handled correctly
-✅ Proper routing to next step (customer pain points)
-✅ Research goals alignment maintained
-
-## FAILURE MODES:
-
-❌ Relying solely on training data without web verification for current facts
-
-❌ Missing critical customer behavior patterns
-❌ Incomplete demographic segmentation analysis
-❌ Missing psychographic profile documentation
-❌ Not writing content immediately to document
-❌ Not presenting [C] continue option after content generation
-❌ Not routing to customer pain points analysis step
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research 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 BEHAVIOR RESEARCH PROTOCOLS:
-
-- Research customer behavior studies and market research
-- Use demographic data from authoritative sources
-- Research psychographic profiling and value systems
-- Analyze customer interaction and engagement patterns
-- Focus on current behavior data and trends
-- Present conflicting information when sources disagree
-- Apply confidence levels appropriately
-
-## BEHAVIOR ANALYSIS STANDARDS:
-
-- Always cite URLs for web search results
-- Use authoritative customer research sources
-- Note data currency and potential limitations
-- Present multiple perspectives when sources conflict
-- Apply confidence levels to uncertain data
-- Focus on actionable customer insights
-
-## NEXT STEP:
-
-After user selects 'C', load `./step-03-customer-pain-points.md` to analyze customer pain points, challenges, and unmet needs for {{research_topic}}.
-
-Remember: Always write research content to document immediately and emphasize current customer data with rigorous source verification!

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

@@ -1,251 +0,0 @@
-# Market Research Step 3: Customer Pain Points and Needs
-
-## 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 NEEDS ANALYST, not content generator
-- 💬 FOCUS on customer pain points, challenges, and unmet needs
-- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
-- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
-- ✅ 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 pain points content generation
-- 📝 WRITE CUSTOMER PAIN POINTS ANALYSIS TO DOCUMENT IMMEDIATELY
-- 💾 ONLY proceed when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from previous steps are available
-- Customer behavior analysis completed in previous step
-- Focus on customer pain points, challenges, and unmet needs
-- Web search capabilities with source verification are enabled
-- **Research topic = "{{research_topic}}"** - established from initial discussion
-- **Research goals = "{{research_goals}}"** - established from initial discussion
-
-## YOUR TASK:
-
-Conduct customer pain points and needs analysis with emphasis on challenges and frustrations.
-
-## CUSTOMER PAIN POINTS ANALYSIS SEQUENCE:
-
-### 1. Begin Customer Pain Points Analysis
-
-**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer pain point areas simultaneously and thoroughly.
-
-Start with customer pain points research approach:
-"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to understand customer challenges.
-
-**Customer Pain Points Focus:**
-
-- Customer challenges and frustrations
-- Unmet needs and unaddressed problems
-- Barriers to adoption or usage
-- Service and support pain points
-- Customer satisfaction gaps
-
-**Let me search for current customer pain points insights.**"
-
-### 2. Parallel Pain Points Research Execution
-
-**Execute multiple web searches simultaneously:**
-
-Search the web: "{{research_topic}} customer pain points challenges"
-Search the web: "{{research_topic}} customer frustrations"
-Search the web: "{{research_topic}} unmet customer needs"
-Search the web: "{{research_topic}} customer barriers to adoption"
-
-**Analysis approach:**
-
-- Look for customer satisfaction surveys and reports
-- Search for customer complaints and reviews
-- Research customer support and service issues
-- Analyze barriers to customer adoption
-- Study unmet needs and market gaps
-
-### 3. Analyze and Aggregate Results
-
-**Collect and analyze findings from all parallel searches:**
-
-"After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings:
-
-**Research Coverage:**
-
-- Customer challenges and frustrations
-- Unmet needs and unaddressed problems
-- Barriers to adoption or usage
-- Service and support pain points
-
-**Cross-Pain Points Analysis:**
-[Identify patterns connecting different types of pain points]
-
-**Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
-
-### 4. Generate Customer Pain Points Content
-
-**WRITE IMMEDIATELY TO DOCUMENT**
-
-Prepare customer pain points analysis with web search citations:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Customer Pain Points and Needs
-
-### Customer Challenges and Frustrations
-
-[Customer challenges analysis with source citations]
-_Primary Frustrations: [Major customer frustrations identified]_
-_Usage Barriers: [Barriers preventing effective usage]_
-_Service Pain Points: [Customer service and support issues]_
-_Frequency Analysis: [How often these challenges occur]_
-_Source: [URL]_
-
-### Unmet Customer Needs
-
-[Unmet needs analysis with source citations]
-_Critical Unmet Needs: [Most important unaddressed needs]_
-_Solution Gaps: [Opportunities to address unmet needs]_
-_Market Gaps: [Market opportunities from unmet needs]_
-_Priority Analysis: [Which needs are most critical]_
-_Source: [URL]_
-
-### Barriers to Adoption
-
-[Adoption barriers analysis with source citations]
-_Price Barriers: [Cost-related barriers to adoption]_
-_Technical Barriers: [Complexity or technical barriers]_
-_Trust Barriers: [Trust and credibility issues]_
-_Convenience Barriers: [Ease of use or accessibility issues]_
-_Source: [URL]_
-
-### Service and Support Pain Points
-
-[Service pain points analysis with source citations]
-_Customer Service Issues: [Common customer service problems]_
-_Support Gaps: [Areas where customer support is lacking]_
-_Communication Issues: [Communication breakdowns and frustrations]_
-_Response Time Issues: [Slow response and resolution problems]_
-_Source: [URL]_
-
-### Customer Satisfaction Gaps
-
-[Satisfaction gap analysis with source citations]
-_Expectation Gaps: [Differences between expectations and reality]_
-_Quality Gaps: [Areas where quality expectations aren't met]_
-_Value Perception Gaps: [Perceived value vs actual value]_
-_Trust and Credibility Gaps: [Trust issues affecting satisfaction]_
-_Source: [URL]_
-
-### Emotional Impact Assessment
-
-[Emotional impact analysis with source citations]
-_Frustration Levels: [Customer frustration severity assessment]_
-_Loyalty Risks: [How pain points affect customer loyalty]_
-_Reputation Impact: [Impact on brand or product reputation]_
-_Customer Retention Risks: [Risk of customer loss from pain points]_
-_Source: [URL]_
-
-### Pain Point Prioritization
-
-[Pain point prioritization with source citations]
-_High Priority Pain Points: [Most critical pain points to address]_
-_Medium Priority Pain Points: [Important but less critical pain points]_
-_Low Priority Pain Points: [Minor pain points with lower impact]_
-_Opportunity Mapping: [Pain points with highest solution opportunity]_
-_Source: [URL]_
-```
-
-### 5. Present Analysis and Continue Option
-
-**Show analysis and present continue option:**
-
-"I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges.
-
-**Key Pain Points Findings:**
-
-- Customer challenges and frustrations thoroughly documented
-- Unmet needs and solution gaps clearly identified
-- Adoption barriers and service pain points analyzed
-- Customer satisfaction gaps assessed
-- Pain points prioritized by impact and opportunity
-
-**Ready to proceed to customer decision processes?**
-[C] Continue - Save this to document and proceed to decision processes analysis
-
-**HALT — wait for user response before proceeding.**
-
-### 6. Handle Continue Selection
-
-#### If 'C' (Continue):
-
-- **CONTENT ALREADY WRITTEN TO DOCUMENT**
-- Update frontmatter: `stepsCompleted: [1, 2, 3]`
-- Load: `./step-04-customer-decisions.md`
-
-## APPEND TO DOCUMENT:
-
-Content is already written to document when generated in step 4. No additional append needed.
-
-## SUCCESS METRICS:
-
-✅ Customer challenges and frustrations clearly documented
-✅ Unmet needs and solution gaps identified
-✅ Adoption barriers and service pain points analyzed
-✅ Customer satisfaction gaps assessed
-✅ Pain points prioritized by impact and opportunity
-✅ Content written immediately to document
-✅ [C] continue option presented and handled correctly
-✅ Proper routing to next step (customer decisions)
-✅ Research goals alignment maintained
-
-## FAILURE MODES:
-
-❌ Relying solely on training data without web verification for current facts
-
-❌ Missing critical customer challenges or frustrations
-❌ Not identifying unmet needs or solution gaps
-❌ Incomplete adoption barriers analysis
-❌ Not writing content immediately to document
-❌ Not presenting [C] continue option after content generation
-❌ Not routing to customer decisions analysis step
-
-❌ **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 PAIN POINTS RESEARCH PROTOCOLS:
-
-- Research customer satisfaction surveys and reviews
-- Use customer feedback and complaint data
-- Analyze customer support and service issues
-- Study barriers to customer adoption
-- Focus on current pain point data
-- Present conflicting information when sources disagree
-- Apply confidence levels appropriately
-
-## PAIN POINTS ANALYSIS STANDARDS:
-
-- Always cite URLs for web search results
-- Use authoritative customer research sources
-- Note data currency and potential limitations
-- Present multiple perspectives when sources conflict
-- Apply confidence levels to uncertain data
-- Focus on actionable pain point insights
-
-## NEXT STEP:
-
-After user selects 'C', load `./step-04-customer-decisions.md` to analyze customer decision processes, journey mapping, and decision factors for {{research_topic}}.
-
-Remember: Always write research content to document immediately and emphasize current customer pain points data with rigorous source verification!

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

@@ -1,261 +0,0 @@
-# Market Research Step 4: Customer Decisions and Journey
-
-## 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 DECISION ANALYST, not content generator
-- 💬 FOCUS on customer decision processes and journey mapping
-- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
-- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
-- ✅ 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 decision processes content generation
-- 📝 WRITE CUSTOMER DECISIONS ANALYSIS TO DOCUMENT IMMEDIATELY
-- 💾 ONLY proceed when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from previous steps are available
-- Customer behavior and pain points analysis completed in previous steps
-- Focus on customer decision processes and journey mapping
-- Web search capabilities with source verification are enabled
-- **Research topic = "{{research_topic}}"** - established from initial discussion
-- **Research goals = "{{research_goals}}"** - established from initial discussion
-
-## YOUR TASK:
-
-Conduct customer decision processes and journey analysis with emphasis on decision factors and journey mapping.
-
-## CUSTOMER DECISIONS ANALYSIS SEQUENCE:
-
-### 1. Begin Customer Decisions Analysis
-
-**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer decision areas simultaneously and thoroughly.
-
-Start with customer decisions research approach:
-"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** to understand customer decision-making.
-
-**Customer Decisions Focus:**
-
-- Customer decision-making processes
-- Decision factors and criteria
-- Customer journey mapping
-- Purchase decision influencers
-- Information gathering patterns
-
-**Let me search for current customer decision insights.**"
-
-### 2. Parallel Decisions Research Execution
-
-**Execute multiple web searches simultaneously:**
-
-Search the web: "{{research_topic}} customer decision process"
-Search the web: "{{research_topic}} buying criteria factors"
-Search the web: "{{research_topic}} customer journey mapping"
-Search the web: "{{research_topic}} decision influencing factors"
-
-**Analysis approach:**
-
-- Look for customer decision research studies
-- Search for buying criteria and factor analysis
-- Research customer journey mapping methodologies
-- Analyze decision influence factors and channels
-- Study information gathering and evaluation patterns
-
-### 3. Analyze and Aggregate Results
-
-**Collect and analyze findings from all parallel searches:**
-
-"After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings:
-
-**Research Coverage:**
-
-- Customer decision-making processes
-- Decision factors and criteria
-- Customer journey mapping
-- Decision influence factors
-
-**Cross-Decisions Analysis:**
-[Identify patterns connecting decision factors and journey stages]
-
-**Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
-
-### 4. Generate Customer Decisions Content
-
-**WRITE IMMEDIATELY TO DOCUMENT**
-
-Prepare customer decisions analysis with web search citations:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Customer Decision Processes and Journey
-
-### Customer Decision-Making Processes
-
-[Decision processes analysis with source citations]
-_Decision Stages: [Key stages in customer decision making]_
-_Decision Timelines: [Timeframes for different decisions]_
-_Complexity Levels: [Decision complexity assessment]_
-_Evaluation Methods: [How customers evaluate options]_
-_Source: [URL]_
-
-### Decision Factors and Criteria
-
-[Decision factors analysis with source citations]
-_Primary Decision Factors: [Most important factors in decisions]_
-_Secondary Decision Factors: [Supporting factors influencing decisions]_
-_Weighing Analysis: [How different factors are weighed]_
-_Evoluton Patterns: [How factors change over time]_
-_Source: [URL]_
-
-### Customer Journey Mapping
-
-[Journey mapping analysis with source citations]
-_Awareness Stage: [How customers become aware of {{research_topic}}]_
-_Consideration Stage: [Evaluation and comparison process]_
-_Decision Stage: [Final decision-making process]_
-_Purchase Stage: [Purchase execution and completion]_
-_Post-Purchase Stage: [Post-decision evaluation and behavior]_
-_Source: [URL]_
-
-### Touchpoint Analysis
-
-[Touchpoint analysis with source citations]
-_Digital Touchpoints: [Online and digital interaction points]_
-_Offline Touchpoints: [Physical and in-person interaction points]_
-_Information Sources: [Where customers get information]_
-_Influence Channels: [What influences customer decisions]_
-_Source: [URL]_
-
-### Information Gathering Patterns
-
-[Information patterns analysis with source citations]
-_Research Methods: [How customers research options]_
-_Information Sources Trusted: [Most trusted information sources]_
-_Research Duration: [Time spent gathering information]_
-_Evaluation Criteria: [How customers evaluate information]_
-_Source: [URL]_
-
-### Decision Influencers
-
-[Decision influencer analysis with source citations]
-_Peer Influence: [How friends and family influence decisions]_
-_Expert Influence: [How expert opinions affect decisions]_
-_Media Influence: [How media and marketing affect decisions]_
-_Social Proof Influence: [How reviews and testimonials affect decisions]_
-_Source: [URL]_
-
-### Purchase Decision Factors
-
-[Purchase decision factors analysis with source citations]
-_Immediate Purchase Drivers: [Factors triggering immediate purchase]_
-_Delayed Purchase Drivers: [Factors causing purchase delays]_
-_Brand Loyalty Factors: [Factors driving repeat purchases]_
-_Price Sensitivity: [How price affects purchase decisions]_
-_Source: [URL]_
-
-### Customer Decision Optimizations
-
-[Decision optimization analysis with source citations]
-_Friction Reduction: [Ways to make decisions easier]_
-_Trust Building: [Building customer trust in decisions]_
-_Conversion Optimization: [Optimizing decision-to-purchase rates]_
-_Loyalty Building: [Building long-term customer relationships]_
-_Source: [URL]_
-```
-
-### 5. Present Analysis and Continue Option
-
-**Show analysis and present continue option:**
-
-"I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making.
-
-**Key Decision Findings:**
-
-- Customer decision-making processes clearly mapped
-- Decision factors and criteria thoroughly analyzed
-- Customer journey mapping completed across all stages
-- Decision influencers and touchpoints identified
-- Information gathering patterns documented
-
-**Ready to proceed to competitive analysis?**
-[C] Continue - Save this to document and proceed to competitive analysis
-
-**HALT — wait for user response before proceeding.**
-
-### 6. Handle Continue Selection
-
-#### If 'C' (Continue):
-
-- **CONTENT ALREADY WRITTEN TO DOCUMENT**
-- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
-- Load: `./step-05-competitive-analysis.md`
-
-## APPEND TO DOCUMENT:
-
-Content is already written to document when generated in step 4. No additional append needed.
-
-## SUCCESS METRICS:
-
-✅ Customer decision-making processes clearly mapped
-✅ Decision factors and criteria thoroughly analyzed
-✅ Customer journey mapping completed across all stages
-✅ Decision influencers and touchpoints identified
-✅ Information gathering patterns documented
-✅ Content written immediately to document
-✅ [C] continue option presented and handled correctly
-✅ Proper routing to next step (competitive analysis)
-✅ Research goals alignment maintained
-
-## FAILURE MODES:
-
-❌ Relying solely on training data without web verification for current facts
-
-❌ Missing critical decision-making process stages
-❌ Not identifying key decision factors
-❌ Incomplete customer journey mapping
-❌ Not writing content immediately to document
-❌ Not presenting [C] continue option after content generation
-❌ Not routing to competitive analysis step
-
-❌ **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 DECISIONS RESEARCH PROTOCOLS:
-
-- Research customer decision studies and psychology
-- Use customer journey mapping methodologies
-- Analyze buying criteria and decision factors
-- Study decision influence and touchpoint analysis
-- Focus on current decision data
-- Present conflicting information when sources disagree
-- Apply confidence levels appropriately
-
-## DECISION ANALYSIS STANDARDS:
-
-- Always cite URLs for web search results
-- Use authoritative customer decision research sources
-- Note data currency and potential limitations
-- Present multiple perspectives when sources conflict
-- Apply confidence levels to uncertain data
-- Focus on actionable decision insights
-
-## NEXT STEP:
-
-After user selects 'C', load `./step-05-competitive-analysis.md` to analyze competitive landscape, market positioning, and competitive strategies for {{research_topic}}.
-
-Remember: Always write research content to document immediately and emphasize current customer decision data with rigorous source verification!

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

@@ -1,173 +0,0 @@
-# Market Research Step 5: Competitive Analysis
-
-## 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 COMPETITIVE ANALYST, not content generator
-- 💬 FOCUS on competitive landscape and market positioning
-- 🔍 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] complete option after competitive analysis content generation
-- 💾 ONLY save when user chooses C (Complete)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
-- 🚫 FORBIDDEN to complete workflow until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from previous steps are available
-- Focus on competitive landscape and market positioning analysis
-- Web search capabilities with source verification are enabled
-- May need to search for specific competitor information
-
-## YOUR TASK:
-
-Conduct comprehensive competitive analysis with emphasis on market positioning.
-
-## COMPETITIVE ANALYSIS SEQUENCE:
-
-### 1. Begin Competitive Analysis
-
-Start with competitive research approach:
-"Now I'll conduct **competitive analysis** to understand the competitive landscape.
-
-**Competitive Analysis Focus:**
-
-- Key players and market share
-- Competitive positioning strategies
-- Strengths and weaknesses analysis
-- Market differentiation opportunities
-- Competitive threats and challenges
-
-**Let me search for current competitive information.**"
-
-### 2. Generate Competitive Analysis Content
-
-Prepare competitive analysis with web search citations:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Competitive Landscape
-
-### Key Market Players
-
-[Key players analysis with market share data]
-_Source: [URL]_
-
-### Market Share Analysis
-
-[Market share analysis with source citations]
-_Source: [URL]_
-
-### Competitive Positioning
-
-[Positioning analysis with source citations]
-_Source: [URL]_
-
-### Strengths and Weaknesses
-
-[SWOT analysis with source citations]
-_Source: [URL]_
-
-### Market Differentiation
-
-[Differentiation analysis with source citations]
-_Source: [URL]_
-
-### Competitive Threats
-
-[Threats analysis with source citations]
-_Source: [URL]_
-
-### Opportunities
-
-[Competitive opportunities analysis with source citations]
-_Source: [URL]_
-```
-
-### 3. Present Analysis and Complete Option
-
-Show the generated competitive analysis and present complete option:
-"I've completed the **competitive analysis** for the competitive landscape.
-
-**Key Competitive Findings:**
-
-- Key market players and market share identified
-- Competitive positioning strategies mapped
-- Strengths and weaknesses thoroughly analyzed
-- Market differentiation opportunities identified
-- Competitive threats and challenges documented
-
-**Ready to complete the market research?**
-[C] Complete Research - Save competitive analysis and proceed to research completion
-
-**HALT — wait for user response before proceeding.**
-
-### 4. Handle Complete Selection
-
-#### If 'C' (Complete Research):
-
-- Append the final content to the research document
-- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
-- Load: `./step-06-research-completion.md`
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C', append the content directly to the research document using the structure from step 2.
-
-## SUCCESS METRICS:
-
-✅ Key market players identified
-✅ Market share analysis completed with source verification
-✅ Competitive positioning strategies clearly mapped
-✅ Strengths and weaknesses thoroughly analyzed
-✅ Market differentiation opportunities identified
-✅ [C] complete option presented and handled correctly
-✅ Content properly appended to document when C selected
-✅ Market research workflow completed successfully
-
-## FAILURE MODES:
-
-❌ Relying solely on training data without web verification for current facts
-
-❌ Missing key market players or market share data
-❌ Incomplete competitive positioning analysis
-❌ Not identifying market differentiation opportunities
-❌ Not presenting completion option for research workflow
-❌ 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
-
-## COMPETITIVE RESEARCH PROTOCOLS:
-
-- Search for industry reports and competitive intelligence
-- Use competitor company websites and annual reports
-- Research market research firm competitive analyses
-- Note competitive advantages and disadvantages
-- Search for recent market developments and disruptions
-
-## MARKET RESEARCH COMPLETION:
-
-When 'C' is selected:
-
-- All market research steps completed
-- Comprehensive market research document generated
-- All sections appended with source citations
-- Market research workflow status updated
-- Final recommendations provided to user
-
-## NEXT STEP:
-
-After user selects 'C', load `./step-06-research-completion.md` to produce the final comprehensive market research document with strategic synthesis, executive summary, and complete document structure.

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

@@ -1,478 +0,0 @@
-# Market Research Step 6: Research Completion
-
-## 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 MARKET RESEARCH STRATEGIST, not content generator
-- 💬 FOCUS on strategic recommendations and actionable insights
-- 🔍 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] complete option after completion content generation
-- 💾 ONLY save when user chooses C (Complete)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow
-- 🚫 FORBIDDEN to complete workflow until C is selected
-- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from previous steps are available
-- **Research topic = "{{research_topic}}"** - comprehensive market analysis
-- **Research goals = "{{research_goals}}"** - achieved through exhaustive market research
-- All market research sections have been completed (customer behavior, pain points, decisions, competitive analysis)
-- Web search capabilities with source verification are enabled
-- This is the final synthesis step producing the complete market research document
-
-## YOUR TASK:
-
-Produce a comprehensive, authoritative market research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive market research.
-
-## MARKET RESEARCH COMPLETION SEQUENCE:
-
-### 1. Begin Strategic Synthesis
-
-Start with strategic synthesis approach:
-"Now I'll complete our market research with **strategic synthesis and recommendations** .
-
-**Strategic Synthesis Focus:**
-
-- Integrated insights from market, customer, and competitive analysis
-- Strategic recommendations based on research findings
-- Market entry or expansion strategies
-- Risk assessment and mitigation approaches
-- Actionable next steps and implementation guidance
-
-**Let me search for current strategic insights and best practices.**"
-
-### 2. Web Search for Market Entry Strategies
-
-Search for current market strategies:
-Search the web: "market entry strategies best practices"
-
-**Strategy focus:**
-
-- Market entry timing and approaches
-- Go-to-market strategies and frameworks
-- Market positioning and differentiation tactics
-- Customer acquisition and growth strategies
-
-### 3. Web Search for Risk Assessment
-
-Search for current risk approaches:
-Search the web: "market research risk assessment frameworks"
-
-**Risk focus:**
-
-- Market risks and uncertainty management
-- Competitive threats and mitigation strategies
-- Regulatory and compliance risks
-- Economic and market volatility considerations
-
-### 4. Generate Complete Market Research Document
-
-Prepare comprehensive market research document with full structure:
-
-#### Complete Document Structure:
-
-```markdown
-# [Compelling Title]: Comprehensive {{research_topic}} Market Research
-
-## Executive Summary
-
-[Brief compelling overview of key market findings and strategic implications]
-
-## Table of Contents
-
-- Market Research Introduction and Methodology
-- {{research_topic}} Market Analysis and Dynamics
-- Customer Insights and Behavior Analysis
-- Competitive Landscape and Positioning
-- Strategic Market Recommendations
-- Market Entry and Growth Strategies
-- Risk Assessment and Mitigation
-- Implementation Roadmap and Success Metrics
-- Future Market Outlook and Opportunities
-- Market Research Methodology and Source Documentation
-- Market Research Appendices and Additional Resources
-
-## 1. Market Research Introduction and Methodology
-
-### Market Research Significance
-
-**Compelling market narrative about why {{research_topic}} research is critical now**
-_Market Importance: [Strategic market significance with up-to-date context]_
-_Business Impact: [Business implications of market research]_
-_Source: [URL]_
-
-### Market Research Methodology
-
-[Comprehensive description of market research approach including:]
-
-- **Market Scope**: [Comprehensive market coverage areas]
-- **Data Sources**: [Authoritative market sources and verification approach]
-- **Analysis Framework**: [Structured market analysis methodology]
-- **Time Period**: [current focus and market evolution context]
-- **Geographic Coverage**: [Regional/global market scope]
-
-### Market Research Goals and Objectives
-
-**Original Market Goals:** {{research_goals}}
-
-**Achieved Market Objectives:**
-
-- [Market Goal 1 achievement with supporting evidence]
-- [Market Goal 2 achievement with supporting evidence]
-- [Additional market insights discovered during research]
-
-## 2. {{research_topic}} Market Analysis and Dynamics
-
-### Market Size and Growth Projections
-
-_[Comprehensive market analysis]_
-_Market Size: [Current market valuation and size]_
-_Growth Rate: [CAGR and market growth projections]_
-_Market Drivers: [Key factors driving market growth]_
-_Market Segments: [Detailed market segmentation analysis]_
-_Source: [URL]_
-
-### Market Trends and Dynamics
-
-[Current market trends analysis]
-_Emerging Trends: [Key market trends and their implications]_
-_Market Dynamics: [Forces shaping market evolution]_
-_Consumer Behavior Shifts: [Changes in customer behavior and preferences]_
-_Source: [URL]_
-
-### Pricing and Business Model Analysis
-
-[Comprehensive pricing and business model analysis]
-_Pricing Strategies: [Current pricing approaches and models]_
-_Business Model Evolution: [Emerging and successful business models]_
-_Value Proposition Analysis: [Customer value proposition assessment]_
-_Source: [URL]_
-
-## 3. Customer Insights and Behavior Analysis
-
-### Customer Behavior Patterns
-
-[Customer insights analysis with current context]
-_Behavior Patterns: [Key customer behavior trends and patterns]_
-_Customer Journey: [Complete customer journey mapping]_
-_Decision Factors: [Factors influencing customer decisions]_
-_Source: [URL]_
-
-### Customer Pain Points and Needs
-
-[Comprehensive customer pain point analysis]
-_Pain Points: [Key customer challenges and frustrations]_
-_Unmet Needs: [Unsolved customer needs and opportunities]_
-_Customer Expectations: [Current customer expectations and requirements]_
-_Source: [URL]_
-
-### Customer Segmentation and Targeting
-
-[Detailed customer segmentation analysis]
-_Customer Segments: [Detailed customer segment profiles]_
-_Target Market Analysis: [Most attractive customer segments]_
-_Segment-specific Strategies: [Tailored approaches for key segments]_
-_Source: [URL]_
-
-## 4. Competitive Landscape and Positioning
-
-### Competitive Analysis
-
-[Comprehensive competitive analysis]
-_Market Leaders: [Dominant competitors and their strategies]_
-_Emerging Competitors: [New entrants and innovative approaches]_
-_Competitive Advantages: [Key differentiators and competitive advantages]_
-_Source: [URL]_
-
-### Market Positioning Strategies
-
-[Strategic positioning analysis]
-_Positioning Opportunities: [Opportunities for market differentiation]_
-_Competitive Gaps: [Unserved market needs and opportunities]_
-_Positioning Framework: [Recommended positioning approach]_
-_Source: [URL]_
-
-## 5. Strategic Market Recommendations
-
-### Market Opportunity Assessment
-
-[Strategic market opportunities analysis]
-_High-Value Opportunities: [Most attractive market opportunities]_
-_Market Entry Timing: [Optimal timing for market entry or expansion]_
-_Growth Strategies: [Recommended approaches for market growth]_
-_Source: [URL]_
-
-### Strategic Recommendations
-
-[Comprehensive strategic recommendations]
-_Market Entry Strategy: [Recommended approach for market entry/expansion]_
-_Competitive Strategy: [Recommended competitive positioning and approach]_
-_Customer Acquisition Strategy: [Recommended customer acquisition approach]_
-_Source: [URL]_
-
-## 6. Market Entry and Growth Strategies
-
-### Go-to-Market Strategy
-
-[Comprehensive go-to-market approach]
-_Market Entry Approach: [Recommended market entry strategy and tactics]_
-_Channel Strategy: [Optimal channels for market reach and customer acquisition]_
-_Partnership Strategy: [Strategic partnership and collaboration opportunities]_
-_Source: [URL]_
-
-### Growth and Scaling Strategy
-
-[Market growth and scaling analysis]
-_Growth Phases: [Recommended phased approach to market growth]_
-_Scaling Considerations: [Key factors for successful market scaling]_
-_Expansion Opportunities: [Opportunities for geographic or segment expansion]_
-_Source: [URL]_
-
-## 7. Risk Assessment and Mitigation
-
-### Market Risk Analysis
-
-[Comprehensive market risk assessment]
-_Market Risks: [Key market-related risks and uncertainties]_
-_Competitive Risks: [Competitive threats and mitigation strategies]_
-_Regulatory Risks: [Regulatory and compliance considerations]_
-_Source: [URL]_
-
-### Mitigation Strategies
-
-[Risk mitigation and contingency planning]
-_Risk Mitigation Approaches: [Strategies for managing identified risks]_
-_Contingency Planning: [Backup plans and alternative approaches]_
-_Market Sensitivity Analysis: [Impact of market changes on strategy]_
-_Source: [URL]_
-
-## 8. Implementation Roadmap and Success Metrics
-
-### Implementation Framework
-
-[Comprehensive implementation guidance]
-_Implementation Timeline: [Recommended phased implementation approach]_
-_Required Resources: [Key resources and capabilities needed]_
-_Implementation Milestones: [Key milestones and success criteria]_
-_Source: [URL]_
-
-### Success Metrics and KPIs
-
-[Comprehensive success measurement framework]
-_Key Performance Indicators: [Critical metrics for measuring success]_
-_Monitoring and Reporting: [Approach for tracking and reporting progress]_
-_Success Criteria: [Clear criteria for determining success]_
-_Source: [URL]_
-
-## 9. Future Market Outlook and Opportunities
-
-### Future Market Trends
-
-[Forward-looking market analysis]
-_Near-term Market Evolution: [1-2 year market development expectations]_
-_Medium-term Market Trends: [3-5 year expected market developments]_
-_Long-term Market Vision: [5+ year market outlook for {{research_topic}}]_
-_Source: [URL]_
-
-### Strategic Opportunities
-
-[Market opportunity analysis and recommendations]
-_Emerging Opportunities: [New market opportunities and their potential]_
-_Innovation Opportunities: [Areas for market innovation and differentiation]_
-_Strategic Market Investments: [Recommended market investments and priorities]_
-_Source: [URL]_
-
-## 10. Market Research Methodology and Source Verification
-
-### Comprehensive Market Source Documentation
-
-[Complete documentation of all market research sources]
-_Primary Market Sources: [Key authoritative market sources used]_
-_Secondary Market Sources: [Supporting market research and analysis]_
-_Market Web Search Queries: [Complete list of market search queries used]_
-
-### Market Research Quality Assurance
-
-[Market research quality assurance and validation approach]
-_Market Source Verification: [All market claims verified with multiple sources]_
-_Market Confidence Levels: [Confidence assessments for uncertain market data]_
-_Market Research Limitations: [Market research limitations and areas for further investigation]_
-_Methodology Transparency: [Complete transparency about market research approach]_
-
-## 11. Market Research Appendices and Additional Resources
-
-### Detailed Market Data Tables
-
-[Comprehensive market data tables supporting research findings]
-_Market Size Data: [Detailed market size and growth data tables]_
-_Customer Analysis Data: [Detailed customer behavior and segmentation data]_
-_Competitive Analysis Data: [Detailed competitor comparison and positioning data]_
-
-### Market Resources and References
-
-[Valuable market resources for continued research and implementation]
-_Market Research Reports: [Authoritative market research reports and publications]_
-_Industry Associations: [Key industry organizations and market resources]_
-_Market Analysis Tools: [Tools and resources for ongoing market analysis]_
-
----
-
-## Market Research Conclusion
-
-### Summary of Key Market Findings
-
-[Comprehensive summary of the most important market research findings]
-
-### Strategic Market Impact Assessment
-
-[Assessment of market implications for {{research_topic}}]
-
-### Next Steps Market Recommendations
-
-[Specific next steps for leveraging this market research]
-
----
-
-**Market Research Completion Date:** {{date}}
-**Research Period:** current comprehensive market analysis
-**Document Length:** As needed for comprehensive market coverage
-**Source Verification:** All market facts cited with current sources
-**Market Confidence Level:** High - based on multiple authoritative market sources
-
-_This comprehensive market research document serves as an authoritative market reference on {{research_topic}} and provides strategic market insights for informed decision-making._
-```
-
-### 5. Present Complete Market Research Document and Final Option
-
-**Market Research Document Completion Presentation:**
-
-"I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with:
-
-**Document Features:**
-
-- **Compelling Market Introduction**: Engaging opening that establishes market research significance
-- **Comprehensive Market TOC**: Complete navigation structure for market reference
-- **Exhaustive Market Research Coverage**: All market aspects of {{research_topic}} thoroughly analyzed
-- **Executive Market Summary**: Key market findings and strategic implications highlighted
-- **Strategic Market Recommendations**: Actionable market insights based on comprehensive research
-- **Complete Market Source Citations**: Every market claim verified with current sources
-
-**Market Research Completeness:**
-
-- Market analysis and dynamics fully documented
-- Customer insights and behavior analysis comprehensively covered
-- Competitive landscape and positioning detailed
-- Strategic market recommendations and implementation guidance provided
-
-**Document Standards Met:**
-
-- Exhaustive market research with no critical gaps
-- Professional market structure and compelling narrative
-- As long as needed for comprehensive market coverage
-- Multiple independent sources for all market claims
-- current market data throughout with proper citations
-
-**Ready to complete this comprehensive market research document?**
-[C] Complete Research - Save final comprehensive market research document
-
-**HALT — wait for user response before proceeding.**
-
-### 6. Handle Complete Selection
-
-#### If 'C' (Complete Research):
-
-- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section
-- Append the final content to the research document
-- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
-- Complete the market research workflow
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C', append the content directly to the research document using the structure from step 4. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document.
-
-## SUCCESS METRICS:
-
-✅ Compelling market introduction with research significance
-✅ Comprehensive market table of contents with complete document structure
-✅ Exhaustive market research coverage across all market aspects
-✅ Executive market summary with key findings and strategic implications
-✅ Strategic market recommendations grounded in comprehensive research
-✅ Complete market source verification with current citations
-✅ Professional market document structure and compelling narrative
-✅ [C] complete option presented and handled correctly
-✅ Market research workflow completed with comprehensive document
-
-## FAILURE MODES:
-
-❌ Not producing compelling market introduction
-❌ Missing comprehensive market table of contents
-❌ Incomplete market research coverage across market aspects
-❌ Not providing executive market summary with key findings
-❌ Missing strategic market recommendations based on research
-❌ Relying solely on training data without web verification for current facts
-❌ Producing market document without professional structure
-❌ Not presenting completion option for final market document
-
-❌ **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
-
-## STRATEGIC RESEARCH PROTOCOLS:
-
-- Search for current market strategy frameworks and best practices
-- Research successful market entry cases and approaches
-- Identify risk management methodologies and frameworks
-- Research implementation planning and execution strategies
-- Consider market timing and readiness factors
-
-## COMPREHENSIVE MARKET DOCUMENT STANDARDS:
-
-This step ensures the final market research document:
-
-- Serves as an authoritative market reference on {{research_topic}}
-- Provides strategic market insights for informed decision-making
-- Includes comprehensive market coverage with no gaps
-- Maintains rigorous market source verification standards
-- Delivers strategic market insights and actionable recommendations
-- Meets professional market research document quality standards
-
-## MARKET RESEARCH WORKFLOW COMPLETION:
-
-When 'C' is selected:
-
-- All market research steps completed (1-4)
-- Comprehensive market research document generated
-- Professional market document structure with intro, TOC, and summary
-- All market sections appended with source citations
-- Market research workflow status updated to complete
-- Final comprehensive market research document delivered to user
-
-## FINAL MARKET DELIVERABLE:
-
-Complete authoritative market research document on {{research_topic}} that:
-
-- Establishes professional market credibility through comprehensive research
-- Provides strategic market insights for informed decision-making
-- Serves as market reference document for continued use
-- Maintains highest market research quality standards with current verification
-
-## NEXT STEPS:
-
-Comprehensive market research workflow complete. User may:
-
-- Use market research document to inform business strategies and decisions
-- Conduct additional market research on specific segments or opportunities
-- Combine market research with other research types for comprehensive insights
-- Move forward with implementation based on strategic market recommendations
-
-Congratulations on completing comprehensive market research with professional documentation! 🎉

src/bmm/workflows/1-analysis/research/bmad-skill-manifest.yaml

@@ -0,0 +1,14 @@
+workflow-domain-research.md:
+  canonicalId: bmad-domain-research
+  type: workflow
+  description: "Conduct domain and industry research. Use when the user says 'lets create a research report on [domain or industry]'"
+
+workflow-market-research.md:
+  canonicalId: bmad-market-research
+  type: workflow
+  description: "Conduct market research on competition and customers. Use when the user says 'create a market research report about [business idea]'"
+
+workflow-technical-research.md:
+  canonicalId: bmad-technical-research
+  type: workflow
+  description: "Conduct technical research on technologies and architecture. Use when the user says 'create a technical research report on [topic]'"

src/bmm/workflows/1-analysis/research/bmad-technical-research/SKILL.md

@@ -1,6 +0,0 @@
----
-name: bmad-technical-research
-description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
----
-
-Follow the instructions in [workflow.md](workflow.md).

src/bmm/workflows/1-analysis/research/bmad-technical-research/research.template.md

@@ -1,29 +0,0 @@
----
-stepsCompleted: []
-inputDocuments: []
-workflowType: 'research'
-lastStep: 1
-research_type: '{{research_type}}'
-research_topic: '{{research_topic}}'
-research_goals: '{{research_goals}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
-web_research_enabled: true
-source_verification: true
----
-
-# Research Report: {{research_type}}
-
-**Date:** {{date}}
-**Author:** {{user_name}}
-**Research Type:** {{research_type}}
-
----
-
-## Research Overview
-
-[Research overview and methodology will be appended here]
-
----
-
-<!-- Content will be appended sequentially through research workflow steps -->

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

@@ -78,7 +78,7 @@ For **{{research_topic}}**, I will research:
 
 - Document scope confirmation in research file
 - Update frontmatter: `stepsCompleted: [1]`
-- Load: `./step-02-domain-analysis.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -132,6 +132,6 @@ When user selects 'C', append scope confirmation:
 
 ## NEXT STEP:
 
-After user selects 'C', load `./step-02-domain-analysis.md` to begin industry analysis.
+After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md` to begin industry analysis.
 
 Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!

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

@@ -171,7 +171,7 @@ _Source: [URL]_
 
 - **CONTENT ALREADY WRITTEN TO DOCUMENT**
 - Update frontmatter: `stepsCompleted: [1, 2]`
-- Load: `./step-03-competitive-landscape.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -224,6 +224,6 @@ Content is already written to document when generated in step 4. No additional a
 
 ## NEXT STEP:
 
-After user selects 'C', load `./step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
+After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
 
 Remember: Always write research content to document immediately and search the web to verify facts!

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

@@ -180,7 +180,7 @@ _Source: [URL]_
 
 - **CONTENT ALREADY WRITTEN TO DOCUMENT**
 - Update frontmatter: `stepsCompleted: [1, 2, 3]`
-- Load: `./step-04-regulatory-focus.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -233,6 +233,6 @@ Content is already written to document when generated in step 4. No additional a
 
 ## NEXT STEP:
 
-After user selects 'C', load `./step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}.
+After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}.
 
 Remember: Always write research content to document immediately and search the web to verify facts!

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

@@ -155,7 +155,7 @@ Show the generated regulatory analysis and present continue option:
 
 - **CONTENT ALREADY WRITTEN TO DOCUMENT**
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
-- Load: `./step-05-technical-trends.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -201,6 +201,6 @@ Content is already written to document when generated in step 5. No additional a
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `./step-05-technical-trends.md` to analyze technical trends and innovations in the domain.
+After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md` to analyze technical trends and innovations in the domain.
 
 Remember: Search the web to verify regulatory facts and provide practical implementation considerations!

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

@@ -174,7 +174,7 @@ Show the generated technical analysis and present complete option:
 
 - **CONTENT ALREADY WRITTEN TO DOCUMENT**
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
-- Load: `./step-06-research-synthesis.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md`
 
 ## APPEND TO DOCUMENT:
 

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

@@ -78,7 +78,7 @@ For **{{research_topic}}**, I will research:
 
 - Document scope confirmation in research file
 - Update frontmatter: `stepsCompleted: [1]`
-- Load: `./step-02-technical-overview.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -132,6 +132,6 @@ When user selects 'C', append scope confirmation:
 
 ## NEXT STEP:
 
-After user selects 'C', load `./step-02-technical-overview.md` to begin technology stack analysis.
+After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md` to begin technology stack analysis.
 
 Remember: This is SCOPE CONFIRMATION ONLY - no actual technical research yet, just confirming the research approach and scope!

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

@@ -180,7 +180,7 @@ _Source: [URL]_
 
 - **CONTENT ALREADY WRITTEN TO DOCUMENT**
 - Update frontmatter: `stepsCompleted: [1, 2]`
-- Load: `./step-03-integration-patterns.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -234,6 +234,6 @@ Content is already written to document when generated in step 4. No additional a
 
 ## NEXT STEP:
 
-After user selects 'C', load `./step-03-integration-patterns.md` to analyze APIs, communication protocols, and system interoperability for {{research_topic}}.
+After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md` to analyze APIs, communication protocols, and system interoperability for {{research_topic}}.
 
 Remember: Always write research content to document immediately and emphasize current technology data with rigorous source verification!

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

@@ -189,7 +189,7 @@ _Source: [URL]_
 
 - **CONTENT ALREADY WRITTEN TO DOCUMENT**
 - Update frontmatter: `stepsCompleted: [1, 2, 3]`
-- Load: `./step-04-architectural-patterns.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -243,6 +243,6 @@ Content is already written to document when generated in step 4. No additional a
 
 ## NEXT STEP:
 
-After user selects 'C', load `./step-04-architectural-patterns.md` to analyze architectural patterns, design decisions, and system structures for {{research_topic}}.
+After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md` to analyze architectural patterns, design decisions, and system structures for {{research_topic}}.
 
 Remember: Always write research content to document immediately and emphasize current integration data with rigorous source verification!

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

@@ -156,7 +156,7 @@ Show the generated architectural patterns and present continue option:
 
 - Append the final content to the research document
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
-- Load: `./step-05-implementation-research.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -197,6 +197,6 @@ When user selects 'C', append the content directly to the research document usin
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `./step-05-implementation-research.md` to focus on implementation approaches and technology adoption.
+After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md` to focus on implementation approaches and technology adoption.
 
 Remember: Always emphasize current architectural data and rigorous source verification!

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

@@ -179,7 +179,7 @@ Show the generated implementation research and present continue option:
 
 - Append the final content to the research document
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
-- Load: `./step-06-research-synthesis.md`
+- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -230,4 +230,4 @@ When 'C' is selected:
 
 ## NEXT STEP:
 
-After user selects 'C', load `./step-06-research-synthesis.md` to produce the comprehensive technical research document with narrative introduction, detailed TOC, and executive summary.
+After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md` to produce the comprehensive technical research document with narrative introduction, detailed TOC, and executive summary.

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

@@ -1,3 +1,8 @@
+---
+name: domain-research
+description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
+---
+
 # 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.

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

@@ -1,3 +1,8 @@
+---
+name: market-research
+description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".'
+---
+
 # 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.
@@ -42,7 +47,7 @@ After gathering the topic and goals:
 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: `./steps/step-01-init.md` with topic context
+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.
 

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

@@ -1,3 +1,7 @@
+---
+name: technical-research
+description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
+---
 
 # Technical Research Workflow
 

src/bmm/workflows/2-plan-workflows/bmad-create-ux-design/SKILL.md

@@ -1,6 +0,0 @@
----
-name: bmad-create-ux-design
-description: 'Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

src/bmm/workflows/2-plan-workflows/bmad-edit-prd/SKILL.md

@@ -1,6 +0,0 @@
----
-name: bmad-edit-prd
-description: 'Edit an existing PRD. Use when the user says "edit this PRD".'
----
-
-Follow the instructions in [workflow.md](workflow.md).

src/bmm/workflows/2-plan-workflows/bmad-validate-prd/SKILL.md

@@ -1,6 +0,0 @@
----
-name: bmad-validate-prd
-description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

src/bmm/workflows/2-plan-workflows/bmad-validate-prd/data/domain-complexity.csv

@@ -1,15 +0,0 @@
-domain,signals,complexity,key_concerns,required_knowledge,suggested_workflow,web_searches,special_sections
-healthcare,"medical,diagnostic,clinical,FDA,patient,treatment,HIPAA,therapy,pharma,drug",high,"FDA approval;Clinical validation;HIPAA compliance;Patient safety;Medical device classification;Liability","Regulatory pathways;Clinical trial design;Medical standards;Data privacy;Integration requirements","domain-research","FDA software medical device guidance {date};HIPAA compliance software requirements;Medical software standards {date};Clinical validation software","clinical_requirements;regulatory_pathway;validation_methodology;safety_measures"
-fintech,"payment,banking,trading,investment,crypto,wallet,transaction,KYC,AML,funds,fintech",high,"Regional compliance;Security standards;Audit requirements;Fraud prevention;Data protection","KYC/AML requirements;PCI DSS;Open banking;Regional laws (US/EU/APAC);Crypto regulations","domain-research","fintech regulations {date};payment processing compliance {date};open banking API standards;cryptocurrency regulations {date}","compliance_matrix;security_architecture;audit_requirements;fraud_prevention"
-govtech,"government,federal,civic,public sector,citizen,municipal,voting",high,"Procurement rules;Security clearance;Accessibility (508);FedRAMP;Privacy;Transparency","Government procurement;Security frameworks;Accessibility standards;Privacy laws;Open data requirements","domain-research","government software procurement {date};FedRAMP compliance requirements;section 508 accessibility;government security standards","procurement_compliance;security_clearance;accessibility_standards;transparency_requirements"
-edtech,"education,learning,student,teacher,curriculum,assessment,K-12,university,LMS",medium,"Student privacy (COPPA/FERPA);Accessibility;Content moderation;Age verification;Curriculum standards","Educational privacy laws;Learning standards;Accessibility requirements;Content guidelines;Assessment validity","domain-research","educational software privacy {date};COPPA FERPA compliance;WCAG education requirements;learning management standards","privacy_compliance;content_guidelines;accessibility_features;curriculum_alignment"
-aerospace,"aircraft,spacecraft,aviation,drone,satellite,propulsion,flight,radar,navigation",high,"Safety certification;DO-178C compliance;Performance validation;Simulation accuracy;Export controls","Aviation standards;Safety analysis;Simulation validation;ITAR/export controls;Performance requirements","domain-research + technical-model","DO-178C software certification;aerospace simulation standards {date};ITAR export controls software;aviation safety requirements","safety_certification;simulation_validation;performance_requirements;export_compliance"
-automotive,"vehicle,car,autonomous,ADAS,automotive,driving,EV,charging",high,"Safety standards;ISO 26262;V2X communication;Real-time requirements;Certification","Automotive standards;Functional safety;V2X protocols;Real-time systems;Testing requirements","domain-research","ISO 26262 automotive software;automotive safety standards {date};V2X communication protocols;EV charging standards","safety_standards;functional_safety;communication_protocols;certification_requirements"
-scientific,"research,algorithm,simulation,modeling,computational,analysis,data science,ML,AI",medium,"Reproducibility;Validation methodology;Peer review;Performance;Accuracy;Computational resources","Scientific method;Statistical validity;Computational requirements;Domain expertise;Publication standards","technical-model","scientific computing best practices {date};research reproducibility standards;computational modeling validation;peer review software","validation_methodology;accuracy_metrics;reproducibility_plan;computational_requirements"
-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"

src/bmm/workflows/2-plan-workflows/bmad-validate-prd/data/prd-purpose.md

@@ -1,197 +0,0 @@
-# BMAD PRD Purpose
-
-**The PRD is the top of the required funnel that feeds all subsequent product development work in rhw BMad Method.**
-
----
-
-## What is a BMAD PRD?
-
-A dual-audience document serving:
-1. **Human Product Managers and builders** - Vision, strategy, stakeholder communication
-2. **LLM Downstream Consumption** - UX Design → Architecture → Epics → Development AI Agents
-
-Each successive document becomes more AI-tailored and granular.
-
----
-
-## Core Philosophy: Information Density
-
-**High Signal-to-Noise Ratio**
-
-Every sentence must carry information weight. LLMs consume precise, dense content efficiently.
-
-**Anti-Patterns (Eliminate These):**
-- ❌ "The system will allow users to..." → ✅ "Users can..."
-- ❌ "It is important to note that..." → ✅ State the fact directly
-- ❌ "In order to..." → ✅ "To..."
-- ❌ Conversational filler and padding → ✅ Direct, concise statements
-
-**Goal:** Maximum information per word. Zero fluff.
-
----
-
-## The Traceability Chain
-
-**PRD starts the chain:**
-```
-Vision → Success Criteria → User Journeys → Functional Requirements → (future: User Stories)
-```
-
-**In the PRD, establish:**
-- Vision → Success Criteria alignment
-- Success Criteria → User Journey coverage
-- User Journey → Functional Requirement mapping
-- All requirements traceable to user needs
-
-**Why:** Each downstream artifact (UX, Architecture, Epics, Stories) must trace back to documented user needs and business objectives. This chain ensures we build the right thing.
-
----
-
-## What Makes Great Functional Requirements?
-
-### FRs are Capabilities, Not Implementation
-
-**Good FR:** "Users can reset their password via email link"
-**Bad FR:** "System sends JWT via email and validates with database" (implementation leakage)
-
-**Good FR:** "Dashboard loads in under 2 seconds for 95th percentile"
-**Bad FR:** "Fast loading time" (subjective, unmeasurable)
-
-### SMART Quality Criteria
-
-**Specific:** Clear, precisely defined capability
-**Measurable:** Quantifiable with test criteria
-**Attainable:** Realistic within constraints
-**Relevant:** Aligns with business objectives
-**Traceable:** Links to source (executive summary or user journey)
-
-### FR Anti-Patterns
-
-**Subjective Adjectives:**
-- ❌ "easy to use", "intuitive", "user-friendly", "fast", "responsive"
-- ✅ Use metrics: "completes task in under 3 clicks", "loads in under 2 seconds"
-
-**Implementation Leakage:**
-- ❌ Technology names, specific libraries, implementation details
-- ✅ Focus on capability and measurable outcomes
-
-**Vague Quantifiers:**
-- ❌ "multiple users", "several options", "various formats"
-- ✅ "up to 100 concurrent users", "3-5 options", "PDF, DOCX, TXT formats"
-
-**Missing Test Criteria:**
-- ❌ "The system shall provide notifications"
-- ✅ "The system shall send email notifications within 30 seconds of trigger event"
-
----
-
-## What Makes Great Non-Functional Requirements?
-
-### NFRs Must Be Measurable
-
-**Template:**
-```
-"The system shall [metric] [condition] [measurement method]"
-```
-
-**Examples:**
-- ✅ "The system shall respond to API requests in under 200ms for 95th percentile as measured by APM monitoring"
-- ✅ "The system shall maintain 99.9% uptime during business hours as measured by cloud provider SLA"
-- ✅ "The system shall support 10,000 concurrent users as measured by load testing"
-
-### NFR Anti-Patterns
-
-**Unmeasurable Claims:**
-- ❌ "The system shall be scalable" → ✅ "The system shall handle 10x load growth through horizontal scaling"
-- ❌ "High availability required" → ✅ "99.9% uptime as measured by cloud provider SLA"
-
-**Missing Context:**
-- ❌ "Response time under 1 second" → ✅ "API response time under 1 second for 95th percentile under normal load"
-
----
-
-## Domain-Specific Requirements
-
-**Auto-Detect and Enforce Based on Project Context**
-
-Certain industries have mandatory requirements that must be present:
-
-- **Healthcare:** HIPAA Privacy & Security Rules, PHI encryption, audit logging, MFA
-- **Fintech:** PCI-DSS Level 1, AML/KYC compliance, SOX controls, financial audit trails
-- **GovTech:** NIST framework, Section 508 accessibility (WCAG 2.1 AA), FedRAMP, data residency
-- **E-Commerce:** PCI-DSS for payments, inventory accuracy, tax calculation by jurisdiction
-
-**Why:** Missing these requirements in the PRD means they'll be missed in architecture and implementation, creating expensive rework. During PRD creation there is a step to cover this - during validation we want to make sure it was covered. For this purpose steps will utilize a domain-complexity.csv and project-types.csv.
-
----
-
-## Document Structure (Markdown, Human-Readable)
-
-### Required Sections
-1. **Executive Summary** - Vision, differentiator, target users
-2. **Success Criteria** - Measurable outcomes (SMART)
-3. **Product Scope** - MVP, Growth, Vision phases
-4. **User Journeys** - Comprehensive coverage
-5. **Domain Requirements** - Industry-specific compliance (if applicable)
-6. **Innovation Analysis** - Competitive differentiation (if applicable)
-7. **Project-Type Requirements** - Platform-specific needs
-8. **Functional Requirements** - Capability contract (FRs)
-9. **Non-Functional Requirements** - Quality attributes (NFRs)
-
-### Formatting for Dual Consumption
-
-**For Humans:**
-- Clear, professional language
-- Logical flow from vision to requirements
-- Easy for stakeholders to review and approve
-
-**For LLMs:**
-- ## Level 2 headers for all main sections (enables extraction)
-- Consistent structure and patterns
-- Precise, testable language
-- High information density
-
----
-
-## Downstream Impact
-
-**How the PRD Feeds Next Artifacts:**
-
-**UX Design:**
-- User journeys → interaction flows
-- FRs → design requirements
-- Success criteria → UX metrics
-
-**Architecture:**
-- FRs → system capabilities
-- NFRs → architecture decisions
-- Domain requirements → compliance architecture
-- Project-type requirements → platform choices
-
-**Epics & Stories (created after architecture):**
-- FRs → user stories (1 FR could map to 1-3 stories potentially)
-- Acceptance criteria → story acceptance tests
-- Priority → sprint sequencing
-- Traceability → stories map back to vision
-
-**Development AI Agents:**
-- Precise requirements → implementation clarity
-- Test criteria → automated test generation
-- Domain requirements → compliance enforcement
-- Measurable NFRs → performance targets
-
----
-
-## Summary: What Makes a Great BMAD PRD?
-
-✅ **High Information Density** - Every sentence carries weight, zero fluff
-✅ **Measurable Requirements** - All FRs and NFRs are testable with specific criteria
-✅ **Clear Traceability** - Each requirement links to user need and business objective
-✅ **Domain Awareness** - Industry-specific requirements auto-detected and included
-✅ **Zero Anti-Patterns** - No subjective adjectives, implementation leakage, or vague quantifiers
-✅ **Dual Audience Optimized** - Human-readable AND LLM-consumable
-✅ **Markdown Format** - Professional, clean, accessible to all stakeholders
-
----
-
-**Remember:** The PRD is the foundation. Quality here ripples through every subsequent phase. A dense, precise, well-traced PRD makes UX design, architecture, epic breakdown, and AI development dramatically more effective.

src/bmm/workflows/2-plan-workflows/bmad-validate-prd/data/project-types.csv

@@ -1,11 +0,0 @@
-project_type,detection_signals,key_questions,required_sections,skip_sections,web_search_triggers,innovation_signals
-api_backend,"API,REST,GraphQL,backend,service,endpoints","Endpoints needed?;Authentication method?;Data formats?;Rate limits?;Versioning?;SDK needed?","endpoint_specs;auth_model;data_schemas;error_codes;rate_limits;api_docs","ux_ui;visual_design;user_journeys","framework best practices;OpenAPI standards","API composition;New protocol"
-mobile_app,"iOS,Android,app,mobile,iPhone,iPad","Native or cross-platform?;Offline needed?;Push notifications?;Device features?;Store compliance?","platform_reqs;device_permissions;offline_mode;push_strategy;store_compliance","desktop_features;cli_commands","app store guidelines;platform requirements","Gesture innovation;AR/VR features"
-saas_b2b,"SaaS,B2B,platform,dashboard,teams,enterprise","Multi-tenant?;Permission model?;Subscription tiers?;Integrations?;Compliance?","tenant_model;rbac_matrix;subscription_tiers;integration_list;compliance_reqs","cli_interface;mobile_first","compliance requirements;integration guides","Workflow automation;AI agents"
-developer_tool,"SDK,library,package,npm,pip,framework","Language support?;Package managers?;IDE integration?;Documentation?;Examples?","language_matrix;installation_methods;api_surface;code_examples;migration_guide","visual_design;store_compliance","package manager best practices;API design patterns","New paradigm;DSL creation"
-cli_tool,"CLI,command,terminal,bash,script","Interactive or scriptable?;Output formats?;Config method?;Shell completion?","command_structure;output_formats;config_schema;scripting_support","visual_design;ux_principles;touch_interactions","CLI design patterns;shell integration","Natural language CLI;AI commands"
-web_app,"website,webapp,browser,SPA,PWA","SPA or MPA?;Browser support?;SEO needed?;Real-time?;Accessibility?","browser_matrix;responsive_design;performance_targets;seo_strategy;accessibility_level","native_features;cli_commands","web standards;WCAG guidelines","New interaction;WebAssembly use"
-game,"game,player,gameplay,level,character","REDIRECT TO USE THE BMad Method Game Module Agent and Workflows - HALT","game-brief;GDD","most_sections","game design patterns","Novel mechanics;Genre mixing"
-desktop_app,"desktop,Windows,Mac,Linux,native","Cross-platform?;Auto-update?;System integration?;Offline?","platform_support;system_integration;update_strategy;offline_capabilities","web_seo;mobile_features","desktop guidelines;platform requirements","Desktop AI;System automation"
-iot_embedded,"IoT,embedded,device,sensor,hardware","Hardware specs?;Connectivity?;Power constraints?;Security?;OTA updates?","hardware_reqs;connectivity_protocol;power_profile;security_model;update_mechanism","visual_ui;browser_support","IoT standards;protocol specs","Edge AI;New sensors"
-blockchain_web3,"blockchain,crypto,DeFi,NFT,smart contract","Chain selection?;Wallet integration?;Gas optimization?;Security audit?","chain_specs;wallet_support;smart_contracts;security_audit;gas_optimization","traditional_auth;centralized_db","blockchain standards;security patterns","Novel tokenomics;DAO structure"

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

@@ -1,226 +0,0 @@
----
-name: 'step-v-01-discovery'
-description: 'Document Discovery & Confirmation - Handle fresh context validation, confirm PRD path, discover input documents'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-02-format-detection.md'
-advancedElicitationTask: 'skill:bmad-advanced-elicitation'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
-prdPurpose: '../data/prd-purpose.md'
----
-
-# Step 1: Document Discovery & Confirmation
-
-## STEP GOAL:
-
-Handle fresh context validation by confirming PRD path, discovering and loading input documents from frontmatter, and initializing the validation report.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring systematic validation expertise and analytical rigor
-- ✅ User brings domain knowledge and specific PRD context
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on discovering PRD and input documents, not validating yet
-- 🚫 FORBIDDEN to perform any validation checks in this step
-- 💬 Approach: Systematic discovery with clear reporting to user
-- 🚪 This is the setup step - get everything ready for validation
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Discover and confirm PRD to validate
-- 💾 Load PRD and all input documents from frontmatter
-- 📖 Initialize validation report next to PRD
-- 🚫 FORBIDDEN to load next step until user confirms setup
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD path (user-specified or discovered), workflow configuration
-- Focus: Document discovery and setup only
-- Limits: Don't perform validation, don't skip discovery
-- Dependencies: Configuration loaded from PRD workflow.md initialization
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load PRD Purpose and Standards
-
-Load and read the complete file at:
-`{prdPurpose}`
-
-This file contains the BMAD PRD philosophy, standards, and validation criteria that will guide all validation checks. Internalize this understanding - it defines what makes a great BMAD PRD.
-
-### 2. Discover PRD to Validate
-
-**If PRD path provided as invocation parameter:**
-- Use provided path
-
-**If no PRD path provided, auto-discover:**
-- Search `{planning_artifacts}` for files matching `*prd*.md`
-- Also check for sharded PRDs: `{planning_artifacts}/*prd*/*.md`
-
-**If exactly ONE PRD found:**
-- Use it automatically
-- Inform user: "Found PRD: {discovered_path} — using it for validation."
-
-**If MULTIPLE PRDs found:**
-- List all discovered PRDs with numbered options
-- "I found multiple PRDs. Which one would you like to validate?"
-- Wait for user selection
-
-**If NO PRDs found:**
-- "I couldn't find any PRD files in {planning_artifacts}. Please provide the path to the PRD file you want to validate."
-- Wait for user to provide PRD path.
-
-### 3. Validate PRD Exists and Load
-
-Once PRD path is provided:
-
-- Check if PRD file exists at specified path
-- If not found: "I cannot find a PRD at that path. Please check the path and try again."
-- If found: Load the complete PRD file including frontmatter
-
-### 4. Extract Frontmatter and Input Documents
-
-From the loaded PRD frontmatter, extract:
-
-- `inputDocuments: []` array (if present)
-- Any other relevant metadata (classification, date, etc.)
-
-**If no inputDocuments array exists:**
-Note this and proceed with PRD-only validation
-
-### 5. Load Input Documents
-
-For each document listed in `inputDocuments`:
-
-- Attempt to load the document
-- Track successfully loaded documents
-- Note any documents that fail to load
-
-**Build list of loaded input documents:**
-- Product Brief (if present)
-- Research documents (if present)
-- Other reference materials (if present)
-
-### 6. Ask About Additional Reference Documents
-
-"**I've loaded the following documents from your PRD frontmatter:**
-
-{list loaded documents with file names}
-
-**Are there any additional reference documents you'd like me to include in this validation?**
-
-These could include:
-- Additional research or context documents
-- Project documentation not tracked in frontmatter
-- Standards or compliance documents
-- Competitive analysis or benchmarks
-
-Please provide paths to any additional documents, or type 'none' to proceed."
-
-**Load any additional documents provided by user.**
-
-### 7. Initialize Validation Report
-
-Create validation report at: `{validationReportPath}`
-
-**Initialize with frontmatter:**
-```yaml
----
-validationTarget: '{prd_path}'
-validationDate: '{current_date}'
-inputDocuments: [list of all loaded documents]
-validationStepsCompleted: []
-validationStatus: IN_PROGRESS
----
-```
-
-**Initial content:**
-```markdown
-# PRD Validation Report
-
-**PRD Being Validated:** {prd_path}
-**Validation Date:** {current_date}
-
-## Input Documents
-
-{list all documents loaded for validation}
-
-## Validation Findings
-
-[Findings will be appended as validation progresses]
-```
-
-### 8. Present Discovery Summary
-
-"**Setup Complete!**
-
-**PRD to Validate:** {prd_path}
-
-**Input Documents Loaded:**
-- PRD: {prd_name} ✓
-- Product Brief: {count} {if count > 0}✓{else}(none found){/if}
-- Research: {count} {if count > 0}✓{else}(none found){/if}
-- Additional References: {count} {if count > 0}✓{else}(none){/if}
-
-**Validation Report:** {validationReportPath}
-
-**Ready to begin validation.**"
-
-### 9. Present MENU OPTIONS
-
-Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Format Detection
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- User can ask questions or add more documents - always respond and redisplay menu
-
-#### Menu Handling Logic:
-
-- IF A: Read fully and follow: {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Read fully and follow: {partyModeWorkflow}, and when finished redisplay the menu
-- IF C: Read fully and follow: {nextStepFile} to begin format detection
-- IF user provides additional document: Load it, update report, redisplay summary
-- IF Any other: help user, then redisplay menu
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- PRD path discovered and confirmed
-- PRD file exists and loads successfully
-- All input documents from frontmatter loaded
-- Additional reference documents (if any) loaded
-- Validation report initialized next to PRD
-- User clearly informed of setup status
-- Menu presented and user input handled correctly
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding with non-existent PRD file
-- Not loading input documents from frontmatter
-- Creating validation report in wrong location
-- Proceeding without user confirming setup
-- Not handling missing input documents gracefully
-
-**Master Rule:** Complete discovery and setup BEFORE validation. This step ensures everything is in place for systematic validation checks.

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

@@ -1,191 +0,0 @@
----
-name: 'step-v-02-format-detection'
-description: 'Format Detection & Structure Analysis - Classify PRD format and route appropriately'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-03-density-validation.md'
-altStepFile: './step-v-02b-parity-check.md'
-prdFile: '{prd_file_path}'
-validationReportPath: '{validation_report_path}'
----
-
-# Step 2: Format Detection & Structure Analysis
-
-## STEP GOAL:
-
-Detect if PRD follows BMAD format and route appropriately - classify as BMAD Standard / BMAD Variant / Non-Standard, with optional parity check for non-standard formats.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring systematic validation expertise and pattern recognition
-- ✅ User brings domain knowledge and PRD context
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on detecting format and classifying structure
-- 🚫 FORBIDDEN to perform other validation checks in this step
-- 💬 Approach: Analytical and systematic, clear reporting of findings
-- 🚪 This is a branch step - may route to parity check for non-standard PRDs
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Analyze PRD structure systematically
-- 💾 Append format findings to validation report
-- 📖 Route appropriately based on format classification
-- 🚫 FORBIDDEN to skip format detection or proceed without classification
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file loaded in step 1, validation report initialized
-- Focus: Format detection and classification only
-- Limits: Don't perform other validation, don't skip classification
-- Dependencies: Step 1 completed - PRD loaded and report initialized
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Extract PRD Structure
-
-Load the complete PRD file and extract:
-
-**All Level 2 (##) headers:**
-- Scan through entire PRD document
-- Extract all ## section headers
-- List them in order
-
-**PRD frontmatter:**
-- Extract classification.domain if present
-- Extract classification.projectType if present
-- Note any other relevant metadata
-
-### 2. Check for BMAD PRD Core Sections
-
-Check if the PRD contains the following BMAD PRD core sections:
-
-1. **Executive Summary** (or variations: ## Executive Summary, ## Overview, ## Introduction)
-2. **Success Criteria** (or: ## Success Criteria, ## Goals, ## Objectives)
-3. **Product Scope** (or: ## Product Scope, ## Scope, ## In Scope, ## Out of Scope)
-4. **User Journeys** (or: ## User Journeys, ## User Stories, ## User Flows)
-5. **Functional Requirements** (or: ## Functional Requirements, ## Features, ## Capabilities)
-6. **Non-Functional Requirements** (or: ## Non-Functional Requirements, ## NFRs, ## Quality Attributes)
-
-**Count matches:**
-- How many of these 6 core sections are present?
-- Which specific sections are present?
-- Which are missing?
-
-### 3. Classify PRD Format
-
-Based on core section count, classify:
-
-**BMAD Standard:**
-- 5-6 core sections present
-- Follows BMAD PRD structure closely
-
-**BMAD Variant:**
-- 3-4 core sections present
-- Generally follows BMAD patterns but may have structural differences
-- Missing some sections but recognizable as BMAD-style
-
-**Non-Standard:**
-- Fewer than 3 core sections present
-- Does not follow BMAD PRD structure
-- May be completely custom format, legacy format, or from another framework
-
-### 4. Report Format Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## Format Detection
-
-**PRD Structure:**
-[List all ## Level 2 headers found]
-
-**BMAD Core Sections Present:**
-- Executive Summary: [Present/Missing]
-- Success Criteria: [Present/Missing]
-- Product Scope: [Present/Missing]
-- User Journeys: [Present/Missing]
-- Functional Requirements: [Present/Missing]
-- Non-Functional Requirements: [Present/Missing]
-
-**Format Classification:** [BMAD Standard / BMAD Variant / Non-Standard]
-**Core Sections Present:** [count]/6
-```
-
-### 5. Route Based on Format Classification
-
-**IF format is BMAD Standard or BMAD Variant:**
-
-Display: "**Format Detected:** {classification}
-
-Proceeding to systematic validation checks..."
-
-Without delay, read fully and follow: {nextStepFile} (step-v-03-density-validation.md)
-
-**IF format is Non-Standard (< 3 core sections):**
-
-Display: "**Format Detected:** Non-Standard PRD
-
-This PRD does not follow BMAD standard structure (only {count}/6 core sections present).
-
-You have options:"
-
-Present MENU OPTIONS below for user selection
-
-### 6. Present MENU OPTIONS (Non-Standard PRDs Only)
-
-**[A] Parity Check** - Analyze gaps and estimate effort to reach BMAD PRD parity
-**[B] Validate As-Is** - Proceed with validation using current structure
-**[C] Exit** - Exit validation and review format findings
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input
-- Only proceed based on user selection
-
-#### Menu Handling Logic:
-
-- IF A (Parity Check): Read fully and follow: {altStepFile} (step-v-02b-parity-check.md)
-- IF B (Validate As-Is): Display "Proceeding with validation..." then read fully and follow: {nextStepFile}
-- IF C (Exit): Display format findings summary and exit validation
-- IF Any other: help user respond, then redisplay menu
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All ## Level 2 headers extracted successfully
-- BMAD core sections checked systematically
-- Format classified correctly based on section count
-- Findings reported to validation report
-- BMAD Standard/Variant PRDs proceed directly to next validation step
-- Non-Standard PRDs pause and present options to user
-- User can choose parity check, validate as-is, or exit
-
-### ❌ SYSTEM FAILURE:
-
-- Not extracting all headers before classification
-- Incorrect format classification
-- Not reporting findings to validation report
-- Not pausing for non-standard PRDs
-- Proceeding without user decision for non-standard formats
-
-**Master Rule:** Format detection determines validation path. Non-standard PRDs require user choice before proceeding.

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

@@ -1,209 +0,0 @@
----
-name: 'step-v-02b-parity-check'
-description: 'Document Parity Check - Analyze non-standard PRD and identify gaps to achieve BMAD PRD parity'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-03-density-validation.md'
-prdFile: '{prd_file_path}'
-validationReportPath: '{validation_report_path}'
----
-
-# Step 2B: Document Parity Check
-
-## STEP GOAL:
-
-Analyze non-standard PRD and identify gaps to achieve BMAD PRD parity, presenting user with options for how to proceed.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring BMAD PRD standards expertise and gap analysis
-- ✅ User brings domain knowledge and PRD context
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on analyzing gaps and estimating parity effort
-- 🚫 FORBIDDEN to perform other validation checks in this step
-- 💬 Approach: Systematic gap analysis with clear recommendations
-- 🚪 This is an optional branch step - user chooses next action
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Analyze each BMAD PRD section for gaps
-- 💾 Append parity analysis to validation report
-- 📖 Present options and await user decision
-- 🚫 FORBIDDEN to proceed without user selection
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Non-standard PRD from step 2, validation report in progress
-- Focus: Parity analysis only - what's missing, what's needed
-- Limits: Don't perform validation checks, don't auto-proceed
-- Dependencies: Step 2 classified PRD as non-standard and user chose parity check
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Analyze Each BMAD PRD Section
-
-For each of the 6 BMAD PRD core sections, analyze:
-
-**Executive Summary:**
-- Does PRD have vision/overview?
-- Is problem statement clear?
-- Are target users identified?
-- Gap: [What's missing or incomplete]
-
-**Success Criteria:**
-- Are measurable goals defined?
-- Is success clearly defined?
-- Gap: [What's missing or incomplete]
-
-**Product Scope:**
-- Is scope clearly defined?
-- Are in-scope items listed?
-- Are out-of-scope items listed?
-- Gap: [What's missing or incomplete]
-
-**User Journeys:**
-- Are user types/personas identified?
-- Are user flows documented?
-- Gap: [What's missing or incomplete]
-
-**Functional Requirements:**
-- Are features/capabilities listed?
-- Are requirements structured?
-- Gap: [What's missing or incomplete]
-
-**Non-Functional Requirements:**
-- Are quality attributes defined?
-- Are performance/security/etc. requirements documented?
-- Gap: [What's missing or incomplete]
-
-### 2. Estimate Effort to Reach Parity
-
-For each missing or incomplete section, estimate:
-
-**Effort Level:**
-- Minimal - Section exists but needs minor enhancements
-- Moderate - Section missing but content exists elsewhere in PRD
-- Significant - Section missing, requires new content creation
-
-**Total Parity Effort:**
-- Based on individual section estimates
-- Classify overall: Quick / Moderate / Substantial effort
-
-### 3. Report Parity Analysis to Validation Report
-
-Append to validation report:
-
-```markdown
-## Parity Analysis (Non-Standard PRD)
-
-### Section-by-Section Gap Analysis
-
-**Executive Summary:**
-- Status: [Present/Missing/Incomplete]
-- Gap: [specific gap description]
-- Effort to Complete: [Minimal/Moderate/Significant]
-
-**Success Criteria:**
-- Status: [Present/Missing/Incomplete]
-- Gap: [specific gap description]
-- Effort to Complete: [Minimal/Moderate/Significant]
-
-**Product Scope:**
-- Status: [Present/Missing/Incomplete]
-- Gap: [specific gap description]
-- Effort to Complete: [Minimal/Moderate/Significant]
-
-**User Journeys:**
-- Status: [Present/Missing/Incomplete]
-- Gap: [specific gap description]
-- Effort to Complete: [Minimal/Moderate/Significant]
-
-**Functional Requirements:**
-- Status: [Present/Missing/Incomplete]
-- Gap: [specific gap description]
-- Effort to Complete: [Minimal/Moderate/Significant]
-
-**Non-Functional Requirements:**
-- Status: [Present/Missing/Incomplete]
-- Gap: [specific gap description]
-- Effort to Complete: [Minimal/Moderate/Significant]
-
-### Overall Parity Assessment
-
-**Overall Effort to Reach BMAD Standard:** [Quick/Moderate/Substantial]
-**Recommendation:** [Brief recommendation based on analysis]
-```
-
-### 4. Present Parity Analysis and Options
-
-Display:
-
-"**Parity Analysis Complete**
-
-Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to reach BMAD standard is: **{effort level}**
-
-**Quick Summary:**
-[2-3 sentence summary of key gaps]
-
-**Recommendation:**
-{recommendation from analysis}
-
-**How would you like to proceed?**"
-
-### 5. Present MENU OPTIONS
-
-**[C] Continue Validation** - Proceed with validation using current structure
-**[E] Exit & Review** - Exit validation and review parity report
-**[S] Save & Exit** - Save parity report and exit
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input
-- Only proceed based on user selection
-
-#### Menu Handling Logic:
-
-- IF C (Continue): Display "Proceeding with validation..." then read fully and follow: {nextStepFile}
-- IF E (Exit): Display parity summary and exit validation
-- IF S (Save): Confirm saved, display summary, exit
-- IF Any other: help user respond, then redisplay menu
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All 6 BMAD PRD sections analyzed for gaps
-- Effort estimates provided for each gap
-- Overall parity effort assessed correctly
-- Parity analysis reported to validation report
-- Clear summary presented to user
-- User can choose to continue validation, exit, or save report
-
-### ❌ SYSTEM FAILURE:
-
-- Not analyzing all 6 sections systematically
-- Missing effort estimates
-- Not reporting parity analysis to validation report
-- Auto-proceeding without user decision
-- Unclear recommendations
-
-**Master Rule:** Parity check informs user of gaps and effort, but user decides whether to proceed with validation or address gaps first.

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

@@ -1,174 +0,0 @@
----
-name: 'step-v-03-density-validation'
-description: 'Information Density Check - Scan for anti-patterns that violate information density principles'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-04-brief-coverage-validation.md'
-prdFile: '{prd_file_path}'
-validationReportPath: '{validation_report_path}'
----
-
-# Step 3: Information Density Validation
-
-## STEP GOAL:
-
-Validate PRD meets BMAD information density standards by scanning for conversational filler, wordy phrases, and redundant expressions that violate conciseness principles.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring analytical rigor and attention to detail
-- ✅ This step runs autonomously - no user input needed
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on information density anti-patterns
-- 🚫 FORBIDDEN to validate other aspects in this step
-- 💬 Approach: Systematic scanning and categorization
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Scan PRD for density anti-patterns systematically
-- 💾 Append density findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file, validation report with format findings
-- Focus: Information density validation only
-- Limits: Don't validate other aspects, don't pause for user input
-- Dependencies: Step 2 completed - format classification done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Attempt Sub-Process Validation
-
-**Try to use Task tool to spawn a subprocess:**
-
-"Perform information density validation on this PRD:
-
-1. Load the PRD file
-2. Scan for the following anti-patterns:
-   - Conversational filler phrases (examples: 'The system will allow users to...', 'It is important to note that...', 'In order to')
-   - Wordy phrases (examples: 'Due to the fact that', 'In the event of', 'For the purpose of')
-   - Redundant phrases (examples: 'Future plans', 'Absolutely essential', 'Past history')
-3. Count violations by category with line numbers
-4. Classify severity: Critical (>10 violations), Warning (5-10), Pass (<5)
-
-Return structured findings with counts and examples."
-
-### 2. Graceful Degradation (if Task tool unavailable)
-
-If Task tool unavailable, perform analysis directly:
-
-**Scan for conversational filler patterns:**
-- "The system will allow users to..."
-- "It is important to note that..."
-- "In order to"
-- "For the purpose of"
-- "With regard to"
-- Count occurrences and note line numbers
-
-**Scan for wordy phrases:**
-- "Due to the fact that" (use "because")
-- "In the event of" (use "if")
-- "At this point in time" (use "now")
-- "In a manner that" (use "how")
-- Count occurrences and note line numbers
-
-**Scan for redundant phrases:**
-- "Future plans" (just "plans")
-- "Past history" (just "history")
-- "Absolutely essential" (just "essential")
-- "Completely finish" (just "finish")
-- Count occurrences and note line numbers
-
-### 3. Classify Severity
-
-**Calculate total violations:**
-- Conversational filler count
-- Wordy phrases count
-- Redundant phrases count
-- Total = sum of all categories
-
-**Determine severity:**
-- **Critical:** Total > 10 violations
-- **Warning:** Total 5-10 violations
-- **Pass:** Total < 5 violations
-
-### 4. Report Density Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## Information Density Validation
-
-**Anti-Pattern Violations:**
-
-**Conversational Filler:** {count} occurrences
-[If count > 0, list examples with line numbers]
-
-**Wordy Phrases:** {count} occurrences
-[If count > 0, list examples with line numbers]
-
-**Redundant Phrases:** {count} occurrences
-[If count > 0, list examples with line numbers]
-
-**Total Violations:** {total}
-
-**Severity Assessment:** [Critical/Warning/Pass]
-
-**Recommendation:**
-[If Critical] "PRD requires significant revision to improve information density. Every sentence should carry weight without filler."
-[If Warning] "PRD would benefit from reducing wordiness and eliminating filler phrases."
-[If Pass] "PRD demonstrates good information density with minimal violations."
-```
-
-### 5. Display Progress and Auto-Proceed
-
-Display: "**Information Density Validation Complete**
-
-Severity: {Critical/Warning/Pass}
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-04-brief-coverage-validation.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- PRD scanned for all three anti-pattern categories
-- Violations counted with line numbers
-- Severity classified correctly
-- Findings reported to validation report
-- Auto-proceeds to next validation step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not scanning all anti-pattern categories
-- Missing severity classification
-- Not reporting findings to validation report
-- Pausing for user input (should auto-proceed)
-- Not attempting subprocess architecture
-
-**Master Rule:** Information density validation runs autonomously. Scan, classify, report, auto-proceed. No user interaction needed.

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

@@ -1,214 +0,0 @@
----
-name: 'step-v-04-brief-coverage-validation'
-description: 'Product Brief Coverage Check - Validate PRD covers all content from Product Brief (if used as input)'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-05-measurability-validation.md'
-prdFile: '{prd_file_path}'
-productBrief: '{product_brief_path}'
-validationReportPath: '{validation_report_path}'
----
-
-# Step 4: Product Brief Coverage Validation
-
-## STEP GOAL:
-
-Validate that PRD covers all content from Product Brief (if brief was used as input), mapping brief content to PRD sections and identifying gaps.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring analytical rigor and traceability expertise
-- ✅ This step runs autonomously - no user input needed
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on Product Brief coverage (conditional on brief existence)
-- 🚫 FORBIDDEN to validate other aspects in this step
-- 💬 Approach: Systematic mapping and gap analysis
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Check if Product Brief exists in input documents
-- 💬 If no brief: Skip this check and report "N/A - No Product Brief"
-- 🎯 If brief exists: Map brief content to PRD sections
-- 💾 Append coverage findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file, input documents from step 1, validation report
-- Focus: Product Brief coverage only (conditional)
-- Limits: Don't validate other aspects, conditional execution
-- Dependencies: Step 1 completed - input documents loaded
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Check for Product Brief
-
-Check if Product Brief was loaded in step 1's inputDocuments:
-
-**IF no Product Brief found:**
-Append to validation report:
-```markdown
-## Product Brief Coverage
-
-**Status:** N/A - No Product Brief was provided as input
-```
-
-Display: "**Product Brief Coverage: Skipped** (No Product Brief provided)
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile}
-
-**IF Product Brief exists:** Continue to step 2 below
-
-### 2. Attempt Sub-Process Validation
-
-**Try to use Task tool to spawn a subprocess:**
-
-"Perform Product Brief coverage validation:
-
-1. Load the Product Brief
-2. Extract key content:
-   - Vision statement
-   - Target users/personas
-   - Problem statement
-   - Key features
-   - Goals/objectives
-   - Differentiators
-   - Constraints
-3. For each item, search PRD for corresponding coverage
-4. Classify coverage: Fully Covered / Partially Covered / Not Found / Intentionally Excluded
-5. Note any gaps with severity: Critical / Moderate / Informational
-
-Return structured coverage map with classifications."
-
-### 3. Graceful Degradation (if Task tool unavailable)
-
-If Task tool unavailable, perform analysis directly:
-
-**Extract from Product Brief:**
-- Vision: What is this product?
-- Users: Who is it for?
-- Problem: What problem does it solve?
-- Features: What are the key capabilities?
-- Goals: What are the success criteria?
-- Differentiators: What makes it unique?
-
-**For each item, search PRD:**
-- Scan Executive Summary for vision
-- Check User Journeys or user personas
-- Look for problem statement
-- Review Functional Requirements for features
-- Check Success Criteria section
-- Search for differentiators
-
-**Classify coverage:**
-- **Fully Covered:** Content present and complete
-- **Partially Covered:** Content present but incomplete
-- **Not Found:** Content missing from PRD
-- **Intentionally Excluded:** Content explicitly out of scope
-
-### 4. Assess Coverage and Severity
-
-**For each gap (Partially Covered or Not Found):**
-- Is this Critical? (Core vision, primary users, main features)
-- Is this Moderate? (Secondary features, some goals)
-- Is this Informational? (Nice-to-have features, minor details)
-
-**Note:** Some exclusions may be intentional (valid scoping decisions)
-
-### 5. Report Coverage Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## Product Brief Coverage
-
-**Product Brief:** {brief_file_name}
-
-### Coverage Map
-
-**Vision Statement:** [Fully/Partially/Not Found/Intentionally Excluded]
-[If gap: Note severity and specific missing content]
-
-**Target Users:** [Fully/Partially/Not Found/Intentionally Excluded]
-[If gap: Note severity and specific missing content]
-
-**Problem Statement:** [Fully/Partially/Not Found/Intentionally Excluded]
-[If gap: Note severity and specific missing content]
-
-**Key Features:** [Fully/Partially/Not Found/Intentionally Excluded]
-[If gap: List specific features with severity]
-
-**Goals/Objectives:** [Fully/Partially/Not Found/Intentionally Excluded]
-[If gap: Note severity and specific missing content]
-
-**Differentiators:** [Fully/Partially/Not Found/Intentionally Excluded]
-[If gap: Note severity and specific missing content]
-
-### Coverage Summary
-
-**Overall Coverage:** [percentage or qualitative assessment]
-**Critical Gaps:** [count] [list if any]
-**Moderate Gaps:** [count] [list if any]
-**Informational Gaps:** [count] [list if any]
-
-**Recommendation:**
-[If critical gaps exist] "PRD should be revised to cover critical Product Brief content."
-[If moderate gaps] "Consider addressing moderate gaps for complete coverage."
-[If minimal gaps] "PRD provides good coverage of Product Brief content."
-```
-
-### 6. Display Progress and Auto-Proceed
-
-Display: "**Product Brief Coverage Validation Complete**
-
-Overall Coverage: {assessment}
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-05-measurability-validation.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Checked for Product Brief existence correctly
-- If no brief: Reported "N/A" and skipped gracefully
-- If brief exists: Mapped all key brief content to PRD sections
-- Coverage classified appropriately (Fully/Partially/Not Found/Intentionally Excluded)
-- Severity assessed for gaps (Critical/Moderate/Informational)
-- Findings reported to validation report
-- Auto-proceeds to next validation step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not checking for brief existence before attempting validation
-- If brief exists: not mapping all key content areas
-- Missing coverage classifications
-- Not reporting findings to validation report
-- Not auto-proceeding
-
-**Master Rule:** Product Brief coverage is conditional - skip if no brief, validate thoroughly if brief exists. Always auto-proceed.

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

@@ -1,228 +0,0 @@
----
-name: 'step-v-05-measurability-validation'
-description: 'Measurability Validation - Validate that all requirements (FRs and NFRs) are measurable and testable'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-06-traceability-validation.md'
-prdFile: '{prd_file_path}'
-validationReportPath: '{validation_report_path}'
----
-
-# Step 5: Measurability Validation
-
-## STEP GOAL:
-
-Validate that all Functional Requirements (FRs) and Non-Functional Requirements (NFRs) are measurable, testable, and follow proper format without implementation details.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring analytical rigor and requirements engineering expertise
-- ✅ This step runs autonomously - no user input needed
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on FR and NFR measurability
-- 🚫 FORBIDDEN to validate other aspects in this step
-- 💬 Approach: Systematic requirement-by-requirement analysis
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Extract all FRs and NFRs from PRD
-- 💾 Validate each for measurability and format
-- 📖 Append findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file, validation report
-- Focus: FR and NFR measurability only
-- Limits: Don't validate other aspects, don't pause for user input
-- Dependencies: Steps 2-4 completed - initial validation checks done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Attempt Sub-Process Validation
-
-**Try to use Task tool to spawn a subprocess:**
-
-"Perform measurability validation on this PRD:
-
-**Functional Requirements (FRs):**
-1. Extract all FRs from Functional Requirements section
-2. Check each FR for:
-   - '[Actor] can [capability]' format compliance
-   - No subjective adjectives (easy, fast, simple, intuitive, etc.)
-   - No vague quantifiers (multiple, several, some, many, etc.)
-   - No implementation details (technology names, library names, data structures unless capability-relevant)
-3. Document violations with line numbers
-
-**Non-Functional Requirements (NFRs):**
-1. Extract all NFRs from Non-Functional Requirements section
-2. Check each NFR for:
-   - Specific metrics with measurement methods
-   - Template compliance (criterion, metric, measurement method, context)
-   - Context included (why this matters, who it affects)
-3. Document violations with line numbers
-
-Return structured findings with violation counts and examples."
-
-### 2. Graceful Degradation (if Task tool unavailable)
-
-If Task tool unavailable, perform analysis directly:
-
-**Functional Requirements Analysis:**
-
-Extract all FRs and check each for:
-
-**Format compliance:**
-- Does it follow "[Actor] can [capability]" pattern?
-- Is actor clearly defined?
-- Is capability actionable and testable?
-
-**No subjective adjectives:**
-- Scan for: easy, fast, simple, intuitive, user-friendly, responsive, quick, efficient (without metrics)
-- Note line numbers
-
-**No vague quantifiers:**
-- Scan for: multiple, several, some, many, few, various, number of
-- Note line numbers
-
-**No implementation details:**
-- Scan for: React, Vue, Angular, PostgreSQL, MongoDB, AWS, Docker, Kubernetes, Redux, etc.
-- Unless capability-relevant (e.g., "API consumers can access...")
-- Note line numbers
-
-**Non-Functional Requirements Analysis:**
-
-Extract all NFRs and check each for:
-
-**Specific metrics:**
-- Is there a measurable criterion? (e.g., "response time < 200ms", not "fast response")
-- Can this be measured or tested?
-
-**Template compliance:**
-- Criterion defined?
-- Metric specified?
-- Measurement method included?
-- Context provided?
-
-### 3. Tally Violations
-
-**FR Violations:**
-- Format violations: count
-- Subjective adjectives: count
-- Vague quantifiers: count
-- Implementation leakage: count
-- Total FR violations: sum
-
-**NFR Violations:**
-- Missing metrics: count
-- Incomplete template: count
-- Missing context: count
-- Total NFR violations: sum
-
-**Total violations:** FR violations + NFR violations
-
-### 4. Report Measurability Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## Measurability Validation
-
-### Functional Requirements
-
-**Total FRs Analyzed:** {count}
-
-**Format Violations:** {count}
-[If violations exist, list examples with line numbers]
-
-**Subjective Adjectives Found:** {count}
-[If found, list examples with line numbers]
-
-**Vague Quantifiers Found:** {count}
-[If found, list examples with line numbers]
-
-**Implementation Leakage:** {count}
-[If found, list examples with line numbers]
-
-**FR Violations Total:** {total}
-
-### Non-Functional Requirements
-
-**Total NFRs Analyzed:** {count}
-
-**Missing Metrics:** {count}
-[If missing, list examples with line numbers]
-
-**Incomplete Template:** {count}
-[If incomplete, list examples with line numbers]
-
-**Missing Context:** {count}
-[If missing, list examples with line numbers]
-
-**NFR Violations Total:** {total}
-
-### Overall Assessment
-
-**Total Requirements:** {FRs + NFRs}
-**Total Violations:** {FR violations + NFR violations}
-
-**Severity:** [Critical if >10 violations, Warning if 5-10, Pass if <5]
-
-**Recommendation:**
-[If Critical] "Many requirements are not measurable or testable. Requirements must be revised to be testable for downstream work."
-[If Warning] "Some requirements need refinement for measurability. Focus on violating requirements above."
-[If Pass] "Requirements demonstrate good measurability with minimal issues."
-```
-
-### 5. Display Progress and Auto-Proceed
-
-Display: "**Measurability Validation Complete**
-
-Total Violations: {count} ({severity})
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-06-traceability-validation.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All FRs extracted and analyzed for measurability
-- All NFRs extracted and analyzed for measurability
-- Violations documented with line numbers
-- Severity assessed correctly
-- Findings reported to validation report
-- Auto-proceeds to next validation step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not analyzing all FRs and NFRs
-- Missing line numbers for violations
-- Not reporting findings to validation report
-- Not assessing severity
-- Not auto-proceeding
-
-**Master Rule:** Requirements must be testable to be useful. Validate every requirement for measurability, document violations, auto-proceed.

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

@@ -1,217 +0,0 @@
----
-name: 'step-v-06-traceability-validation'
-description: 'Traceability Validation - Validate the traceability chain from vision → success → journeys → FRs is intact'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-07-implementation-leakage-validation.md'
-prdFile: '{prd_file_path}'
-validationReportPath: '{validation_report_path}'
----
-
-# Step 6: Traceability Validation
-
-## STEP GOAL:
-
-Validate the traceability chain from Executive Summary → Success Criteria → User Journeys → Functional Requirements is intact, ensuring every requirement traces back to a user need or business objective.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring analytical rigor and traceability matrix expertise
-- ✅ This step runs autonomously - no user input needed
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on traceability chain validation
-- 🚫 FORBIDDEN to validate other aspects in this step
-- 💬 Approach: Systematic chain validation and orphan detection
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Build and validate traceability matrix
-- 💾 Identify broken chains and orphan requirements
-- 📖 Append findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file, validation report
-- Focus: Traceability chain validation only
-- Limits: Don't validate other aspects, don't pause for user input
-- Dependencies: Steps 2-5 completed - initial validations done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Attempt Sub-Process Validation
-
-**Try to use Task tool to spawn a subprocess:**
-
-"Perform traceability validation on this PRD:
-
-1. Extract content from Executive Summary (vision, goals)
-2. Extract Success Criteria
-3. Extract User Journeys (user types, flows, outcomes)
-4. Extract Functional Requirements (FRs)
-5. Extract Product Scope (in-scope items)
-
-**Validate chains:**
-- Executive Summary → Success Criteria: Does vision align with defined success?
-- Success Criteria → User Journeys: Are success criteria supported by user journeys?
-- User Journeys → Functional Requirements: Does each FR trace back to a user journey?
-- Scope → FRs: Do MVP scope FRs align with in-scope items?
-
-**Identify orphans:**
-- FRs not traceable to any user journey or business objective
-- Success criteria not supported by user journeys
-- User journeys without supporting FRs
-
-Build traceability matrix and identify broken chains and orphan FRs.
-
-Return structured findings with chain status and orphan list."
-
-### 2. Graceful Degradation (if Task tool unavailable)
-
-If Task tool unavailable, perform analysis directly:
-
-**Step 1: Extract key elements**
-- Executive Summary: Note vision, goals, objectives
-- Success Criteria: List all criteria
-- User Journeys: List user types and their flows
-- Functional Requirements: List all FRs
-- Product Scope: List in-scope items
-
-**Step 2: Validate Executive Summary → Success Criteria**
-- Does Executive Summary mention the success dimensions?
-- Are Success Criteria aligned with vision?
-- Note any misalignment
-
-**Step 3: Validate Success Criteria → User Journeys**
-- For each success criterion, is there a user journey that achieves it?
-- Note success criteria without supporting journeys
-
-**Step 4: Validate User Journeys → FRs**
-- For each user journey/flow, are there FRs that enable it?
-- List FRs with no clear user journey origin
-- Note orphan FRs (requirements without traceable source)
-
-**Step 5: Validate Scope → FR Alignment**
-- Does MVP scope align with essential FRs?
-- Are in-scope items supported by FRs?
-- Note misalignments
-
-**Step 6: Build traceability matrix**
-- Map each FR to its source (journey or business objective)
-- Note orphan FRs
-- Identify broken chains
-
-### 3. Tally Traceability Issues
-
-**Broken chains:**
-- Executive Summary → Success Criteria gaps: count
-- Success Criteria → User Journeys gaps: count
-- User Journeys → FRs gaps: count
-- Scope → FR misalignments: count
-
-**Orphan elements:**
-- Orphan FRs (no traceable source): count
-- Unsupported success criteria: count
-- User journeys without FRs: count
-
-**Total issues:** Sum of all broken chains and orphans
-
-### 4. Report Traceability Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## Traceability Validation
-
-### Chain Validation
-
-**Executive Summary → Success Criteria:** [Intact/Gaps Identified]
-{If gaps: List specific misalignments}
-
-**Success Criteria → User Journeys:** [Intact/Gaps Identified]
-{If gaps: List unsupported success criteria}
-
-**User Journeys → Functional Requirements:** [Intact/Gaps Identified]
-{If gaps: List journeys without supporting FRs}
-
-**Scope → FR Alignment:** [Intact/Misaligned]
-{If misaligned: List specific issues}
-
-### Orphan Elements
-
-**Orphan Functional Requirements:** {count}
-{List orphan FRs with numbers}
-
-**Unsupported Success Criteria:** {count}
-{List unsupported criteria}
-
-**User Journeys Without FRs:** {count}
-{List journeys without FRs}
-
-### Traceability Matrix
-
-{Summary table showing traceability coverage}
-
-**Total Traceability Issues:** {total}
-
-**Severity:** [Critical if orphan FRs exist, Warning if gaps, Pass if intact]
-
-**Recommendation:**
-[If Critical] "Orphan requirements exist - every FR must trace back to a user need or business objective."
-[If Warning] "Traceability gaps identified - strengthen chains to ensure all requirements are justified."
-[If Pass] "Traceability chain is intact - all requirements trace to user needs or business objectives."
-```
-
-### 5. Display Progress and Auto-Proceed
-
-Display: "**Traceability Validation Complete**
-
-Total Issues: {count} ({severity})
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-07-implementation-leakage-validation.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All traceability chains validated systematically
-- Orphan FRs identified with numbers
-- Broken chains documented
-- Traceability matrix built
-- Severity assessed correctly
-- Findings reported to validation report
-- Auto-proceeds to next validation step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not validating all traceability chains
-- Missing orphan FR detection
-- Not building traceability matrix
-- Not reporting findings to validation report
-- Not auto-proceeding
-
-**Master Rule:** Every requirement should trace to a user need or business objective. Orphan FRs indicate broken traceability that must be fixed.

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

@@ -1,205 +0,0 @@
----
-name: 'step-v-07-implementation-leakage-validation'
-description: 'Implementation Leakage Check - Ensure FRs and NFRs don\'t include implementation details'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-08-domain-compliance-validation.md'
-prdFile: '{prd_file_path}'
-validationReportPath: '{validation_report_path}'
----
-
-# Step 7: Implementation Leakage Validation
-
-## STEP GOAL:
-
-Ensure Functional Requirements and Non-Functional Requirements don't include implementation details - they should specify WHAT, not HOW.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring analytical rigor and separation of concerns expertise
-- ✅ This step runs autonomously - no user input needed
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on implementation leakage detection
-- 🚫 FORBIDDEN to validate other aspects in this step
-- 💬 Approach: Systematic scanning for technology and implementation terms
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Scan FRs and NFRs for implementation terms
-- 💾 Distinguish capability-relevant vs leakage
-- 📖 Append findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file, validation report
-- Focus: Implementation leakage detection only
-- Limits: Don't validate other aspects, don't pause for user input
-- Dependencies: Steps 2-6 completed - initial validations done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Attempt Sub-Process Validation
-
-**Try to use Task tool to spawn a subprocess:**
-
-"Perform implementation leakage validation on this PRD:
-
-**Scan for:**
-1. Technology names (React, Vue, Angular, PostgreSQL, MongoDB, AWS, GCP, Azure, Docker, Kubernetes, etc.)
-2. Library names (Redux, axios, lodash, Express, Django, Rails, Spring, etc.)
-3. Data structures (JSON, XML, CSV) unless relevant to capability
-4. Architecture patterns (MVC, microservices, serverless) unless business requirement
-5. Protocol names (HTTP, REST, GraphQL, WebSockets) - check if capability-relevant
-
-**For each term found:**
-- Is this capability-relevant? (e.g., 'API consumers can access...' - API is capability)
-- Or is this implementation detail? (e.g., 'React component for...' - implementation)
-
-Document violations with line numbers and explanation.
-
-Return structured findings with leakage counts and examples."
-
-### 2. Graceful Degradation (if Task tool unavailable)
-
-If Task tool unavailable, perform analysis directly:
-
-**Implementation leakage terms to scan for:**
-
-**Frontend Frameworks:**
-React, Vue, Angular, Svelte, Solid, Next.js, Nuxt, etc.
-
-**Backend Frameworks:**
-Express, Django, Rails, Spring, Laravel, FastAPI, etc.
-
-**Databases:**
-PostgreSQL, MySQL, MongoDB, Redis, DynamoDB, Cassandra, etc.
-
-**Cloud Platforms:**
-AWS, GCP, Azure, Cloudflare, Vercel, Netlify, etc.
-
-**Infrastructure:**
-Docker, Kubernetes, Terraform, Ansible, etc.
-
-**Libraries:**
-Redux, Zustand, axios, fetch, lodash, jQuery, etc.
-
-**Data Formats:**
-JSON, XML, YAML, CSV (unless capability-relevant)
-
-**For each term found in FRs/NFRs:**
-- Determine if it's capability-relevant or implementation leakage
-- Example: "API consumers can access data via REST endpoints" - API/REST is capability
-- Example: "React components fetch data using Redux" - implementation leakage
-
-**Count violations and note line numbers**
-
-### 3. Tally Implementation Leakage
-
-**By category:**
-- Frontend framework leakage: count
-- Backend framework leakage: count
-- Database leakage: count
-- Cloud platform leakage: count
-- Infrastructure leakage: count
-- Library leakage: count
-- Other implementation details: count
-
-**Total implementation leakage violations:** sum
-
-### 4. Report Implementation Leakage Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## Implementation Leakage Validation
-
-### Leakage by Category
-
-**Frontend Frameworks:** {count} violations
-{If violations, list examples with line numbers}
-
-**Backend Frameworks:** {count} violations
-{If violations, list examples with line numbers}
-
-**Databases:** {count} violations
-{If violations, list examples with line numbers}
-
-**Cloud Platforms:** {count} violations
-{If violations, list examples with line numbers}
-
-**Infrastructure:** {count} violations
-{If violations, list examples with line numbers}
-
-**Libraries:** {count} violations
-{If violations, list examples with line numbers}
-
-**Other Implementation Details:** {count} violations
-{If violations, list examples with line numbers}
-
-### Summary
-
-**Total Implementation Leakage Violations:** {total}
-
-**Severity:** [Critical if >5 violations, Warning if 2-5, Pass if <2]
-
-**Recommendation:**
-[If Critical] "Extensive implementation leakage found. Requirements specify HOW instead of WHAT. Remove all implementation details - these belong in architecture, not PRD."
-[If Warning] "Some implementation leakage detected. Review violations and remove implementation details from requirements."
-[If Pass] "No significant implementation leakage found. Requirements properly specify WHAT without HOW."
-
-**Note:** API consumers, GraphQL (when required), and other capability-relevant terms are acceptable when they describe WHAT the system must do, not HOW to build it.
-```
-
-### 5. Display Progress and Auto-Proceed
-
-Display: "**Implementation Leakage Validation Complete**
-
-Total Violations: {count} ({severity})
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-08-domain-compliance-validation.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Scanned FRs and NFRs for all implementation term categories
-- Distinguished capability-relevant from implementation leakage
-- Violations documented with line numbers and explanations
-- Severity assessed correctly
-- Findings reported to validation report
-- Auto-proceeds to next validation step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not scanning all implementation term categories
-- Not distinguishing capability-relevant from leakage
-- Missing line numbers for violations
-- Not reporting findings to validation report
-- Not auto-proceeding
-
-**Master Rule:** Requirements specify WHAT, not HOW. Implementation details belong in architecture documents, not PRDs.

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

@@ -1,243 +0,0 @@
----
-name: 'step-v-08-domain-compliance-validation'
-description: 'Domain Compliance Validation - Validate domain-specific requirements are present for high-complexity domains'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-09-project-type-validation.md'
-prdFile: '{prd_file_path}'
-prdFrontmatter: '{prd_frontmatter}'
-validationReportPath: '{validation_report_path}'
-domainComplexityData: '../data/domain-complexity.csv'
----
-
-# Step 8: Domain Compliance Validation
-
-## STEP GOAL:
-
-Validate domain-specific requirements are present for high-complexity domains (Healthcare, Fintech, GovTech, etc.), ensuring regulatory and compliance requirements are properly documented.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring domain expertise and compliance knowledge
-- ✅ This step runs autonomously - no user input needed
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on domain-specific compliance requirements
-- 🚫 FORBIDDEN to validate other aspects in this step
-- 💬 Approach: Conditional validation based on domain classification
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Check classification.domain from PRD frontmatter
-- 💬 If low complexity (general): Skip detailed checks
-- 🎯 If high complexity: Validate required special sections
-- 💾 Append compliance findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file with frontmatter classification, validation report
-- Focus: Domain compliance only (conditional on domain complexity)
-- Limits: Don't validate other aspects, conditional execution
-- Dependencies: Steps 2-7 completed - format and requirements validation done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load Domain Complexity Data
-
-Load and read the complete file at:
-`{domainComplexityData}` (../data/domain-complexity.csv)
-
-This CSV contains:
-- Domain classifications and complexity levels (high/medium/low)
-- Required special sections for each domain
-- Key concerns and requirements for regulated industries
-
-Internalize this data - it drives which domains require special compliance sections.
-
-### 2. Extract Domain Classification
-
-From PRD frontmatter, extract:
-- `classification.domain` - what domain is this PRD for?
-
-**If no domain classification found:**
-Treat as "general" (low complexity) and proceed to step 4
-
-### 2. Determine Domain Complexity
-
-**Low complexity domains (skip detailed checks):**
-- General
-- Consumer apps (standard e-commerce, social, productivity)
-- Content websites
-- Business tools (standard)
-
-**High complexity domains (require special sections):**
-- Healthcare / Healthtech
-- Fintech / Financial services
-- GovTech / Public sector
-- EdTech (educational records, accredited courses)
-- Legal tech
-- Other regulated domains
-
-### 3. For High-Complexity Domains: Validate Required Special Sections
-
-**Attempt subprocess validation:**
-
-"Perform domain compliance validation for {domain}:
-
-Based on {domain} requirements, check PRD for:
-
-**Healthcare:**
-- Clinical Requirements section
-- Regulatory Pathway (FDA, HIPAA, etc.)
-- Safety Measures
-- HIPAA Compliance (data privacy, security)
-- Patient safety considerations
-
-**Fintech:**
-- Compliance Matrix (SOC2, PCI-DSS, GDPR, etc.)
-- Security Architecture
-- Audit Requirements
-- Fraud Prevention measures
-- Financial transaction handling
-
-**GovTech:**
-- Accessibility Standards (WCAG 2.1 AA, Section 508)
-- Procurement Compliance
-- Security Clearance requirements
-- Data residency requirements
-
-**Other regulated domains:**
-- Check for domain-specific regulatory sections
-- Compliance requirements
-- Special considerations
-
-For each required section:
-- Is it present in PRD?
-- Is it adequately documented?
-- Note any gaps
-
-Return compliance matrix with presence/adequacy assessment."
-
-**Graceful degradation (if no Task tool):**
-- Manually check for required sections based on domain
-- List present sections and missing sections
-- Assess adequacy of documentation
-
-### 5. For Low-Complexity Domains: Skip Detailed Checks
-
-Append to validation report:
-```markdown
-## Domain Compliance Validation
-
-**Domain:** {domain}
-**Complexity:** Low (general/standard)
-**Assessment:** N/A - No special domain compliance requirements
-
-**Note:** This PRD is for a standard domain without regulatory compliance requirements.
-```
-
-Display: "**Domain Compliance Validation Skipped**
-
-Domain: {domain} (low complexity)
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile}
-
-### 6. Report Compliance Findings (High-Complexity Domains)
-
-Append to validation report:
-
-```markdown
-## Domain Compliance Validation
-
-**Domain:** {domain}
-**Complexity:** High (regulated)
-
-### Required Special Sections
-
-**{Section 1 Name}:** [Present/Missing/Adequate]
-{If missing or inadequate: Note specific gaps}
-
-**{Section 2 Name}:** [Present/Missing/Adequate]
-{If missing or inadequate: Note specific gaps}
-
-[Continue for all required sections]
-
-### Compliance Matrix
-
-| Requirement | Status | Notes |
-|-------------|--------|-------|
-| {Requirement 1} | [Met/Partial/Missing] | {Notes} |
-| {Requirement 2} | [Met/Partial/Missing] | {Notes} |
-[... continue for all requirements]
-
-### Summary
-
-**Required Sections Present:** {count}/{total}
-**Compliance Gaps:** {count}
-
-**Severity:** [Critical if missing regulatory sections, Warning if incomplete, Pass if complete]
-
-**Recommendation:**
-[If Critical] "PRD is missing required domain-specific compliance sections. These are essential for {domain} products."
-[If Warning] "Some domain compliance sections are incomplete. Strengthen documentation for full compliance."
-[If Pass] "All required domain compliance sections are present and adequately documented."
-```
-
-### 7. Display Progress and Auto-Proceed
-
-Display: "**Domain Compliance Validation Complete**
-
-Domain: {domain} ({complexity})
-Compliance Status: {status}
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-09-project-type-validation.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Domain classification extracted correctly
-- Complexity assessed appropriately
-- Low complexity domains: Skipped with clear "N/A" documentation
-- High complexity domains: All required sections checked
-- Compliance matrix built with status for each requirement
-- Severity assessed correctly
-- Findings reported to validation report
-- Auto-proceeds to next validation step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not checking domain classification before proceeding
-- Performing detailed checks on low complexity domains
-- For high complexity: missing required section checks
-- Not building compliance matrix
-- Not reporting findings to validation report
-- Not auto-proceeding
-
-**Master Rule:** Domain compliance is conditional. High-complexity domains require special sections - low complexity domains skip these checks.

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

@@ -1,263 +0,0 @@
----
-name: 'step-v-09-project-type-validation'
-description: 'Project-Type Compliance Validation - Validate project-type specific requirements are properly documented'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-10-smart-validation.md'
-prdFile: '{prd_file_path}'
-prdFrontmatter: '{prd_frontmatter}'
-validationReportPath: '{validation_report_path}'
-projectTypesData: '../data/project-types.csv'
----
-
-# Step 9: Project-Type Compliance Validation
-
-## STEP GOAL:
-
-Validate project-type specific requirements are properly documented - different project types (api_backend, web_app, mobile_app, etc.) have different required and excluded sections.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring project type expertise and architectural knowledge
-- ✅ This step runs autonomously - no user input needed
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on project-type compliance
-- 🚫 FORBIDDEN to validate other aspects in this step
-- 💬 Approach: Validate required sections present, excluded sections absent
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Check classification.projectType from PRD frontmatter
-- 🎯 Validate required sections for that project type are present
-- 🎯 Validate excluded sections for that project type are absent
-- 💾 Append compliance findings to validation report
-- 📖 Display "Proceeding to next check..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file with frontmatter classification, validation report
-- Focus: Project-type compliance only
-- Limits: Don't validate other aspects, don't pause for user input
-- Dependencies: Steps 2-8 completed - domain and requirements validation done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load Project Types Data
-
-Load and read the complete file at:
-`{projectTypesData}` (../data/project-types.csv)
-
-This CSV contains:
-- Detection signals for each project type
-- Required sections for each project type
-- Skip/excluded sections for each project type
-- Innovation signals
-
-Internalize this data - it drives what sections must be present or absent for each project type.
-
-### 2. Extract Project Type Classification
-
-From PRD frontmatter, extract:
-- `classification.projectType` - what type of project is this?
-
-**Common project types:**
-- api_backend
-- web_app
-- mobile_app
-- desktop_app
-- data_pipeline
-- ml_system
-- library_sdk
-- infrastructure
-- other
-
-**If no projectType classification found:**
-Assume "web_app" (most common) and note in findings
-
-### 3. Determine Required and Excluded Sections from CSV Data
-
-**From loaded project-types.csv data, for this project type:**
-
-**Required sections:** (from required_sections column)
-These MUST be present in the PRD
-
-**Skip sections:** (from skip_sections column)
-These MUST NOT be present in the PRD
-
-**Example mappings from CSV:**
-- api_backend: Required=[endpoint_specs, auth_model, data_schemas], Skip=[ux_ui, visual_design]
-- mobile_app: Required=[platform_reqs, device_permissions, offline_mode], Skip=[desktop_features, cli_commands]
-- cli_tool: Required=[command_structure, output_formats, config_schema], Skip=[visual_design, ux_principles, touch_interactions]
-- etc.
-
-### 4. Validate Against CSV-Based Requirements
-
-**Based on project type, determine:**
-
-**api_backend:**
-- Required: Endpoint Specs, Auth Model, Data Schemas, API Versioning
-- Excluded: UX/UI sections, mobile-specific sections
-
-**web_app:**
-- Required: User Journeys, UX/UI Requirements, Responsive Design
-- Excluded: None typically
-
-**mobile_app:**
-- Required: Mobile UX, Platform specifics (iOS/Android), Offline mode
-- Excluded: Desktop-specific sections
-
-**desktop_app:**
-- Required: Desktop UX, Platform specifics (Windows/Mac/Linux)
-- Excluded: Mobile-specific sections
-
-**data_pipeline:**
-- Required: Data Sources, Data Transformation, Data Sinks, Error Handling
-- Excluded: UX/UI sections
-
-**ml_system:**
-- Required: Model Requirements, Training Data, Inference Requirements, Model Performance
-- Excluded: UX/UI sections (unless ML UI)
-
-**library_sdk:**
-- Required: API Surface, Usage Examples, Integration Guide
-- Excluded: UX/UI sections, deployment sections
-
-**infrastructure:**
-- Required: Infrastructure Components, Deployment, Monitoring, Scaling
-- Excluded: Feature requirements (this is infrastructure, not product)
-
-### 4. Attempt Sub-Process Validation
-
-"Perform project-type compliance validation for {projectType}:
-
-**Check that required sections are present:**
-{List required sections for this project type}
-For each: Is it present in PRD? Is it adequately documented?
-
-**Check that excluded sections are absent:**
-{List excluded sections for this project type}
-For each: Is it absent from PRD? (Should not be present)
-
-Build compliance table showing:
-- Required sections: [Present/Missing/Incomplete]
-- Excluded sections: [Absent/Present] (Present = violation)
-
-Return compliance table with findings."
-
-**Graceful degradation (if no Task tool):**
-- Manually check PRD for required sections
-- Manually check PRD for excluded sections
-- Build compliance table
-
-### 5. Build Compliance Table
-
-**Required sections check:**
-- For each required section: Present / Missing / Incomplete
-- Count: Required sections present vs total required
-
-**Excluded sections check:**
-- For each excluded section: Absent / Present (violation)
-- Count: Excluded sections present (violations)
-
-**Total compliance score:**
-- Required: {present}/{total}
-- Excluded violations: {count}
-
-### 6. Report Project-Type Compliance Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## Project-Type Compliance Validation
-
-**Project Type:** {projectType}
-
-### Required Sections
-
-**{Section 1}:** [Present/Missing/Incomplete]
-{If missing or incomplete: Note specific gaps}
-
-**{Section 2}:** [Present/Missing/Incomplete]
-{If missing or incomplete: Note specific gaps}
-
-[Continue for all required sections]
-
-### Excluded Sections (Should Not Be Present)
-
-**{Section 1}:** [Absent/Present] ✓
-{If present: This section should not be present for {projectType}}
-
-**{Section 2}:** [Absent/Present] ✓
-{If present: This section should not be present for {projectType}}
-
-[Continue for all excluded sections]
-
-### Compliance Summary
-
-**Required Sections:** {present}/{total} present
-**Excluded Sections Present:** {violations} (should be 0)
-**Compliance Score:** {percentage}%
-
-**Severity:** [Critical if required sections missing, Warning if incomplete, Pass if complete]
-
-**Recommendation:**
-[If Critical] "PRD is missing required sections for {projectType}. Add missing sections to properly specify this type of project."
-[If Warning] "Some required sections for {projectType} are incomplete. Strengthen documentation."
-[If Pass] "All required sections for {projectType} are present. No excluded sections found."
-```
-
-### 7. Display Progress and Auto-Proceed
-
-Display: "**Project-Type Compliance Validation Complete**
-
-Project Type: {projectType}
-Compliance: {score}%
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-10-smart-validation.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Project type extracted correctly (or default assumed)
-- Required sections validated for presence and completeness
-- Excluded sections validated for absence
-- Compliance table built with status for all sections
-- Severity assessed correctly
-- Findings reported to validation report
-- Auto-proceeds to next validation step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not checking project type before proceeding
-- Missing required section checks
-- Missing excluded section checks
-- Not building compliance table
-- Not reporting findings to validation report
-- Not auto-proceeding
-
-**Master Rule:** Different project types have different requirements. API PRDs don't need UX sections - validate accordingly.

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

@@ -1,209 +0,0 @@
----
-name: 'step-v-10-smart-validation'
-description: 'SMART Requirements Validation - Validate Functional Requirements meet SMART quality criteria'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-11-holistic-quality-validation.md'
-prdFile: '{prd_file_path}'
-validationReportPath: '{validation_report_path}'
----
-
-# Step 10: SMART Requirements Validation
-
-## STEP GOAL:
-
-Validate Functional Requirements meet SMART quality criteria (Specific, Measurable, Attainable, Relevant, Traceable), ensuring high-quality requirements.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring requirements engineering expertise and quality assessment
-- ✅ This step runs autonomously - no user input needed
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on FR quality assessment using SMART framework
-- 🚫 FORBIDDEN to validate other aspects in this step
-- 💬 Approach: Score each FR on SMART criteria (1-5 scale)
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Extract all FRs from PRD
-- 🎯 Score each FR on SMART criteria (Specific, Measurable, Attainable, Relevant, Traceable)
-- 💾 Flag FRs with score < 3 in any category
-- 📖 Append scoring table and suggestions to validation report
-- 📖 Display "Proceeding to next check..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file, validation report
-- Focus: FR quality assessment only using SMART framework
-- Limits: Don't validate NFRs or other aspects, don't pause for user input
-- Dependencies: Steps 2-9 completed - comprehensive validation checks done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Extract All Functional Requirements
-
-From the PRD's Functional Requirements section, extract:
-- All FRs with their FR numbers (FR-001, FR-002, etc.)
-- Count total FRs
-
-### 2. Attempt Sub-Process Validation
-
-**Try to use Task tool to spawn a subprocess:**
-
-"Perform SMART requirements validation on these Functional Requirements:
-
-{List all FRs}
-
-**For each FR, score on SMART criteria (1-5 scale):**
-
-**Specific (1-5):**
-- 5: Clear, unambiguous, well-defined
-- 3: Somewhat clear but could be more specific
-- 1: Vague, ambiguous, unclear
-
-**Measurable (1-5):**
-- 5: Quantifiable metrics, testable
-- 3: Partially measurable
-- 1: Not measurable, subjective
-
-**Attainable (1-5):**
-- 5: Realistic, achievable with constraints
-- 3: Probably achievable but uncertain
-- 1: Unrealistic, technically infeasible
-
-**Relevant (1-5):**
-- 5: Clearly aligned with user needs and business objectives
-- 3: Somewhat relevant but connection unclear
-- 1: Not relevant, doesn't align with goals
-
-**Traceable (1-5):**
-- 5: Clearly traces to user journey or business objective
-- 3: Partially traceable
-- 1: Orphan requirement, no clear source
-
-**For each FR with score < 3 in any category:**
-- Provide specific improvement suggestions
-
-Return scoring table with all FR scores and improvement suggestions for low-scoring FRs."
-
-**Graceful degradation (if no Task tool):**
-- Manually score each FR on SMART criteria
-- Note FRs with low scores
-- Provide improvement suggestions
-
-### 3. Build Scoring Table
-
-For each FR:
-- FR number
-- Specific score (1-5)
-- Measurable score (1-5)
-- Attainable score (1-5)
-- Relevant score (1-5)
-- Traceable score (1-5)
-- Average score
-- Flag if any category < 3
-
-**Calculate overall FR quality:**
-- Percentage of FRs with all scores ≥ 3
-- Percentage of FRs with all scores ≥ 4
-- Average score across all FRs and categories
-
-### 4. Report SMART Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## SMART Requirements Validation
-
-**Total Functional Requirements:** {count}
-
-### Scoring Summary
-
-**All scores ≥ 3:** {percentage}% ({count}/{total})
-**All scores ≥ 4:** {percentage}% ({count}/{total})
-**Overall Average Score:** {average}/5.0
-
-### Scoring Table
-
-| FR # | Specific | Measurable | Attainable | Relevant | Traceable | Average | Flag |
-|------|----------|------------|------------|----------|-----------|--------|------|
-| FR-001 | {s1} | {m1} | {a1} | {r1} | {t1} | {avg1} | {X if any <3} |
-| FR-002 | {s2} | {m2} | {a2} | {r2} | {t2} | {avg2} | {X if any <3} |
-[Continue for all FRs]
-
-**Legend:** 1=Poor, 3=Acceptable, 5=Excellent
-**Flag:** X = Score < 3 in one or more categories
-
-### Improvement Suggestions
-
-**Low-Scoring FRs:**
-
-**FR-{number}:** {specific suggestion for improvement}
-[For each FR with score < 3 in any category]
-
-### Overall Assessment
-
-**Severity:** [Critical if >30% flagged FRs, Warning if 10-30%, Pass if <10%]
-
-**Recommendation:**
-[If Critical] "Many FRs have quality issues. Revise flagged FRs using SMART framework to improve clarity and testability."
-[If Warning] "Some FRs would benefit from SMART refinement. Focus on flagged requirements above."
-[If Pass] "Functional Requirements demonstrate good SMART quality overall."
-```
-
-### 5. Display Progress and Auto-Proceed
-
-Display: "**SMART Requirements Validation Complete**
-
-FR Quality: {percentage}% with acceptable scores ({severity})
-
-**Proceeding to next validation check...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-11-holistic-quality-validation.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All FRs extracted from PRD
-- Each FR scored on all 5 SMART criteria (1-5 scale)
-- FRs with scores < 3 flagged for improvement
-- Improvement suggestions provided for low-scoring FRs
-- Scoring table built with all FR scores
-- Overall quality assessment calculated
-- Findings reported to validation report
-- Auto-proceeds to next validation step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not scoring all FRs on all SMART criteria
-- Missing improvement suggestions for low-scoring FRs
-- Not building scoring table
-- Not calculating overall quality metrics
-- Not reporting findings to validation report
-- Not auto-proceeding
-
-**Master Rule:** FRs should be high-quality, not just present. SMART framework provides objective quality measure.

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

@@ -1,265 +0,0 @@
----
-name: 'step-v-11-holistic-quality-validation'
-description: 'Holistic Quality Assessment - Assess PRD as cohesive, compelling document - is it a good PRD?'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-12-completeness-validation.md'
-prdFile: '{prd_file_path}'
-validationReportPath: '{validation_report_path}'
-advancedElicitationTask: 'skill:bmad-advanced-elicitation'
----
-
-# Step 11: Holistic Quality Assessment
-
-## STEP GOAL:
-
-Assess the PRD as a cohesive, compelling document - evaluating document flow, dual audience effectiveness (humans and LLMs), BMAD PRD principles compliance, and overall quality rating.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring analytical rigor and document quality expertise
-- ✅ This step runs autonomously - no user input needed
-- ✅ Uses Advanced Elicitation for multi-perspective evaluation
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on holistic document quality assessment
-- 🚫 FORBIDDEN to validate individual components (done in previous steps)
-- 💬 Approach: Multi-perspective evaluation using Advanced Elicitation
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Use Advanced Elicitation for multi-perspective assessment
-- 🎯 Evaluate document flow, dual audience, BMAD principles
-- 💾 Append comprehensive assessment to validation report
-- 📖 Display "Proceeding to next check..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Complete PRD file, validation report with findings from steps 1-10
-- Focus: Holistic quality - the WHOLE document
-- Limits: Don't re-validate individual components, don't pause for user input
-- Dependencies: Steps 1-10 completed - all systematic checks done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Attempt Sub-Process with Advanced Elicitation
-
-**Try to use Task tool to spawn a subprocess using Advanced Elicitation:**
-
-"Perform holistic quality assessment on this PRD using multi-perspective evaluation:
-
-**Read fully and follow the Advanced Elicitation workflow:**
-{advancedElicitationTask}
-
-**Evaluate the PRD from these perspectives:**
-
-**1. Document Flow & Coherence:**
-- Read entire PRD
-- Evaluate narrative flow - does it tell a cohesive story?
-- Check transitions between sections
-- Assess consistency - is it coherent throughout?
-- Evaluate readability - is it clear and well-organized?
-
-**2. Dual Audience Effectiveness:**
-
-**For Humans:**
-- Executive-friendly: Can executives understand vision and goals quickly?
-- Developer clarity: Do developers have clear requirements to build from?
-- Designer clarity: Do designers understand user needs and flows?
-- Stakeholder decision-making: Can stakeholders make informed decisions?
-
-**For LLMs:**
-- Machine-readable structure: Is the PRD structured for LLM consumption?
-- UX readiness: Can an LLM generate UX designs from this?
-- Architecture readiness: Can an LLM generate architecture from this?
-- Epic/Story readiness: Can an LLM break down into epics and stories?
-
-**3. BMAD PRD Principles Compliance:**
-- Information density: Every sentence carries weight?
-- Measurability: Requirements testable?
-- Traceability: Requirements trace to sources?
-- Domain awareness: Domain-specific considerations included?
-- Zero anti-patterns: No filler or wordiness?
-- Dual audience: Works for both humans and LLMs?
-- Markdown format: Proper structure and formatting?
-
-**4. Overall Quality Rating:**
-Rate the PRD on 5-point scale:
-- Excellent (5/5): Exemplary, ready for production use
-- Good (4/5): Strong with minor improvements needed
-- Adequate (3/5): Acceptable but needs refinement
-- Needs Work (2/5): Significant gaps or issues
-- Problematic (1/5): Major flaws, needs substantial revision
-
-**5. Top 3 Improvements:**
-Identify the 3 most impactful improvements to make this a great PRD
-
-Return comprehensive assessment with all perspectives, rating, and top 3 improvements."
-
-**Graceful degradation (if no Task tool or Advanced Elicitation unavailable):**
-- Perform holistic assessment directly in current context
-- Read complete PRD
-- Evaluate document flow, coherence, transitions
-- Assess dual audience effectiveness
-- Check BMAD principles compliance
-- Assign overall quality rating
-- Identify top 3 improvements
-
-### 2. Synthesize Assessment
-
-**Compile findings from multi-perspective evaluation:**
-
-**Document Flow & Coherence:**
-- Overall assessment: [Excellent/Good/Adequate/Needs Work/Problematic]
-- Key strengths: [list]
-- Key weaknesses: [list]
-
-**Dual Audience Effectiveness:**
-- For Humans: [assessment]
-- For LLMs: [assessment]
-- Overall dual audience score: [1-5]
-
-**BMAD Principles Compliance:**
-- Principles met: [count]/7
-- Principles with issues: [list]
-
-**Overall Quality Rating:** [1-5 with label]
-
-**Top 3 Improvements:**
-1. [Improvement 1]
-2. [Improvement 2]
-3. [Improvement 3]
-
-### 3. Report Holistic Quality Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## Holistic Quality Assessment
-
-### Document Flow & Coherence
-
-**Assessment:** [Excellent/Good/Adequate/Needs Work/Problematic]
-
-**Strengths:**
-{List key strengths}
-
-**Areas for Improvement:**
-{List key weaknesses}
-
-### Dual Audience Effectiveness
-
-**For Humans:**
-- Executive-friendly: [assessment]
-- Developer clarity: [assessment]
-- Designer clarity: [assessment]
-- Stakeholder decision-making: [assessment]
-
-**For LLMs:**
-- Machine-readable structure: [assessment]
-- UX readiness: [assessment]
-- Architecture readiness: [assessment]
-- Epic/Story readiness: [assessment]
-
-**Dual Audience Score:** {score}/5
-
-### BMAD PRD Principles Compliance
-
-| Principle | Status | Notes |
-|-----------|--------|-------|
-| Information Density | [Met/Partial/Not Met] | {notes} |
-| Measurability | [Met/Partial/Not Met] | {notes} |
-| Traceability | [Met/Partial/Not Met] | {notes} |
-| Domain Awareness | [Met/Partial/Not Met] | {notes} |
-| Zero Anti-Patterns | [Met/Partial/Not Met] | {notes} |
-| Dual Audience | [Met/Partial/Not Met] | {notes} |
-| Markdown Format | [Met/Partial/Not Met] | {notes} |
-
-**Principles Met:** {count}/7
-
-### Overall Quality Rating
-
-**Rating:** {rating}/5 - {label}
-
-**Scale:**
-- 5/5 - Excellent: Exemplary, ready for production use
-- 4/5 - Good: Strong with minor improvements needed
-- 3/5 - Adequate: Acceptable but needs refinement
-- 2/5 - Needs Work: Significant gaps or issues
-- 1/5 - Problematic: Major flaws, needs substantial revision
-
-### Top 3 Improvements
-
-1. **{Improvement 1}**
-   {Brief explanation of why and how}
-
-2. **{Improvement 2}**
-   {Brief explanation of why and how}
-
-3. **{Improvement 3}**
-   {Brief explanation of why and how}
-
-### Summary
-
-**This PRD is:** {one-sentence overall assessment}
-
-**To make it great:** Focus on the top 3 improvements above.
-```
-
-### 4. Display Progress and Auto-Proceed
-
-Display: "**Holistic Quality Assessment Complete**
-
-Overall Rating: {rating}/5 - {label}
-
-**Proceeding to final validation checks...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-12-completeness-validation.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Advanced Elicitation used for multi-perspective evaluation (or graceful degradation)
-- Document flow & coherence assessed
-- Dual audience effectiveness evaluated (humans and LLMs)
-- BMAD PRD principles compliance checked
-- Overall quality rating assigned (1-5 scale)
-- Top 3 improvements identified
-- Comprehensive assessment reported to validation report
-- Auto-proceeds to next validation step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not using Advanced Elicitation for multi-perspective evaluation
-- Missing document flow assessment
-- Missing dual audience evaluation
-- Not checking all BMAD principles
-- Not assigning overall quality rating
-- Missing top 3 improvements
-- Not reporting comprehensive assessment to validation report
-- Not auto-proceeding
-
-**Master Rule:** This evaluates the WHOLE document, not just components. Answers "Is this a good PRD?" and "What would make it great?"

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

@@ -1,242 +0,0 @@
----
-name: 'step-v-12-completeness-validation'
-description: 'Completeness Check - Final comprehensive completeness check before report generation'
-
-# File references (ONLY variables used in this step)
-nextStepFile: './step-v-13-report-complete.md'
-prdFile: '{prd_file_path}'
-prdFrontmatter: '{prd_frontmatter}'
-validationReportPath: '{validation_report_path}'
----
-
-# Step 12: Completeness Validation
-
-## STEP GOAL:
-
-Final comprehensive completeness check - validate no template variables remain, each section has required content, section-specific completeness, and frontmatter is properly populated.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in systematic validation, not collaborative dialogue
-- ✅ You bring attention to detail and completeness verification
-- ✅ This step runs autonomously - no user input needed
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on completeness verification
-- 🚫 FORBIDDEN to validate quality (done in step 11) or other aspects
-- 💬 Approach: Systematic checklist-style verification
-- 🚪 This is a validation sequence step - auto-proceeds when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Check template completeness (no variables remaining)
-- 🎯 Validate content completeness (each section has required content)
-- 🎯 Validate section-specific completeness
-- 🎯 Validate frontmatter completeness
-- 💾 Append completeness matrix to validation report
-- 📖 Display "Proceeding to final step..." and load next step
-- 🚫 FORBIDDEN to pause or request user input
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Complete PRD file, frontmatter, validation report
-- Focus: Completeness verification only (final gate)
-- Limits: Don't assess quality, don't pause for user input
-- Dependencies: Steps 1-11 completed - all validation checks done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Attempt Sub-Process Validation
-
-**Try to use Task tool to spawn a subprocess:**
-
-"Perform completeness validation on this PRD - final gate check:
-
-**1. Template Completeness:**
-- Scan PRD for any remaining template variables
-- Look for: {variable}, {{variable}}, {placeholder}, [placeholder], etc.
-- List any found with line numbers
-
-**2. Content Completeness:**
-- Executive Summary: Has vision statement? ({key content})
-- Success Criteria: All criteria measurable? ({metrics present})
-- Product Scope: In-scope and out-of-scope defined? ({both present})
-- User Journeys: User types identified? ({users listed})
-- Functional Requirements: FRs listed with proper format? ({FRs present})
-- Non-Functional Requirements: NFRs with metrics? ({NFRs present})
-
-For each section: Is required content present? (Yes/No/Partial)
-
-**3. Section-Specific Completeness:**
-- Success Criteria: Each has specific measurement method?
-- User Journeys: Cover all user types?
-- Functional Requirements: Cover MVP scope?
-- Non-Functional Requirements: Each has specific criteria?
-
-**4. Frontmatter Completeness:**
-- stepsCompleted: Populated?
-- classification: Present (domain, projectType)?
-- inputDocuments: Tracked?
-- date: Present?
-
-Return completeness matrix with status for each check."
-
-**Graceful degradation (if no Task tool):**
-- Manually scan for template variables
-- Manually check each section for required content
-- Manually verify frontmatter fields
-- Build completeness matrix
-
-### 2. Build Completeness Matrix
-
-**Template Completeness:**
-- Template variables found: count
-- List if any found
-
-**Content Completeness by Section:**
-- Executive Summary: Complete / Incomplete / Missing
-- Success Criteria: Complete / Incomplete / Missing
-- Product Scope: Complete / Incomplete / Missing
-- User Journeys: Complete / Incomplete / Missing
-- Functional Requirements: Complete / Incomplete / Missing
-- Non-Functional Requirements: Complete / Incomplete / Missing
-- Other sections: [List completeness]
-
-**Section-Specific Completeness:**
-- Success criteria measurable: All / Some / None
-- Journeys cover all users: Yes / Partial / No
-- FRs cover MVP scope: Yes / Partial / No
-- NFRs have specific criteria: All / Some / None
-
-**Frontmatter Completeness:**
-- stepsCompleted: Present / Missing
-- classification: Present / Missing
-- inputDocuments: Present / Missing
-- date: Present / Missing
-
-**Overall completeness:**
-- Sections complete: X/Y
-- Critical gaps: [list if any]
-
-### 3. Report Completeness Findings to Validation Report
-
-Append to validation report:
-
-```markdown
-## Completeness Validation
-
-### Template Completeness
-
-**Template Variables Found:** {count}
-{If count > 0, list variables with line numbers}
-{If count = 0, note: No template variables remaining ✓}
-
-### Content Completeness by Section
-
-**Executive Summary:** [Complete/Incomplete/Missing]
-{If incomplete or missing, note specific gaps}
-
-**Success Criteria:** [Complete/Incomplete/Missing]
-{If incomplete or missing, note specific gaps}
-
-**Product Scope:** [Complete/Incomplete/Missing]
-{If incomplete or missing, note specific gaps}
-
-**User Journeys:** [Complete/Incomplete/Missing]
-{If incomplete or missing, note specific gaps}
-
-**Functional Requirements:** [Complete/Incomplete/Missing]
-{If incomplete or missing, note specific gaps}
-
-**Non-Functional Requirements:** [Complete/Incomplete/Missing]
-{If incomplete or missing, note specific gaps}
-
-### Section-Specific Completeness
-
-**Success Criteria Measurability:** [All/Some/None] measurable
-{If Some or None, note which criteria lack metrics}
-
-**User Journeys Coverage:** [Yes/Partial/No] - covers all user types
-{If Partial or No, note missing user types}
-
-**FRs Cover MVP Scope:** [Yes/Partial/No]
-{If Partial or No, note scope gaps}
-
-**NFRs Have Specific Criteria:** [All/Some/None]
-{If Some or None, note which NFRs lack specificity}
-
-### Frontmatter Completeness
-
-**stepsCompleted:** [Present/Missing]
-**classification:** [Present/Missing]
-**inputDocuments:** [Present/Missing]
-**date:** [Present/Missing]
-
-**Frontmatter Completeness:** {complete_fields}/4
-
-### Completeness Summary
-
-**Overall Completeness:** {percentage}% ({complete_sections}/{total_sections})
-
-**Critical Gaps:** [count] [list if any]
-**Minor Gaps:** [count] [list if any]
-
-**Severity:** [Critical if template variables exist or critical sections missing, Warning if minor gaps, Pass if complete]
-
-**Recommendation:**
-[If Critical] "PRD has completeness gaps that must be addressed before use. Fix template variables and complete missing sections."
-[If Warning] "PRD has minor completeness gaps. Address minor gaps for complete documentation."
-[If Pass] "PRD is complete with all required sections and content present."
-```
-
-### 4. Display Progress and Auto-Proceed
-
-Display: "**Completeness Validation Complete**
-
-Overall Completeness: {percentage}% ({severity})
-
-**Proceeding to final step...**"
-
-Without delay, read fully and follow: {nextStepFile} (step-v-13-report-complete.md)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Scanned for template variables systematically
-- Validated each section for required content
-- Validated section-specific completeness (measurability, coverage, scope)
-- Validated frontmatter completeness
-- Completeness matrix built with all checks
-- Severity assessed correctly
-- Findings reported to validation report
-- Auto-proceeds to final step
-- Subprocess attempted with graceful degradation
-
-### ❌ SYSTEM FAILURE:
-
-- Not scanning for template variables
-- Missing section-specific completeness checks
-- Not validating frontmatter
-- Not building completeness matrix
-- Not reporting findings to validation report
-- Not auto-proceeding
-
-**Master Rule:** Final gate to ensure document is complete before presenting findings. Template variables or critical gaps must be fixed.

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

@@ -1,232 +0,0 @@
----
-name: 'step-v-13-report-complete'
-description: 'Validation Report Complete - Finalize report, summarize findings, present to user, offer next steps'
-
-# File references (ONLY variables used in this step)
-validationReportPath: '{validation_report_path}'
-prdFile: '{prd_file_path}'
----
-
-# Step 13: Validation Report Complete
-
-## STEP GOAL:
-
-Finalize validation report, summarize all findings from steps 1-12, present summary to user conversationally, and offer actionable next steps.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and Quality Assurance Specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring synthesis and summary expertise
-- ✅ This is the FINAL step - requires user interaction
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on summarizing findings and presenting options
-- 🚫 FORBIDDEN to perform additional validation
-- 💬 Approach: Conversational summary with clear next steps
-- 🚪 This is the final step - no next step after this
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load complete validation report
-- 🎯 Summarize all findings from steps 1-12
-- 🎯 Update report frontmatter with final status
-- 💬 Present summary to user conversationally
-- 💬 Offer menu options for next actions
-- 🚫 FORBIDDEN to proceed without user selection
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Complete validation report with findings from all validation steps
-- Focus: Summary and presentation only (no new validation)
-- Limits: Don't add new findings, just synthesize existing
-- Dependencies: Steps 1-12 completed - all validation checks done
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load Complete Validation Report
-
-Read the entire validation report from {validationReportPath}
-
-Extract all findings from:
-- Format Detection (Step 2)
-- Parity Analysis (Step 2B, if applicable)
-- Information Density (Step 3)
-- Product Brief Coverage (Step 4)
-- Measurability (Step 5)
-- Traceability (Step 6)
-- Implementation Leakage (Step 7)
-- Domain Compliance (Step 8)
-- Project-Type Compliance (Step 9)
-- SMART Requirements (Step 10)
-- Holistic Quality (Step 11)
-- Completeness (Step 12)
-
-### 2. Update Report Frontmatter with Final Status
-
-Update validation report frontmatter:
-
-```yaml
----
-validationTarget: '{prd_path}'
-validationDate: '{current_date}'
-inputDocuments: [list of documents]
-validationStepsCompleted: ['step-v-01-discovery', 'step-v-02-format-detection', 'step-v-03-density-validation', 'step-v-04-brief-coverage-validation', 'step-v-05-measurability-validation', 'step-v-06-traceability-validation', 'step-v-07-implementation-leakage-validation', 'step-v-08-domain-compliance-validation', 'step-v-09-project-type-validation', 'step-v-10-smart-validation', 'step-v-11-holistic-quality-validation', 'step-v-12-completeness-validation']
-validationStatus: COMPLETE
-holisticQualityRating: '{rating from step 11}'
-overallStatus: '{Pass/Warning/Critical based on all findings}'
----
-```
-
-### 3. Create Summary of Findings
-
-**Overall Status:**
-- Determine from all validation findings
-- **Pass:** All critical checks pass, minor warnings acceptable
-- **Warning:** Some issues found but PRD is usable
-- **Critical:** Major issues that prevent PRD from being fit for purpose
-
-**Quick Results Table:**
-- Format: [classification]
-- Information Density: [severity]
-- Measurability: [severity]
-- Traceability: [severity]
-- Implementation Leakage: [severity]
-- Domain Compliance: [status]
-- Project-Type Compliance: [compliance score]
-- SMART Quality: [percentage]
-- Holistic Quality: [rating/5]
-- Completeness: [percentage]
-
-**Critical Issues:** List from all validation steps
-**Warnings:** List from all validation steps
-**Strengths:** List positives from all validation steps
-
-**Holistic Quality Rating:** From step 11
-**Top 3 Improvements:** From step 11
-
-**Recommendation:** Based on overall status
-
-### 4. Present Summary to User Conversationally
-
-Display:
-
-"**✓ PRD Validation Complete**
-
-**Overall Status:** {Pass/Warning/Critical}
-
-**Quick Results:**
-{Present quick results table with key findings}
-
-**Critical Issues:** {count or "None"}
-{If any, list briefly}
-
-**Warnings:** {count or "None"}
-{If any, list briefly}
-
-**Strengths:**
-{List key strengths}
-
-**Holistic Quality:** {rating}/5 - {label}
-
-**Top 3 Improvements:**
-1. {Improvement 1}
-2. {Improvement 2}
-3. {Improvement 3}
-
-**Recommendation:**
-{Based on overall status:
-- Pass: "PRD is in good shape. Address minor improvements to make it great."
-- Warning: "PRD is usable but has issues that should be addressed. Review warnings and improve where needed."
-- Critical: "PRD has significant issues that should be fixed before use. Focus on critical issues above."}
-
-**What would you like to do next?**"
-
-### 5. Present MENU OPTIONS
-
-Display:
-
-**[R] Review Detailed Findings** - Walk through validation report section by section
-**[E] Use Edit Workflow** - Use validation report with Edit workflow for systematic improvements
-**[F] Fix Simpler Items** - Immediate fixes for simple issues (anti-patterns, leakage, missing headers)
-**[X] Exit** - Exit and Suggest Next Steps.
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- Only proceed based on user selection
-
-#### Menu Handling Logic:
-
-- **IF R (Review Detailed Findings):**
-  - Walk through validation report section by section
-  - Present findings from each validation step
-  - Allow user to ask questions
-  - After review, return to menu
-
-- **IF E (Use Edit Workflow):**
-  - Explain: "The Edit workflow (steps-e/) can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
-  - Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
-  - If yes: Read fully and follow: steps-e/step-e-01-discovery.md
-  - If no: Return to menu
-
-- **IF F (Fix Simpler Items):**
-  - Offer immediate fixes for:
-    - Template variables (fill in with appropriate content)
-    - Conversational filler (remove wordy phrases)
-    - Implementation leakage (remove technology names from FRs/NFRs)
-    - Missing section headers (add ## headers)
-  - Ask: "Which simple fixes would you like me to make?"
-  - If user specifies fixes, make them and update validation report
-  - Return to menu
-
-- **IF X (Exit):**
-  - Display: "**Validation Report Saved:** {validationReportPath}"
-  - Display: "**Summary:** {overall status} - {recommendation}"
-  - PRD Validation complete. Invoke the `bmad-help` skill.
-
-- **IF Any other:** Help user, then redisplay menu
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Complete validation report loaded successfully
-- All findings from steps 1-12 summarized
-- Report frontmatter updated with final status
-- Overall status determined correctly (Pass/Warning/Critical)
-- Quick results table presented
-- Critical issues, warnings, and strengths listed
-- Holistic quality rating included
-- Top 3 improvements presented
-- Clear recommendation provided
-- Menu options presented with clear explanations
-- User can review findings, get help, or exit
-
-### ❌ SYSTEM FAILURE:
-
-- Not loading complete validation report
-- Missing summary of findings
-- Not updating report frontmatter
-- Not determining overall status
-- Missing menu options
-- Unclear next steps
-
-**Master Rule:** User needs clear summary and actionable next steps. Edit workflow is best for complex issues; immediate fixes available for simpler ones.

src/bmm/workflows/2-plan-workflows/bmad-validate-prd/workflow.md

@@ -1,62 +0,0 @@
----
-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}`.
-✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
-
-### 2. Route to Validate Workflow
-
-"**Validate Mode: Validating an existing PRD against BMAD standards.**"
-
-Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)

src/bmm/workflows/2-plan-workflows/create-prd/bmad-skill-manifest.yaml

@@ -0,0 +1,14 @@
+workflow-create-prd.md:
+  canonicalId: bmad-create-prd
+  type: workflow
+  description: "Create a PRD from scratch. Use when the user says 'lets create a product requirements document' or 'I want to create a new PRD'"
+
+workflow-edit-prd.md:
+  canonicalId: bmad-edit-prd
+  type: workflow
+  description: "Edit an existing PRD. Use when the user says 'edit this PRD'"
+
+workflow-validate-prd.md:
+  canonicalId: bmad-validate-prd
+  type: workflow
+  description: "Validate a PRD against standards. Use when the user says 'validate this PRD' or 'run PRD validation'"

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

@@ -1,3 +1,16 @@
+---
+name: 'step-01-init'
+description: 'Initialize the PRD workflow by detecting continuation state and setting up the document'
+
+# File References
+nextStepFile: './step-02-discovery.md'
+continueStepFile: './step-01b-continue.md'
+outputFile: '{planning_artifacts}/prd.md'
+
+# Template Reference
+prdTemplate: '../templates/prd-template.md'
+---
+
 # Step 1: Workflow Initialization
 
 **Progress: Step 1 of 11** - Next: Project Discovery
@@ -58,11 +71,11 @@ First, check if the output document already exists:
 
 ### 2. Handle Continuation (If Document Exists)
 
-If the document exists and has frontmatter with `stepsCompleted` BUT `step-12-complete` is NOT in the list, follow the Continuation Protocol since the document is incomplete:
+If the document exists and has frontmatter with `stepsCompleted` BUT `step-11-complete` is NOT in the list, follow the Continuation Protocol since the document is incomplete:
 
 **Continuation Protocol:**
 
-- **STOP immediately** and load `./step-01b-continue.md`
+- **STOP immediately** and load `{continueStepFile}`
 - Do not proceed with any initialization tasks
 - Let step-01b handle all continuation logic
 - This is an auto-proceed situation - no user choice needed
@@ -76,7 +89,7 @@ If no document exists or no `stepsCompleted` in frontmatter:
 Discover and load context documents using smart discovery. Documents can be in the following locations:
 - {planning_artifacts}/**
 - {output_folder}/**
-- {project_knowledge}/**
+- {product_knowledge}/**
 - docs/**
 
 Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
@@ -84,7 +97,7 @@ Also - when searching - documents can be a single markdown file, or a folder wit
 Try to discover the following:
 - Product Brief (`*brief*.md`)
 - Research Documents (`/*research*.md`)
-- Project Documentation (generally multiple documents might be found for this in the `{project_knowledge}` or `docs` folder.)
+- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
 - Project Context (`**/project-context.md`)
 
 <critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
@@ -101,7 +114,7 @@ Try to discover the following:
 
 **Document Setup:**
 
-- Copy the template from `../templates/prd-template.md` to `{outputFile}`
+- Copy the template from `{prdTemplate}` to `{outputFile}`
 - Initialize frontmatter with proper structure including inputDocuments array.
 
 #### C. Present Initialization Results
@@ -138,7 +151,7 @@ Display menu after setup report:
 
 #### Menu Handling Logic:
 
-- IF C: Update output file frontmatter, adding this step name to the end of the list of stepsCompleted, then read fully and follow: ./step-02-discovery.md
+- IF C: Update output file frontmatter, adding this step name to the end of the list of stepsCompleted, then read fully and follow: {nextStepFile}
 - IF user provides additional files: Load them, update inputDocuments and documentCounts, redisplay report
 - IF user asks questions: Answer and redisplay menu
 
@@ -149,7 +162,7 @@ Display menu after setup report:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [frontmatter properly updated with this step added to stepsCompleted and documentCounts], will you then read fully and follow: `./step-02-discovery.md` to begin project discovery.
+ONLY WHEN [C continue option] is selected and [frontmatter properly updated with this step added to stepsCompleted and documentCounts], will you then read fully and follow: `{nextStepFile}` to begin project discovery.
 
 ---
 

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

@@ -1,3 +1,11 @@
+---
+name: 'step-01b-continue'
+description: 'Resume an interrupted PRD workflow from the last completed step'
+
+# File References
+outputFile: '{planning_artifacts}/prd.md'
+---
+
 # Step 1B: Workflow Continuation
 
 ## STEP GOAL:
@@ -62,38 +70,21 @@ Review the frontmatter to understand:
 
 ### 3. Determine Next Step
 
-**Step Sequence Lookup:**
-
-Use the following ordered sequence to determine the next step from the last completed step:
-
-| Last Completed | Next Step |
-|---|---|
-| step-01-init.md | step-02-discovery.md |
-| step-02-discovery.md | step-02b-vision.md |
-| step-02b-vision.md | step-02c-executive-summary.md |
-| step-02c-executive-summary.md | step-03-success.md |
-| step-03-success.md | step-04-journeys.md |
-| step-04-journeys.md | step-05-domain.md |
-| step-05-domain.md | step-06-innovation.md |
-| step-06-innovation.md | step-07-project-type.md |
-| step-07-project-type.md | step-08-scoping.md |
-| step-08-scoping.md | step-09-functional.md |
-| step-09-functional.md | step-10-nonfunctional.md |
-| step-10-nonfunctional.md | step-11-polish.md |
-| step-11-polish.md | step-12-complete.md |
-
-1. Get the last element from the `stepsCompleted` array
-2. Look it up in the table above to find the next step
-3. That's the next step to load!
+**Simplified Next Step Logic:**
+1. Get the last element from the `stepsCompleted` array (this is the filename of the last completed step, e.g., "step-03-success.md")
+2. Load that step file and read its frontmatter
+3. Extract the `nextStepFile` value from the frontmatter
+4. That's the next step to load!
 
 **Example:**
 - If `stepsCompleted = ["step-01-init.md", "step-02-discovery.md", "step-03-success.md"]`
 - Last element is `"step-03-success.md"`
-- Table lookup → next step is `./step-04-journeys.md`
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md`, read its frontmatter
+- Read fully and follow: `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md`
 
 ### 4. Handle Workflow Completion
 
-**If `stepsCompleted` array contains `"step-12-complete.md"`:**
+**If `stepsCompleted` array contains `"step-11-complete.md"`:**
 "Great news! It looks like we've already completed the PRD workflow for {{project_name}}.
 
 The final document is ready at `{outputFile}` with all sections completed.
@@ -113,7 +104,7 @@ What would be most helpful?"
 
 **Current Progress:**
 - Last completed: {last step filename from stepsCompleted array}
-- Next up: {next step from lookup table}
+- Next up: {nextStepFile determined from that step's frontmatter}
 - Context documents available: {len(inputDocuments)} files
 
 **Document Status:**
@@ -128,7 +119,7 @@ Display: "**Select an Option:** [C] Continue to {next step name}"
 
 #### Menu Handling Logic:
 
-- IF C: Read fully and follow the next step determined from the lookup table in step 3
+- IF C: Read fully and follow the {nextStepFile} determined in step 3
 - IF Any other comments or queries: respond and redisplay menu
 
 #### EXECUTION RULES:
@@ -138,7 +129,7 @@ Display: "**Select an Option:** [C] Continue to {next step name}"
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [current state confirmed], will you then read fully and follow the next step (from the lookup table) to resume the workflow.
+ONLY WHEN [C continue option] is selected and [current state confirmed], will you then read fully and follow: {nextStepFile} to resume the workflow.
 
 ---
 
@@ -155,7 +146,7 @@ ONLY WHEN [C continue option] is selected and [current state confirmed], will yo
 
 - Discovering new input documents instead of reloading existing ones
 - Modifying content from already completed steps
-- Failing to determine the next step from the lookup table
+- Failing to extract nextStepFile from the last completed step's frontmatter
 - Proceeding without user confirmation of current state
 
 **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

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

@@ -1,3 +1,20 @@
+---
+name: 'step-02-discovery'
+description: 'Discover project type, domain, and context through collaborative dialogue'
+
+# File References
+nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02b-vision.md'
+outputFile: '{planning_artifacts}/prd.md'
+
+# Data Files
+projectTypesCSV: '../data/project-types.csv'
+domainComplexityCSV: '../data/domain-complexity.csv'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
+---
+
 # Step 2: Project Discovery
 
 **Progress: Step 2 of 13** - Next: Product Vision
@@ -16,7 +33,6 @@ Discover and classify the project - understand what type of product this is, wha
 - ✅ ALWAYS treat this as collaborative discovery between PM peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -80,7 +96,7 @@ Read the frontmatter from `{outputFile}` to get document counts:
 **Attempt subprocess data lookup:**
 
 **Project Type Lookup:**
-"Your task: Lookup data in ../data/project-types.csv
+"Your task: Lookup data in {projectTypesCSV}
 
 **Search criteria:**
 - Find row where project_type matches {{detectedProjectType}}
@@ -92,7 +108,7 @@ project_type, detection_signals
 **Do NOT return the entire CSV - only the matching row.**"
 
 **Domain Complexity Lookup:**
-"Your task: Lookup data in ../data/domain-complexity.csv
+"Your task: Lookup data in {domainComplexityCSV}
 
 **Search criteria:**
 - Find row where domain matches {{detectedDomain}}
@@ -169,9 +185,9 @@ Present the project classification for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Product Vision (Step 2b of 13)"
 
 #### Menu Handling Logic:
-- IF A: Invoke the `bmad-advanced-elicitation` skill with the current classification, process the enhanced insights that come back, ask user if they accept the improvements, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
-- IF P: Invoke the `bmad-party-mode` skill with the current classification, process the collaborative insights, ask user if they accept the changes, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
-- IF C: Save classification to {outputFile} frontmatter, add this step name to the end of stepsCompleted array, then read fully and follow: ./step-02b-vision.md
+- IF A: Read fully and follow: {advancedElicitationTask} with the current classification, process the enhanced insights that come back, ask user if they accept the improvements, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current classification, process the collaborative insights, ask user if they accept the changes, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
+- IF C: Save classification to {outputFile} frontmatter, add this step name to the end of stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:
@@ -181,7 +197,7 @@ Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Pr
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [classification saved to frontmatter], will you then read fully and follow: `./step-02b-vision.md` to explore product vision.
+ONLY WHEN [C continue option] is selected and [classification saved to frontmatter], will you then read fully and follow: `{nextStepFile}` to explore product vision.
 
 ---
 

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

@@ -1,3 +1,16 @@
+---
+name: 'step-02b-vision'
+description: 'Discover the product vision and differentiator through collaborative dialogue'
+
+# File References
+nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02c-executive-summary.md'
+outputFile: '{planning_artifacts}/prd.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
+---
+
 # Step 2b: Product Vision Discovery
 
 **Progress: Step 2b of 13** - Next: Executive Summary
@@ -16,7 +29,6 @@ Discover what makes this product special and understand the product vision throu
 - ✅ ALWAYS treat this as collaborative discovery between PM peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -101,9 +113,9 @@ Present your understanding of the product vision for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Executive Summary (Step 2c of 13)"
 
 #### Menu Handling Logic:
-- IF A: Invoke the `bmad-advanced-elicitation` skill with the current vision insights, process the enhanced insights that come back, ask user if they accept the improvements, if yes update understanding then redisplay menu, if no keep original understanding then redisplay menu
-- IF P: Invoke the `bmad-party-mode` skill with the current vision insights, process the collaborative insights, ask user if they accept the changes, if yes update understanding then redisplay menu, if no keep original understanding then redisplay menu
-- IF C: Update {outputFile} frontmatter by adding this step name to the end of stepsCompleted array, then read fully and follow: ./step-02c-executive-summary.md
+- IF A: Read fully and follow: {advancedElicitationTask} with the current vision insights, process the enhanced insights that come back, ask user if they accept the improvements, if yes update understanding then redisplay menu, if no keep original understanding then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current vision insights, process the collaborative insights, ask user if they accept the changes, if yes update understanding then redisplay menu, if no keep original understanding then redisplay menu
+- IF C: Update {outputFile} frontmatter by adding this step name to the end of stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:
@@ -113,7 +125,7 @@ Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Ex
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [stepsCompleted updated], will you then read fully and follow: `./step-02c-executive-summary.md` to generate the Executive Summary.
+ONLY WHEN [C continue option] is selected and [stepsCompleted updated], will you then read fully and follow: `{nextStepFile}` to generate the Executive Summary.
 
 ---
 

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

@@ -1,3 +1,16 @@
+---
+name: 'step-02c-executive-summary'
+description: 'Generate and append the Executive Summary section to the PRD document'
+
+# File References
+nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md'
+outputFile: '{planning_artifacts}/prd.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
+---
+
 # Step 2c: Executive Summary Generation
 
 **Progress: Step 2c of 13** - Next: Success Criteria
@@ -16,7 +29,6 @@ Generate the Executive Summary content using insights from classification (step
 - ✅ ALWAYS treat this as collaborative discovery between PM peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -91,9 +103,9 @@ Present the executive summary content for user review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Success Criteria (Step 3 of 13)"
 
 #### Menu Handling Logic:
-- IF A: Invoke the `bmad-advanced-elicitation` skill with the current executive summary content, process the enhanced content that comes back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu
-- IF P: Invoke the `bmad-party-mode` skill with the current executive summary content, process the collaborative improvements, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
-- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: ./step-03-success.md
+- IF A: Read fully and follow: {advancedElicitationTask} with the current executive summary content, process the enhanced content that comes back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current executive summary content, process the collaborative improvements, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:
@@ -126,7 +138,7 @@ Where:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [content appended to document], will you then read fully and follow: `./step-03-success.md` to define success criteria.
+ONLY WHEN [C continue option] is selected and [content appended to document], will you then read fully and follow: `{nextStepFile}` to define success criteria.
 
 ---
 

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

@@ -1,3 +1,16 @@
+---
+name: 'step-03-success'
+description: 'Define comprehensive success criteria covering user, business, and technical success'
+
+# File References
+nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md'
+outputFile: '{planning_artifacts}/prd.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
+---
+
 # Step 3: Success Criteria Definition
 
 **Progress: Step 3 of 11** - Next: User Journey Mapping
@@ -13,7 +26,6 @@
 - 💬 FOCUS on defining what winning looks like for this product
 - 🎯 COLLABORATIVE discovery, not assumption-based goal setting
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -163,9 +175,9 @@ Present the success criteria content for user review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to User Journey Mapping (Step 4 of 11)"
 
 #### Menu Handling Logic:
-- IF A: Invoke the `bmad-advanced-elicitation` skill with the current success criteria content, process the enhanced success metrics that come back, ask user "Accept these improvements to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF P: Invoke the `bmad-party-mode` skill with the current success criteria, process the collaborative improvements to metrics and scope, ask user "Accept these changes to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: ./step-04-journeys.md
+- IF A: Read fully and follow: {advancedElicitationTask} with the current success criteria content, process the enhanced success metrics that come back, ask user "Accept these improvements to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current success criteria, process the collaborative improvements to metrics and scope, ask user "Accept these changes to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:
@@ -209,6 +221,6 @@ If working in regulated domains (healthcare, fintech, govtech):
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `./step-04-journeys.md` to map user journeys.
+After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md` to map user journeys.
 
 Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!