ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

prettier no longer should screw up md files underscores

This commit is contained in:
Brian Madison 2025-12-23 22:29:51 +08:00
parent e4a4f47a1e
commit 925b715d4f
81 changed files with 187 additions and 187 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md
View File

@ -30,7 +30,7 @@
### IDE Manager & Base ### IDE Manager & Base
- @/tools/cli/installers/lib/ide/manager.js - IdeManager class (dynamic handler loading) - @/tools/cli/installers/lib/ide/manager.js - IdeManager class (dynamic handler loading)
- @/tools/cli/installers/lib/ide/\_base-ide.js - BaseIdeSetup class (all handlers extend this) - @/tools/cli/installers/lib/ide/_base-ide.js - BaseIdeSetup class (all handlers extend this)
### Shared Utilities ### Shared Utilities
@ -116,7 +116,7 @@ Contains:
- Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup - Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup
- Fix installer bug: Check installer.js (94KB - main logic) - Fix installer bug: Check installer.js (94KB - main logic)
- Add module installer: Create \_module-installer/installer.js if custom installer logic needed - Add module installer: Create _module-installer/installer.js if custom installer logic needed
- Update shared generators: Modify files in /shared/ directory - Update shared generators: Modify files in /shared/ directory
## Relationships ## Relationships

2
docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md
View File

@ -142,7 +142,7 @@ Defined in @/tools/cli/lib/platform-codes.js
## Common Tasks ## Common Tasks
- Create new module installer: Add \_module-installer/installer.js - Create new module installer: Add _module-installer/installer.js
- Add IDE sub-module: Create sub-modules/{ide-name}/ with config - Add IDE sub-module: Create sub-modules/{ide-name}/ with config
- Add new IDE support: Create handler in installers/lib/ide/ - Add new IDE support: Create handler in installers/lib/ide/
- Customize module installation: Modify module.yaml - Customize module installation: Modify module.yaml

2
docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-01-init.md
View File

@ -66,7 +66,7 @@ To set up the quiz game by selecting game mode, choosing a category, and prepari
### 1. Welcome and Configuration Loading ### 1. Welcome and Configuration Loading
Load config from {project-root}/\_bmad/bmb/config.yaml to get user_name. Load config from {project-root}/_bmad/bmb/config.yaml to get user_name.
Present dramatic welcome: Present dramatic welcome:
"🎺 _DRAMATIC MUSIC PLAYS_ 🎺 "🎺 _DRAMATIC MUSIC PLAYS_ 🎺

2
docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/workflow.md
View File

@ -45,7 +45,7 @@ web_bundle: true
### 1. Module Configuration Loading ### 1. Module Configuration Loading
Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve: Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
- `user_name`, `output_folder`, `communication_language`, `document_output_language` - `user_name`, `output_folder`, `communication_language`, `document_output_language`

4
package.json
View File

@ -27,8 +27,8 @@
"bmad:install": "node tools/cli/bmad-cli.js install", "bmad:install": "node tools/cli/bmad-cli.js install",
"bundle": "node tools/cli/bundlers/bundle-web.js all", "bundle": "node tools/cli/bundlers/bundle-web.js all",
"flatten": "node tools/flattener/main.js", "flatten": "node tools/flattener/main.js",
"format:check": "prettier --check \"**/*.{js,cjs,mjs,json,md,yaml}\"", "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,yaml}\"",
"format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,md,yaml}\"", "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,yaml}\"",
"install:bmad": "node tools/cli/bmad-cli.js install", "install:bmad": "node tools/cli/bmad-cli.js install",
"lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0", "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0",
"lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix", "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix",

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

@ -355,8 +355,8 @@ identity: |
- [ ] Sidecar folder structure created and populated - [ ] Sidecar folder structure created and populated
- [ ] memories.md has clear section structure - [ ] memories.md has clear section structure
- [ ] instructions.md contains core directives - [ ] instructions.md contains core directives
- [ ] Menu actions reference \_bmad/\_memory correctly - [ ] Menu actions reference _bmad/_memory correctly
- [ ] File paths use \_bmad/\_memory/[agentname]-sidecar/ to reference sidecar content - [ ] File paths use _bmad/_memory/[agentname]-sidecar/ to reference sidecar content
- [ ] Install config personalizes sidecar references - [ ] Install config personalizes sidecar references
- [ ] Agent folder named consistently: `{agent-name}/` - [ ] Agent folder named consistently: `{agent-name}/`
- [ ] YAML file named: `{agent-name}.agent.yaml` - [ ] YAML file named: `{agent-name}.agent.yaml`

2
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 - ✓ Write to {output_folder}, {project-root}, or anywhere on system
- ✓ Update artifacts and files - ✓ Update artifacts and files
- ✓ Execute bash commands - ✓ Execute bash commands
- ✓ Use core variables (\_bmad, {output_folder}, etc.) - ✓ Use core variables (_bmad, {output_folder}, etc.)
- ✓ Have complex prompts and logic - ✓ Have complex prompts and logic
- ✓ Invoke external tools - ✓ Invoke external tools

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 --> <!-- 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) # File References (all use {variable} format in file)

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 --> <!-- 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) # 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 ) # 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' advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
partyModeWorkflow: '{project-root}/\_bmad/core/workflows/party-mode/workflow.md' partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
# Template References (if this step uses a specific templates) # Template References (if this step uses a specific templates)

2
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 ### 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] - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, [MODULE VARS]

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 ### 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` - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`

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

@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
### 1. Configuration Loading ### 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` - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`

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

@ -126,7 +126,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
- [ ] Web bundles configured in workflow.yaml files - [ ] Web bundles configured in workflow.yaml files
- [ ] All referenced files included in web_bundle_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 - [ ] No config_source references in web bundles
- [ ] Invoked workflows included in dependencies - [ ] Invoked workflows included in dependencies

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

@ -1,7 +1,7 @@
# Edit Module - Module Editor Instructions # Edit Module - Module Editor Instructions
<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmb/workflows/edit-module/workflow.yaml</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>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>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
<critical>Communicate all responses in {communication_language}</critical> <critical>Communicate all responses in {communication_language}</critical>
@ -186,7 +186,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look
**If setting up cross-module integration:** **If setting up cross-module integration:**
- Identify which workflows from other modules are needed - 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 - Document the integration in README
- Ensure dependencies are clear - Ensure dependencies are clear
- Consider adding example usage - Consider adding example usage

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

@ -1,7 +1,7 @@
# Module Brief Instructions # Module Brief Instructions
<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmb/workflows/module-brief/workflow.yaml</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>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> <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>

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

@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
### 1. Configuration Loading ### 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` - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`

6
src/modules/bmb/workflows/create-agent/templates/expert-agent.template.md
View File

@ -313,7 +313,7 @@ critical_actions:
1. **Load sidecar files in critical_actions** - Must be explicit and MANDATORY 1. **Load sidecar files in critical_actions** - Must be explicit and MANDATORY
2. **Enforce domain restrictions** - Clear boundaries prevent scope creep 2. **Enforce domain restrictions** - Clear boundaries prevent scope creep
3. **Use \_bmad/\_memory/[agentname]-sidcar/ paths** - For reference to any sidecar content 3. **Use _bmad/_memory/[agentname]-sidcar/ paths** - For reference to any sidecar content
4. **Design for memory growth** - Structure sidecar files for accumulation 4. **Design for memory growth** - Structure sidecar files for accumulation
5. **Reference past naturally** - Don't dump memory, weave it into conversation 5. **Reference past naturally** - Don't dump memory, weave it into conversation
6. **Separate concerns** - Memories, instructions, knowledge in distinct files 6. **Separate concerns** - Memories, instructions, knowledge in distinct files
@ -356,8 +356,8 @@ identity: |
- [ ] Sidecar folder structure created and populated - [ ] Sidecar folder structure created and populated
- [ ] memories.md has clear section structure - [ ] memories.md has clear section structure
- [ ] instructions.md contains core directives - [ ] instructions.md contains core directives
- [ ] Menu actions reference \_bmad/\_memory/[agentname]-sidcar/ correctly if needing sidecar content reference - [ ] Menu actions reference _bmad/_memory/[agentname]-sidcar/ correctly if needing sidecar content reference
- [ ] File paths use \_bmad/\_memory/[agentname]-sidcar/ to reference where the file will be after sidecar content is installed - [ ] File paths use _bmad/_memory/[agentname]-sidcar/ to reference where the file will be after sidecar content is installed
- [ ] Install config personalizes sidecar references - [ ] Install config personalizes sidecar references
- [ ] Agent folder named consistently: `{agent-name}/` - [ ] Agent folder named consistently: `{agent-name}/`
- [ ] YAML file named: `{agent-name}.agent.yaml` - [ ] YAML file named: `{agent-name}.agent.yaml`

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

@ -129,7 +129,7 @@ Create all directories in {bmb_creations_output_folder}/{module_name}/:
3. **tasks/** - For task files (if tasks planned) 3. **tasks/** - For task files (if tasks planned)
4. **templates/** - For shared templates 4. **templates/** - For shared templates
5. **data/** - For module data 5. **data/** - For module data
6. **\_module-installer/** - For installation configuration 6. **_module-installer/** - For installation configuration
### 4. Create Placeholder README ### 4. Create Placeholder README

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

@ -71,8 +71,8 @@ From step 5, we planned these configuration fields:
### 2. Create Installer Directory ### 2. Create Installer Directory
Ensure \_module-installer directory exists Ensure _module-installer directory exists
Directory: {bmb_creations_output_folder}/{module_name}/\_module-installer/ Directory: {bmb_creations_output_folder}/{module_name}/_module-installer/
### 3. Create module.yaml ### 3. Create module.yaml
@ -95,7 +95,7 @@ Does your module need any special setup during installation? For example:
"I'll create an installer.js file for custom logic." "I'll create an installer.js file for custom logic."
Create file: {bmb_creations_output_folder}/{module_name}/\_module-installer/installer.js from {installerTemplate} Create file: {bmb_creations_output_folder}/{module_name}/_module-installer/installer.js from {installerTemplate}
Update installer.js with module-specific logic Update installer.js with module-specific logic
@ -105,7 +105,7 @@ Update installer.js with module-specific logic
If your module needs to copy files during installation (templates, examples, documentation), we can add them to the assets directory." If your module needs to copy files during installation (templates, examples, documentation), we can add them to the assets directory."
Create directory: \_module-installer/assets/ Create directory: _module-installer/assets/
Add note about what assets to include Add note about what assets to include
### 6. Document Installer Setup ### 6. Document Installer Setup
@ -131,7 +131,7 @@ Update module-plan.md with installer section:
1. User runs: `bmad install {module_name}` 1. User runs: `bmad install {module_name}`
2. Installer asks: [list of questions] 2. Installer asks: [list of questions]
3. Creates: \_bmad/{module_name}/ 3. Creates: _bmad/{module_name}/
4. Generates: config.yaml with user settings 4. Generates: config.yaml with user settings
### Validation ### Validation

2
src/modules/bmb/workflows/create-module/templates/agent.template.md
View File

@ -264,7 +264,7 @@ Analyze the visual design with my signature dramatic flair
menu: # Core interactions - multi: "[CH] Chat with Caravaggio or [SPM] Start Party Mode" menu: # Core interactions - multi: "[CH] Chat with Caravaggio or [SPM] Start Party Mode"
triggers: - party-mode: triggers: - party-mode:
input: SPM or fuzzy match start party mode input: SPM or fuzzy match start party mode
route: "{project-root}/\_bmad/core/workflows/edit-agent/workflow.md" route: "{project-root}/_bmad/core/workflows/edit-agent/workflow.md"
data: what's being discussed, plus custom party agents if specified data: what's being discussed, plus custom party agents if specified
type: exec - expert-chat: type: exec - expert-chat:
input: CH or fuzzy match validate agent input: CH or fuzzy match validate agent

4
src/modules/bmb/workflows/create-module/validation.md
View File

@ -11,11 +11,11 @@ This document provides the validation criteria used in step-11-validate.md to en
- [ ] tasks/ - Task files (if needed) - [ ] tasks/ - Task files (if needed)
- [ ] templates/ - Shared templates - [ ] templates/ - Shared templates
- [ ] data/ - Module data - [ ] data/ - Module data
- [ ] \_module-installer/ - Installation config - [ ] _module-installer/ - Installation config
- [ ] README.md - Module documentation - [ ] README.md - Module documentation
- [ ] module.yaml - module config file - [ ] module.yaml - module config file
### Optional File in \_module-installer/ ### Optional File in _module-installer/
- [ ] installer.js - Custom logic (if needed) - [ ] installer.js - Custom logic (if needed)

2
src/modules/bmb/workflows/create-module/workflow.md
View File

@ -46,7 +46,7 @@ installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
### 1. Module Configuration Loading ### 1. Module Configuration Loading
Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve: Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder` - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`

4
src/modules/bmb/workflows/create-workflow/steps/step-07-build.md
View File

@ -72,7 +72,7 @@ To generate all the workflow files (workflow.md, step files, templates, and supp
- When building continuable step-01-init.md files, use template `{project-root}/_bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md` - When building continuable step-01-init.md files, use template `{project-root}/_bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md`
- When building continuation steps, use template `{project-root}/_bmad/bmb/docs/workflows/templates/step-1b-template.md` - When building continuation steps, use template `{project-root}/_bmad/bmb/docs/workflows/templates/step-1b-template.md`
- When building the main workflow.md file, you must follow template `{project-root}/_bmad/bmb/docs/workflows/templates/workflow-template.md` - When building the main workflow.md file, you must follow template `{project-root}/_bmad/bmb/docs/workflows/templates/workflow-template.md`
- Example step files from {project-root}/\_bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md for patterns - Example step files from {project-root}/_bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md for patterns
## FILE GENERATION SEQUENCE: ## FILE GENERATION SEQUENCE:
@ -117,7 +117,7 @@ Load and follow {workflowTemplate}:
- Create workflow.md using template structure - Create workflow.md using template structure
- Insert workflow name and description - Insert workflow name and description
- Configure all path variables ({project-root}, \_bmad, {workflow_path}) - Configure all path variables ({project-root}, _bmad, {workflow_path})
- Set web_bundle flag to true unless user has indicated otherwise - Set web_bundle flag to true unless user has indicated otherwise
- Define role and goal - Define role and goal
- Include initialization path to step-01 - Include initialization path to step-01

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

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

2
src/modules/bmb/workflows/edit-agent/workflow.md
View File

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

2
src/modules/bmb/workflows/edit-workflow/workflow.md
View File

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

2
src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md
View File

@ -135,7 +135,7 @@ For each deviation:
- Configuration Loading uses correct path format: `{project-root}/_bmad/[module]/config.yaml` (variable substitution pattern) - Configuration Loading uses correct path format: `{project-root}/_bmad/[module]/config.yaml` (variable substitution pattern)
- First step follows pattern: `step-01-init.md` OR documented deviation - First step follows pattern: `step-01-init.md` OR documented deviation
- Required config variables properly listed - Required config variables properly listed
- Variables use proper substitution pattern: {project-root}, \_bmad, {workflow_path}, etc. - Variables use proper substitution pattern: {project-root}, _bmad, {workflow_path}, etc.
For violations: For violations:

2
src/modules/bmb/workflows/workflow-compliance-check/workflow.md
View File

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

2
src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md
View File

@ -1,4 +1,4 @@
<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical> <critical>Communicate all responses in {communication_language}</critical>
<critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques</critical> <critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques</critical>

2
src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md
View File

@ -1,6 +1,6 @@
# Game Brief - Interactive Workflow Instructions # Game Brief - Interactive Workflow Instructions
<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical> <critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
<critical>Generate all documents in {document_output_language}</critical> <critical>Generate all documents in {document_output_language}</critical>

2
src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md
View File

@ -2,7 +2,7 @@
<workflow> <workflow>
<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already completed the GDD workflow</critical> <critical>You MUST have already completed the GDD workflow</critical>
<critical>Communicate all responses in {communication_language}</critical> <critical>Communicate all responses in {communication_language}</critical>
<critical>This workflow creates detailed narrative content for story-driven games</critical> <critical>This workflow creates detailed narrative content for story-driven games</critical>

2
src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md
View File

@ -2,7 +2,7 @@
<workflow name="architecture"> <workflow name="architecture">
<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical> <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
<critical>The goal is ARCHITECTURAL DECISIONS that prevent AI agent conflicts, not detailed implementation specs</critical> <critical>The goal is ARCHITECTURAL DECISIONS that prevent AI agent conflicts, not detailed implementation specs</critical>

4
src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-02-generate.md
View File

@ -28,8 +28,8 @@ This step will generate content and present choices for each rule category:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding

2
src/modules/bmgd/workflows/4-production/correct-course/checklist.md
View File

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

4
src/modules/bmgd/workflows/4-production/correct-course/instructions.md
View File

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

4
src/modules/bmgd/workflows/4-production/retrospective/instructions.md
View File

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

4
src/modules/bmgd/workflows/4-production/sprint-planning/instructions.md
View File

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

4
src/modules/bmgd/workflows/4-production/sprint-status/instructions.md
View File

@ -1,7 +1,7 @@
# Sprint Status - Multi-Mode Service # Sprint Status - Multi-Mode Service
<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {project-root}/_bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml</critical>
<critical>Modes: interactive (default), validate, data</critical> <critical>Modes: interactive (default), validate, data</critical>
<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines.</critical> <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines.</critical>

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

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

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

@ -1,7 +1,7 @@
# Workflow Status Check - Multi-Mode Service (BMGD) # Workflow Status Check - Multi-Mode Service (BMGD)
<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmgd/workflows/workflow-status/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml</critical>
<critical>This workflow operates in multiple modes: interactive (default), validate, data, init-check, update</critical> <critical>This workflow operates in multiple modes: interactive (default), validate, data, init-check, update</critical>
<critical>Other workflows can call this as a service to avoid duplicating status logic</critical> <critical>Other workflows can call this as a service to avoid duplicating status logic</critical>
<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions.</critical> <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions.</critical>

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

@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
### 1. Configuration Loading ### 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`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level` - `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -160,7 +160,7 @@ Show the generated core experience content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current core experience content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current core experience content
- Process the enhanced experience insights that come back - Process the enhanced experience insights that come back
- Ask user: "Accept these improvements to the core experience definition? (y/n)" - Ask user: "Accept these improvements to the core experience definition? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -168,7 +168,7 @@ Show the generated core experience content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current core experience definition - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current core experience definition
- Process the collaborative experience improvements that come back - Process the collaborative experience improvements that come back
- Ask user: "Accept these changes to the core experience definition? (y/n)" - Ask user: "Accept these changes to the core experience definition? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -163,7 +163,7 @@ Show the generated emotional response content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current emotional response content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current emotional response content
- Process the enhanced emotional insights that come back - Process the enhanced emotional insights that come back
- Ask user: "Accept these improvements to the emotional response definition? (y/n)" - Ask user: "Accept these improvements to the emotional response definition? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -171,7 +171,7 @@ Show the generated emotional response content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current emotional response definition - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current emotional response definition
- Process the collaborative emotional insights that come back - Process the collaborative emotional insights that come back
- Ask user: "Accept these changes to the emotional response definition? (y/n)" - Ask user: "Accept these changes to the emotional response definition? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -178,7 +178,7 @@ Show the generated inspiration analysis content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current inspiration analysis content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current inspiration analysis content
- Process the enhanced pattern insights that come back - Process the enhanced pattern insights that come back
- Ask user: "Accept these improvements to the inspiration analysis? (y/n)" - Ask user: "Accept these improvements to the inspiration analysis? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -186,7 +186,7 @@ Show the generated inspiration analysis content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis
- Process the collaborative pattern insights that come back - Process the collaborative pattern insights that come back
- Ask user: "Accept these changes to the inspiration analysis? (y/n)" - Ask user: "Accept these changes to the inspiration analysis? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -196,7 +196,7 @@ Show the generated design system content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current design system content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current design system content
- Process the enhanced design system insights that come back - Process the enhanced design system insights that come back
- Ask user: "Accept these improvements to the design system decision? (y/n)" - Ask user: "Accept these improvements to the design system decision? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -204,7 +204,7 @@ Show the generated design system content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current design system choice - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design system choice
- Process the collaborative design system insights that come back - Process the collaborative design system insights that come back
- Ask user: "Accept these changes to the design system decision? (y/n)" - Ask user: "Accept these changes to the design system decision? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -198,7 +198,7 @@ Show the generated defining experience content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current defining experience content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current defining experience content
- Process the enhanced experience insights that come back - Process the enhanced experience insights that come back
- Ask user: "Accept these improvements to the defining experience? (y/n)" - Ask user: "Accept these improvements to the defining experience? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -206,7 +206,7 @@ Show the generated defining experience content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current defining experience - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current defining experience
- Process the collaborative experience insights that come back - Process the collaborative experience insights that come back
- Ask user: "Accept these changes to the defining experience? (y/n)" - Ask user: "Accept these changes to the defining experience? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -168,7 +168,7 @@ Show the generated visual foundation content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current visual foundation content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current visual foundation content
- Process the enhanced visual insights that come back - Process the enhanced visual insights that come back
- Ask user: "Accept these improvements to the visual foundation? (y/n)" - Ask user: "Accept these improvements to the visual foundation? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -176,7 +176,7 @@ Show the generated visual foundation content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current visual foundation - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current visual foundation
- Process the collaborative visual insights that come back - Process the collaborative visual insights that come back
- Ask user: "Accept these changes to the visual foundation? (y/n)" - Ask user: "Accept these changes to the visual foundation? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -168,7 +168,7 @@ Show the generated design direction content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current design direction content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current design direction content
- Process the enhanced design insights that come back - Process the enhanced design insights that come back
- Ask user: "Accept these improvements to the design direction? (y/n)" - Ask user: "Accept these improvements to the design direction? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -176,7 +176,7 @@ Show the generated design direction content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current design direction - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design direction
- Process the collaborative design insights that come back - Process the collaborative design insights that come back
- Ask user: "Accept these changes to the design direction? (y/n)" - Ask user: "Accept these changes to the design direction? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -186,7 +186,7 @@ Show the generated user journey content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current user journey content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current user journey content
- Process the enhanced journey insights that come back - Process the enhanced journey insights that come back
- Ask user: "Accept these improvements to the user journeys? (y/n)" - Ask user: "Accept these improvements to the user journeys? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -194,7 +194,7 @@ Show the generated user journey content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current user journeys - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current user journeys
- Process the collaborative journey insights that come back - Process the collaborative journey insights that come back
- Ask user: "Accept these changes to the user journeys? (y/n)" - Ask user: "Accept these changes to the user journeys? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -192,7 +192,7 @@ Show the generated component strategy content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current component strategy content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current component strategy content
- Process the enhanced component insights that come back - Process the enhanced component insights that come back
- Ask user: "Accept these improvements to the component strategy? (y/n)" - Ask user: "Accept these improvements to the component strategy? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -200,7 +200,7 @@ Show the generated component strategy content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current component strategy - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current component strategy
- Process the collaborative component insights that come back - Process the collaborative component insights that come back
- Ask user: "Accept these changes to the component strategy? (y/n)" - Ask user: "Accept these changes to the component strategy? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -181,7 +181,7 @@ Show the generated UX patterns content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current UX patterns content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current UX patterns content
- Process the enhanced pattern insights that come back - Process the enhanced pattern insights that come back
- Ask user: "Accept these improvements to the UX patterns? (y/n)" - Ask user: "Accept these improvements to the UX patterns? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -189,7 +189,7 @@ Show the generated UX patterns content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current UX patterns - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current UX patterns
- Process the collaborative pattern insights that come back - Process the collaborative pattern insights that come back
- Ask user: "Accept these changes to the UX patterns? (y/n)" - Ask user: "Accept these changes to the UX patterns? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

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

@ -29,8 +29,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -208,7 +208,7 @@ Show the generated responsive and accessibility content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content
- Process the enhanced insights that come back - Process the enhanced insights that come back
- Ask user: "Accept these improvements to the responsive/accessibility strategy? (y/n)" - Ask user: "Accept these improvements to the responsive/accessibility strategy? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -216,7 +216,7 @@ Show the generated responsive and accessibility content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy
- Process the collaborative insights that come back - Process the collaborative insights that come back
- Ask user: "Accept these changes to the responsive/accessibility strategy? (y/n)" - Ask user: "Accept these changes to the responsive/accessibility strategy? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

8
src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md
View File

@ -49,8 +49,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -228,7 +228,7 @@ Show the generated content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current success criteria content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current success criteria content
- Process the enhanced success metrics that come back - Process the enhanced success metrics that come back
- Ask user: "Accept these improvements to the success criteria? (y/n)" - Ask user: "Accept these improvements to the success criteria? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -236,7 +236,7 @@ Show the generated content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current success criteria - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current success criteria
- Process the collaborative improvements to metrics and scope - Process the collaborative improvements to metrics and scope
- Ask user: "Accept these changes to the success criteria? (y/n)" - Ask user: "Accept these changes to the success criteria? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

8
src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md
View File

@ -49,8 +49,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -222,7 +222,7 @@ Show the generated journey content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current journey content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current journey content
- Process the enhanced journey insights that come back - Process the enhanced journey insights that come back
- Ask user: "Accept these improvements to the user journeys? (y/n)" - Ask user: "Accept these improvements to the user journeys? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -230,7 +230,7 @@ Show the generated journey content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current journeys - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current journeys
- Process the collaborative journey improvements and additions - Process the collaborative journey improvements and additions
- Ask user: "Accept these changes to the user journeys? (y/n)" - Ask user: "Accept these changes to the user journeys? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

8
src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md
View File

@ -52,8 +52,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -207,7 +207,7 @@ Show the generated domain content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current domain content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current domain content
- Process the enhanced domain insights that come back - Process the enhanced domain insights that come back
- Ask user: "Accept these domain requirement improvements? (y/n)" - Ask user: "Accept these domain requirement improvements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -215,7 +215,7 @@ Show the generated domain content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current domain requirements - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current domain requirements
- Process the collaborative domain expertise and validation - Process the collaborative domain expertise and validation
- Ask user: "Accept these changes to domain requirements? (y/n)" - Ask user: "Accept these changes to domain requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

8
src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md
View File

@ -52,8 +52,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -186,7 +186,7 @@ Show the generated innovation content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current innovation content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current innovation content
- Process the enhanced innovation insights that come back - Process the enhanced innovation insights that come back
- Ask user: "Accept these improvements to the innovation analysis? (y/n)" - Ask user: "Accept these improvements to the innovation analysis? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -194,7 +194,7 @@ Show the generated innovation content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current innovation content - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current innovation content
- Process the collaborative innovation exploration and ideation - Process the collaborative innovation exploration and ideation
- Ask user: "Accept these changes to the innovation analysis? (y/n)" - Ask user: "Accept these changes to the innovation analysis? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

8
src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md
View File

@ -52,8 +52,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -182,7 +182,7 @@ Show the generated project-type content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current project-type content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current project-type content
- Process the enhanced technical insights that come back - Process the enhanced technical insights that come back
- Ask user: "Accept these improvements to the technical requirements? (y/n)" - Ask user: "Accept these improvements to the technical requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -190,7 +190,7 @@ Show the generated project-type content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current project-type requirements - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project-type requirements
- Process the collaborative technical expertise and validation - Process the collaborative technical expertise and validation
- Ask user: "Accept these changes to the technical requirements? (y/n)" - Ask user: "Accept these changes to the technical requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

8
src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md
View File

@ -50,8 +50,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -243,7 +243,7 @@ Show the scoping decisions and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with current scoping analysis - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current scoping analysis
- Process enhanced scoping insights that come back - Process enhanced scoping insights that come back
- Ask user: "Accept these improvements to the scoping decisions? (y/n)" - Ask user: "Accept these improvements to the scoping decisions? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu
@ -251,7 +251,7 @@ Show the scoping decisions and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with scoping context - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with scoping context
- Process collaborative insights on MVP and roadmap decisions - Process collaborative insights on MVP and roadmap decisions
- Ask user: "Accept these changes to the scoping decisions? (y/n)" - Ask user: "Accept these changes to the scoping decisions? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu

8
src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md
View File

@ -49,8 +49,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -209,7 +209,7 @@ Show the generated functional requirements and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current FR list - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current FR list
- Process the enhanced capability coverage that comes back - Process the enhanced capability coverage that comes back
- Ask user: "Accept these additions to the functional requirements? (y/n)" - Ask user: "Accept these additions to the functional requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -217,7 +217,7 @@ Show the generated functional requirements and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current FR list - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current FR list
- Process the collaborative capability validation and additions - Process the collaborative capability validation and additions
- Ask user: "Accept these changes to the functional requirements? (y/n)" - Ask user: "Accept these changes to the functional requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

8
src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md
View File

@ -49,8 +49,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to this step's A/P/C menu - PROTOCOLS always return to this step's A/P/C menu
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -209,7 +209,7 @@ Show the generated NFR content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current NFR content - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current NFR content
- Process the enhanced quality attribute insights that come back - Process the enhanced quality attribute insights that come back
- Ask user: "Accept these improvements to the non-functional requirements? (y/n)" - Ask user: "Accept these improvements to the non-functional requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -217,7 +217,7 @@ Show the generated NFR content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current NFR list - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current NFR list
- Process the collaborative technical validation and additions - Process the collaborative technical validation and additions
- Ask user: "Accept these changes to the non-functional requirements? (y/n)" - Ask user: "Accept these changes to the non-functional requirements? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

2
src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md
View File

@ -45,7 +45,7 @@ web_bundle: false
### 1. Module Configuration Loading ### 1. Module 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`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language` - `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`

8
src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md
View File

@ -30,8 +30,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -169,7 +169,7 @@ Show the generated content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current context analysis - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current context analysis
- Process the enhanced architectural insights that come back - Process the enhanced architectural insights that come back
- Ask user: "Accept these enhancements to the project context analysis? (y/n)" - Ask user: "Accept these enhancements to the project context analysis? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu
@ -177,7 +177,7 @@ Show the generated content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current project context - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project context
- Process the collaborative improvements to architectural understanding - Process the collaborative improvements to architectural understanding
- Ask user: "Accept these changes to the project context analysis? (y/n)" - Ask user: "Accept these changes to the project context analysis? (y/n)"
- If yes: Update content with improvements, then return to A/P/C menu - If yes: Update content with improvements, then return to A/P/C menu

4
src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md
View File

@ -30,8 +30,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding

8
src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md
View File

@ -31,8 +31,8 @@ This step will generate content and present choices for each decision category:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -263,7 +263,7 @@ Show the generated decisions content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with specific decision categories - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with specific decision categories
- Process enhanced insights about particular decisions - Process enhanced insights about particular decisions
- Ask user: "Accept these enhancements to the architectural decisions? (y/n)" - Ask user: "Accept these enhancements to the architectural decisions? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu
@ -271,7 +271,7 @@ Show the generated decisions content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with architectural decisions context - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with architectural decisions context
- Process collaborative insights about decision trade-offs - Process collaborative insights about decision trade-offs
- Ask user: "Accept these changes to the architectural decisions? (y/n)" - Ask user: "Accept these changes to the architectural decisions? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu

8
src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md
View File

@ -31,8 +31,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -304,7 +304,7 @@ Show the generated patterns content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with current patterns - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current patterns
- Process enhanced consistency rules that come back - Process enhanced consistency rules that come back
- Ask user: "Accept these additional pattern refinements? (y/n)" - Ask user: "Accept these additional pattern refinements? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu
@ -312,7 +312,7 @@ Show the generated patterns content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with implementation patterns context - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with implementation patterns context
- Process collaborative insights about potential conflicts - Process collaborative insights about potential conflicts
- Ask user: "Accept these changes to the implementation patterns? (y/n)" - Ask user: "Accept these changes to the implementation patterns? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu

8
src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md
View File

@ -31,8 +31,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -324,7 +324,7 @@ Show the generated project structure content and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with current project structure - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current project structure
- Process enhanced organizational insights that come back - Process enhanced organizational insights that come back
- Ask user: "Accept these changes to the project structure? (y/n)" - Ask user: "Accept these changes to the project structure? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu
@ -332,7 +332,7 @@ Show the generated project structure content and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with project structure context - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with project structure context
- Process collaborative insights about organization trade-offs - Process collaborative insights about organization trade-offs
- Ask user: "Accept these changes to the project structure? (y/n)" - Ask user: "Accept these changes to the project structure? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu

8
src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md
View File

@ -31,8 +31,8 @@ This step will generate content and present choices:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding
@ -304,7 +304,7 @@ Show the validation results and present choices:
#### If 'A' (Advanced Elicitation): #### If 'A' (Advanced Elicitation):
- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with validation issues - Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with validation issues
- Process enhanced solutions for complex concerns - Process enhanced solutions for complex concerns
- Ask user: "Accept these architectural improvements? (y/n)" - Ask user: "Accept these architectural improvements? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu
@ -312,7 +312,7 @@ Show the validation results and present choices:
#### If 'P' (Party Mode): #### If 'P' (Party Mode):
- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with validation context - Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with validation context
- Process collaborative insights on implementation readiness - Process collaborative insights on implementation readiness
- Ask user: "Accept these changes to the validation results? (y/n)" - Ask user: "Accept these changes to the validation results? (y/n)"
- If yes: Update content, then return to A/P/C menu - If yes: Update content, then return to A/P/C menu

2
src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md
View File

@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
### 1. Configuration Loading ### 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`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language` - `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`

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

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

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

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

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

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

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

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

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

@ -1,7 +1,7 @@
# Sprint Status - Multi-Mode Service # Sprint Status - Multi-Mode Service
<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml</critical>
<critical>Modes: interactive (default), validate, data</critical> <critical>Modes: interactive (default), validate, data</critical>
<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines.</critical> <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines.</critical>

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

@ -1,7 +1,7 @@
# Document Project Workflow Router # Document Project Workflow Router
<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/document-project/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/document-project/workflow.yaml</critical>
<critical>Communicate all responses in {communication_language}</critical> <critical>Communicate all responses in {communication_language}</critical>
<workflow> <workflow>

4
src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md
View File

@ -28,8 +28,8 @@ This step will generate content and present choices for each rule category:
## PROTOCOL INTEGRATION: ## PROTOCOL INTEGRATION:
- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml - When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode
- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
- User accepts/rejects protocol changes before proceeding - User accepts/rejects protocol changes before proceeding

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

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

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

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

4
src/modules/cis/workflows/design-thinking/instructions.md
View File

@ -1,7 +1,7 @@
# Design Thinking Workflow Instructions # Design Thinking Workflow Instructions
<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/design-thinking/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/design-thinking/workflow.yaml</critical>
<critical>Load and understand design methods from: {design_methods}</critical> <critical>Load and understand design methods from: {design_methods}</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> <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>
<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical> <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

4
src/modules/cis/workflows/innovation-strategy/instructions.md
View File

@ -1,7 +1,7 @@
# Innovation Strategy Workflow Instructions # Innovation Strategy Workflow Instructions
<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/innovation-strategy/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/innovation-strategy/workflow.yaml</critical>
<critical>Load and understand innovation frameworks from: {innovation_frameworks}</critical> <critical>Load and understand innovation frameworks from: {innovation_frameworks}</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> <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>
<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical> <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

4
src/modules/cis/workflows/problem-solving/instructions.md
View File

@ -1,7 +1,7 @@
# Problem Solving Workflow Instructions # Problem Solving Workflow Instructions
<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical> <critical>The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml</critical>
<critical>You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/problem-solving/workflow.yaml</critical> <critical>You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/problem-solving/workflow.yaml</critical>
<critical>Load and understand solving methods from: {solving_methods}</critical> <critical>Load and understand solving methods from: {solving_methods}</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> <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>
<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical> <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>