External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

The install directory is now configurable, with a few minute issues

Browse Source
This commit is contained in:
Brian Madison
2025-11-08 13:58:43 -06:00
parent a4bbfc4b6e
commit 1728acfb0f
224 changed files with 1303 additions and 1036 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
src/modules/bmm/_module-installer/install-config.yaml
View File

@@ -14,17 +14,14 @@ prompt:
## communication_language
## output_folder
## bmad_folder
## install_user_docs
## kb_install
project_name:
prompt: "What is the title of your project you will be working on?"
default: "{directory_name}"
result: "{value}"
include_game_planning:
prompt: "Include Game Planning Agents and Workflows?"
default: false
result: "{value}"
user_skill_level:
prompt:
- "What is your technical experience level?"
@@ -42,29 +39,19 @@ user_skill_level:
tech_docs:
prompt: "Where is Technical Documentation located within the project?"
default: "docs"
default: "{output_folder}/technical"
result: "{project-root}/{value}"
dev_story_location:
prompt: "Where should development stories be stored?"
default: "docs/stories"
dev_ephemeral_location:
prompt: "Where should ephemeral development artifacts be stored (stories, epics, temp context, etc...)?"
default: "{bmad_folder}-ephemeral"
result: "{project-root}/{value}"
install_user_docs:
prompt: "Install user documentation to project directory?"
default: true
result: "{value}"
# TEA Agent Configuration
tea_use_mcp_enhancements:
prompt: "Enable Playwright MCP capabilities (healing, exploratory, verification)?"
prompt: "Enable Test Architect Playwright MCP capabilities (healing, exploratory, verification)?"
default: false
result: "{value}"
# kb_location:
# prompt: "Where should bmad knowledge base articles be stored?"
# default: "~/bmad/bmm/kb.md"
# result: "{value}"
# desired_mcp_tools:
# prompt:
# - "Which MCP Tools will you be using? (Select all that apply)"

4
src/modules/bmm/_module-installer/installer.js
View File

@@ -63,9 +63,9 @@ async function install(options) {
}
// Create dev story location if configured
if (config['dev_story_location']) {
if (config['dev_ephemeral_location']) {
// Strip {project-root}/ prefix if present
const storyConfig = config['dev_story_location'].replace('{project-root}/', '');
const storyConfig = config['dev_ephemeral_location'].replace('{project-root}/', '');
const storyPath = path.join(projectRoot, storyConfig);
if (!(await fs.pathExists(storyPath))) {
logger.log(chalk.yellow(`Creating story directory: ${storyConfig}`));

14
src/modules/bmm/agents/analyst.agent.yaml
View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmm/agents/analyst.md
id: "{bmad_folder}/bmm/agents/analyst.md"
name: Mary
title: Business Analyst
icon: 📊
@@ -19,25 +19,25 @@ agent:
menu:
- trigger: workflow-init
workflow: "{project-root}/bmad/bmm/workflows/workflow-status/init/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml"
description: Start a new sequenced workflow path
- trigger: workflow-status
workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
description: Check workflow status and get recommendations (START HERE!)
- trigger: brainstorm-project
workflow: "{project-root}/bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml"
description: Guide me through Brainstorming
- trigger: product-brief
workflow: "{project-root}/bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/workflow.yaml"
description: Produce Project Brief
- trigger: document-project
workflow: "{project-root}/bmad/bmm/workflows/document-project/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
description: Generate comprehensive documentation of an existing Project
- trigger: research
workflow: "{project-root}/bmad/bmm/workflows/1-analysis/research/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml"
description: Guide me through Research

12
src/modules/bmm/agents/architect.agent.yaml
View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmm/agents/architect.md
id: "{bmad_folder}/bmm/agents/architect.md"
name: Winston
title: Architect
icon: 🏗️
@@ -19,19 +19,19 @@ agent:
menu:
- trigger: workflow-status
workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
description: Check workflow status and get recommendations
- trigger: create-architecture
workflow: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.yaml"
description: Produce a Scale Adaptive Architecture
- trigger: validate-architecture
validate-workflow: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml"
checklist: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture/checklist.md"
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.yaml"
checklist: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/checklist.md"
document: "{output_folder}/architecture.md"
description: Validate Architecture Document
- trigger: solutioning-gate-check
workflow: "{project-root}/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml"
description: Validate solutioning complete, ready for Phase 4 (Level 2-4 only)

10
src/modules/bmm/agents/dev.agent.yaml
View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmm/agents/dev.md
id: "{bmad_folder}/bmm/agents/dev.md"
name: Amelia
title: Developer Agent
icon: 💻
@@ -27,17 +27,17 @@ agent:
menu:
- trigger: workflow-status
workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
description: "Check workflow status and get recommendations"
- trigger: develop-story
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story/workflow.yaml"
description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
- trigger: story-done
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/story-done/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done/workflow.yaml"
description: "Mark story done after DoD complete"
- trigger: code-review
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml"
description: "Perform a thorough clean context QA code review on a story flagged Ready for Review"

22
src/modules/bmm/agents/pm.agent.yaml
View File

@@ -3,7 +3,7 @@
agent:
metadata:
id: bmad/bmm/agents/pm.md
id: "{bmad_folder}/bmm/agents/pm.md"
name: John
title: Product Manager
icon: 📋
@@ -24,37 +24,37 @@ agent:
# help and exit are auto-injected, don't define them here
menu:
- trigger: workflow-init
workflow: "{project-root}/bmad/bmm/workflows/workflow-status/init/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml"
description: Start a new sequenced workflow path
- trigger: workflow-status
workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
description: Check workflow status and get recommendations (START HERE!)
- trigger: create-prd
workflow: "{project-root}/bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/workflow.yaml"
description: Create Product Requirements Document (PRD) for Level 2-4 projects
- trigger: create-epics-and-stories
workflow: "{project-root}/bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml"
description: Break PRD requirements into implementable epics and stories
- trigger: validate-prd
validate-workflow: "{project-root}/bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml"
checklist: "{project-root}/bmad/bmm/workflows/2-plan-workflows/prd/checklist.md"
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/workflow.yaml"
checklist: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/checklist.md"
document: "{output_folder}/PRD.md"
description: Validate PRD + Epics + Stories completeness and quality
- trigger: tech-spec
workflow: "{project-root}/bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml"
description: Create Tech Spec for Level 0-1 (sometimes Level 2) projects
- trigger: validate-tech-spec
validate-workflow: "{project-root}/bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml"
checklist: "{project-root}/bmad/bmm/workflows/2-plan-workflows/tech-spec/checklist.md"
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml"
checklist: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/checklist.md"
document: "{output_folder}/tech-spec.md"
description: Validate Technical Specification Document
- trigger: correct-course
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
description: Course Correction Analysis

26
src/modules/bmm/agents/sm.agent.yaml
View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmm/agents/sm.md
id: "{bmad_folder}/bmm/agents/sm.md"
name: Bob
title: Scrum Master
icon: 🏃
@@ -22,46 +22,46 @@ agent:
menu:
- trigger: workflow-status
workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
description: Check workflow status and get recommendations
- trigger: sprint-planning
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
description: Generate or update sprint-status.yaml from epic files
- trigger: epic-tech-context
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
description: (Optional) Use the PRD and Architecture to create a Epic-Tech-Spec for a specific epic
- trigger: validate-epic-tech-context
validate-workflow: "{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
description: (Optional) Validate latest Tech Spec against checklist
- trigger: create-story
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml"
description: Create a Draft Story
- trigger: validate-create-story
validate-workflow: "{project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml"
description: (Optional) Validate Story Draft with Independent Review
- trigger: story-context
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/story-context/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context/workflow.yaml"
description: (Optional) Assemble dynamic Story Context (XML) from latest docs and code and mark story ready for dev
- trigger: validate-story-context
validate-workflow: "{project-root}/bmad/bmm/workflows/4-implementation/story-context/workflow.yaml"
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context/workflow.yaml"
description: (Optional) Validate latest Story Context XML against checklist
- trigger: story-ready-for-dev
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready/workflow.yaml"
description: (Optional) Mark drafted story ready for dev without generating Story Context
- trigger: epic-retrospective
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
data: "{project-root}/bmad/_cfg/agent-manifest.csv"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml"
data: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
description: (Optional) Facilitate team retrospective after an epic is completed
- trigger: correct-course
workflow: "{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
description: (Optional) Execute correct-course task

26
src/modules/bmm/agents/tea.agent.yaml
View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmm/agents/tea.md
id: "{bmad_folder}/bmm/agents/tea.md"
name: Murat
title: Master Test Architect
icon: 🧪
@@ -17,43 +17,43 @@ agent:
- Testing is feature work. Prioritize unit/integration over E2E. Flakiness is critical debt. ATDD tests first, AI implements, suite validates.
critical_actions:
- "Consult {project-root}/bmad/bmm/testarch/tea-index.csv to select knowledge fragments under `knowledge/` and load only the files needed for the current task"
- "Load the referenced fragment(s) from `{project-root}/bmad/bmm/testarch/knowledge/` before giving recommendations"
- "Cross-check recommendations with the current official Playwright, Cypress, Pact, and CI platform documentation; fall back to {project-root}/bmad/bmm/testarch/test-resources-for-ai-flat.txt only when deeper sourcing is required"
- "Consult {project-root}/{bmad_folder}/bmm/testarch/tea-index.csv to select knowledge fragments under `knowledge/` and load only the files needed for the current task"
- "Load the referenced fragment(s) from `{project-root}/{bmad_folder}/bmm/testarch/knowledge/` before giving recommendations"
- "Cross-check recommendations with the current official Playwright, Cypress, Pact, and CI platform documentation; fall back to {project-root}/{bmad_folder}/bmm/testarch/test-resources-for-ai-flat.txt only when deeper sourcing is required"
menu:
- trigger: workflow-status
workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
description: Check workflow status and get recommendations
- trigger: framework
workflow: "{project-root}/bmad/bmm/workflows/testarch/framework/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/framework/workflow.yaml"
description: Initialize production-ready test framework architecture
- trigger: atdd
workflow: "{project-root}/bmad/bmm/workflows/testarch/atdd/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/atdd/workflow.yaml"
description: Generate E2E tests first, before starting implementation
- trigger: automate
workflow: "{project-root}/bmad/bmm/workflows/testarch/automate/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/automate/workflow.yaml"
description: Generate comprehensive test automation
- trigger: test-design
workflow: "{project-root}/bmad/bmm/workflows/testarch/test-design/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-design/workflow.yaml"
description: Create comprehensive test scenarios
- trigger: trace
workflow: "{project-root}/bmad/bmm/workflows/testarch/trace/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/trace/workflow.yaml"
description: Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)
- trigger: nfr-assess
workflow: "{project-root}/bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/nfr-assess/workflow.yaml"
description: Validate non-functional requirements
- trigger: ci
workflow: "{project-root}/bmad/bmm/workflows/testarch/ci/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/ci/workflow.yaml"
description: Scaffold CI/CD quality pipeline
- trigger: test-review
workflow: "{project-root}/bmad/bmm/workflows/testarch/test-review/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-review/workflow.yaml"
description: Review test quality using comprehensive knowledge base and best practices

6
src/modules/bmm/agents/tech-writer.agent.yaml
View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmm/agents/tech-writer.md
id: "{bmad_folder}/bmm/agents/tech-writer.md"
name: paige
title: Technical Writer
icon: 📚
@@ -20,7 +20,7 @@ agent:
critical_actions:
- "CRITICAL: Load COMPLETE file {project-root}/src/modules/bmm/workflows/techdoc/documentation-standards.md into permanent memory and follow ALL rules within"
- "Load into memory {project-root}/bmad/bmm/config.yaml and set variables"
- "Load into memory {project-root}/{bmad_folder}/bmm/config.yaml and set variables"
- "Remember the user's name is {user_name}"
- "ALWAYS communicate in {communication_language}"
- "ALWAYS write documentation in {document_output_language}"
@@ -29,7 +29,7 @@ agent:
menu:
- trigger: document-project
workflow: "{project-root}/bmad/bmm/workflows/document-project/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
description: Comprehensive project documentation (brownfield analysis, architecture scanning)
- trigger: create-api-docs

10
src/modules/bmm/agents/ux-designer.agent.yaml
View File

@@ -2,7 +2,7 @@
agent:
metadata:
id: bmad/bmm/agents/ux-designer.md
id: "{bmad_folder}/bmm/agents/ux-designer.md"
name: Sally
title: UX Designer
icon: 🎨
@@ -19,15 +19,15 @@ agent:
menu:
- trigger: workflow-status
workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
description: Check workflow status and get recommendations (START HERE!)
- trigger: create-design
workflow: "{project-root}/bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
description: Conduct Design Thinking Workshop to Define the User Specification
- trigger: validate-design
validate-workflow: "{project-root}/bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
checklist: "{project-root}/bmad/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
checklist: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
document: "{output_folder}/ux-spec.md"
description: Validate UX Specification and Design Artifacts

8
src/modules/bmm/docs/agents-guide.md
View File

@@ -629,14 +629,14 @@ You can customize any agent's personality without modifying core agent files.
### Location
**Customization Directory:** `{project-root}/bmad/_cfg/agents/`
**Customization Directory:** `{project-root}/{bmad_folder}/_cfg/agents/`
**Naming Convention:** `{module}-{agent-name}.customize.yaml`
**Examples:**
```
bmad/_cfg/agents/
{bmad_folder}/_cfg/agents/
├── bmm-pm.customize.yaml
├── bmm-dev.customize.yaml
├── cis-storyteller.customize.yaml
@@ -736,9 +736,9 @@ Other agents collaborate with PM's specialized perspective.
```bash
# Create customization file at:
# {project-root}/bmad/_cfg/agents/{module}-{agent-name}.customize.yaml
# {project-root}/{bmad_folder}/_cfg/agents/{module}-{agent-name}.customize.yaml
# Example: bmad/_cfg/agents/bmm-pm.customize.yaml
# Example: {bmad_folder}/_cfg/agents/bmm-pm.customize.yaml
```
**Step 2: Regenerate Agent Manifest**

8
src/modules/bmm/docs/brownfield-guide.md
View File

@@ -137,7 +137,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections):
```bash
# Load BMad Master or any agent
bmad/core/tools/shard-doc.xml --input docs/massive-doc.md
{bmad_folder}/core/tools/shard-doc.xml --input docs/massive-doc.md
```
- Splits on level 2 sections by default
@@ -147,7 +147,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections):
2. **Then:** Run `index-docs` task to create navigation:
```bash
bmad/core/tasks/index-docs.xml --directory ./docs
{bmad_folder}/core/tasks/index-docs.xml --directory ./docs
```
3. **Finally:** Validate quality - if sharded docs still seem incomplete/outdated → Run `document-project`
@@ -210,7 +210,7 @@ If you have **good, current documentation** but it's in massive files:
```bash
# For each massive doc (>500 lines or 10+ level 2 sections)
bmad/core/tools/shard-doc.xml \
{bmad_folder}/core/tools/shard-doc.xml \
--input docs/api-documentation.md \
--output docs/api/ \
--level 2 # Split on ## headers (default)
@@ -219,7 +219,7 @@ bmad/core/tools/shard-doc.xml \
**Step 2: Generate index**
```bash
bmad/core/tasks/index-docs.xml --directory ./docs
{bmad_folder}/core/tasks/index-docs.xml --directory ./docs
```
**Step 3: Validate**

6
src/modules/bmm/docs/enterprise-agentic-development.md
View File

@@ -419,7 +419,7 @@ Team C (2 devs): Analytics feature (3 epics)
**Problem:** Teams customize BMad (agents, workflows, configs) but don't want personal tooling in main repo.
**Anti-pattern:** Adding `bmad/` to `.gitignore` breaks IDE tools, submodule management.
**Anti-pattern:** Adding `{bmad_folder}/` to `.gitignore` breaks IDE tools, submodule management.
### The Solution: Git Submodules
@@ -457,7 +457,7 @@ git commit -m "Add BMM as submodule"
git clone https://github.com/your-org/your-project.git
cd your-project
git submodule update --init --recursive
# Make personal customizations in bmad/
# Make personal customizations in {bmad_folder}/
```
### Daily Workflow
@@ -466,7 +466,7 @@ git submodule update --init --recursive
```bash
cd /path/to/your-project
# BMad available at ./bmad/, load agents normally
# BMad available at ./{bmad_folder}/, load agents normally
```
**Update personal config:**

2
src/modules/bmm/docs/faq.md
View File

@@ -403,7 +403,7 @@ See [IDE Setup Guides](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/do
### Q: Can I customize agents?
**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `bmad/_cfg/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `{bmad_folder}/_cfg/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
**Note:** While source agents in this repo are YAML, they install as `.md` files with XML-style tags - a format any LLM can read and follow.

6
src/modules/bmm/docs/party-mode.md
View File

@@ -27,7 +27,7 @@ Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent), and su
**The basics:**
1. Party mode reads `bmad/_cfg/agent-manifest.csv`
1. Party mode reads `{bmad_folder}/_cfg/agent-manifest.csv`
2. Loads ALL installed agents (already includes your customizations from install)
3. BMad Master orchestrates - picks 2-3 relevant agents per message based on topic
4. Agents respond in character, can agree/disagree/build on each other's ideas
@@ -126,11 +126,11 @@ _(Multiple perspectives reveal the right answer)_
## Agent Customization
Party mode uses agents from `bmad/[module]/agents/*.md` - these already include any customizations you applied during install.
Party mode uses agents from `{bmad_folder}/[module]/agents/*.md` - these already include any customizations you applied during install.
**To customize agents for party mode:**
1. Create customization file: `bmad/_cfg/agents/bmm-pm.customize.yaml`
1. Create customization file: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
2. Run `npx bmad-method install` to rebuild agents
3. Customizations now active in party mode

2
src/modules/bmm/docs/quick-start.md
View File

@@ -29,7 +29,7 @@ BMad Method (BMM) helps you build software through guided workflows with special
npx bmad-method@alpha install
```
The interactive installer will guide you through setup and create a `bmad/` folder with all agents and workflows.
The interactive installer will guide you through setup and create a `{bmad_folder}/` folder with all agents and workflows.
---

2
src/modules/bmm/docs/test-architecture.md
View File

@@ -374,7 +374,7 @@ MCP provides additional capabilities on top of TEA's default AI-based approach:
}
```
**To disable**: Set `tea_use_mcp_enhancements: false` in `bmad/bmm/config.yaml` OR remove MCPs from IDE config.
**To disable**: Set `tea_use_mcp_enhancements: false` in `{bmad_folder}/bmm/config.yaml` OR remove MCPs from IDE config.
</details>

2
src/modules/bmm/docs/workflow-document-project-reference.md
View File

@@ -179,7 +179,7 @@ The workflow uses a single comprehensive CSV file:
**documentation-requirements.csv** - Complete project analysis guide
- Location: `/bmad/bmm/workflows/document-project/documentation-requirements.csv`
- Location: `/{bmad_folder}/bmm/workflows/document-project/documentation-requirements.csv`
- 12 project types (web, mobile, backend, cli, library, desktop, game, data, extension, infra, embedded)
- 24 columns combining:
- **Detection columns**: `project_type_id`, `key_file_patterns` (identifies project type from codebase)

44
src/modules/bmm/sub-modules/claude-code/injections.yaml
View File

@@ -4,16 +4,16 @@
#
# The installer will:
# 1. Ask users if they want to install subagents (all/selective/none)
# 2. Ask where to install (project-level .claude/agents/bmad/ or user-level ~/.claude/agents/bmad/)
# 2. Ask where to install (project-level .claude/agents/{bmad_folder}/ or user-level ~/.claude/agents/{bmad_folder}/)
# 3. Only inject content related to selected subagents
# 4. Templates stay in bmad/ directory and are referenced from there
# 4. Templates stay in {bmad_folder}/ directory and are referenced from there
# 5. Injections are placed at specific sections where each subagent is most valuable
injections:
# ===== PRD WORKFLOW INJECTIONS =====
# PRD Subagent Instructions
- file: "bmad/bmm/workflows/prd/instructions.md"
- file: "{bmad_folder}/bmm/workflows/prd/instructions.md"
point: "prd-subagent-instructions"
requires: "all-prd-subagents"
content: |
@@ -25,7 +25,7 @@ injections:
- <CRITICAL>Use `bmm-technical-decisions-curator` to capture all technical mentions</CRITICAL>
# PRD Requirements Analysis
- file: "bmad/bmm/workflows/prd/instructions.md"
- file: "{bmad_folder}/bmm/workflows/prd/instructions.md"
point: "prd-requirements-analysis"
requires: "requirements-analyst"
content: |
@@ -33,7 +33,7 @@ injections:
**Subagent Hint**: Use `bmm-requirements-analyst` to validate requirements are testable and complete.
# PRD User Journey Mapping
- file: "bmad/bmm/workflows/prd/instructions.md"
- file: "{bmad_folder}/bmm/workflows/prd/instructions.md"
point: "prd-user-journey"
requires: "user-journey-mapper"
content: |
@@ -41,7 +41,7 @@ injections:
**Subagent Hint**: Use `bmm-user-journey-mapper` to map all user types and their value paths.
# PRD Epic Optimization
- file: "bmad/bmm/workflows/prd/instructions.md"
- file: "{bmad_folder}/bmm/workflows/prd/instructions.md"
point: "prd-epic-optimization"
requires: "epic-optimizer"
content: |
@@ -49,7 +49,7 @@ injections:
**Subagent Hint**: Use `bmm-epic-optimizer` to validate epic boundaries deliver coherent value.
# PRD Document Review
- file: "bmad/bmm/workflows/prd/instructions.md"
- file: "{bmad_folder}/bmm/workflows/prd/instructions.md"
point: "prd-checklist-review"
requires: "document-reviewer"
content: |
@@ -57,7 +57,7 @@ injections:
**Subagent Hint**: Use `bmm-document-reviewer` to validate PRD completeness before finalizing.
# Technical Decisions Curator
- file: "bmad/bmm/workflows/prd/instructions.md"
- file: "{bmad_folder}/bmm/workflows/prd/instructions.md"
point: "technical-decisions-curator"
requires: "technical-decisions-curator"
content: |
@@ -71,7 +71,7 @@ injections:
# ===== MARKET RESEARCH TEMPLATE INJECTIONS =====
# Market TAM/SAM/SOM Calculations
- file: "bmad/bmm/templates/market.md"
- file: "{bmad_folder}/bmm/templates/market.md"
point: "market-tam-calculations"
requires: "data-analyst"
content: |
@@ -82,7 +82,7 @@ injections:
</llm>
# Market Trends Analysis
- file: "bmad/bmm/templates/market.md"
- file: "{bmad_folder}/bmm/templates/market.md"
point: "market-trends-analysis"
requires: "trend-spotter"
content: |
@@ -93,7 +93,7 @@ injections:
</llm>
# Market Customer Personas
- file: "bmad/bmm/templates/market.md"
- file: "{bmad_folder}/bmm/templates/market.md"
point: "market-customer-segments"
requires: "user-researcher"
content: |
@@ -104,7 +104,7 @@ injections:
</llm>
# Market Research Review
- file: "bmad/bmm/templates/market.md"
- file: "{bmad_folder}/bmm/templates/market.md"
point: "market-executive-summary"
requires: "document-reviewer"
content: |
@@ -116,7 +116,7 @@ injections:
# ===== COMPETITOR ANALYSIS TEMPLATE INJECTIONS =====
# Competitor Intelligence Gathering
- file: "bmad/bmm/templates/competitor.md"
- file: "{bmad_folder}/bmm/templates/competitor.md"
point: "competitor-intelligence"
requires: "market-researcher"
content: |
@@ -127,7 +127,7 @@ injections:
</llm>
# Competitor Technical Analysis
- file: "bmad/bmm/templates/competitor.md"
- file: "{bmad_folder}/bmm/templates/competitor.md"
point: "competitor-tech-stack"
requires: "technical-evaluator"
content: |
@@ -138,7 +138,7 @@ injections:
</llm>
# Competitor Metrics Analysis
- file: "bmad/bmm/templates/competitor.md"
- file: "{bmad_folder}/bmm/templates/competitor.md"
point: "competitor-metrics"
requires: "data-analyst"
content: |
@@ -148,7 +148,7 @@ injections:
</llm>
# Competitor Analysis Review
- file: "bmad/bmm/templates/competitor.md"
- file: "{bmad_folder}/bmm/templates/competitor.md"
point: "competitor-executive-summary"
requires: "document-reviewer"
content: |
@@ -160,7 +160,7 @@ injections:
# ===== PROJECT BRIEF TEMPLATE INJECTIONS =====
# Brief Problem Validation
- file: "bmad/bmm/templates/brief.md"
- file: "{bmad_folder}/bmm/templates/brief.md"
point: "brief-problem-validation"
requires: "market-researcher"
content: |
@@ -170,7 +170,7 @@ injections:
</llm>
# Brief Target User Analysis
- file: "bmad/bmm/templates/brief.md"
- file: "{bmad_folder}/bmm/templates/brief.md"
point: "brief-user-analysis"
requires: "user-researcher"
content: |
@@ -180,7 +180,7 @@ injections:
</llm>
# Brief Success Metrics
- file: "bmad/bmm/templates/brief.md"
- file: "{bmad_folder}/bmm/templates/brief.md"
point: "brief-success-metrics"
requires: "data-analyst"
content: |
@@ -190,7 +190,7 @@ injections:
</llm>
# Brief Technical Feasibility
- file: "bmad/bmm/templates/brief.md"
- file: "{bmad_folder}/bmm/templates/brief.md"
point: "brief-technical-feasibility"
requires: "technical-evaluator"
content: |
@@ -200,7 +200,7 @@ injections:
</llm>
# Brief Requirements Extraction
- file: "bmad/bmm/templates/brief.md"
- file: "{bmad_folder}/bmm/templates/brief.md"
point: "brief-requirements"
requires: "requirements-analyst"
content: |
@@ -210,7 +210,7 @@ injections:
</llm>
# Brief Document Review
- file: "bmad/bmm/templates/brief.md"
- file: "{bmad_folder}/bmm/templates/brief.md"
point: "brief-final-review"
requires: "document-reviewer"
content: |

2
src/modules/bmm/sub-modules/claude-code/readme.md
View File

@@ -84,4 +84,4 @@ To test subagent installation:
2. Select BMM module and Claude Code
3. Verify prompts appear for subagent selection
4. Check `.claude/agents/` for installed subagents
5. Verify injection points are replaced in `.claude/commands/bmad/` and the various tasks and templates under `bmad/...`
5. Verify injection points are replaced in `.claude/commands/{bmad_folder}/` and the various tasks and templates under `{bmad_folder}/...`

4
src/modules/bmm/tasks/daily-standup.xml
View File

@@ -1,4 +1,4 @@
<task id="bmad/bmm/tasks/daily-standup.xml" name="Daily Standup">
<task id="{bmad_folder}/bmm/tasks/daily-standup.xml" name="Daily Standup">
<llm critical="true">
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
<i>DO NOT skip steps or change the sequence</i>
@@ -26,7 +26,7 @@
- Blockers: {{blockers-from-story}}
Team assembled based on story participants:
{{ List Agents from {project-root}/bmad/_cfg/agent-manifest.csv }}
{{ List Agents from {project-root}/{bmad_folder}/_cfg/agent-manifest.csv }}
</output>
</step>

2
src/modules/bmm/workflows/1-analysis/brainstorm-project/instructions.md
View File

@@ -1,7 +1,7 @@
# Brainstorm Project - Workflow Instructions
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with project-specific context</critical>

16
src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Facilitate project brainstorming sessions by orchestrating the CIS
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ user_skill_level: "{config_source}:user_skill_level"
date: system-generated
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/brainstorm-project"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project"
template: false
instructions: "{installed_path}/instructions.md"
@@ -21,7 +21,7 @@ instructions: "{installed_path}/instructions.md"
project_context: "{installed_path}/project-context.md"
# CORE brainstorming workflow to invoke
core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
core_brainstorming: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
standalone: true
@@ -29,11 +29,11 @@ web_bundle:
name: "brainstorm-project"
description: "Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance."
author: "BMad"
instructions: "bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
instructions: "{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
template: false
web_bundle_files:
- "bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
- "bmad/bmm/workflows/1-analysis/brainstorm-project/project-context.md"
- "bmad/core/workflows/brainstorming/workflow.yaml"
- "{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/instructions.md"
- "{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/project-context.md"
- "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"
existing_workflows:
- core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"
- core_brainstorming: "{bmad_folder}/core/workflows/brainstorming/workflow.yaml"

2
src/modules/bmm/workflows/1-analysis/domain-research/instructions.md
View File

@@ -1,6 +1,6 @@
# Domain Research - Collaborative Domain Exploration
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This is COLLABORATIVE RESEARCH - engage the user as a partner, not just a data source</critical>
<critical>The goal is PRACTICAL UNDERSTANDING that directly informs requirements and architecture</critical>

16
src/modules/bmm/workflows/1-analysis/domain-research/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Collaborative exploration of domain-specific requirements, regulat
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ user_skill_level: "{config_source}:user_skill_level"
date: system-generated
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/domain-research"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/domain-research"
instructions: "{installed_path}/instructions.md"
template: "{installed_path}/template.md"
@@ -44,9 +44,9 @@ web_bundle:
description: "Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects"
author: "BMad"
# Core workflow files (bmad/-relative paths)
instructions: "bmad/bmm/workflows/1-analysis/domain-research/instructions.md"
template: "bmad/bmm/workflows/1-analysis/domain-research/template.md"
# Core workflow files ({bmad_folder}/-relative paths)
instructions: "{bmad_folder}/bmm/workflows/1-analysis/domain-research/instructions.md"
template: "{bmad_folder}/bmm/workflows/1-analysis/domain-research/template.md"
# Default configuration values (can be overridden during bundle setup)
defaults:
@@ -62,8 +62,8 @@ web_bundle:
# Complete file list - ALL files this workflow depends on
web_bundle_files:
# Core workflow files
- "bmad/bmm/workflows/1-analysis/domain-research/instructions.md"
- "bmad/bmm/workflows/1-analysis/domain-research/template.md"
- "{bmad_folder}/bmm/workflows/1-analysis/domain-research/instructions.md"
- "{bmad_folder}/bmm/workflows/1-analysis/domain-research/template.md"
# Task dependencies (referenced in instructions.md)
- "bmad/core/tasks/workflow.xml"
- "{bmad_folder}/core/tasks/workflow.xml"

2
src/modules/bmm/workflows/1-analysis/product-brief/instructions.md
View File

@@ -1,6 +1,6 @@
# Product Brief - Context-Adaptive Discovery Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow uses INTENT-DRIVEN FACILITATION - adapt organically to what emerges</critical>
<critical>The goal is DISCOVERING WHAT MATTERS through natural conversation, not filling a template</critical>

18
src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Interactive product brief creation workflow that guides users thro
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -34,7 +34,7 @@ input_file_patterns:
sharded: "{output_folder}/docs/index.md"
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/product-brief"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief"
template: "{installed_path}/template.md"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
@@ -48,14 +48,14 @@ web_bundle:
name: "product-brief"
description: "Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration"
author: "BMad"
instructions: "bmad/bmm/workflows/1-analysis/product-brief/instructions.md"
validation: "bmad/bmm/workflows/1-analysis/product-brief/checklist.md"
template: "bmad/bmm/workflows/1-analysis/product-brief/template.md"
instructions: "{bmad_folder}/bmm/workflows/1-analysis/product-brief/instructions.md"
validation: "{bmad_folder}/bmm/workflows/1-analysis/product-brief/checklist.md"
template: "{bmad_folder}/bmm/workflows/1-analysis/product-brief/template.md"
web_bundle_files:
# Core workflow files
- "bmad/bmm/workflows/1-analysis/product-brief/template.md"
- "bmad/bmm/workflows/1-analysis/product-brief/instructions.md"
- "bmad/bmm/workflows/1-analysis/product-brief/checklist.md"
- "{bmad_folder}/bmm/workflows/1-analysis/product-brief/template.md"
- "{bmad_folder}/bmm/workflows/1-analysis/product-brief/instructions.md"
- "{bmad_folder}/bmm/workflows/1-analysis/product-brief/checklist.md"
# Task dependencies (referenced in instructions.md)
- "bmad/core/tasks/workflow.xml"
- "{bmad_folder}/core/tasks/workflow.xml"

4
src/modules/bmm/workflows/1-analysis/research/instructions-deep-prompt.md
View File

@@ -1,6 +1,6 @@
# Deep Research Prompt Generator Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
<critical>This workflow generates structured research prompts optimized for AI platforms</critical>
@@ -211,7 +211,7 @@ Examples:
<template-output>special_requirements</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>

10
src/modules/bmm/workflows/1-analysis/research/instructions-market.md
View File

@@ -1,6 +1,6 @@
# Market Research Workflow Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
<critical>This is a HIGHLY INTERACTIVE workflow - collaborate with user throughout, don't just gather info and disappear</critical>
@@ -114,7 +114,7 @@ Work with the user to establish:
<action if="user_has_questions">Explore surprising data points together</action>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<template-output>sources_market_size</template-output>
</step>
@@ -239,7 +239,7 @@ For each major segment, research and define:
- Purchasing frequency
- Budget allocation
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<template-output>segment*profile*{{segment_number}}</template-output>
</step>
@@ -313,7 +313,7 @@ Use {{current_year}} in all searches.
<action if="user has follow-up questions">Dig deeper based on their interests</action>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<template-output>competitor*analysis*{{competitor_name}}</template-output>
</step>
@@ -437,7 +437,7 @@ For each opportunity:
- Risk assessment
- Success criteria
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<template-output>market_opportunities</template-output>
</step>

2
src/modules/bmm/workflows/1-analysis/research/instructions-router.md
View File

@@ -1,6 +1,6 @@
# Research Workflow Router Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate in {communication_language}, generate documents in {document_output_language}</critical>
<critical>Web research is ENABLED - always use current {{current_year}} data</critical>

8
src/modules/bmm/workflows/1-analysis/research/instructions-technical.md
View File

@@ -1,6 +1,6 @@
# Technical/Architecture Research Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
<critical>This is a HIGHLY INTERACTIVE workflow - make technical decisions WITH user, not FOR them</critical>
@@ -143,7 +143,7 @@ Each of these is popular for different reasons. Let me know if you want me to ex
</check>
</action>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<template-output>technology_options</template-output>
@@ -221,7 +221,7 @@ Each of these is popular for different reasons. Let me know if you want me to ex
- Training costs
- Total cost of ownership estimate
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<template-output>tech*profile*{{option_number}}</template-output>
</step>
@@ -392,7 +392,7 @@ Research and document:
- Contingency options if primary choice doesn't work
- Exit strategy considerations
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<template-output>recommendations</template-output>

28
src/modules/bmm/workflows/1-analysis/research/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Adaptive research workflow supporting multiple research types: mar
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -24,7 +24,7 @@ minimum_sources_per_claim: 2
fact_check_critical_data: true
# Workflow components - ROUTER PATTERN
installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/research"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research"
instructions: "{installed_path}/instructions-router.md" # Router loads specific instruction sets
validation: "{installed_path}/checklist.md"
@@ -47,16 +47,16 @@ web_bundle:
name: "research"
description: "Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis"
author: "BMad"
instructions: "bmad/bmm/workflows/1-analysis/research/instructions-router.md" # Router loads specific instruction sets
validation: "bmad/bmm/workflows/1-analysis/research/checklist.md"
instructions: "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-router.md" # Router loads specific instruction sets
validation: "{bmad_folder}/bmm/workflows/1-analysis/research/checklist.md"
web_bundle_files:
- "bmad/bmm/workflows/1-analysis/research/instructions-router.md"
- "bmad/bmm/workflows/1-analysis/research/instructions-market.md"
- "bmad/bmm/workflows/1-analysis/research/instructions-deep-prompt.md"
- "bmad/bmm/workflows/1-analysis/research/instructions-technical.md"
- "bmad/bmm/workflows/1-analysis/research/template-market.md"
- "bmad/bmm/workflows/1-analysis/research/template-deep-prompt.md"
- "bmad/bmm/workflows/1-analysis/research/template-technical.md"
- "bmad/bmm/workflows/1-analysis/research/checklist.md"
- "bmad/bmm/workflows/1-analysis/research/checklist-deep-prompt.md"
- "bmad/bmm/workflows/1-analysis/research/checklist-technical.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-router.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-market.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-deep-prompt.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/instructions-technical.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/template-market.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/template-deep-prompt.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/template-technical.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/checklist.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/checklist-deep-prompt.md"
- "{bmad_folder}/bmm/workflows/1-analysis/research/checklist-technical.md"

2
src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md
View File

@@ -2,7 +2,7 @@
<workflow name="create-ux-design">
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
<critical>The goal is COLLABORATIVE UX DESIGN through visual exploration, not content generation</critical>

20
src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Collaborative UX design facilitation workflow that creates excepti
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -46,7 +46,7 @@ input_file_patterns:
sharded: "{output_folder}/docs/index.md"
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/create-ux-design"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
template: "{installed_path}/ux-design-template.md"
@@ -64,10 +64,10 @@ web_bundle:
description: "Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step."
author: "BMad"
# Core workflow files (bmad/-relative paths)
instructions: "bmad/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
validation: "bmad/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
template: "bmad/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
# Core workflow files ({bmad_folder}/-relative paths)
instructions: "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
validation: "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
template: "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
# Default configuration values (can be overridden during bundle setup)
defaults:
@@ -85,9 +85,9 @@ web_bundle:
# Complete file list - ALL files this workflow depends on
web_bundle_files:
# Core workflow files
- "bmad/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
- "bmad/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
- "bmad/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
# Task dependencies (referenced in instructions.md)
- "bmad/core/tasks/workflow.xml"
- "{bmad_folder}/core/tasks/workflow.xml"

6
src/modules/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md
View File

@@ -1,6 +1,6 @@
# Epic and Story Decomposition - Intent-Based Implementation Planning
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow transforms requirements into BITE-SIZED STORIES for development agents</critical>
<critical>EVERY story must be completable by a single dev agent in one focused session</critical>
@@ -80,7 +80,7 @@ Present proposed epic structure showing:
- Why this grouping makes sense</action>
<template-output>epics_summary</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="3" goal="Decompose each epic into bite-sized stories" repeat="for-each-epic">
@@ -138,7 +138,7 @@ For each story in epic {{N}}, output variables following this pattern:
<action>For each story M in epic {{N}}, generate story content</action>
<template-output>story*title*{{N}}\_{{M}}</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="4" goal="Review and finalize epic breakdown">

12
src/modules/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Transform PRD requirements into bite-sized stories organized in ep
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
project_name: "{config_source}:project_name"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
@@ -35,7 +35,7 @@ input_file_patterns:
sharded: "{output_folder}/*domain*brief*/index.md"
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories"
instructions: "{installed_path}/instructions.md"
template: "{installed_path}/epics-template.md"
@@ -48,8 +48,8 @@ web_bundle:
name: "create-epics-and-stories"
description: "Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents"
author: "BMad"
instructions: "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
template: "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
instructions: "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
template: "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
web_bundle_files:
- "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
- "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"

10
src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md
View File

@@ -1,6 +1,6 @@
# PRD Workflow - Intent-Driven Product Planning
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context</critical>
<critical>Communicate all responses in {communication_language} and adapt deeply to {user_skill_level}</critical>
@@ -115,7 +115,7 @@ Weave in the magic:
<check if="business focus">
<template-output>business_metrics</template-output>
</check>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="3" goal="Scope Definition">
@@ -140,7 +140,7 @@ For complex domains:
<template-output>mvp_scope</template-output>
<template-output>growth_features</template-output>
<template-output>vision_features</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="4" goal="Domain-Specific Exploration" optional="true">
@@ -289,7 +289,7 @@ The magic thread:
Highlight which requirements deliver the special experience</action>
<template-output>functional_requirements_complete</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="9" goal="Non-Functional Requirements Discovery">
@@ -341,7 +341,7 @@ Skip categories that don't apply!</action>
Does this capture your product vision?"</action>
<template-output>prd_summary</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
<action>After PRD review and refinement complete:

32
src/modules/bmm/workflows/2-plan-workflows/prd/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Unified PRD workflow for BMad Method and Enterprise Method tracks.
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
project_name: "{config_source}:project_name"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
@@ -14,7 +14,7 @@ user_skill_level: "{config_source}:user_skill_level"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/prd"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd"
instructions: "{installed_path}/instructions.md"
# Templates
@@ -49,24 +49,24 @@ web_bundle:
name: "prd"
description: "Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow."
author: "BMad"
instructions: "bmad/bmm/workflows/2-plan-workflows/prd/instructions.md"
validation: "bmad/bmm/workflows/2-plan-workflows/prd/checklist.md"
instructions: "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/instructions.md"
validation: "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/checklist.md"
web_bundle_files:
# Core workflow files
- "bmad/bmm/workflows/2-plan-workflows/prd/instructions.md"
- "bmad/bmm/workflows/2-plan-workflows/prd/prd-template.md"
- "bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv"
- "bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv"
- "bmad/bmm/workflows/2-plan-workflows/prd/checklist.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/instructions.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/prd-template.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/project-types.csv"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/checklist.md"
# Child workflow and its files
- "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml"
- "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
- "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
# Task dependencies (referenced in instructions.md)
- "bmad/core/tasks/workflow.xml"
- "bmad/core/tasks/adv-elicit.xml"
- "bmad/core/tasks/adv-elicit-methods.csv"
- "{bmad_folder}/core/tasks/workflow.xml"
- "{bmad_folder}/core/tasks/adv-elicit.xml"
- "{bmad_folder}/core/tasks/adv-elicit-methods.csv"
child_workflows:
- create-epics-and-stories: "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml"
- create-epics-and-stories: "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml"

2
src/modules/bmm/workflows/2-plan-workflows/tech-spec/checklist.md
View File

@@ -13,7 +13,7 @@
## 1. Output Files Exist
- [ ] tech-spec.md created in output folder
- [ ] Story file(s) created in dev_story_location
- [ ] Story file(s) created in dev_ephemeral_location
- Level 0: 1 story file (story-{slug}.md)
- Level 1: epics.md + 2-3 story files (story-{epic-slug}-N.md)
- [ ] bmm-workflow-status.yaml updated (if not standalone mode)

10
src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md
View File

@@ -11,7 +11,7 @@
<action>Read the completed tech-spec.md file from {output_folder}/tech-spec.md</action>
<action>Load bmm-workflow-status.yaml from {output_folder}/bmm-workflow-status.yaml (if exists)</action>
<action>Extract dev_story_location from config (where stories are stored)</action>
<action>Extract dev_ephemeral_location from config (where stories are stored)</action>
<action>Extract from the ENHANCED tech-spec structure:
@@ -42,7 +42,7 @@
</example>
<action>Set story_filename = "story-{slug}.md"</action>
<action>Set story_path = "{dev_story_location}/story-{slug}.md"</action>
<action>Set story_path = "{dev_ephemeral_location}/story-{slug}.md"</action>
</step>
@@ -122,7 +122,7 @@ Since tech-spec is now context-rich, populate all new template fields:
<step n="4" goal="Update status - Level 0 single story">
<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
<param>mode: update</param>
<param>action: complete_workflow</param>
<param>workflow_name: tech-spec</param>
@@ -170,7 +170,7 @@ Since the tech-spec is now CONTEXT-RICH with:
**You can skip story-context and go straight to dev!**
1. Load DEV agent: `{project-root}/bmad/bmm/agents/dev.md`
1. Load DEV agent: `{project-root}/{bmad_folder}/bmm/agents/dev.md`
2. Run `dev-story` workflow
3. Begin implementation immediately
@@ -178,7 +178,7 @@ Since the tech-spec is now CONTEXT-RICH with:
Only needed for extremely complex scenarios:
1. Load SM agent: `{project-root}/bmad/bmm/agents/sm.md`
1. Load SM agent: `{project-root}/{bmad_folder}/bmm/agents/sm.md`
2. Run `story-context` workflow (generates additional XML context)
3. Then load DEV agent and run `dev-story` workflow

12
src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions-level1-stories.md
View File

@@ -12,7 +12,7 @@
<action>Read the completed tech-spec.md file from {output_folder}/tech-spec.md</action>
<action>Load bmm-workflow-status.yaml from {output_folder}/bmm-workflow-status.yaml (if exists)</action>
<action>Extract dev_story_location from config (where stories are stored)</action>
<action>Extract dev_ephemeral_location from config (where stories are stored)</action>
<action>Extract from the ENHANCED tech-spec structure:
@@ -178,7 +178,7 @@ Since tech-spec is context-rich, populate ALL template fields:
</guidelines>
<for-each story="1 to story_count">
<action>Set story_path_{n} = "{dev_story_location}/story-{epic_slug}-{n}.md"</action>
<action>Set story_path_{n} = "{dev_ephemeral_location}/story-{epic_slug}-{n}.md"</action>
<action>Create story file from user_story_template with the following content:</action>
<template-output file="{story_path_{n}}">
@@ -271,7 +271,7 @@ Epic: Icon Reliability
<step n="6" goal="Update status and populate story backlog">
<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
<param>mode: update</param>
<param>action: complete_workflow</param>
<param>workflow_name: tech-spec</param>
@@ -391,7 +391,7 @@ Stories are implementation-ready!</output>
- `story-{epic_slug}-3.md` → Third story
{{/if}}
**Story Location:** `{dev_story_location}/`
**Story Location:** `{dev_ephemeral_location}/`
**Next Steps - Iterative Implementation:**
@@ -408,7 +408,7 @@ Since the tech-spec is now CONTEXT-RICH with:
**You can skip story-context for most Level 1 stories!**
**1. Start with Story 1:**
a. Load DEV agent: `{project-root}/bmad/bmm/agents/dev.md`
a. Load DEV agent: `{project-root}/{bmad_folder}/bmm/agents/dev.md`
b. Run `dev-story` workflow (select story-{epic_slug}-1.md)
c. Tech-spec provides all context needed
d. Implement story 1
@@ -429,7 +429,7 @@ d. Implement story 1
Only needed for extremely complex multi-story dependencies:
1. Load SM agent: `{project-root}/bmad/bmm/agents/sm.md`
1. Load SM agent: `{project-root}/{bmad_folder}/bmm/agents/sm.md`
2. Run `story-context` workflow for complex stories
3. Then load DEV agent and run `dev-story`

4
src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md
View File

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>
@@ -914,7 +914,7 @@ What to watch after deployment:
<template-output file="tech-spec.md">rollback_plan</template-output>
<template-output file="tech-spec.md">monitoring_approach</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>

24
src/modules/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Technical specification workflow for Level 0 projects (single atom
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
project_name: "{config_source}:project_name"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
@@ -21,7 +21,7 @@ change_type: runtime-captured
field_type: runtime-captured
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/tech-spec"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec"
instructions: "{installed_path}/instructions.md"
template: "{installed_path}/tech-spec-template.md"
@@ -63,17 +63,17 @@ web_bundle:
name: "tech-spec-sm"
description: "Technical specification workflow for Level 0-1 projects. Creates focused tech spec with story generation. Level 0: tech-spec + user story. Level 1: tech-spec + epic/stories."
author: "BMad"
instructions: "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md"
instructions: "{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/instructions.md"
web_bundle_files:
# Core workflow files
- "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md"
- "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md"
- "bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions-level1-stories.md"
- "bmad/bmm/workflows/2-plan-workflows/tech-spec/tech-spec-template.md"
- "bmad/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md"
- "bmad/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/instructions.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/instructions-level1-stories.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/tech-spec-template.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md"
- "{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md"
# Task dependencies (referenced in instructions.md)
- "bmad/core/tasks/workflow.xml"
- "bmad/core/tasks/adv-elicit.xml"
- "bmad/core/tasks/adv-elicit-methods.csv"
- "{bmad_folder}/core/tasks/workflow.xml"
- "{bmad_folder}/core/tasks/adv-elicit.xml"
- "{bmad_folder}/core/tasks/adv-elicit-methods.csv"

12
src/modules/bmm/workflows/3-solutioning/architecture/instructions.md
View File

@@ -2,7 +2,7 @@
<workflow name="architecture">
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
<critical>The goal is ARCHITECTURAL DECISIONS that prevent AI agent conflicts, not detailed implementation specs</critical>
@@ -363,7 +363,7 @@ Provided by Starter: {{yes_if_from_starter}}
</action>
<template-output>decision_record</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="5" goal="Address cross-cutting concerns">
@@ -393,7 +393,7 @@ Provided by Starter: {{yes_if_from_starter}}
</action>
<template-output>project_structure</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="7" goal="Design novel architectural patterns" optional="true">
@@ -467,7 +467,7 @@ Provided by Starter: {{yes_if_from_starter}}
</check>
<template-output>novel_pattern_designs</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="8" goal="Define implementation patterns to prevent agent conflicts">
@@ -560,7 +560,7 @@ Enforcement: "All agents MUST follow this pattern"
</action>
<template-output>implementation_patterns</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="9" goal="Validate architectural coherence">
@@ -614,7 +614,7 @@ Enforcement: "All agents MUST follow this pattern"
</action>
<template-output>architecture_document</template-output>
<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
</step>
<step n="11" goal="Validate document completeness">

38
src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Collaborative architectural decision facilitation for AI-agent con
author: "BMad"
# Critical variables
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -37,7 +37,7 @@ input_file_patterns:
sharded: "{output_folder}/docs/index.md"
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
template: "{installed_path}/architecture-template.md"
@@ -72,18 +72,18 @@ web_bundle:
description: "Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts."
author: "BMad"
# Core workflow files (bmad/-relative paths)
instructions: "bmad/bmm/workflows/3-solutioning/architecture/instructions.md"
validation: "bmad/bmm/workflows/3-solutioning/architecture/checklist.md"
template: "bmad/bmm/workflows/3-solutioning/architecture/architecture-template.md"
# Core workflow files ({bmad_folder}/-relative paths)
instructions: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/instructions.md"
validation: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/checklist.md"
template: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/architecture-template.md"
# Knowledge base files for decision making
decision_catalog: "bmad/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml"
architecture_patterns: "bmad/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml"
pattern_categories: "bmad/bmm/workflows/3-solutioning/architecture/pattern-categories.csv"
decision_catalog: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml"
architecture_patterns: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml"
pattern_categories: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/pattern-categories.csv"
# Task dependencies
adv_elicit_task: "bmad/core/tasks/adv-elicit.xml"
adv_elicit_task: "{bmad_folder}/core/tasks/adv-elicit.xml"
# Default configuration values (can be overridden during bundle setup)
defaults:
@@ -99,16 +99,16 @@ web_bundle:
# Complete file list - ALL files this workflow depends on
web_bundle_files:
# Core workflow files
- "bmad/bmm/workflows/3-solutioning/architecture/instructions.md"
- "bmad/bmm/workflows/3-solutioning/architecture/checklist.md"
- "bmad/bmm/workflows/3-solutioning/architecture/architecture-template.md"
- "{bmad_folder}/bmm/workflows/3-solutioning/architecture/instructions.md"
- "{bmad_folder}/bmm/workflows/3-solutioning/architecture/checklist.md"
- "{bmad_folder}/bmm/workflows/3-solutioning/architecture/architecture-template.md"
# Knowledge base data files
- "bmad/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml"
- "bmad/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml"
- "bmad/bmm/workflows/3-solutioning/architecture/pattern-categories.csv"
- "{bmad_folder}/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml"
- "{bmad_folder}/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml"
- "{bmad_folder}/bmm/workflows/3-solutioning/architecture/pattern-categories.csv"
# Task dependencies (referenced in instructions.md)
- "bmad/core/tasks/workflow.xml"
- "bmad/core/tasks/adv-elicit.xml"
- "bmad/core/tasks/adv-elicit-methods.csv"
- "{bmad_folder}/core/tasks/workflow.xml"
- "{bmad_folder}/core/tasks/adv-elicit.xml"
- "{bmad_folder}/core/tasks/adv-elicit-methods.csv"

4
src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md
View File

@@ -1,7 +1,7 @@
# Implementation Ready Check - Workflow Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml</critical>
<critical>Communicate all findings and analysis in {communication_language} throughout the assessment</critical>
<critical>Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically</critical>

8
src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Systematically validate that all planning and solutioning phases a
author: "BMad Builder"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -12,11 +12,11 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow status integration
workflow_status_workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
workflow_paths_dir: "{project-root}/bmad/bmm/workflows/workflow-status/paths"
workflow_status_workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
workflow_paths_dir: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/paths"
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/3-solutioning/solutioning-gate-check"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/solutioning-gate-check"
template: "{installed_path}/template.md"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

4
src/modules/bmm/workflows/4-implementation/code-review/instructions.md
View File

@@ -1,7 +1,7 @@
# Senior Developer Review - Workflow Instructions
````xml
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>
@@ -376,7 +376,7 @@ Review was saved to story file, but sprint-status.yaml may be out of sync.
</step>
<step n="10" goal="Validation and completion">
<invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/bmad/core/tasks/validate-workflow.xml</invoke-task>
<invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
<action>Report workflow completion.</action>
<check if="ad_hoc_review_mode == true">

6
src/modules/bmm/workflows/4-implementation/code-review/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Perform a Senior Developer code review on a completed story flagge
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/code-review"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
@@ -23,7 +23,7 @@ template: false
# Variables (can be provided by caller)
variables:
story_path: "" # Optional: Explicit path to story file. If not provided, finds first story with status "review"
story_dir: "{config_source}:dev_story_location" # Directory containing story files
story_dir: "{config_source}:dev_ephemeral_location" # Directory containing story files
tech_spec_search_dir: "{project-root}/docs"
tech_spec_glob_template: "tech-spec-epic-{{epic_num}}*.md"
arch_docs_search_dirs: |

2
src/modules/bmm/workflows/4-implementation/correct-course/checklist.md
View File

@@ -1,6 +1,6 @@
# Change Navigation Checklist
<critical>This checklist is executed as part of: {project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
<critical>This checklist is executed as part of: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
<critical>Work through each section systematically with the user, recording findings and impacts</critical>
<checklist>

4
src/modules/bmm/workflows/4-implementation/correct-course/instructions.md
View File

@@ -1,7 +1,7 @@
# Correct Course - Sprint Change Management Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>

4
src/modules/bmm/workflows/4-implementation/correct-course/workflow.yaml
View File

@@ -3,7 +3,7 @@ name: "correct-course"
description: "Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation"
author: "BMad Method"
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -11,7 +11,7 @@ user_skill_level: "{config_source}:user_skill_level"
document_output_language: "{config_source}:document_output_language"
date: system-generated
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/correct-course"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course"
template: false
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

6
src/modules/bmm/workflows/4-implementation/create-story/instructions.md
View File

@@ -1,7 +1,7 @@
# Create Story - Workflow Instructions (Spec-compliant, non-interactive by default)
````xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Generate all documents in {document_output_language}</critical>
<critical>This workflow creates or updates the next user story from epics/PRD and architecture context, saving to the configured stories directory and optionally invoking Story Context.</critical>
@@ -39,7 +39,7 @@
<workflow>
<step n="1" goal="Load config and initialize">
<action>Resolve variables from config_source: story_dir (dev_story_location), output_folder, user_name, communication_language. If story_dir missing and {{non_interactive}} == false → ASK user to provide a stories directory and update variable. If {{non_interactive}} == true and missing, HALT with a clear message.</action>
<action>Resolve variables from config_source: story_dir (dev_ephemeral_location), output_folder, user_name, communication_language. If story_dir missing and {{non_interactive}} == false → ASK user to provide a stories directory and update variable. If {{non_interactive}} == true and missing, HALT with a clear message.</action>
<action>Create {{story_dir}} if it does not exist</action>
<action>Resolve installed component paths from workflow.yaml: template, instructions, validation</action>
<action>Resolve recommended inputs if present: epics_file, prd_file, architecture_file</action>
@@ -240,7 +240,7 @@ Will update existing story file rather than creating new one.
</step>
<step n="8" goal="Validate, save, and mark story drafted" tag="sprint-status">
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
<action>Save document unconditionally (non-interactive default). In interactive mode, allow user confirmation.</action>
<!-- Mark story as drafted in sprint status -->

6
src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml
View File

@@ -3,21 +3,21 @@ description: "Create the next user story markdown from epics/PRD and architectur
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/create-story"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story"
template: "{installed_path}/template.md"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
# Variables and inputs
variables:
story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
epics_file: "{output_folder}/epics.md" # Preferred source for epic/story breakdown
prd_file: "{output_folder}/PRD.md" # Fallback for requirements
architecture_file: "{output_folder}/architecture.md" # Optional architecture context

6
src/modules/bmm/workflows/4-implementation/dev-story/AUDIT-REPORT.md
View File

@@ -26,7 +26,7 @@ The dev-story workflow is well-structured and follows most BMAD v6 standards. Th
The workflow.yaml contains all required standard config variables:
- ✓ `config_source: "{project-root}/bmad/bmm/config.yaml"` - Correctly defined
- ✓ `config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"` - Correctly defined
- ✓ `output_folder: "{config_source}:output_folder"` - Pulls from config_source
- ✓ `user_name: "{config_source}:user_name"` - Pulls from config_source
- ✓ `communication_language: "{config_source}:communication_language"` - Pulls from config_source
@@ -67,7 +67,7 @@ These variables appear to be pulling from config.yaml but are not explicitly def
### Unused Variables (Bloat)
1. **context_path** - Defined as `"{config_source}:dev_story_location"` but never used. This duplicates `story_dir` functionality.
1. **context_path** - Defined as `"{config_source}:dev_ephemeral_location"` but never used. This duplicates `story_dir` functionality.
---
@@ -140,7 +140,7 @@ The workflow correctly sets `web_bundle: false`. This is the expected configurat
### Unused YAML Fields
1. **context_path** (line 11 in workflow.yaml)
- Defined as: `"{config_source}:dev_story_location"`
- Defined as: `"{config_source}:dev_ephemeral_location"`
- Never referenced in instructions.md
- Duplicates functionality of `story_dir` variable
- **Recommendation:** Remove this variable as `story_dir` serves the same purpose

4
src/modules/bmm/workflows/4-implementation/dev-story/instructions.md
View File

@@ -1,7 +1,7 @@
# Develop Story - Workflow Instructions
```xml
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>
@@ -227,7 +227,7 @@ Story is marked Ready for Review in file, but sprint-status.yaml may be out of s
</step>
<step n="7" goal="Completion communication and user support">
<action>Optionally run the workflow validation task against the story using {project-root}/bmad/core/tasks/validate-workflow.xml</action>
<action>Optionally run the workflow validation task against the story using {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml</action>
<action>Prepare a concise summary in Dev Agent Record → Completion Notes</action>
<action>Communicate to {user_name} that story implementation is complete and ready for review</action>

6
src/modules/bmm/workflows/4-implementation/dev-story/workflow.yaml
View File

@@ -3,13 +3,13 @@ description: "Execute a story by implementing tasks/subtasks, writing tests, val
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
user_skill_level: "{config_source}:user_skill_level"
document_output_language: "{config_source}:document_output_language"
story_dir: "{config_source}:dev_story_location"
story_dir: "{config_source}:dev_ephemeral_location"
run_until_complete: "{config_source}:run_until_complete"
run_tests_command: "{config_source}:run_tests_command"
date: system-generated
@@ -19,7 +19,7 @@ story_file: "" # Explicit story path; auto-discovered if empty
context_file: "{story_dir}/{{story_key}}.context.xml"
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

2
src/modules/bmm/workflows/4-implementation/epic-tech-context/checklist.md
View File

@@ -1,7 +1,7 @@
# Tech Spec Validation Checklist
```xml
<checklist id="bmad/bmm/workflows/4-implementation/epic-tech-context/checklist">
<checklist id="{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context/checklist">
<item>Overview clearly ties to PRD goals</item>
<item>Scope explicitly lists in-scope and out-of-scope</item>
<item>Design lists all services/modules with responsibilities</item>

4
src/modules/bmm/workflows/4-implementation/epic-tech-context/instructions.md
View File

@@ -1,7 +1,7 @@
<!-- BMAD BMM Tech Spec Workflow Instructions (v6) -->
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping.</critical>
@@ -157,7 +157,7 @@ Continuing to regenerate tech spec...
</step>
<step n="9" goal="Validate and mark epic contexted" tag="sprint-status">
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
<!-- Mark epic as contexted -->
<action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>

4
src/modules/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml
View File

@@ -3,7 +3,7 @@ description: "Generate a comprehensive Technical Specification from PRD and Arch
author: "BMAD BMM"
# Critical variables
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -47,7 +47,7 @@ input_file_patterns:
sharded: "{output_folder}/docs/index.md"
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context"
template: "{installed_path}/template.md"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

4
src/modules/bmm/workflows/4-implementation/retrospective/instructions.md
View File

@@ -1,7 +1,7 @@
# Retrospective - Epic Completion Review Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>

8
src/modules/bmm/workflows/4-implementation/retrospective/workflow.yaml
View File

@@ -3,7 +3,7 @@ name: "retrospective"
description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic"
author: "BMad"
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -11,7 +11,7 @@ user_skill_level: "{config_source}:user_skill_level"
document_output_language: "{config_source}:document_output_language"
date: system-generated
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/retrospective"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective"
template: false
instructions: "{installed_path}/instructions.md"
@@ -19,7 +19,7 @@ mode: interactive
trigger: "Run AFTER completing an epic"
required_inputs:
- agent_manifest: "{project-root}/bmad/_cfg/agent-manifest.csv"
- agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
# Smart input file references - handles both whole docs and sharded docs
# Priority: Whole document first, then sharded version
@@ -46,7 +46,7 @@ input_file_patterns:
# Required files
sprint_status_file: "{output_folder}/sprint-status.yaml"
story_directory: "{config_source}:dev_story_location"
story_directory: "{config_source}:dev_ephemeral_location"
retrospectives_folder: "{output_folder}/retrospectives"
output_artifacts:

4
src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md
View File

@@ -1,7 +1,7 @@
# Sprint Planning - Sprint Status Generator
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml</critical>
## 📚 Document Discovery - Full Epic Loading

6
src/modules/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
View File

@@ -3,14 +3,14 @@ description: "Generate and manage the sprint status tracking file for Phase 4 im
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/sprint-planning"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning"
instructions: "{installed_path}/instructions.md"
template: "{installed_path}/sprint-status-template.yaml"
validation: "{installed_path}/checklist.md"
@@ -24,7 +24,7 @@ variables:
# Tracking system configuration
tracking_system: "file-system" # Options: file-system, Future will support other options from config of mcp such as jira, linear, trello
story_location: "{project-root}/docs/stories" # Relative path for file-system, Future will support URL for Jira/Linear/Trello
story_location_absolute: "{config_source}:dev_story_location" # Absolute path for file operations
story_location_absolute: "{config_source}:dev_ephemeral_location" # Absolute path for file operations
# Source files (file-system only)
epics_location: "{output_folder}" # Directory containing epic*.md files

2
src/modules/bmm/workflows/4-implementation/story-context/checklist.md
View File

@@ -1,7 +1,7 @@
# Story Context Assembly Checklist
```xml
<checklist id="bmad/bmm/workflows/4-implementation/story-context/checklist">
<checklist id="{bmad_folder}/bmm/workflows/4-implementation/story-context/checklist">
<item>Story fields (asA/iWant/soThat) captured</item>
<item>Acceptance criteria list matches story draft exactly (no invention)</item>
<item>Tasks/subtasks captured as task list</item>

2
src/modules/bmm/workflows/4-implementation/story-context/context-template.xml
View File

@@ -1,4 +1,4 @@
<story-context id="bmad/bmm/workflows/4-implementation/story-context/template" v="1.0">
<story-context id="{bmad_folder}/bmm/workflows/4-implementation/story-context/template" v="1.0">
<metadata>
<epicId>{{epic_id}}</epicId>
<storyId>{{story_id}}</storyId>

4
src/modules/bmm/workflows/4-implementation/story-context/instructions.md
View File

@@ -1,7 +1,7 @@
<!-- BMAD BMM Story Context Assembly Instructions (v6) -->
```xml
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<critical>Generate all documents in {document_output_language}</critical>
@@ -181,7 +181,7 @@ All stories are either still in backlog or already marked ready/in-progress/done
<step n="6" goal="Validate and save">
<anchor id="validation_step" />
<action>Validate output context file structure and content</action>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
</step>
<step n="7" goal="Update story file and mark ready for dev" tag="sprint-status">

8
src/modules/bmm/workflows/4-implementation/story-context/workflow.yaml
View File

@@ -4,16 +4,16 @@ description: "Assemble a dynamic Story Context XML by pulling latest documentati
author: "BMad"
# Critical variables
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
document_output_language: "{config_source}:document_output_language"
story_path: "{config_source}:dev_story_location"
story_path: "{config_source}:dev_ephemeral_location"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-context"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context"
template: "{installed_path}/context-template.xml"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
@@ -21,7 +21,7 @@ validation: "{installed_path}/checklist.md"
# Variables and inputs
variables:
story_path: "" # Optional: Explicit story path. If not provided, finds first story with status "drafted"
story_dir: "{config_source}:dev_story_location"
story_dir: "{config_source}:dev_ephemeral_location"
# Smart input file references - handles both whole docs and sharded docs
# Priority: Whole document first, then sharded version

2
src/modules/bmm/workflows/4-implementation/story-done/instructions.md
View File

@@ -1,6 +1,6 @@
# Story Approved Workflow Instructions (DEV Agent)
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>

6
src/modules/bmm/workflows/4-implementation/story-done/workflow.yaml
View File

@@ -4,20 +4,20 @@ description: "Marks a story as done (DoD complete) and moves it from its current
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-done"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done"
instructions: "{installed_path}/instructions.md"
# Variables and inputs
variables:
story_path: "" # Explicit path to story file
story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
# Output configuration - no output file, just status updates
default_output_file: ""

2
src/modules/bmm/workflows/4-implementation/story-ready/instructions.md
View File

@@ -1,6 +1,6 @@
# Story Ready Workflow Instructions (SM Agent)
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical>

6
src/modules/bmm/workflows/4-implementation/story-ready/workflow.yaml
View File

@@ -4,20 +4,20 @@ description: "Marks a drafted story as ready for development and moves it from T
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-ready"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready"
instructions: "{installed_path}/instructions.md"
# Variables and inputs
variables:
story_path: "" # Explicit path to story file
story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
# Output configuration - no output file, just status updates
default_output_file: ""

10
src/modules/bmm/workflows/document-project/instructions.md
View File

@@ -1,7 +1,7 @@
# Document Project Workflow Router
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/document-project/workflow.yaml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical>
<workflow>
@@ -10,7 +10,7 @@
<step n="1" goal="Validate workflow and get project info">
<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
<param>mode: data</param>
<param>data_request: project_config</param>
</invoke-workflow>
@@ -36,7 +36,7 @@
</check>
<!-- Now validate sequencing -->
<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
<param>mode: validate</param>
<param>calling_workflow: document-project</param>
</invoke-workflow>
@@ -179,7 +179,7 @@ Your choice [1/2/3]:
<step n="4" goal="Update status and complete">
<check if="status_file_found == true">
<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
<param>mode: update</param>
<param>action: complete_workflow</param>
<param>workflow_name: document-project</param>

4
src/modules/bmm/workflows/document-project/workflow.yaml
View File

@@ -5,7 +5,7 @@ description: "Analyzes and documents brownfield projects by scanning codebase, a
author: "BMad"
# Critical variables
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -14,7 +14,7 @@ user_skill_level: "{config_source}:user_skill_level"
date: system-generated
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/document-project"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project"
template: false # This is an action workflow with multiple output files
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

10
src/modules/bmm/workflows/document-project/workflows/deep-dive.yaml
View File

@@ -4,22 +4,22 @@ description: "Exhaustive deep-dive documentation of specific project areas"
author: "BMad"
# This is a sub-workflow called by document-project/workflow.yaml
parent_workflow: "{project-root}/bmad/bmm/workflows/document-project/workflow.yaml"
parent_workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
# Critical variables inherited from parent
config_source: "{project-root}/bmad/bmb/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
date: system-generated
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/document-project/workflows"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflows"
template: false # Action workflow
instructions: "{installed_path}/deep-dive-instructions.md"
validation: "{project-root}/bmad/bmm/workflows/document-project/checklist.md"
validation: "{project-root}/{bmad_folder}/bmm/workflows/document-project/checklist.md"
# Templates
deep_dive_template: "{project-root}/bmad/bmm/workflows/document-project/templates/deep-dive-template.md"
deep_dive_template: "{project-root}/{bmad_folder}/bmm/workflows/document-project/templates/deep-dive-template.md"
# Runtime inputs (passed from parent workflow)
workflow_mode: "deep_dive"

10
src/modules/bmm/workflows/document-project/workflows/full-scan.yaml
View File

@@ -4,22 +4,22 @@ description: "Complete project documentation workflow (initial scan or full resc
author: "BMad"
# This is a sub-workflow called by document-project/workflow.yaml
parent_workflow: "{project-root}/bmad/bmm/workflows/document-project/workflow.yaml"
parent_workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
# Critical variables inherited from parent
config_source: "{project-root}/bmad/bmb/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
date: system-generated
# Data files
documentation_requirements_csv: "{project-root}/bmad/bmm/workflows/document-project/documentation-requirements.csv"
documentation_requirements_csv: "{project-root}/{bmad_folder}/bmm/workflows/document-project/documentation-requirements.csv"
# Module path and component files
installed_path: "{project-root}/bmad/bmm/workflows/document-project/workflows"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflows"
template: false # Action workflow
instructions: "{installed_path}/full-scan-instructions.md"
validation: "{project-root}/bmad/bmm/workflows/document-project/checklist.md"
validation: "{project-root}/{bmad_folder}/bmm/workflows/document-project/checklist.md"
# Runtime inputs (passed from parent workflow)
workflow_mode: "" # "initial_scan" or "full_rescan"

4
src/modules/bmm/workflows/testarch/atdd/instructions.md
View File

@@ -2,7 +2,7 @@
# Acceptance Test-Driven Development (ATDD)
**Workflow ID**: `bmad/bmm/testarch/atdd`
**Workflow ID**: `{bmad_folder}/bmm/testarch/atdd`
**Version**: 4.0 (BMad v6)
---
@@ -50,7 +50,7 @@ Generates failing acceptance tests BEFORE implementation following TDD's red-gre
4. **Load Knowledge Base Fragments**
**Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to load:
**Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load:
- `fixture-architecture.md` - Test fixture patterns with auto-cleanup (pure function → fixture → mergeTests composition, 406 lines, 5 examples)
- `data-factories.md` - Factory patterns using faker (override patterns, nested factories, API seeding, 498 lines, 5 examples)
- `component-tdd.md` - Component test strategies (red-green-refactor, provider isolation, accessibility, visual regression, 480 lines, 4 examples)

4
src/modules/bmm/workflows/testarch/atdd/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Generate failing acceptance tests before implementation using TDD
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/testarch/atdd"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/atdd"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
template: "{installed_path}/atdd-checklist-template.md"

4
src/modules/bmm/workflows/testarch/automate/instructions.md
View File

@@ -2,7 +2,7 @@
# Test Automation Expansion
**Workflow ID**: `bmad/bmm/testarch/automate`
**Workflow ID**: `{bmad_folder}/bmm/testarch/automate`
**Version**: 4.0 (BMad v6)
---
@@ -83,7 +83,7 @@ Expands test automation coverage by generating comprehensive test suites at appr
5. **Load Knowledge Base Fragments**
**Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to load:
**Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load:
- `test-levels-framework.md` - Test level selection (E2E vs API vs Component vs Unit with decision matrix, 467 lines, 4 examples)
- `test-priorities-matrix.md` - Priority classification (P0-P3 with automated scoring, risk mapping, 389 lines, 2 examples)
- `fixture-architecture.md` - Test fixture patterns (pure function → fixture → mergeTests, auto-cleanup, 406 lines, 5 examples)

4
src/modules/bmm/workflows/testarch/automate/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Expand test automation coverage after implementation or analyze ex
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/testarch/automate"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/automate"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
template: false

4
src/modules/bmm/workflows/testarch/ci/instructions.md
View File

@@ -2,7 +2,7 @@
# CI/CD Pipeline Setup
**Workflow ID**: `bmad/bmm/testarch/ci`
**Workflow ID**: `{bmad_folder}/bmm/testarch/ci`
**Version**: 4.0 (BMad v6)
---
@@ -353,7 +353,7 @@ Scaffolds a production-ready CI/CD quality pipeline with test execution, burn-in
### Knowledge Base Integration
**Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
**Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
- `ci-burn-in.md` - Burn-in loop patterns: 10-iteration detection, GitHub Actions workflow, shard orchestration, selective execution (678 lines, 4 examples)
- `selective-testing.md` - Changed test detection strategies: tag-based, spec filters, diff-based selection, promotion rules (727 lines, 4 examples)

4
src/modules/bmm/workflows/testarch/ci/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Scaffold CI/CD quality pipeline with test execution, burn-in loops
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/testarch/ci"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/ci"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

4
src/modules/bmm/workflows/testarch/framework/instructions.md
View File

@@ -2,7 +2,7 @@
# Test Framework Setup
**Workflow ID**: `bmad/bmm/testarch/framework`
**Workflow ID**: `{bmad_folder}/bmm/testarch/framework`
**Version**: 4.0 (BMad v6)
---
@@ -349,7 +349,7 @@ The generated `tests/README.md` should include:
### Knowledge Base Integration
**Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
**Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
- `fixture-architecture.md` - Pure function → fixture → `mergeTests` composition with auto-cleanup (406 lines, 5 examples)
- `data-factories.md` - Faker-based factories with overrides, nested factories, API seeding, auto-cleanup (498 lines, 5 examples)

4
src/modules/bmm/workflows/testarch/framework/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Initialize production-ready test framework architecture (Playwrigh
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/testarch/framework"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/framework"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

2
src/modules/bmm/workflows/testarch/nfr-assess/instructions.md
View File

@@ -50,7 +50,7 @@ This workflow performs a comprehensive assessment of non-functional requirements
**Actions:**
1. Load relevant knowledge fragments from `{project-root}/bmad/bmm/testarch/tea-index.csv`:
1. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`:
- `nfr-criteria.md` - Non-functional requirements criteria and thresholds (security, performance, reliability, maintainability with code examples, 658 lines, 4 examples)
- `ci-burn-in.md` - CI/CD burn-in patterns for reliability validation (10-iteration detection, sharding, selective execution, 678 lines, 4 examples)
- `test-quality.md` - Test quality expectations for maintainability (deterministic, isolated, explicit assertions, length/time limits, 658 lines, 5 examples)

4
src/modules/bmm/workflows/testarch/nfr-assess/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Assess non-functional requirements (performance, security, reliabi
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/testarch/nfr-assess"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/nfr-assess"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
template: "{installed_path}/nfr-report-template.md"

4
src/modules/bmm/workflows/testarch/test-design/instructions.md
View File

@@ -2,7 +2,7 @@
# Test Design and Risk Assessment
**Workflow ID**: `bmad/bmm/testarch/test-design`
**Workflow ID**: `{bmad_folder}/bmm/testarch/test-design`
**Version**: 4.0 (BMad v6)
---
@@ -48,7 +48,7 @@ Plans comprehensive test coverage strategy with risk assessment, priority classi
4. **Load Knowledge Base Fragments**
**Critical:** Consult `{project-root}/bmad/bmm/testarch/tea-index.csv` to load:
**Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load:
- `risk-governance.md` - Risk classification framework (6 categories: TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, owner tracking (625 lines, 4 examples)
- `probability-impact.md` - Risk scoring methodology (probability × impact matrix, automated classification, dynamic re-assessment, gate integration, 604 lines, 4 examples)
- `test-levels-framework.md` - Test level selection guidance (E2E vs API vs Component vs Unit with decision matrix, characteristics, when to use each, 467 lines, 4 examples)

2
src/modules/bmm/workflows/testarch/test-design/test-design-template.md
View File

@@ -281,5 +281,5 @@
---
**Generated by**: BMad TEA Agent - Test Architect Module
**Workflow**: `bmad/bmm/testarch/test-design`
**Workflow**: `{bmad_folder}/bmm/testarch/test-design`
**Version**: 4.0 (BMad v6)

4
src/modules/bmm/workflows/testarch/test-design/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Plan risk mitigation and test coverage strategy before development
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/testarch/test-design"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-design"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
template: "{installed_path}/test-design-template.md"

2
src/modules/bmm/workflows/testarch/test-review/instructions.md
View File

@@ -49,7 +49,7 @@ This workflow performs comprehensive test quality reviews using TEA's knowledge
**Actions:**
1. Load relevant knowledge fragments from `{project-root}/bmad/bmm/testarch/tea-index.csv`:
1. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`:
- `test-quality.md` - Definition of Done (deterministic tests, isolated with cleanup, explicit assertions, <300 lines, <1.5 min, 658 lines, 5 examples)
- `fixture-architecture.md` - Pure function → Fixture → mergeTests composition with auto-cleanup (406 lines, 5 examples)
- `network-first.md` - Route intercept before navigate to prevent race conditions (intercept before navigate, HAR capture, deterministic waiting, 489 lines, 5 examples)

4
src/modules/bmm/workflows/testarch/test-review/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Review test quality using comprehensive knowledge base and best pr
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/testarch/test-review"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-review"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
template: "{installed_path}/test-review-template.md"

18
src/modules/bmm/workflows/testarch/trace/instructions.md
View File

@@ -64,7 +64,7 @@ This phase focuses on mapping requirements to tests, analyzing coverage, and ide
**Actions:**
1. Load relevant knowledge fragments from `{project-root}/bmad/bmm/testarch/tea-index.csv`:
1. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`:
- `test-priorities-matrix.md` - P0/P1/P2/P3 risk framework with automated priority calculation, risk-based mapping, tagging strategy (389 lines, 2 examples)
- `risk-governance.md` - Risk-based testing approach: 6 categories (TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, coverage traceability (625 lines, 4 examples)
- `probability-impact.md` - Risk scoring methodology: probability × impact matrix, automated classification, dynamic re-assessment, gate integration (604 lines, 4 examples)
@@ -126,9 +126,9 @@ This phase focuses on mapping requirements to tests, analyzing coverage, and ide
2. Build traceability matrix:
```
| Criterion ID | Description | Test ID | Test File | Test Level | Coverage Status |
|--------------|-------------|---------|-----------|------------|-----------------|
| AC-1 | User can... | 1.3-E2E-001 | e2e/auth.spec.ts | E2E | FULL |
| Criterion ID | Description | Test ID | Test File | Test Level | Coverage Status |
| ------------ | ----------- | ----------- | ---------------- | ---------- | --------------- |
| AC-1 | User can... | 1.3-E2E-001 | e2e/auth.spec.ts | E2E | FULL |
```
3. Classify coverage status for each criterion:
@@ -476,10 +476,10 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE
## References
- Traceability Matrix: `bmad/output/traceability-matrix.md`
- Test Design: `bmad/output/test-design-epic-2.md`
- Traceability Matrix: `{bmad_folder}/output/traceability-matrix.md`
- Test Design: `{bmad_folder}/output/test-design-epic-2.md`
- Test Results: `ci-artifacts/test-report-2025-01-15.xml`
- NFR Assessment: `bmad/output/nfr-assessment-release-1.2.md`
- NFR Assessment: `{bmad_folder}/output/nfr-assessment-release-1.2.md`
```
3. **Include evidence links** (if `require_evidence: true`):
@@ -515,7 +515,7 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE
- **Decision**: CONCERNS
- **Reason**: P1 coverage 88% (below 90%)
- **Document**: [gate-decision-story-1.3.md](bmad/output/gate-decision-story-1.3.md)
- **Document**: [gate-decision-story-1.3.md]({bmad_folder}/output/gate-decision-story-1.3.md)
- **Action**: Deploy with follow-up story for AC-5
```
@@ -536,7 +536,7 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE
- Create follow-up story for AC-5 E2E test
- Deploy to staging for validation
Full Report: bmad/output/gate-decision-story-1.3.md
Full Report: {bmad_folder}/output/gate-decision-story-1.3.md
```
3. **Request sign-off** (if `require_sign_off: true`):

4
src/modules/bmm/workflows/testarch/trace/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Generate requirements-to-tests traceability matrix, analyze covera
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/testarch/trace"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/trace"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"
template: "{installed_path}/trace-template.md"

2
src/modules/bmm/workflows/workflow-status/init/instructions.md
View File

@@ -1,6 +1,6 @@
# Workflow Init - Project Setup Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: workflow-init/workflow.yaml</critical>
<critical>Communicate in {communication_language} with {user_name}</critical>
<critical>This workflow handles BOTH new projects AND legacy projects being migrated to BMad Method</critical>

8
src/modules/bmm/workflows/workflow-status/init/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: "Initialize a new BMM project by determining level, type, and creat
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
project_name: "{config_source}:project_name"
@@ -14,12 +14,12 @@ user_skill_level: "{config_source}:user_skill_level"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/workflow-status/init"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init"
instructions: "{installed_path}/instructions.md"
template: "{project-root}/bmad/bmm/workflows/workflow-status/workflow-status-template.yaml"
template: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow-status-template.yaml"
# Path data files
path_files: "{project-root}/bmad/bmm/workflows/workflow-status/paths/"
path_files: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/paths/"
# Output configuration
default_output_file: "{output_folder}/bmm-workflow-status.yaml"

4
src/modules/bmm/workflows/workflow-status/instructions.md
View File

@@ -1,7 +1,7 @@
# Workflow Status Check - Multi-Mode Service
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml</critical>
<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml</critical>
<critical>This workflow operates in multiple modes: interactive (default), validate, data, init-check, update</critical>
<critical>Other workflows can call this as a service to avoid duplicating status logic</critical>

2
src/modules/bmm/workflows/workflow-status/project-levels.yaml
View File

@@ -1,5 +1,5 @@
# BMM Project Scale Levels - Source of Truth
# Reference: /bmad/bmm/README.md lines 77-85
# Reference: /{bmad_folder}/bmm/README.md lines 77-85
levels:
0:

4
src/modules/bmm/workflows/workflow-status/workflow.yaml
View File

@@ -4,7 +4,7 @@ description: 'Lightweight status checker - answers "what should I do now?" for a
author: "BMad"
# Critical variables from config
config_source: "{project-root}/bmad/bmm/config.yaml"
config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
@@ -13,7 +13,7 @@ user_skill_level: "{config_source}:user_skill_level"
date: system-generated
# Workflow components
installed_path: "{project-root}/bmad/bmm/workflows/workflow-status"
installed_path: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status"
instructions: "{installed_path}/instructions.md"
# Template for status file creation (used by workflow-init)