External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-17 09:45:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

folder rename from .bmad to _bmad

Browse Source
This commit is contained in:
Brian Madison 2025-12-13 16:22:34 +08:00
parent 0c873638ab
commit 25c79e3fe5
375 changed files with 1421 additions and 2745 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
.gitignore vendored
View File

@ -31,7 +31,7 @@ Thumbs.db
# IDE and editor configs
.windsurf/
.trae/
.bmad*/.cursor/
_bmad*/.cursor/
# AI assistant files
CLAUDE.md
@ -44,8 +44,8 @@ CLAUDE.local.md
.claude/settings.local.json
# Project-specific
.bmad-core
.bmad-creator-tools
_bmad-core
_bmad-creator-tools
test-project-install/*
sample-project/*
flattened-codebase.xml
@ -65,7 +65,7 @@ src/modules/bmgd/sub-modules/
shared-modules
z*/
.bmad
_bmad
.claude
.codex
.github/chatmodes

4
.markdownlint-cli2.yaml
View File

@ -5,8 +5,8 @@ ignores:
- node_modules/**
- test/fixtures/**
- CODE_OF_CONDUCT.md
- .bmad/**
- .bmad*/**
- _bmad/**
- _bmad*/**
- .agent/**
- .claude/**
- .roo/**

4
.prettierignore
View File

@ -5,5 +5,5 @@ test/fixtures/**
CODE_OF_CONDUCT.md
# BMAD runtime folders (user-specific, not in repo)
.bmad/
.bmad*/
_bmad/
_bmad*/

14
docs/agent-customization-guide.md
View File

@ -9,7 +9,7 @@ Customize BMad agents without modifying core files. All customizations persist t
After installation, find agent customization files in:
```
.bmad/_cfg/agents/
_bmad/_cfg/agents/
├── core-bmad-master.customize.yaml
├── bmm-dev.customize.yaml
├── bmm-pm.customize.yaml
@ -119,7 +119,7 @@ prompts:
**Example 1: Customize Developer Agent for TDD**
```yaml
# .bmad/_cfg/agents/bmm-dev.customize.yaml
# _bmad/_cfg/agents/bmm-dev.customize.yaml
agent:
metadata:
name: 'TDD Developer'
@ -135,20 +135,20 @@ critical_actions:
**Example 2: Add Custom Deployment Workflow**
```yaml
# .bmad/_cfg/agents/bmm-dev.customize.yaml
# _bmad/_cfg/agents/bmm-dev.customize.yaml
menu:
- trigger: deploy-staging
workflow: '{project-root}/.bmad/deploy-staging.yaml'
workflow: '{project-root}/_bmad/deploy-staging.yaml'
description: Deploy to staging environment
- trigger: deploy-prod
workflow: '{project-root}/.bmad/deploy-prod.yaml'
workflow: '{project-root}/_bmad/deploy-prod.yaml'
description: Deploy to production (with approval)
```
**Example 3: Multilingual Product Manager**
```yaml
# .bmad/_cfg/agents/bmm-pm.customize.yaml
# _bmad/_cfg/agents/bmm-pm.customize.yaml
persona:
role: 'Bilingual Product Manager'
identity: 'Expert in US and LATAM markets'
@ -174,7 +174,7 @@ memories:
**Module-Level (Recommended):**
- Customize agents per-project in `.bmad/_cfg/agents/`
- Customize agents per-project in `_bmad/_cfg/agents/`
- Different projects can have different agent behaviors
**Global Config (Coming Soon):**

8
docs/custom-content-installation.md
View File

@ -135,7 +135,7 @@ The installer presents a unified selection interface:
## Agent Sidecar Support
Agents with sidecar content can store personal data, memories, and working files outside of the `.bmad` directory. This separation keeps personal content separate from BMAD's core files.
Agents with sidecar content can store personal data, memories, and working files outside of the `_bmad` directory. This separation keeps personal content separate from BMAD's core files.
### What is Sidecar Content?
@ -152,7 +152,7 @@ The sidecar folder location is configured during BMAD core installation:
```
? Where should users' agent sidecar memory folders be stored?
❯ .bmad-user-memory
❯ _bmad-user-memory
```
### How It Works
@ -175,7 +175,7 @@ my-agent/
### Git Integration
Since sidecar content is stored outside the `.bmad` directory (and typically outside version control), users can:
Since sidecar content is stored outside the `_bmad` directory (and typically outside version control), users can:
- Add the sidecar folder to `.gitignore` to exclude personal data
- Share agent definitions without exposing personal content
@ -185,7 +185,7 @@ Example `.gitignore` entry:
```
# Exclude agent personal data
.bmad-user-memory/
_bmad-user-memory/
```
## Creating Custom Content with BMAD Builder

2
docs/ide-info/crush.md
View File

@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.crush/commands/bmad/`.
### How to Use
1. **Open Command Palette**: Use Crush command interface
2. **Navigate**: Browse to `.bmad/{module}/agents/`
2. **Navigate**: Browse to `_bmad/{module}/agents/`
3. **Select Agent**: Choose the agent command
4. **Execute**: Run to activate agent persona

14
docs/ide-info/cursor.md
View File

@ -6,20 +6,20 @@ BMAD agents are installed in `.cursor/rules/bmad/` as MDC rules.
### How to Use
1. **Reference in Chat**: Use `@.bmad/{module}/agents/{agent-name}`
2. **Include Entire Module**: Use `@.bmad/{module}`
3. **Reference Index**: Use `@.bmad/index` for all available agents
1. **Reference in Chat**: Use `@_bmad/{module}/agents/{agent-name}`
2. **Include Entire Module**: Use `@_bmad/{module}`
3. **Reference Index**: Use `@_bmad/index` for all available agents
### Examples
```
@.bmad/core/agents/dev - Activate dev agent
@.bmad/bmm/agents/architect - Activate architect agent
@.bmad/core - Include all core agents/tasks
@_bmad/core/agents/dev - Activate dev agent
@_bmad/bmm/agents/architect - Activate architect agent
@_bmad/core - Include all core agents/tasks
```
### Notes
- Rules are Manual type - only loaded when explicitly referenced
- No automatic context pollution
- Can combine multiple agents: `@.bmad/core/agents/dev @.bmad/core/agents/test`
- Can combine multiple agents: `@_bmad/core/agents/dev @_bmad/core/agents/test`

6
docs/ide-info/iflow.md
View File

@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`.
### How to Use
1. **Access Commands**: Use iFlow command interface
2. **Navigate**: Browse to `.bmad/agents/` or `.bmad/tasks/`
2. **Navigate**: Browse to `_bmad/agents/` or `_bmad/tasks/`
3. **Select**: Choose the agent or task command
4. **Execute**: Run to activate
@ -22,8 +22,8 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`.
### Examples
```
/.bmad/agents/core-dev - Activate dev agent
/.bmad/tasks/core-setup - Execute setup task
/_bmad/agents/core-dev - Activate dev agent
/_bmad/tasks/core-setup - Execute setup task
```
### Notes

2
docs/ide-info/opencode.md
View File

@ -14,7 +14,7 @@ BMAD agents are installed as OpenCode agents in `.opencode/agent/BMAD/{module_na
```
/agents - to see a list of agents and switch between them
/.bmad/bmm/workflows/workflow-init - Activate the workflow-init command
/_bmad/bmm/workflows/workflow-init - Activate the workflow-init command
```
### Notes

2
docs/ide-info/rovo-dev.md
View File

@ -55,7 +55,7 @@ project-root/
│ ├── config.yml (Rovo Dev configuration)
│ ├── prompts.yml (Optional: reusable prompts)
│ └── ...
├── .bmad/ (BMAD installation directory)
├── _bmad/ (BMAD installation directory)
└── ...
```

4
docs/installers-bundlers/ide-injections.md
View File

@ -158,7 +158,7 @@ src/modules/bmm/
```yaml
injections:
- file: '.bmad/bmm/agents/pm.md'
- file: '_bmad/bmm/agents/pm.md'
point: 'pm-agent-instructions'
requires: 'any' # Injected if ANY subagent is selected
content: |
@ -166,7 +166,7 @@ injections:
<i>Use 'market-researcher' subagent for analysis</i>
</llm>
- file: '.bmad/bmm/templates/prd.md'
- file: '_bmad/bmm/templates/prd.md'
point: 'prd-goals-context-delegation'
requires: 'market-researcher' # Only if this specific subagent selected
content: |

22
docs/installers-bundlers/installers-modules-platforms-reference.md
View File

@ -19,7 +19,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor
- **Modular Design**: Core + optional modules (BMB, BMM, CIS)
- **Smart Installation**: Interactive configuration with dependency resolution
- **Clean Architecture**: Centralized `.bmad` directory add to project, no source pollution with multiple folders added
- **Clean Architecture**: Centralized `_bmad` directory add to project, no source pollution with multiple folders added
## Architecture
@ -27,7 +27,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor
```
project-root/
├── .bmad/ # Centralized installation
├── _bmad/ # Centralized installation
│ ├── _cfg/ # Configuration
│ │ ├── agents/ # Agent configs
│ │ └── agent-manifest.csv # Agent manifest
@ -185,7 +185,7 @@ Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Cr
```yaml
injections:
- file: '.bmad/bmm/agents/pm.md'
- file: '_bmad/bmm/agents/pm.md'
point: 'pm-agent-instructions'
content: |
<i>Platform-specific instruction</i>
@ -273,9 +273,9 @@ Generated in: `bmad/_cfg/agents/{module}-{agent}.md`
| Issue | Solution |
| ----------------------- | ------------------------------------ |
| Existing installation | Use `bmad update` or remove `.bmad/` |
| Existing installation | Use `bmad update` or remove `_bmad/` |
| Module not found | Check `src/modules/` exists |
| Config not applied | Verify `.bmad/{module}/config.yaml` |
| Config not applied | Verify `_bmad/{module}/config.yaml` |
| Missing config.yaml | Fixed: All modules now get configs |
| Agent unavailable | Check for `localskip="true"` |
| module-installer copied | Fixed: Now excluded from copy |
@ -290,7 +290,7 @@ bmad status -v # Detailed status
### Best Practices
1. Run from project root
2. Backup `.bmad/_cfg/` before updates
2. Backup `_bmad/_cfg/` before updates
3. Use interactive mode for guidance
4. Review generated configs post-install
@ -298,7 +298,7 @@ bmad status -v # Detailed status
| v4 | v6 |
| ------------------- | -------------------- |
| Scattered files | Centralized `.bmad/` |
| Scattered files | Centralized `_bmad/` |
| Monolithic | Modular |
| Manual config | Interactive setup |
| Limited IDE support | 15+ platforms |
@ -327,8 +327,8 @@ Agents can specify both `workflow` (source location) and `workflow-install` (des
```yaml
menu:
- trigger: create-story
workflow: '{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml'
workflow-install: '{project-root}/.bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml'
workflow-install: '{project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
description: 'Create a game feature story'
```
@ -348,10 +348,10 @@ menu:
```yaml
# Source workflow (in bmm):
config_source: "{project-root}/.bmad/bmm/config.yaml"
config_source: "{project-root}/_bmad/bmm/config.yaml"
# Vendored workflow (in bmgd):
config_source: "{project-root}/.bmad/bmgd/config.yaml"
config_source: "{project-root}/_bmad/bmgd/config.yaml"
```
**Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.

52
docs/v4-to-v6-upgrade.md
View File

@ -10,14 +10,14 @@ BMad v6 represents a complete ground-up rewrite with significant architectural c
When you run `npm run install:bmad` on a project with v4 installed, the installer automatically detects:
- **Legacy folders**: Any folders starting with `.bmad`, `bmad` (lowercase), or `Bmad`
- **Legacy folders**: Any folders starting with `_bmad`, `bmad` (lowercase), or `Bmad`
- **IDE command artifacts**: Legacy bmad folders in IDE configuration directories (`.claude/commands/`, `.cursor/commands/`, etc.)
### What Happens During Detection
1. **Automatic Backup of v4 Modules**: All `.bmad-*` folders are moved to `v4-backup/` in your project root
1. **Automatic Backup of v4 Modules**: All `_bmad-*` folders are moved to `v4-backup/` in your project root
- If a backup already exists, a timestamp is added to avoid conflicts
- Example: `.bmad-core` → `v4-backup/.bmad-core`
- Example: `_bmad-core` → `v4-backup/_bmad-core`
- Your project files and data are NOT affected
2. **IDE Command Cleanup Recommended**: Legacy v4 IDE commands should be manually removed
@ -34,12 +34,12 @@ When you run `npm run install:bmad` on a project with v4 installed, the installe
| v4 Module | v6 Status |
| ----------------------------- | ------------------------------------------------ |
| `.bmad-2d-phaser-game-dev` | Integrated into BMM |
| `.bmad-2d-unity-game-dev` | Integrated into BMM |
| `.bmad-godot-game-dev` | Integrated into BMM |
| `.bmad-*-game-dev` (any) | Integrated into BMM |
| `.bmad-infrastructure-devops` | Deprecated - New core devops agent coming in BMM |
| `.bmad-creative-writing` | Not adapted - New module releasing soon |
| `_bmad-2d-phaser-game-dev` | Integrated into BMM |
| `_bmad-2d-unity-game-dev` | Integrated into BMM |
| `_bmad-godot-game-dev` | Integrated into BMM |
| `_bmad-*-game-dev` (any) | Integrated into BMM |
| `_bmad-infrastructure-devops` | Deprecated - New core devops agent coming in BMM |
| `_bmad-creative-writing` | Not adapted - New module releasing soon |
**Game Development**: All game development functionality has been consolidated and expanded within the BMM (BMad Method) module. Game-specific workflows now adapt to your game type and engine.
@ -53,17 +53,17 @@ When you run `npm run install:bmad` on a project with v4 installed, the installe
```
your-project/
├── .bmad-core/ # Was actually the BMad Method
├── .bmad-game-dev/ # Separate expansion packs
├── .bmad-creative-writing/
└── .bmad-infrastructure-devops/
├── _bmad-core/ # Was actually the BMad Method
├── _bmad-game-dev/ # Separate expansion packs
├── _bmad-creative-writing/
└── _bmad-infrastructure-devops/
```
**v6 Unified Structure:**
```
your-project/
└── .bmad/ # Single installation folder, default .bmad
└── _bmad/ # Single installation folder, default _bmad
├── core/ # Real core framework (applies to all modules)
├── bmm/ # BMad Method (software/game dev)
├── bmb/ # BMad Builder (create agents/workflows)
@ -74,9 +74,9 @@ your-project/
### Key Concept Changes
- **v4 `.bmad-core`**: Was actually the BMad Method
- **v6 `.bmad/core/`**: Is the real universal core framework
- **v6 `.bmad/bmm/`**: Is the BMad Method module
- **v4 `_bmad-core`**: Was actually the BMad Method
- **v6 `_bmad/core/`**: Is the real universal core framework
- **v6 `_bmad/bmm/`**: Is the BMad Method module
- **Module identification**: All modules now have a `config.yaml` file
---
@ -110,15 +110,15 @@ After running the v6 installer:
### v4 Agent Customization
In v4, you may have modified agent files directly in `.bmad-*` folders.
In v4, you may have modified agent files directly in `_bmad-*` folders.
### v6 Agent Customization
**All customizations** now go in `.bmad/_cfg/agents/` using customize files:
**All customizations** now go in `_bmad/_cfg/agents/` using customize files:
**Example: Renaming an agent and changing communication style**
File: `.bmad/_cfg/agents/bmm-pm.customize.yaml`
File: `_bmad/_cfg/agents/bmm-pm.customize.yaml`
```yaml
# Customize the PM agent
@ -133,8 +133,8 @@ persona:
**How it works:**
- Base agent: `.bmad/bmm/agents/pm.md`
- Customization: `.bmad/_cfg/agents/bmm-pm.customize.yaml`
- Base agent: `_bmad/bmm/agents/pm.md`
- Customization: `_bmad/_cfg/agents/bmm-pm.customize.yaml`
- Result: Agent uses your custom name and style, but updates don't overwrite your changes
---
@ -176,7 +176,7 @@ npx bmad-method install
The installer will:
1. Detect v4 installation and offer to backup `.bmad-*` folders
1. Detect v4 installation and offer to backup `_bmad-*` folders
2. Prompt for recommended cleanup (you can skip)
3. Let you select modules (recommend: BMM for software and or game development)
4. Configure core settings (name, language, etc.)
@ -212,9 +212,9 @@ Since you are migrating an existing project from v4, it's most likely **Level 3
## Post-Migration Checklist
- [ ] v4 folders backed up to `v4-backup/`
- [ ] v6 installed to `.bmad/` folder
- [ ] v6 installed to `_bmad/` folder
- [ ] `workflow-init` run with correct project level selected
- [ ] Agent customizations migrated to `.bmad/_cfg/agents/` if needed
- [ ] Agent customizations migrated to `_bmad/_cfg/agents/` if needed
- [ ] IDE integration working (test by listing agents)
- [ ] For active development: `sprint-planning` workflow executed
@ -224,4 +224,4 @@ Since you are migrating an existing project from v4, it's most likely **Level 3
- **Discord**: [Join the BMad Community](https://discord.gg/gk8jAdXWmj)
- **Issues**: [GitHub Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues)
- **Docs**: Check `.bmad/docs/` in your installation for IDE-specific instructions
- **Docs**: Check `_bmad/docs/` in your installation for IDE-specific instructions

2
docs/web-bundles-gemini-gpt-guide.md
View File

@ -336,7 +336,7 @@ Agents adapt their menus based on project phase and available workflows.
Customize agents using the [Agent Customization Guide](./agent-customization-guide.md):
1. Edit `.bmad/_cfg/agents/<agent>.customize.yaml`
1. Edit `_bmad/_cfg/agents/<agent>.customize.yaml`
2. Rebuild: `npx bmad-method build <agent-name>`
3. Generate bundles: `npm run bundle`

4
eslint.config.mjs
View File

@ -16,8 +16,8 @@ export default [
'test/template-test-generator/**/*.md',
'test/fixtures/**',
'test/fixtures/**/*.yaml',
'.bmad/**',
'.bmad*/**',
'_bmad/**',
'_bmad*/**',
// Gitignored patterns
'z*/**', // z-samples, z1, z2, etc.
'.claude/**',

10
src/core/agents/bmad-master.agent.yaml
View File

@ -3,7 +3,7 @@
agent:
metadata:
id: ".bmad/core/agents/bmad-master.md"
id: "_bmad/core/agents/bmad-master.md"
name: "BMad Master"
title: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator"
icon: "🧙"
@ -17,22 +17,22 @@ agent:
# Agent-specific critical actions
critical_actions:
- "Load into memory {project-root}/.bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
- "Load into memory {project-root}/_bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
- "Remember the users name is {user_name}"
- "ALWAYS communicate in {communication_language}"
# Agent menu items
menu:
- trigger: "list-tasks"
action: "list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv"
action: "list all tasks from {project-root}/_bmad/_cfg/task-manifest.csv"
description: "List Available Tasks"
- trigger: "list-workflows"
action: "list all workflows from {project-root}/.bmad/_cfg/workflow-manifest.csv"
action: "list all workflows from {project-root}/_bmad/_cfg/workflow-manifest.csv"
description: "List Workflows"
- trigger: "party-mode"
exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
description: "Group chat with all agents"
# Empty prompts section (no custom prompts for this agent)

113
src/core/agents/bmad-web-orchestrator.agent.xml
View File

@ -1,113 +0,0 @@
<agent id=".bmad/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
<activation critical="MANDATORY">
<step n="1">Load this complete web bundle XML - you are the BMad Orchestrator, first agent in this bundle</step>
<step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id=".bmad/..." and ALL workflows/tasks as nodes findable
by type
and id</step>
<step n="3">Greet user as BMad Orchestrator and display numbered list of ALL menu items from menu section below</step>
<step n="4">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
<step n="5">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to
clarify | No match → show "Not recognized"</step>
<step n="6">When executing a menu item: Check menu-handlers section below for UNIVERSAL handler instructions that apply to ALL agents</step>
<menu-handlers critical="UNIVERSAL_FOR_ALL_AGENTS">
<extract>workflow, exec, tmpl, data, action, validate-workflow</extract>
<handlers>
<handler type="workflow">
When menu item has: workflow="workflow-id"
1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
2. CRITICAL: Always LOAD .bmad/core/tasks/workflow.xml if referenced
3. Execute the workflow content precisely following all steps
4. Save outputs after completing EACH workflow step (never batch)
5. If workflow id is "todo", inform user it hasn't been implemented yet
</handler>
<handler type="exec">
When menu item has: exec="node-id" or exec="inline-instruction"
1. If value looks like a path/id → Find and execute node with that id
2. If value is text → Execute as direct instruction
3. Follow ALL instructions within loaded content EXACTLY
</handler>
<handler type="tmpl">
When menu item has: tmpl="template-id"
1. Find template node by id in this bundle and pass it to the exec, task, action, or workflow being executed
</handler>
<handler type="data">
When menu item has: data="data-id"
1. Find data node by id in this bundle
2. Parse according to node type (json/yaml/xml/csv)
3. Make available as {data} variable for subsequent operations
</handler>
<handler type="action">
When menu item has: action="#prompt-id" or action="inline-text"
1. If starts with # → Find prompt with matching id in current agent
2. Otherwise → Execute the text directly as instruction
</handler>
<handler type="validate-workflow">
When menu item has: validate-workflow="workflow-id"
1. MUST LOAD .bmad/core/tasks/validate-workflow.xml
2. Execute all validation instructions from that file
3. Check workflow's validation property for schema
4. Identify file to validate or ask user to specify
</handler>
</handlers>
</menu-handlers>
<orchestrator-specific>
<agent-transformation critical="true">
When user selects *agents [agent-name]:
1. Find agent XML node with matching name/id in this bundle
2. Announce transformation: "Transforming into [agent name]... 🎭"
3. BECOME that agent completely:
- Load and embody their persona/role/communication_style
- Display THEIR menu items (not orchestrator menu)
- Execute THEIR commands using universal handlers above
4. Stay as that agent until user types *exit
5. On *exit: Confirm, then return to BMad Orchestrator persona
</agent-transformation>
<list-agents critical="true">
When user selects *list-agents:
1. Scan all agent nodes in this bundle
2. Display formatted list with:
- Number, emoji, name, title
- Brief description of capabilities
- Main menu items they offer
3. Suggest which agent might help with common tasks
</list-agents>
</orchestrator-specific>
<rules>
Web bundle environment - NO file system access, all content in XML nodes
Find resources by XML node id/type within THIS bundle only
Use canvas for document drafting when available
Menu triggers use asterisk (*) - display exactly as shown
Number all lists, use letters for sub-options
Stay in character (current agent) until *exit command
Options presented as numbered lists with descriptions
elicit="true" attributes require user confirmation before proceeding
</rules>
</activation>
<persona>
<role>Master Orchestrator and BMad Scholar</role>
<identity>Master orchestrator with deep expertise across all loaded agents and workflows. Technical brilliance balanced with
approachable communication.</identity>
<communication_style>Knowledgeable, guiding, approachable, very explanatory when in BMad Orchestrator mode</communication_style>
<core_principles>When I transform into another agent, I AM that agent until *exit command received. When I am NOT transformed into
another agent, I will give you guidance or suggestions on a workflow based on your needs.</core_principles>
</persona>
<menu>
<item cmd="*help">Show numbered command list</item>
<item cmd="*list-agents">List all available agents with their capabilities</item>
<item cmd="*agents [agent-name]">Transform into a specific agent</item>
<item cmd="*party-mode" exec=".bmad/core/workflows/party-mode/workflow.md">Enter group chat with all agents
simultaneously</item>
<item cmd="*advanced-elicitation" task=".bmad/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
<item cmd="*exit">Exit current session</item>
</menu>
</agent>

2
src/core/module.yaml
View File

@ -23,5 +23,5 @@ output_folder:
agent_sidecar_folder:
prompt: "Where should users agent sidecar memory folders be stored?"
default: ".bmad-user-memory"
default: "_bmad-user-memory"
result: "{project-root}/{value}"

8
src/core/resources/excalidraw/README.md
View File

@ -72,8 +72,8 @@ Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (do
```yaml
# workflows/diagrams/create-flowchart/workflow.yaml
helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md'
json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md'
helpers: '{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md'
json_validation: '{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md'
```
**Domain-specific additions:**
@ -99,8 +99,8 @@ flowchart:
```yaml
# workflows/create-visual-metaphor/workflow.yaml
helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md'
json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md'
helpers: '{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md'
json_validation: '{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md'
```
**Domain-specific additions:**

6
src/core/tasks/advanced-elicitation.xml
View File

@ -1,6 +1,6 @@
<task id=".bmad/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
methods="{project-root}/.bmad/core/tasks/advanced-elicitation-methods.csv"
agent-party="{project-root}/.bmad/_cfg/agent-manifest.csv">
<task id="_bmad/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
methods="{project-root}/_bmad/core/tasks/advanced-elicitation-methods.csv"
agent-party="{project-root}/_bmad/_cfg/agent-manifest.csv">
<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>

2
src/core/tasks/index-docs.xml
View File

@ -1,4 +1,4 @@
<task id=".bmad/core/tasks/index-docs" name="Index Docs"
<task id="_bmad/core/tasks/index-docs" name="Index Docs"
description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
<llm critical="true">
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>

2
src/core/tasks/validate-workflow.xml
View File

@ -1,4 +1,4 @@
<task id=".bmad/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
<task id="_bmad/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
<objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
<inputs>

8
src/core/tasks/workflow.xml
View File

@ -1,4 +1,4 @@
<task id=".bmad/core/tasks/workflow.xml" name="Execute Workflow">
<task id="_bmad/core/tasks/workflow.xml" name="Execute Workflow">
<objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
<llm critical="true">
@ -74,14 +74,14 @@
<action>Display generated content</action>
<ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
response="a">
<action>Start the advanced elicitation workflow {project-root}/.bmad/core/tasks/advanced-elicitation.xml</action>
<action>Start the advanced elicitation workflow {project-root}/_bmad/core/tasks/advanced-elicitation.xml</action>
</if>
<if
response="c">
<action>Continue to next step</action>
</if>
<if response="p">
<action>Start the party-mode workflow {project-root}/.bmad/core/workflows/party-mode/workflow.yaml</action>
<action>Start the party-mode workflow {project-root}/_bmad/core/workflows/party-mode/workflow.yaml</action>
</if>
<if
response="y">
@ -225,7 +225,7 @@
<critical-rules>
• This is the complete workflow execution engine
• You MUST Follow instructions exactly as written
• The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml
• The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml
• You MUST have already loaded and processed: {installed_path}/workflow.yaml
• This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context
• YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be

24
src/core/tools/shard-doc.xml
View File

@ -1,4 +1,4 @@
<tool id=".bmad/core/tasks/shard-doc" name="Shard Document"
<tool id="_bmad/core/tasks/shard-doc" name="Shard Document"
description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
standalone="true">
<objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>
@ -64,12 +64,12 @@
<ask>What would you like to do with the original document `[source-document-name]`?
Options:
[d] Delete - Remove the original (recommended - shards can always be recombined)
[m] Move to archive - Move original to a backup/archive location
[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
Options:
[d] Delete - Remove the original (recommended - shards can always be recombined)
[m] Move to archive - Move original to a backup/archive location
[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
Your choice (d/m/k):</ask>
Your choice (d/m/k):</ask>
<check if="user selects 'd' (delete)">
<action>Delete the original source document file</action>
@ -92,12 +92,12 @@ Your choice (d/m/k):</ask>
<action>Display warning to user:</action>
<output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
This creates confusion because:
- The discover_inputs protocol may load the wrong version
- Updates to one won't reflect in the other
- You'll have duplicate content taking up space
This creates confusion because:
- The discover_inputs protocol may load the wrong version
- Updates to one won't reflect in the other
- You'll have duplicate content taking up space
Consider deleting or archiving the original document.</output>
Consider deleting or archiving the original document.</output>
<action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
</check>
</step>
@ -106,4 +106,4 @@ Consider deleting or archiving the original document.</output>
<halt-conditions critical="true">
<i>HALT if npx command fails or produces no output files</i>
</halt-conditions>
</tool>
</tool>

4
src/core/workflows/brainstorming/workflow.md
View File

@ -28,7 +28,7 @@ This uses **micro-file architecture** for disciplined execution:
### Configuration Loading
Load config from `{project-root}/.bmad/core/config.yaml` and resolve:
Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
- `project_name`, `output_folder`, `user_name`
- `communication_language`, `document_output_language`, `user_skill_level`
@ -36,7 +36,7 @@ Load config from `{project-root}/.bmad/core/config.yaml` and resolve:
### Paths
- `installed_path` = `{project-root}/.bmad/core/workflows/brainstorming`
- `installed_path` = `{project-root}/_bmad/core/workflows/brainstorming`
- `template_path` = `{installed_path}/template.md`
- `brain_techniques_path` = `{installed_path}/brain-methods.csv`
- `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`

4
src/core/workflows/party-mode/steps/step-01-agent-loading.md
View File

@ -18,7 +18,7 @@
## CONTEXT BOUNDARIES:
- Agent manifest CSV is available at `{project-root}/.bmad/_cfg/agent-manifest.csv`
- Agent manifest CSV is available at `{project-root}/_bmad/_cfg/agent-manifest.csv`
- User configuration from config.yaml is loaded and resolved
- Party mode is standalone interactive workflow
- All agent data is available for conversation orchestration
@ -37,7 +37,7 @@ Begin agent loading process:
**Agent Manifest Loading:**"
Load and parse the agent manifest CSV from `{project-root}/.bmad/_cfg/agent-manifest.csv`
Load and parse the agent manifest CSV from `{project-root}/_bmad/_cfg/agent-manifest.csv`
### 2. Extract Agent Data

8
src/core/workflows/party-mode/workflow.md
View File

@ -27,17 +27,17 @@ This uses **micro-file architecture** with **sequential conversation orchestrati
### Configuration Loading
Load config from `{project-root}/.bmad/core/config.yaml` and resolve:
Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
- `project_name`, `output_folder`, `user_name`
- `communication_language`, `document_output_language`, `user_skill_level`
- `date` as a system-generated value
- Agent manifest path: `{project-root}/.bmad/_cfg/agent-manifest.csv`
- Agent manifest path: `{project-root}/_bmad/_cfg/agent-manifest.csv`
### Paths
- `installed_path` = `{project-root}/.bmad/core/workflows/party-mode`
- `agent_manifest_path` = `{project-root}/.bmad/_cfg/agent-manifest.csv`
- `installed_path` = `{project-root}/_bmad/core/workflows/party-mode`
- `agent_manifest_path` = `{project-root}/_bmad/_cfg/agent-manifest.csv`
- `standalone_mode` = `true` (party mode is an interactive workflow)
---

2
src/modules/bmb/README.md
View File

@ -18,7 +18,7 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
**BMad Builder** - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.
- Location: `.bmad/bmb/agents/bmad-builder.md`
- Location: `_bmad/bmb/agents/bmad-builder.md`
### 📋 Workflows

30
src/modules/bmb/agents/bmad-builder.agent.yaml
View File

@ -4,7 +4,7 @@
agent:
webskip: true
metadata:
id: ".bmad/bmb/agents/bmad-builder.md"
id: "_bmad/bmb/agents/bmad-builder.md"
name: BMad Builder
title: BMad Builder
icon: 🧙
@ -24,26 +24,26 @@ agent:
discussion: true
conversational_knowledge:
- agents: "{project-root}/.bmad/bmb/docs/agents/kb.csv"
- workflows: "{project-root}/.bmad/bmb/docs/workflows/kb.csv"
- modules: "{project-root}/.bmad/bmb/docs/modules/kb.csv"
- agents: "{project-root}/_bmad/bmb/docs/agents/kb.csv"
- workflows: "{project-root}/_bmad/bmb/docs/workflows/kb.csv"
- modules: "{project-root}/_bmad/bmb/docs/modules/kb.csv"
menu:
- multi: "[CA] Create, [EA] Edit, or [VA] Validate with Compliance CheckBMAD agents with best practices"
triggers:
- create-agent:
- input: CA or fuzzy match create agent
- route: "{project-root}/.bmad/bmb/workflows/create-agent/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/create-agent/workflow.md"
- data: null
- type: exec
- edit-agent:
- input: EA or fuzzy match edit agent
- route: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/edit-agent/workflow.md"
- data: null
- type: exec
- run-agent-compliance-check:
- input: VA or fuzzy match validate agent
- route: "{project-root}/.bmad/bmb/workflows/agent-compliance-check/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/agent-compliance-check/workflow.md"
- data: null
- type: exec
@ -51,17 +51,17 @@ agent:
triggers:
- create-workflow:
- input: CW or fuzzy match create workflow
- route: "{project-root}/.bmad/bmb/workflows/create-workflow/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/create-workflow/workflow.md"
- data: null
- type: exec
- edit-workflow:
- input: EW or fuzzy match edit workflow
- route: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/edit-workflow/workflow.md"
- data: null
- type: exec
- run-workflow-compliance-check:
- input: VW or fuzzy match validate workflow
- route: "{project-root}/.bmad/bmb/workflows/workflow-compliance-check/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/workflow-compliance-check/workflow.md"
- data: null
- type: exec
@ -69,26 +69,26 @@ agent:
triggers:
- brainstorm-module:
- input: BM or fuzzy match brainstorm module
- route: "{project-root}/.bmad/bmb/workflows/brainstorm-module/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/brainstorm-module/workflow.md"
- data: null
- type: exec
- product-brief-module:
- input: PBM or fuzzy match product brief module
- route: "{project-root}/.bmad/bmb/workflows/product-brief-module/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/product-brief-module/workflow.md"
- data: null
- type: exec
- create-module:
- input: CM or fuzzy match create module
- route: "{project-root}/.bmad/bmb/workflows/create-module/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/create-module/workflow.md"
- data: null
- type: exec
- edit-module:
- input: EM or fuzzy match edit module
- route: "{project-root}/.bmad/bmb/workflows/edit-module/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/edit-module/workflow.md"
- data: null
- type: exec
- run-module-compliance-check:
- input: VM or fuzzy match validate module
- route: "{project-root}/.bmad/bmb/workflows/module-compliance-check/workflow.md"
- route: "{project-root}/_bmad/bmb/workflows/module-compliance-check/workflow.md"
- data: null
- type: exec

6
src/modules/bmb/docs/agents/agent-compilation.md
View File

@ -35,7 +35,7 @@ rex.agent.yaml ← Persona name (users might rename to "Max")
**Pattern:**
- Filename: `{role-or-function}.agent.yaml` (kebab-case)
- Metadata ID: `.bmad/{module}/agents/{role-or-function}.md`
- Metadata ID: `_bmad/{module}/agents/{role-or-function}.md`
- Persona Name: User-customizable in metadata or customize.yaml
**Example:**
@ -44,7 +44,7 @@ rex.agent.yaml ← Persona name (users might rename to "Max")
# File: presentation-master.agent.yaml
agent:
metadata:
id: '.bmad/cis/agents/presentation-master.md'
id: '_bmad/cis/agents/presentation-master.md'
name: Caravaggio # ← Users can change this to "Pablo" or "Vince"
title: Visual Communication & Presentation Expert
```
@ -83,7 +83,7 @@ You must fully embody this agent's persona...
<step n="N+3">Input resolution rules</step>
<menu-handlers>
<!-- Only handlers used in YOUR menu are included -->
<!-- Only handler instructions for the handler types used in the agents specific menu are included -->
</menu-handlers>
<rules>

46
src/modules/bmb/docs/agents/agent-menu-patterns.md
View File

@ -65,11 +65,11 @@ For module agents orchestrating multi-step processes.
```yaml
menu:
- trigger: create-prd
workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/prd/workflow.yaml'
description: 'Create Product Requirements Document'
- trigger: brainstorm
workflow: '{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml'
workflow: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
description: 'Guided brainstorming session'
# Placeholder for unimplemented workflows
@ -92,11 +92,11 @@ For executing tasks directly.
```yaml
menu:
- trigger: validate
exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
exec: '{project-root}/_bmad/core/tasks/validate-workflow.xml'
description: 'Validate document structure'
- trigger: advanced-elicitation
exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
exec: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
description: 'Advanced elicitation techniques'
```
@ -113,8 +113,8 @@ For document generation with templates.
```yaml
menu:
- trigger: create-brief
exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
tmpl: '{project-root}/.bmad/bmm/templates/brief.md'
exec: '{project-root}/_bmad/core/tasks/create-doc.xml'
tmpl: '{project-root}/_bmad/bmm/templates/brief.md'
description: 'Create a Product Brief'
```
@ -131,8 +131,8 @@ Universal attribute for supplementary information.
```yaml
menu:
- trigger: team-standup
exec: '{project-root}/.bmad/bmm/tasks/standup.xml'
data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
exec: '{project-root}/_bmad/bmm/tasks/standup.xml'
data: '{project-root}/_bmad/_cfg/agent-manifest.csv'
description: 'Run team standup'
- trigger: analyze-metrics
@ -154,12 +154,12 @@ Control visibility based on deployment target:
```yaml
menu:
- trigger: git-flow
exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml'
exec: '{project-root}/_bmad/bmm/tasks/git-flow.xml'
description: 'Git workflow operations'
ide-only: true # Only in IDE environments
- trigger: advanced-elicitation
exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
exec: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
description: 'Advanced elicitation'
web-only: true # Only in web bundles
```
@ -251,20 +251,20 @@ menu:
menu:
# Analysis Phase
- trigger: brainstorm
workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
description: 'Brainstorm ideas'
- trigger: research
workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow.yaml'
description: 'Conduct research'
# Planning Phase
- trigger: prd
workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/2-planning/prd/workflow.yaml'
description: 'Create PRD'
- trigger: architecture
workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
description: 'Design architecture'
```
@ -362,19 +362,19 @@ prompts:
```yaml
# GOOD - Portable paths
workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml"
exec: "{project-root}/.bmad/core/tasks/validate.xml"
workflow: "{project-root}/_bmad/bmm/workflows/prd/workflow.yaml"
exec: "{project-root}/_bmad/core/tasks/validate.xml"
data: "{project-root}/_data/metrics.csv"
# BAD - Hardcoded paths
workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml"
workflow: "/Users/john/project/_bmad/bmm/workflows/prd/workflow.yaml"
exec: "../../../core/tasks/validate.xml"
```
### Available Variables
- `{project-root}` - Project root directory
- `.bmad` - BMAD installation folder
- `_bmad` - BMAD installation folder
- `{agent_sidecar_folder}` - Agent installation directory (Expert agents)
- `{output_folder}` - Document output location
- `{user_name}` - User's name from config
@ -444,23 +444,23 @@ menu:
```yaml
menu:
- trigger: workflow-init
workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/workflow-status/init/workflow.yaml'
description: 'Initialize workflow path (START HERE)'
- trigger: brainstorm
workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
description: 'Guided brainstorming'
- trigger: prd
workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/2-planning/prd/workflow.yaml'
description: 'Create PRD'
- trigger: architecture
workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
description: 'Design architecture'
- trigger: party-mode
workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
workflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.yaml'
description: 'Multi-agent discussion'
```

4
src/modules/bmb/docs/agents/expert-agent-architecture.md
View File

@ -202,7 +202,7 @@ Special variable resolved during installation:
- Points to the agent's installation directory
- Used to reference sidecar files
- Example: `.bmad/custom/agents/journal-keeper/`
- Example: `_bmad/custom/agents/journal-keeper/`
## What Gets Injected at Compile Time
@ -238,7 +238,7 @@ Features demonstrated:
```bash
# Copy entire folder to your project
cp -r /path/to/journal-keeper/ .bmad/custom/agents/
cp -r /path/to/journal-keeper/ _bmad/custom/agents/
# Install with personalization
bmad agent-install

76
src/modules/bmb/docs/agents/module-agent-architecture.md
View File

@ -19,7 +19,7 @@ src/modules/{module-code}/agents/{agent-name}.agent.yaml
Compiles to:
```
.bmad/{module-code}/agents/{agent-name}.md
_bmad/{module-code}/agents/{agent-name}.md
```
## YAML Structure
@ -27,7 +27,7 @@ Compiles to:
```yaml
agent:
metadata:
id: '.bmad/{module-code}/agents/{agent-name}.md'
id: '_bmad/{module-code}/agents/{agent-name}.md'
name: 'Persona Name'
title: 'Professional Title'
icon: 'emoji'
@ -41,29 +41,29 @@ agent:
menu:
- trigger: workflow-action
workflow: '{project-root}/.bmad/{module-code}/workflows/{workflow-name}/workflow.yaml'
workflow: '{project-root}/_bmad/{module-code}/workflows/{workflow-name}/workflow.yaml'
description: 'Execute module workflow'
- trigger: another-workflow
workflow: '{project-root}/.bmad/core/workflows/{workflow-name}/workflow.yaml'
workflow: '{project-root}/_bmad/core/workflows/{workflow-name}/workflow.yaml'
description: 'Execute core workflow'
- trigger: task-action
exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml'
exec: '{project-root}/_bmad/{module-code}/tasks/{task-name}.xml'
description: 'Execute module task'
- trigger: cross-module
workflow: '{project-root}/.bmad/other-module/workflows/{workflow-name}/workflow.yaml'
workflow: '{project-root}/_bmad/other-module/workflows/{workflow-name}/workflow.yaml'
description: 'Execute workflow from another module'
- trigger: with-template
exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
tmpl: '{project-root}/.bmad/{module-code}/templates/{template-name}.md'
exec: '{project-root}/_bmad/core/tasks/create-doc.xml'
tmpl: '{project-root}/_bmad/{module-code}/templates/{template-name}.md'
description: 'Create document from template'
- trigger: with-data
exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml'
data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
exec: '{project-root}/_bmad/{module-code}/tasks/{task-name}.xml'
data: '{project-root}/_bmad/_cfg/agent-manifest.csv'
description: 'Execute task with data file'
```
@ -71,7 +71,7 @@ agent:
### Metadata
- **id**: Path with `.bmad` variable (resolved at install time)
- **id**: Path with `_bmad` variable (resolved at install time)
- **name**: Agent persona name
- **title**: Professional role
- **icon**: Single emoji
@ -101,7 +101,7 @@ persona:
```yaml
menu:
- trigger: create-prd
workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/prd/workflow.yaml'
description: 'Create Product Requirements Document'
```
@ -112,7 +112,7 @@ Invokes BMAD workflow engine to execute multi-step processes.
```yaml
menu:
- trigger: validate
exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
exec: '{project-root}/_bmad/core/tasks/validate-workflow.xml'
description: 'Validate document structure'
```
@ -123,8 +123,8 @@ Executes single-operation tasks.
```yaml
menu:
- trigger: create-brief
exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
tmpl: '{project-root}/.bmad/bmm/templates/brief.md'
exec: '{project-root}/_bmad/core/tasks/create-doc.xml'
tmpl: '{project-root}/_bmad/bmm/templates/brief.md'
description: 'Create a Product Brief from template'
```
@ -135,8 +135,8 @@ Combines task execution with template file.
```yaml
menu:
- trigger: team-standup
exec: '{project-root}/.bmad/bmm/tasks/standup.xml'
data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
exec: '{project-root}/_bmad/bmm/tasks/standup.xml'
data: '{project-root}/_bmad/_cfg/agent-manifest.csv'
description: 'Run team standup with agent roster'
```
@ -160,12 +160,12 @@ Control visibility based on platform:
```yaml
menu:
- trigger: advanced-elicitation
exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
exec: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
description: 'Advanced elicitation techniques'
web-only: true # Only shows in web bundle
- trigger: git-operations
exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml'
exec: '{project-root}/_bmad/bmm/tasks/git-flow.xml'
description: 'Git workflow operations'
ide-only: true # Only shows in IDE environments
```
@ -175,7 +175,7 @@ menu:
### Core Variables
- `{project-root}` - Root directory of installed project
- `.bmad` - BMAD installation folder (usually `.bmad`)
- `_bmad` - BMAD installation folder (usually `_bmad`)
- `{user_name}` - User's name from module config
- `{communication_language}` - Language preference
- `{output_folder}` - Document output directory
@ -186,10 +186,10 @@ menu:
```yaml
# GOOD
workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml"
workflow: "{project-root}/_bmad/bmm/workflows/prd/workflow.yaml"
# BAD
workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml"
workflow: "/Users/john/project/_bmad/bmm/workflows/prd/workflow.yaml"
# BAD
workflow: "../../../bmm/workflows/prd/workflow.yaml"
@ -208,7 +208,7 @@ Module agents use the same injection process as simple agents:
**Key difference:** Module agents load **module-specific config** instead of core config:
```xml
<step n="2">Load and read {project-root}/.bmad/{module}/config.yaml...</step>
<step n="2">Load and read {project-root}/_bmad/{module}/config.yaml...</step>
```
## Reference Examples
@ -252,15 +252,15 @@ Agents load this at activation for consistent behavior.
```yaml
menu:
- trigger: init
workflow: '{project-root}/.bmad/bmm/workflows/workflow-init/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/workflow-init/workflow.yaml'
description: 'Initialize workflow path (START HERE)'
- trigger: status
workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml'
description: 'Check current workflow status'
- trigger: next-step
workflow: '{project-root}/.bmad/bmm/workflows/next-step/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/next-step/workflow.yaml'
description: 'Execute next workflow in sequence'
```
@ -270,20 +270,20 @@ menu:
menu:
# Phase 1: Analysis
- trigger: brainstorm
workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
description: 'Guided brainstorming session'
- trigger: research
workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow.yaml'
description: 'Market and technical research'
# Phase 2: Planning
- trigger: prd
workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/2-planning/prd/workflow.yaml'
description: 'Create PRD'
- trigger: architecture
workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
workflow: '{project-root}/_bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
description: 'Design architecture'
```
@ -292,11 +292,11 @@ menu:
```yaml
menu:
- trigger: party-mode
workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
workflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.yaml'
description: 'Bring all agents together'
- trigger: brainstorm
workflow: '{project-root}/.bmad/cis/workflows/brainstorming/workflow.yaml'
workflow: '{project-root}/_bmad/cis/workflows/brainstorming/workflow.yaml'
description: 'Use CIS brainstorming techniques'
```
@ -317,7 +317,7 @@ menu:
```yaml
menu:
- trigger: start
workflow: '{project-root}/.bmad/{module}/workflows/init/workflow.yaml'
workflow: '{project-root}/_bmad/{module}/workflows/init/workflow.yaml'
description: 'Start new project (BEGIN HERE)'
```
@ -326,7 +326,7 @@ menu:
```yaml
menu:
- trigger: status
workflow: '{project-root}/.bmad/{module}/workflows/status/workflow.yaml'
workflow: '{project-root}/_bmad/{module}/workflows/status/workflow.yaml'
description: 'Check workflow progress'
```
@ -335,7 +335,7 @@ menu:
```yaml
menu:
- trigger: party
workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
workflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.yaml'
description: 'Multi-agent discussion'
```
@ -343,7 +343,7 @@ menu:
| Aspect | Module Agent | Simple/Expert Agent |
| ------------- | --------------------------- | ------------------------------- |
| Location | `.bmad/{module}/agents/` | `.bmad/custom/agents/` |
| Location | `_bmad/{module}/agents/` | `_bmad/custom/agents/` |
| Persona | Fixed, professional | Customizable via install_config |
| Handlebars | No templating | Yes, extensive |
| Menu actions | Workflows, tasks, templates | Prompts, inline actions |
@ -354,8 +354,8 @@ menu:
- [ ] Valid YAML syntax
- [ ] Metadata includes `module: "{module-code}"`
- [ ] id uses `.bmad/{module}/agents/{name}.md`
- [ ] All workflow paths use `{project-root}/.bmad/` prefix
- [ ] id uses `_bmad/{module}/agents/{name}.md`
- [ ] All workflow paths use `{project-root}/_bmad/` prefix
- [ ] No hardcoded paths
- [ ] No duplicate triggers
- [ ] Each menu item has description

6
src/modules/bmb/docs/agents/simple-agent-architecture.md
View File

@ -14,7 +14,7 @@ Self-contained agents with prompts, menus, and optional install-time customizati
```yaml
agent:
metadata:
id: .bmad/agents/{agent-name}/{agent-name}.md
id: _bmad/agents/{agent-name}/{agent-name}.md
name: 'Persona Name'
title: 'Agent Title'
icon: 'emoji'
@ -104,7 +104,7 @@ agent:
### Metadata
- **id**: Final compiled path (`.bmad/agents/{name}/{name}.md` for standalone)
- **id**: Final compiled path (`_bmad/agents/{name}/{name}.md` for standalone)
- **name**: Agent's persona name displayed to users
- **title**: Professional role/function
- **icon**: Single emoji for visual identification
@ -215,7 +215,7 @@ Features demonstrated:
```bash
# Copy to your project
cp /path/to/commit-poet.agent.yaml .bmad/custom/agents/
cp /path/to/commit-poet.agent.yaml _bmad/custom/agents/
# Create custom.yaml and install
echo "code: my-agent

12
src/modules/bmb/docs/agents/understanding-agent-types.md
View File

@ -7,7 +7,7 @@ ALL agent types can:
- ✓ Write to {output_folder}, {project-root}, or anywhere on system
- ✓ Update artifacts and files
- ✓ Execute bash commands
- ✓ Use core variables (.bmad, {output_folder}, etc.)
- ✓ Use core variables (\_bmad, {output_folder}, etc.)
- ✓ Have complex prompts and logic
- ✓ Invoke external tools
@ -98,11 +98,11 @@ agent:
menu:
- trigger: implement-story
workflow: '.bmad/bmm/workflows/dev-story/workflow.yaml'
workflow: '_bmad/bmm/workflows/dev-story/workflow.yaml'
description: Implement user story
- trigger: refactor
workflow: '.bmad/bmm/workflows/refactor/workflow.yaml'
workflow: '_bmad/bmm/workflows/refactor/workflow.yaml'
description: Refactor codebase
```
@ -122,7 +122,7 @@ agent:
### The Reality
- **Any agent type** (Simple, Expert, Module) can be bundled with or added to a module
- A Simple agent COULD live in `.bmad/bmm/agents/`
- A Simple agent COULD live in `_bmad/bmm/agents/`
- An Expert agent COULD be included in a module bundle
### What Makes a "Module Agent" Special
@ -138,14 +138,14 @@ A **Module Agent** is specifically:
**Simple Agent added to BMM:**
- Lives in `.bmad/bmm/agents/formatter.agent.yaml`
- Lives in `_bmad/bmm/agents/formatter.agent.yaml`
- Bundled with BMM for convenience
- But still stateless, self-contained
- NOT a "Module Agent" - just a Simple agent in a module
**Module Agent in BMM:**
- Lives in `.bmad/bmm/agents/tech-writer.agent.yaml`
- Lives in `_bmad/bmm/agents/tech-writer.agent.yaml`
- Orchestrates BMM documentation workflows
- Coordinates with other BMM agents (PM, Dev, Analyst)
- Included in default BMM bundle

2
src/modules/bmb/docs/workflows/architecture.md
View File

@ -69,7 +69,7 @@ workflow-folder/
Standard variables in step files:
```yaml
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/[workflow-name]'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/[workflow-name]'
thisStepFile: '{workflow_path}/steps/step-[N]-[name].md'
nextStepFile: '{workflow_path}/steps/step-[N+1]-[name].md'
workflowFile: '{workflow_path}/workflow.md'

6
src/modules/bmb/docs/workflows/common-workflow-tools.csv
View File

@ -1,7 +1,7 @@
propose,type,tool_name,description,url,requires_install
always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/.bmad/core/workflows/party-mode/workflow.md,no
always,task,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/.bmad/core/tasks/advanced-elicitation.xml,no
always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/.bmad/core/tasks/brainstorming.xml,no
always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/_bmad/core/workflows/party-mode/workflow.md,no
always,task,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/_bmad/core/tasks/advanced-elicitation.xml,no
always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/_bmad/core/tasks/brainstorming.xml,no
always,llm-tool-feature,web-browsing,"Provides LLM with capabilities to perform real-time web searches, extract relevant data, and incorporate current information into responses when up-to-date information is required beyond training knowledge.",,no
always,llm-tool-feature,file-io,"Enables LLM to manage file operations such as creating, reading, updating, and deleting files, facilitating seamless data handling, storage, and document management within user environments.",,no
always,llm-tool-feature,sub-agents,"Allows LLM to create and manage specialized sub-agents that handle specific tasks or modules within larger workflows, improving efficiency through parallel processing and modular task delegation.",,no

1 propose type tool_name description url requires_install
2 always workflow party-mode Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress. {project-root}/.bmad/core/workflows/party-mode/workflow.md {project-root}/_bmad/core/workflows/party-mode/workflow.md no
3 always task advanced-elicitation Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques. {project-root}/.bmad/core/tasks/advanced-elicitation.xml {project-root}/_bmad/core/tasks/advanced-elicitation.xml no
4 always task brainstorming Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration. {project-root}/.bmad/core/tasks/brainstorming.xml {project-root}/_bmad/core/tasks/brainstorming.xml no
5 always llm-tool-feature web-browsing Provides LLM with capabilities to perform real-time web searches, extract relevant data, and incorporate current information into responses when up-to-date information is required beyond training knowledge. no
6 always llm-tool-feature file-io Enables LLM to manage file operations such as creating, reading, updating, and deleting files, facilitating seamless data handling, storage, and document management within user environments. no
7 always llm-tool-feature sub-agents Allows LLM to create and manage specialized sub-agents that handle specific tasks or modules within larger workflows, improving efficiency through parallel processing and modular task delegation. no

2
src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md
View File

@ -13,7 +13,7 @@ description: 'Initialize the [workflow-type] workflow by detecting continuation
<!-- Path Definitions -->
workflow\*path: '{project-root}/.bmad/[module-path]/workflows/[workflow-name]'
workflow\*path: '{project-root}/\_bmad/[module-path]/workflows/[workflow-name]'
# File References (all use {variable} format in file)

2
src/modules/bmb/docs/workflows/templates/step-1b-template.md
View File

@ -13,7 +13,7 @@ description: 'Handle workflow continuation from previous session'
<!-- Path Definitions -->
workflow\*path: '{project-root}/.bmad/[module-path]/workflows/[workflow-name]'
workflow\*path: '{project-root}/\_bmad/[module-path]/workflows/[workflow-name]'
# File References (all use {variable} format in file)

6
src/modules/bmb/docs/workflows/templates/step-file.md
View File

@ -3,7 +3,7 @@ name: "step-{{stepNumber}}-{{stepName}}"
description: "{{stepDescription}}"
# Path Definitions
workflow_path: "{project-root}/.bmad/{{targetModule}}/workflows/{{workflowName}}"
workflow_path: "{project-root}/_bmad/{{targetModule}}/workflows/{{workflowName}}"
# File References
thisStepFile: "{workflow_path}/steps/step-{{stepNumber}}-{{stepName}}.md"
@ -16,8 +16,8 @@ outputFile: "{output_folder}/{{outputFileName}}-{project_name}.md"
{{/hasOutput}}
# Task References (list only if used in THIS step file instance and only the ones used, there might be others)
advancedElicitationTask: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"
partyModeWorkflow: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
advancedElicitationTask: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
partyModeWorkflow: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
{{#hasTemplates}}
# Template References

6
src/modules/bmb/docs/workflows/templates/step-template.md
View File

@ -11,7 +11,7 @@ description: '[Brief description of what this step accomplishes]'
<!-- Path Definitions -->
workflow\*path: '{project-root}/.bmad/[module]/reference/workflows/[workflow-name]' # the folder the workflow.md file is in
workflow\*path: '{project-root}/\_bmad/[module]/reference/workflows/[workflow-name]' # the folder the workflow.md file is in
# File References (all use {variable} format in file)
@ -23,8 +23,8 @@ outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
# Task References (IF THE workflow uses and it makes sense in this step to have these )
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/\_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/\_bmad/core/workflows/party-mode/workflow.md'
# Template References (if this step uses a specific templates)

4
src/modules/bmb/docs/workflows/templates/workflow-template.md
View File

@ -53,7 +53,7 @@ web_bundle: [true/false] # Set to true for inclusion in web bundle builds
### 1. Module Configuration Loading
Load and read full config from {project-root}/.bmad/[MODULE FOLDER]/config.yaml and resolve:
Load and read full config from {project-root}/\_bmad/[MODULE FOLDER]/config.yaml and resolve:
- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, [MODULE VARS]
@ -101,4 +101,4 @@ Example: Load, read the full file and then execute `{workflow_path}/steps/step-0
### NOTE: You can View a real example of a perfect workflow.md file that was created from this template
`{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md`
`{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md`

2
src/modules/bmb/docs/workflows/templates/workflow.md
View File

@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
### 1. Configuration Loading
Load and read full config from {project-root}/.bmad/{{targetModule}}/config.yaml and resolve:
Load and read full config from {project-root}/\_bmad/{{targetModule}}/config.yaml and resolve:
- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`

2
src/modules/bmb/reference/agents/module-examples/README.md
View File

@ -7,7 +7,7 @@ Reference examples for module-integrated agents.
Module agents integrate with BMAD module workflows (BMM, CIS, BMB). They:
- Orchestrate multi-step workflows
- Use `.bmad` path variables
- Use `_bmad` path variables
- Have fixed professional personas (no install_config)
- Reference module-specific configurations

10
src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml
View File

@ -10,7 +10,7 @@
agent:
metadata:
id: ".bmad/bmm/agents/security-engineer.md"
id: "_bmad/bmm/agents/security-engineer.md"
name: "Sam"
title: "Security Engineer"
icon: "🔐"
@ -32,11 +32,11 @@ agent:
menu:
# NOTE: These workflows are hypothetical examples assuming add to a module called bmm - not implemented
- trigger: threat-model
exec: "{project-root}/.bmad/bmm/workflows/threat-model/workflow.md"
exec: "{project-root}/_bmad/bmm/workflows/threat-model/workflow.md"
description: "Create STRIDE threat model for architecture"
- trigger: security-review
exec: "{project-root}/.bmad/bmm/workflows/security-review/workflow.md"
exec: "{project-root}/_bmad/bmm/workflows/security-review/workflow.md"
description: "Review code/design for security issues"
- trigger: owasp-check
@ -44,10 +44,10 @@ agent:
description: "Check against OWASP Top 10"
- trigger: compliance
exec: "{project-root}/.bmad/bmm/workflows/compliance-check/workflow.md"
exec: "{project-root}/_bmad/bmm/workflows/compliance-check/workflow.md"
description: "Verify compliance requirements (SOC2, GDPR, etc.)"
# Core workflow that exists
- trigger: party-mode
exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
description: "Multi-agent security discussion"

14
src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml
View File

@ -10,7 +10,7 @@
agent:
metadata:
id: ".bmad/cis/agents/trend-analyst.md"
id: "_bmad/cis/agents/trend-analyst.md"
name: "Nova"
title: "Trend Analyst"
icon: "📈"
@ -32,26 +32,26 @@ agent:
menu:
# NOTE: These workflows are hypothetical examples - not implemented
- trigger: scan-trends
exec: "{project-root}/.bmad/cis/workflows/trend-scan/workflow.md"
exec: "{project-root}/_bmad/cis/workflows/trend-scan/workflow.md"
description: "Scan for emerging trends in a domain"
- trigger: analyze-trend
exec: "{project-root}/.bmad/cis/workflows/trend-analysis/workflow.md"
exec: "{project-root}/_bmad/cis/workflows/trend-analysis/workflow.md"
description: "Deep dive on a specific trend"
- trigger: opportunity-map
exec: "{project-root}/.bmad/cis/workflows/opportunity-mapping/workflow.md"
exec: "{project-root}/_bmad/cis/workflows/opportunity-mapping/workflow.md"
description: "Map trend to strategic opportunities"
- trigger: competitor-trends
exec: "{project-root}/.bmad/cis/tasks/competitor-trend-watch.xml"
exec: "{project-root}/_bmad/cis/tasks/competitor-trend-watch.xml"
description: "Monitor competitor trend adoption"
# Core workflows that exist
- trigger: brainstorm
exec: "{project-root}/.bmad/core/workflows/brainstorming/workflow.md"
exec: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
description: "Brainstorm trend implications"
- trigger: party-mode
exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
description: "Discuss trends with other agents"

2
src/modules/bmb/reference/agents/simple-examples/README.md
View File

@ -127,7 +127,7 @@ This personality is maintained across ALL commands through the persona definitio
```yaml
agent:
metadata:
id: .bmad/agents/{agent-name}/{agent-name}.md # Build path
id: _bmad/agents/{agent-name}/{agent-name}.md # Build path
name: "Display Name"
title: "Professional Title"
icon: "🎭"

2
src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml
View File

@ -1,6 +1,6 @@
agent:
metadata:
id: .bmad/agents/commit-poet/commit-poet.md
id: _bmad/agents/commit-poet/commit-poet.md
name: "Inkwell Von Comitizen"
title: "Commit Message Artisan"
icon: "📜"

2
src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md
View File

@ -3,7 +3,7 @@ name: 'step-01-init'
description: 'Initialize the nutrition plan workflow by detecting continuation state and creating output document'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-01-init.md'

2
src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md
View File

@ -3,7 +3,7 @@ name: 'step-01b-continue'
description: 'Handle workflow continuation from previous session'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-01b-continue.md'

6
src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md
View File

@ -3,7 +3,7 @@ name: 'step-02-profile'
description: 'Gather comprehensive user profile information through collaborative conversation'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References (all use {variable} format in file)
thisStepFile: '{workflow_path}/steps/step-02-profile.md'
@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Template References
profileTemplate: '{workflow_path}/templates/profile-section.md'

6
src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md
View File

@ -3,7 +3,7 @@ name: 'step-03-assessment'
description: 'Analyze nutritional requirements, identify restrictions, and calculate target macros'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-03-assessment.md'
@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Data References
dietaryRestrictionsDB: '{workflow_path}/data/dietary-restrictions.csv'

10
src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md
View File

@ -3,7 +3,7 @@ name: 'step-04-strategy'
description: 'Design a personalized meal strategy that meets nutritional needs and fits lifestyle'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-04-strategy.md'
@ -13,8 +13,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Data References
recipeDatabase: '{workflow_path}/data/recipe-database.csv'
@ -167,8 +167,8 @@ Display: **Select an Option:** [A] Meal Variety Optimization [P] Chef & Dietitia
#### Menu Handling Logic:
- HALT and AWAIT ANSWER
- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md` with a chef and dietitian expert also as part of the party
- IF A: Execute `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md` with a chef and dietitian expert also as part of the party
- IF C: Save content to nutrition-plan.md, update frontmatter `stepsCompleted` to add 4 at the end of the array before loading next step, check cooking frequency:
- IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md`
- IF cooking frequency ≤ 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`

10
src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md
View File

@ -3,7 +3,7 @@ name: 'step-05-shopping'
description: 'Create a comprehensive shopping list that supports the meal strategy'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-05-shopping.md'
@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Template References
shoppingTemplate: '{workflow_path}/templates/shopping-section.md'
@ -157,8 +157,8 @@ Display: **Select an Option:** [A] Budget Optimization Strategies [P] Shopping P
#### Menu Handling Logic:
- HALT and AWAIT ANSWER
- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
- IF A: Execute `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
- IF C: Save content to nutrition-plan.md, update frontmatter `stepsCompleted` to add 5 at the end of the array before loading next step, then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)

10
src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md
View File

@ -3,7 +3,7 @@ name: 'step-06-prep-schedule'
description: "Create a realistic meal prep schedule that fits the user's lifestyle"
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
@ -11,8 +11,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Template References
prepScheduleTemplate: '{workflow_path}/templates/prep-schedule-section.md'
@ -178,8 +178,8 @@ Display: **Select an Option:** [A] Advanced Prep Techniques [P] Coach Perspectiv
#### Menu Handling Logic:
- HALT and AWAIT ANSWER
- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
- IF A: Execute `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
- IF C: update frontmatter `stepsCompleted` to add 6 at the end of the array before loading next step, mark workflow complete, display final message
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)

4
src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md
View File

@ -49,10 +49,10 @@ This uses **step-file architecture** for disciplined execution:
### 1. Configuration Loading
Load and read full config from {project-root}/.bmad/core/config.yaml and resolve:
Load and read full config from {project-root}/\_bmad/core/config.yaml and resolve:
- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
### 2. First Step EXECUTION
Load, read the full file and then execute `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.
Load, read the full file and then execute `{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.

4
src/modules/bmb/workflows-legacy/edit-module/README.md
View File

@ -106,7 +106,7 @@ Modules can share workflows:
```yaml
# In agent menu item:
workflow: '{project-root}/.bmad/other-module/workflows/shared-workflow/workflow.yaml'
workflow: '{project-root}/_bmad/other-module/workflows/shared-workflow/workflow.yaml'
```
Common patterns:
@ -151,7 +151,7 @@ Changes are reviewed and approved by you before being applied.
- Can configure web bundles
- Are the development source of truth
**Installed modules** (in .bmad/):
**Installed modules** (in \_bmad/):
- Are deployed to target projects
- Use config.yaml for user customization

4
src/modules/bmb/workflows-legacy/edit-module/checklist.md
View File

@ -5,7 +5,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
## Module Structure Validation
- [ ] Module has clear 3-letter code (bmm, bmb, cis, etc.)
- [ ] Module is in correct location (src/modules/ for source, .bmad/ for installed)
- [ ] Module is in correct location (src/modules/ for source, \_bmad/ for installed)
- [ ] agents/ directory exists
- [ ] workflows/ directory exists
- [ ] config.yaml exists in module root
@ -127,7 +127,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
- [ ] Web bundles configured in workflow.yaml files
- [ ] All referenced files included in web_bundle_files
- [ ] Paths are .bmad/-relative (not project-root)
- [ ] Paths are \_bmad/-relative (not project-root)
- [ ] No config_source references in web bundles
- [ ] Invoked workflows included in dependencies

8
src/modules/bmb/workflows-legacy/edit-module/instructions.md
View File

@ -1,7 +1,7 @@
# Edit Module - Module Editor 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/bmb/workflows/edit-module/workflow.yaml</critical>
<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/bmb/workflows/edit-module/workflow.yaml</critical>
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
<critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
<critical>Communicate all responses in {communication_language}</critical>
@ -9,7 +9,7 @@
<workflow>
<step n="1" goal="Load and deeply understand the target module">
<ask>What is the path to the module you want to edit? (provide path to module directory like .bmad/bmm/ or src/modules/bmm/)</ask>
<ask>What is the path to the module you want to edit? (provide path to module directory like _bmad/bmm/ or src/modules/bmm/)</ask>
<action>Load the module directory structure completely:
@ -187,7 +187,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look
**If setting up cross-module integration:**
- Identify which workflows from other modules are needed
- Show how to reference workflows properly: {project-root}/.bmad/{{module}}/workflows/{{workflow}}/workflow.yaml
- Show how to reference workflows properly: {project-root}/\_bmad/{{module}}/workflows/{{workflow}}/workflow.yaml
- Document the integration in README
- Ensure dependencies are clear
- Consider adding example usage

20
src/modules/bmb/workflows-legacy/edit-module/workflow.yaml
View File

@ -4,26 +4,26 @@ description: "Edit existing BMAD modules (structure, agents, workflows, document
author: "BMad"
# Critical variables load from config_source
config_source: "{project-root}/.bmad/bmb/config.yaml"
config_source: "{project-root}/_bmad/bmb/config.yaml"
communication_language: "{config_source}:communication_language"
user_name: "{config_source}:user_name"
# Required Data Files - Critical for understanding module conventions
module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
module_structure_guide: "{project-root}/_bmad/bmb/workflows/create-module/module-structure.md"
# Related workflow editors
agent_editor: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.yaml"
workflow_editor: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.yaml"
agent_editor: "{project-root}/_bmad/bmb/workflows/edit-agent/workflow.yaml"
workflow_editor: "{project-root}/_bmad/bmb/workflows/edit-workflow/workflow.yaml"
# Reference examples - for learning patterns
bmm_module_dir: "{project-root}/.bmad/bmm/"
bmb_module_dir: "{project-root}/.bmad/bmb/"
cis_module_dir: "{project-root}/.bmad/cis/"
existing_agents_dir: "{project-root}/.bmad/*/agents/"
existing_workflows_dir: "{project-root}/.bmad/*/workflows/"
bmm_module_dir: "{project-root}/_bmad/bmm/"
bmb_module_dir: "{project-root}/_bmad/bmb/"
cis_module_dir: "{project-root}/_bmad/cis/"
existing_agents_dir: "{project-root}/_bmad/*/agents/"
existing_workflows_dir: "{project-root}/_bmad/*/workflows/"
# Module path and component files
installed_path: "{project-root}/.bmad/bmb/workflows/edit-module"
installed_path: "{project-root}/_bmad/bmb/workflows/edit-module"
template: false # This is an action workflow - no template needed
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

4
src/modules/bmb/workflows-legacy/module-brief/README.md
View File

@ -254,8 +254,8 @@ To customize this workflow:
For issues or questions:
- Review the workflow creation guide at `/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
- Study existing module examples in `/.bmad/` for patterns and inspiration
- Review the workflow creation guide at `/_bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
- Study existing module examples in `/_bmad/` for patterns and inspiration
- Validate output using `checklist.md`
- Consult module structure guide at `create-module/module-structure.md`

4
src/modules/bmb/workflows-legacy/module-brief/instructions.md
View File

@ -1,7 +1,7 @@
# Module Brief 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/bmb/workflows/module-brief/workflow.yaml</critical>
<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/bmb/workflows/module-brief/workflow.yaml</critical>
<critical>Communicate in {communication_language} throughout the module brief creation process</critical>
<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>

8
src/modules/bmb/workflows-legacy/module-brief/workflow.yaml
View File

@ -4,15 +4,15 @@ description: "Create a comprehensive Module Brief that serves as the blueprint f
author: "BMad Builder"
# Critical variables
config_source: "{project-root}/.bmad/bmb/config.yaml"
config_source: "{project-root}/_bmad/bmb/config.yaml"
output_folder: "{config_source}:output_folder"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
# Reference examples and documentation
existing_modules_dir: "{project-root}/.bmad/"
module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
existing_modules_dir: "{project-root}/_bmad/"
module_structure_guide: "{project-root}/_bmad/bmb/workflows/create-module/module-structure.md"
# Optional user inputs - discovered if they exist
input_file_patterns:
@ -22,7 +22,7 @@ input_file_patterns:
load_strategy: "FULL_LOAD"
# Module path and component files
installed_path: "{project-root}/.bmad/bmb/workflows/module-brief"
installed_path: "{project-root}/_bmad/bmb/workflows/module-brief"
template: "{installed_path}/template.md"
instructions: "{installed_path}/instructions.md"
validation: "{installed_path}/checklist.md"

2
src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/README.md
View File

@ -7,7 +7,7 @@ Reference examples for module-integrated agents.
Module agents integrate with BMAD module workflows (BMM, CIS, BMB). They:
- Orchestrate multi-step workflows
- Use `.bmad` path variables
- Use `_bmad` path variables
- Have fixed professional personas (no install_config)
- Reference module-specific configurations

12
src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/security-engineer.agent.yaml
View File

@ -10,7 +10,7 @@
agent:
metadata:
id: ".bmad/bmm/agents/security-engineer.md"
id: "_bmad/bmm/agents/security-engineer.md"
name: "Sam"
title: "Security Engineer"
icon: "🔐"
@ -32,22 +32,22 @@ agent:
menu:
# NOTE: These workflows are hypothetical examples - not implemented
- trigger: threat-model
workflow: "{project-root}/.bmad/bmm/workflows/threat-model/workflow.yaml"
workflow: "{project-root}/_bmad/bmm/workflows/threat-model/workflow.yaml"
description: "Create STRIDE threat model for architecture"
- trigger: security-review
workflow: "{project-root}/.bmad/bmm/workflows/security-review/workflow.yaml"
workflow: "{project-root}/_bmad/bmm/workflows/security-review/workflow.yaml"
description: "Review code/design for security issues"
- trigger: owasp-check
exec: "{project-root}/.bmad/bmm/tasks/owasp-top-10.xml"
exec: "{project-root}/_bmad/bmm/tasks/owasp-top-10.xml"
description: "Check against OWASP Top 10"
- trigger: compliance
workflow: "{project-root}/.bmad/bmm/workflows/compliance-check/workflow.yaml"
workflow: "{project-root}/_bmad/bmm/workflows/compliance-check/workflow.yaml"
description: "Verify compliance requirements (SOC2, GDPR, etc.)"
# Core workflow that exists
- trigger: party-mode
exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
description: "Multi-agent security discussion"

14
src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/trend-analyst.agent.yaml
View File

@ -10,7 +10,7 @@
agent:
metadata:
id: ".bmad/cis/agents/trend-analyst.md"
id: "_bmad/cis/agents/trend-analyst.md"
name: "Nova"
title: "Trend Analyst"
icon: "📈"
@ -32,26 +32,26 @@ agent:
menu:
# NOTE: These workflows are hypothetical examples - not implemented
- trigger: scan-trends
workflow: "{project-root}/.bmad/cis/workflows/trend-scan/workflow.yaml"
workflow: "{project-root}/_bmad/cis/workflows/trend-scan/workflow.yaml"
description: "Scan for emerging trends in a domain"
- trigger: analyze-trend
workflow: "{project-root}/.bmad/cis/workflows/trend-analysis/workflow.yaml"
workflow: "{project-root}/_bmad/cis/workflows/trend-analysis/workflow.yaml"
description: "Deep dive on a specific trend"
- trigger: opportunity-map
workflow: "{project-root}/.bmad/cis/workflows/opportunity-mapping/workflow.yaml"
workflow: "{project-root}/_bmad/cis/workflows/opportunity-mapping/workflow.yaml"
description: "Map trend to strategic opportunities"
- trigger: competitor-trends
exec: "{project-root}/.bmad/cis/tasks/competitor-trend-watch.xml"
exec: "{project-root}/_bmad/cis/tasks/competitor-trend-watch.xml"
description: "Monitor competitor trend adoption"
# Core workflows that exist
- trigger: brainstorm
workflow: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml"
workflow: "{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml"
description: "Brainstorm trend implications"
- trigger: party-mode
exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
description: "Discuss trends with other agents"

2
src/modules/bmb/workflows/create-agent/data/reference/agents/simple-examples/README.md
View File

@ -127,7 +127,7 @@ This personality is maintained across ALL commands through the persona definitio
```yaml
agent:
metadata:
id: .bmad/agents/{agent-name}/{agent-name}.md # Build path
id: _bmad/agents/{agent-name}/{agent-name}.md # Build path
name: "Display Name"
title: "Professional Title"
icon: "🎭"

2
src/modules/bmb/workflows/create-agent/data/reference/agents/simple-examples/commit-poet.agent.yaml
View File

@ -1,6 +1,6 @@
agent:
metadata:
id: .bmad/agents/commit-poet/commit-poet.md
id: _bmad/agents/commit-poet/commit-poet.md
name: "Inkwell Von Comitizen"
title: "Commit Message Artisan"
icon: "📜"

2
src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01-init.md
View File

@ -3,7 +3,7 @@ name: 'step-01-init'
description: 'Initialize the nutrition plan workflow by detecting continuation state and creating output document'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-01-init.md'

2
src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md
View File

@ -3,7 +3,7 @@ name: 'step-01b-continue'
description: 'Handle workflow continuation from previous session'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-01b-continue.md'

6
src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md
View File

@ -3,7 +3,7 @@ name: 'step-02-profile'
description: 'Gather comprehensive user profile information through collaborative conversation'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References (all use {variable} format in file)
thisStepFile: '{workflow_path}/steps/step-02-profile.md'
@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Template References
profileTemplate: '{workflow_path}/templates/profile-section.md'

6
src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md
View File

@ -3,7 +3,7 @@ name: 'step-03-assessment'
description: 'Analyze nutritional requirements, identify restrictions, and calculate target macros'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-03-assessment.md'
@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Data References
dietaryRestrictionsDB: '{workflow_path}/data/dietary-restrictions.csv'

10
src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md
View File

@ -3,7 +3,7 @@ name: 'step-04-strategy'
description: 'Design a personalized meal strategy that meets nutritional needs and fits lifestyle'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-04-strategy.md'
@ -13,8 +13,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Data References
recipeDatabase: '{workflow_path}/data/recipe-database.csv'
@ -167,8 +167,8 @@ Display: **Select an Option:** [A] Meal Variety Optimization [P] Chef & Dietitia
#### Menu Handling Logic:
- HALT and AWAIT ANSWER
- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
- IF A: Execute `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
- IF C: Save content to nutrition-plan.md, update frontmatter, check cooking frequency:
- IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md`
- IF cooking frequency ≤ 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`

10
src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md
View File

@ -3,7 +3,7 @@ name: 'step-05-shopping'
description: 'Create a comprehensive shopping list that supports the meal strategy'
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-05-shopping.md'
@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Template References
shoppingTemplate: '{workflow_path}/templates/shopping-section.md'
@ -157,8 +157,8 @@ Display: **Select an Option:** [A] Budget Optimization Strategies [P] Shopping P
#### Menu Handling Logic:
- HALT and AWAIT ANSWER
- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
- IF A: Execute `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
- IF C: Save content to nutrition-plan.md, update frontmatter, then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md`
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)

10
src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md
View File

@ -3,7 +3,7 @@ name: 'step-06-prep-schedule'
description: "Create a realistic meal prep schedule that fits the user's lifestyle"
# Path Definitions
workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition'
workflow_path: '{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition'
# File References
thisStepFile: '{workflow_path}/steps/step-06-prep-schedule.md'
@ -11,8 +11,8 @@ workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/nutrition-plan-{project_name}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Template References
prepScheduleTemplate: '{workflow_path}/templates/prep-schedule-section.md'
@ -178,8 +178,8 @@ Display: **Select an Option:** [A] Advanced Prep Techniques [P] Coach Perspectiv
#### Menu Handling Logic:
- HALT and AWAIT ANSWER
- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md`
- IF A: Execute `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
- IF P: Execute `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
- IF C: Update frontmatter with all steps completed, mark workflow complete, display final message
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)

4
src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md
View File

@ -49,10 +49,10 @@ This uses **step-file architecture** for disciplined execution:
### 1. Configuration Loading
Load and read full config from {project-root}/.bmad/bmm/config.yaml and resolve:
Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve:
- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
### 2. First Step EXECUTION
Load, read the full file and then execute `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.
Load, read the full file and then execute `{project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow.

6
src/modules/bmb/workflows/create-agent/data/validation-complete.md
View File

@ -81,10 +81,10 @@
**Agent Documentation References**
- Agent compilation guide: `{project-root}/.bmad/bmb/docs/agents/agent-compilation.md`
- Agent types guide: `{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md`
- Agent compilation guide: `{project-root}/_bmad/bmb/docs/agents/agent-compilation.md`
- Agent types guide: `{project-root}/_bmad/bmb/docs/agents/understanding-agent-types.md`
- Architecture docs: simple, expert, module agent architectures
- Menu patterns guide: `{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md`
- Menu patterns guide: `{project-root}/_bmad/bmb/docs/agents/agent-menu-patterns.md`
- Status: ✅ ALL REFERENCES PRESERVED
**Communication Presets**

6
src/modules/bmb/workflows/create-agent/steps/step-01-brainstorm.md
View File

@ -10,11 +10,11 @@ thisStepFile: '{workflow_path}/steps/step-01-brainstorm.md'
nextStepFile: '{workflow_path}/steps/step-02-discover.md'
workflowFile: '{workflow_path}/workflow.md'
brainstormContext: '{workflow_path}/data/brainstorm-context.md'
brainstormWorkflow: '{project-root}/.bmad/core/workflows/brainstorming/workflow.md'
brainstormWorkflow: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 1: Optional Brainstorming

6
src/modules/bmb/workflows/create-agent/steps/step-02-discover.md
View File

@ -10,7 +10,7 @@ thisStepFile: '{workflow_path}/steps/step-02-discover.md'
nextStepFile: '{workflow_path}/steps/step-03-persona.md'
workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/agent-purpose-{project_name}.md'
agentTypesGuide: '{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md'
agentTypesGuide: '{project-root}/_bmad/bmb/docs/agents/understanding-agent-types.md'
simpleExamples: '{workflow_path}/data/reference/agents/simple-examples/'
expertExamples: '{workflow_path}/data/reference/agents/expert-examples/'
moduleExamples: '{workflow_path}/data/reference/agents/module-examples/'
@ -19,8 +19,8 @@ moduleExamples: '{workflow_path}/data/reference/agents/module-examples/'
agentPurposeTemplate: '{workflow_path}/templates/agent-purpose-and-type.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 2: Discover Agent Purpose and Type

6
src/modules/bmb/workflows/create-agent/steps/step-03-persona.md
View File

@ -11,14 +11,14 @@ nextStepFile: '{workflow_path}/steps/step-04-commands.md'
workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/agent-persona-{project_name}.md'
communicationPresets: '{workflow_path}/data/communication-presets.csv'
agentMenuPatterns: '{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md'
agentMenuPatterns: '{project-root}/_bmad/bmb/docs/agents/agent-menu-patterns.md'
# Template References
personaTemplate: '{workflow_path}/templates/agent-persona.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 3: Shape Agent's Personality

12
src/modules/bmb/workflows/create-agent/steps/step-04-commands.md
View File

@ -10,17 +10,17 @@ thisStepFile: '{workflow_path}/steps/step-04-commands.md'
nextStepFile: '{workflow_path}/steps/step-05-name.md'
workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/agent-commands-{project_name}.md'
agentMenuPatterns: '{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md'
simpleArchitecture: '{project-root}/.bmad/bmb/docs/agents/simple-agent-architecture.md'
expertArchitecture: '{project-root}/.bmad/bmb/docs/agents/expert-agent-architecture.md'
moduleArchitecture: '{project-root}/.bmad/bmb/docs/agents/module-agent-architecture.md'
agentMenuPatterns: '{project-root}/_bmad/bmb/docs/agents/agent-menu-patterns.md'
simpleArchitecture: '{project-root}/_bmad/bmb/docs/agents/simple-agent-architecture.md'
expertArchitecture: '{project-root}/_bmad/bmb/docs/agents/expert-agent-architecture.md'
moduleArchitecture: '{project-root}/_bmad/bmb/docs/agents/module-agent-architecture.md'
# Template References
commandsTemplate: '{workflow_path}/templates/agent-commands.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 4: Build Capabilities and Commands

4
src/modules/bmb/workflows/create-agent/steps/step-05-name.md
View File

@ -15,8 +15,8 @@ outputFile: '{output_folder}/agent-identity-{project_name}.md'
identityTemplate: '{workflow_path}/templates/agent-identity.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 5: Agent Naming and Identity

6
src/modules/bmb/workflows/create-agent/steps/step-06-build.md
View File

@ -10,15 +10,15 @@ thisStepFile: '{workflow_path}/steps/step-06-build.md'
nextStepFile: '{workflow_path}/steps/step-07-validate.md'
workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/agent-yaml-{project_name}.md'
moduleOutputFile: '{project-root}/.bmad/{target_module}/agents/{agent_filename}.agent.yaml'
moduleOutputFile: '{project-root}/_bmad/{target_module}/agents/{agent_filename}.agent.yaml'
standaloneOutputFile: '{workflow_path}/data/{agent_filename}/{agent_filename}.agent.yaml'
# Template References
completeAgentTemplate: '{workflow_path}/templates/agent-complete-{agent_type}.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 6: Build Complete Agent YAML

6
src/modules/bmb/workflows/create-agent/steps/step-07-validate.md
View File

@ -10,15 +10,15 @@ thisStepFile: '{workflow_path}/steps/step-07-validate.md'
nextStepFile: '{workflow_path}/steps/step-08-setup.md'
workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/agent-validation-{project_name}.md'
agentValidationChecklist: '{project-root}/.bmad/bmb/workflows/create-agent/agent-validation-checklist.md'
agentValidationChecklist: '{project-root}/_bmad/bmb/workflows/create-agent/agent-validation-checklist.md'
agentFile: '{{output_file_path}}'
# Template References
validationTemplate: '{workflow_path}/templates/validation-results.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 7: Quality Check and Validation

4
src/modules/bmb/workflows/create-agent/steps/step-08-setup.md
View File

@ -16,8 +16,8 @@ agentSidecarFolder: '{{standalone_output_folder}}/{{agent_filename}}-sidecar'
sidecarTemplate: '{workflow_path}/templates/expert-sidecar-structure.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 8: Expert Agent Workspace Setup

6
src/modules/bmb/workflows/create-agent/steps/step-09-customize.md
View File

@ -10,14 +10,14 @@ thisStepFile: '{workflow_path}/steps/step-09-customize.md'
nextStepFile: '{workflow_path}/steps/step-10-build-tools.md'
workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/agent-customization-{project_name}.md'
configOutputFile: '{project-root}/.bmad/_cfg/agents/{target_module}-{agent_filename}.customize.yaml'
configOutputFile: '{project-root}/_bmad/_cfg/agents/{target_module}-{agent_filename}.customize.yaml'
# Template References
customizationTemplate: '{workflow_path}/templates/agent-customization.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 9: Optional Customization File

4
src/modules/bmb/workflows/create-agent/steps/step-10-build-tools.md
View File

@ -17,8 +17,8 @@ compiledAgentFile: '{{output_folder}}/{{agent_filename}}.md'
buildHandlingTemplate: '{workflow_path}/templates/build-results.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 10: Build Tools Handling

4
src/modules/bmb/workflows/create-agent/steps/step-11-celebrate.md
View File

@ -16,8 +16,8 @@ compiledAgentFile: '{{compiled_agent_path}}'
completionTemplate: '{workflow_path}/templates/completion-summary.md'
# Task References
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 11: Celebration and Next Steps

20
src/modules/bmb/workflows/create-agent/workflow.md
View File

@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
### 1. Configuration Loading
Load and read full config from `{project-root}/.bmad/bmb/config.yaml`:
Load and read full config from `{project-root}/_bmad/bmb/config.yaml`:
- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
@ -63,12 +63,12 @@ Load, read completely, then execute `steps/step-01-brainstorm.md` to begin the w
# Technical documentation for agent building
agent_compilation: "{project-root}/.bmad/bmb/docs/agents/agent-compilation.md"
understanding_agent_types: "{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md"
simple_agent_architecture: "{project-root}/.bmad/bmb/docs/agents/simple-agent-architecture.md"
expert_agent_architecture: "{project-root}/.bmad/bmb/docs/agents/expert-agent-architecture.md"
module_agent_architecture: "{project-root}/.bmad/bmb/docs/agents/module-agent-architecture.md"
agent_menu_patterns: "{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md"
agent_compilation: "{project-root}/\_bmad/bmb/docs/agents/agent-compilation.md"
understanding_agent_types: "{project-root}/\_bmad/bmb/docs/agents/understanding-agent-types.md"
simple_agent_architecture: "{project-root}/\_bmad/bmb/docs/agents/simple-agent-architecture.md"
expert_agent_architecture: "{project-root}/\_bmad/bmb/docs/agents/expert-agent-architecture.md"
module_agent_architecture: "{project-root}/\_bmad/bmb/docs/agents/module-agent-architecture.md"
agent_menu_patterns: "{project-root}/\_bmad/bmb/docs/agents/agent-menu-patterns.md"
# Data and templates
@ -83,9 +83,9 @@ module_agent_examples: "{project-root}/bmb/reference/agents/module-examples/"
# Output configuration
custom_agent_location: "{project-root}/.bmad/custom/src/agents"
module_output_file: "{project-root}/.bmad/{target_module}/agents/{agent_filename}.agent.yaml"
custom_agent_location: "{project-root}/\_bmad/custom/src/agents"
module_output_file: "{project-root}/\_bmad/{target_module}/agents/{agent_filename}.agent.yaml"
standalone_output_folder: "{custom_agent_location}/{agent_filename}"
standalone_output_file: "{standalone_output_folder}/{agent_filename}.agent.yaml"
standalone_info_guide: "{standalone_output_folder}/info-and-installation-guide.md"
config_output_file: "{project-root}/.bmad/\_cfg/agents/{target_module}-{agent_filename}.customize.yaml"
config_output_file: "{project-root}/\_bmad/\_cfg/agents/{target_module}-{agent_filename}.customize.yaml"

4
src/modules/bmb/workflows/create-module/steps/step-01-init.md
View File

@ -2,8 +2,8 @@
nextStepFile: '{installed_path}/steps/step-02-concept.md'
continueFile: '{installed_path}/steps/step-01b-continue.md'
modulePlanTemplate: '{installed_path}/templates/module-plan.template.md'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
customModuleLocation: '{custom_module_location}'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
---

6
src/modules/bmb/workflows/create-module/steps/step-02-concept.md
View File

@ -1,10 +1,10 @@
---
installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
nextStepFile: '{installed_path}/steps/step-03-components.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
moduleStructureGuide: '{project-root}/bmb/workflows/create-agent-legacy/create-module/module-structure.md'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 2: Define Module Concept and Scope

6
src/modules/bmb/workflows/create-module/steps/step-03-components.md
View File

@ -1,10 +1,10 @@
---
installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
nextStepFile: '{installed_path}/steps/step-04-structure.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
agent_examples_path: '{project-root}/bmb/reference/agents/module-examples'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 3: Plan Module Components

6
src/modules/bmb/workflows/create-module/steps/step-04-structure.md
View File

@ -1,9 +1,9 @@
---
installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
nextStepFile: '{installed_path}/steps/step-05-config.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 4: Create Module Structure

8
src/modules/bmb/workflows/create-module/steps/step-05-config.md
View File

@ -1,9 +1,9 @@
---
installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
nextStepFile: '{installed_path}/steps/step-06-agents.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 5: Plan Module Configuration
@ -185,7 +185,7 @@ Update module-plan.md with configuration section:
### Result Configuration Structure
The module.yaml will generate:
- Module configuration at: .bmad/{module_code}/config.yaml
- Module configuration at: _bmad/{module_code}/config.yaml
- User settings stored as: [describe structure]
````

10
src/modules/bmb/workflows/create-module/steps/step-06-agents.md
View File

@ -1,11 +1,11 @@
---
installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
nextStepFile: '{installed_path}/steps/step-07-workflows.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
agentTemplate: '{installed_path}/templates/agent.template.md'
agent_examples_path: '{project-root}/bmb/reference/agents/module-examples'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 6: Create Module Agents
@ -183,7 +183,7 @@ agent:
triggers:
- party-mode:
input: SPM
route: '{project-root}/.bmad/core/workflows/edit-agent/workflow.md'
route: '{project-root}/_bmad/core/workflows/edit-agent/workflow.md'
type: exec
- expert-chat:
input: CH
@ -204,7 +204,7 @@ agent:
# Workflow only for complex processes
- trigger: 'complex-process'
route: '{project-root}/.bmad/{custom_module}/workflows/[workflow]/workflow.md'
route: '{project-root}/_bmad/{custom_module}/workflows/[workflow]/workflow.md'
description: 'Complex process [icon]'
# Quick inline actions

6
src/modules/bmb/workflows/create-module/steps/step-07-workflows.md
View File

@ -1,10 +1,10 @@
---
installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
nextStepFile: '{installed_path}/steps/step-08-installer.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
workflowPlanTemplate: '{installed_path}/templates/workflow-plan-template.md'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 7: Review Workflow Plans

8
src/modules/bmb/workflows/create-module/steps/step-08-installer.md
View File

@ -1,11 +1,11 @@
---
installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
nextStepFile: '{installed_path}/steps/step-09-documentation.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
installerTemplate: '{installed_path}/templates/installer.template.js'
installConfigTemplate: '{installed_path}/templates/install-config.template.yaml'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 8: Setup Module Installer
@ -131,7 +131,7 @@ Update module-plan.md with installer section:
1. User runs: `bmad install {module_name}`
2. Installer asks: [list of questions]
3. Creates: .bmad/{module_name}/
3. Creates: \_bmad/{module_name}/
4. Generates: config.yaml with user settings
### Validation

8
src/modules/bmb/workflows/create-module/steps/step-09-documentation.md
View File

@ -1,10 +1,10 @@
---
installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
nextStepFile: '{installed_path}/steps/step-10-roadmap.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
moduleReadmeFile: '{custom_module_location}/{module_name}/README.md'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 9: Create Module Documentation
@ -140,7 +140,7 @@ bmad install {module_name}
## Configuration
The module can be configured in `.bmad/{module_name}/config.yaml`
The module can be configured in `_bmad/{module_name}/config.yaml`
**Key Settings:**

6
src/modules/bmb/workflows/create-module/steps/step-10-roadmap.md
View File

@ -1,10 +1,10 @@
---
installed_path: '{project-root}/.bmad/bmb/workflows/create-module'
installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
nextStepFile: '{installed_path}/steps/step-11-validate.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
moduleTodoFile: '{custom_module_location}/{module_name}/TODO.md'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 10: Generate Development Roadmap

8
src/modules/bmb/workflows/create-module/steps/step-11-validate.md
View File

@ -2,8 +2,8 @@
workflowFile: '{installed_path}/workflow.md'
modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md'
validationChecklist: '{installed_path}/validation.md'
advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
---
# Step 11: Validate and Finalize Module
@ -297,8 +297,8 @@ Display: **Module Creation Complete!** [A] Advanced Elicitation [P] Party Mode [
#### Menu Handling Logic:
- IF A: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml for reflection on process
- IF P: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md to celebrate completion
- IF A: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml for reflection on process
- IF P: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md to celebrate completion
- IF C: Mark as complete and exit gracefully
- IF Any other comments or queries: help user respond then redisplay menu

Some files were not shown because too many files have changed in this diff Show More