ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

bundle agents front matter optimized, along with the orchestrators activation instructions;

Browse Source
This commit is contained in:
Brian Madison
2025-10-03 21:46:53 -05:00
parent 5ac18cb55c
commit 9e8c7f3503
86 changed files with 289 additions and 3227 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -15,7 +15,7 @@
<handler type="workflow">
When menu item has: workflow="workflow-id"
1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
2. CRITICAL: Always LOAD bmad/core/tasks/workflow.md if referenced
2. CRITICAL: Always LOAD bmad/core/tasks/workflow.xml if referenced
3. Execute the workflow content precisely following all steps
4. Save outputs after completing EACH workflow step (never batch)
5. If workflow id is "todo", inform user it hasn't been implemented yet
@@ -48,7 +48,7 @@
<handler type="validate-workflow">
When menu item has: validate-workflow="workflow-id"
1. MUST LOAD bmad/core/tasks/validate-workflow.md
1. MUST LOAD bmad/core/tasks/validate-workflow.xml
2. Execute all validation instructions from that file
3. Check workflow's validation property for schema
4. Identify file to validate or ask user to specify

13
src/core/tasks/adv-elicit.md → src/core/tasks/adv-elicit.xml
View File

@@ -1,9 +1,4 @@
<!-- BMAD-CORE™ Advanced Elicitation Task v2.0 (LLM-Native) -->
# Advanced Elicitation v2.0 (LLM-Native)
```xml
<task id="bmad/core/tasks/adv-elicit.md" name="Advanced Elicitation">
<task id="bmad/core/tasks/adv-elicit.xml" name="Advanced Elicitation">
<llm critical="true">
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
<i>DO NOT skip steps or change the sequence</i>
@@ -66,7 +61,8 @@
<i>Apply the method creatively to the current section content being enhanced</i>
<i>Display the enhanced version showing what the method revealed or improved</i>
<i>CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.</i>
<i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to follow the instructions given by the user.</i>
<i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to
follow the instructions given by the user.</i>
<i>CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
</case>
<case n="r">
@@ -105,5 +101,4 @@
<i> 3. Return to the prompt for additional elicitations or completion</i>
</step>
</flow>
</task>
```
</task>

8
src/core/tasks/index-docs.md → src/core/tasks/index-docs.xml
View File

@@ -1,8 +1,3 @@
<!-- BMAD-CORE™ Index Documentation Task -->
# Index Docs v1.1
```xml
<task id="bmad/core/tasks/index-docs" name="Index Docs" webskip="true">
<llm critical="true">
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
@@ -65,5 +60,4 @@
<i>Sort alphabetically within groups</i>
<i>Skip hidden files (starting with .) unless specified</i>
</validation>
</task>
```
</task>

57
src/core/tasks/shard-doc.md
View File

@@ -1,57 +0,0 @@
<!-- BMAD-CORE™ Document Sharding Task -->
# Shard Doc v1.1
```xml
<task id="bmad/core/tasks/shard-doc.md" name="Shard Doc">
<llm critical="true">
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
<i>DO NOT skip steps or change the sequence</i>
<i>HALT immediately when halt-conditions are met</i>
<i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
<i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
</llm>
<flow>
<step n="1" title="Check for Tool">
<i>First check if md-tree command is available</i>
</step>
<step n="2" title="Install if Needed">
<i>If not available, ask user permission to install: npm install -g @kayvan/markdown-tree-parser</i>
</step>
<step n="3" title="Shard Document">
<i>Use the explode command to split the document</i>
</step>
</flow>
<usage>
<commands>
# Install the tool (if needed)
npm install -g @kayvan/markdown-tree-parser
# Shard a document
md-tree explode [source-document] [destination-folder]
# Examples
md-tree explode docs/prd.md docs/prd
md-tree explode docs/architecture.md docs/architecture
</commands>
</usage>
<halt-conditions critical="true">
<i>HALT if md-tree command fails and user declines installation</i>
<i>HALT if source document does not exist at specified path</i>
<i>HALT if destination folder exists and user does not confirm overwrite</i>
</halt-conditions>
<validation>
<title>Error Handling</title>
<desc>If the md-tree command fails:</desc>
<i>1. Check if the tool is installed globally</i>
<i>2. Ask user permission to install it</i>
<i>3. Retry the operation after installation</i>
</validation>
</task>
```

8
src/core/tasks/validate-workflow.md → src/core/tasks/validate-workflow.xml
View File

@@ -1,7 +1,4 @@
# Validate Workflow
```xml
<task id="bmad/core/tasks/validate-workflow.md" name="Validate Workflow Output">
<task id="bmad/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
<objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
<inputs>
@@ -88,5 +85,4 @@
<rule>Save report to document's folder automatically</rule>
<rule>HALT after presenting summary - wait for user</rule>
</critical-rules>
</task>
```
</task>

27
src/core/tasks/workflow.md → src/core/tasks/workflow.xml
View File

@@ -1,9 +1,4 @@
<!-- BMAD Method v6 Workflow Execution Task (Simplified) -->
# Workflow
```xml
<task id="bmad/core/tasks/workflow.md" name="Execute Workflow">
<task id="bmad/core/tasks/workflow.xml" name="Execute Workflow">
<objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
<llm critical="true">
@@ -63,12 +58,12 @@
<action>Process step instructions (markdown or XML tags)</action>
<action>Replace {{variables}} with values (ask user if unknown)</action>
<execute-tags>
<tag><action> → Perform the action</tag>
<tag><check> → Evaluate condition</tag>
<tag><ask> → Prompt user and WAIT for response</tag>
<tag><invoke-workflow> → Execute another workflow with given inputs</tag>
<tag><invoke-task> → Execute specified task</tag>
<tag><goto step="x"> → Jump to specified step</tag>
<tag>action xml tag → Perform the action</tag>
<tag>check xml tag → Evaluate condition</tag>
<tag>ask xml tag → Prompt user and WAIT for response</tag>
<tag>invoke-workflow xml tag → Execute another workflow with given inputs</tag>
<tag>invoke-task xml tag → Execute specified task</tag>
<tag>goto step="x" → Jump to specified step</tag>
</execute-tags>
</substep>
@@ -82,8 +77,9 @@
</if>
<if tag="elicit-required">
<mandate critical="true">YOU MUST READ the file at {project-root}/bmad/core/tasks/adv-elicit.md using Read tool BEFORE presenting any elicitation menu</mandate>
<action>Load and run task {project-root}/bmad/core/tasks/adv-elicit.md with current context</action>
<mandate critical="true">YOU MUST READ the file at {project-root}/bmad/core/tasks/adv-elicit.xml using Read tool BEFORE presenting
any elicitation menu</mandate>
<action>Load and run task {project-root}/bmad/core/tasks/adv-elicit.xml with current context</action>
<action>Show elicitation menu 5 relevant options (list 1-5 options, Continue [c] or Reshuffle [r])</action>
<mandate>HALT and WAIT for user selection</mandate>
</if>
@@ -137,5 +133,4 @@
<mandate>You MUST Follow instructions exactly as written and maintain conversation context between steps</mandate>
<mandate>If confused, re-read this task, the workflow yaml, and any yaml indicated files</mandate>
</llm>
</task>
```
</task>

2
src/core/workflows/party-mode/instructions.md
View File

@@ -1,6 +1,6 @@
# Party Mode - Multi-Agent Discussion Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
<workflow>

2
src/modules/bmb/workflows/convert-legacy/instructions.md
View File

@@ -1,6 +1,6 @@
# Convert Legacy - v4 to v5 Conversion Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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/convert-legacy/workflow.yaml</critical>
<workflow>

4
src/modules/bmb/workflows/create-agent/agent-architecture.md
View File

@@ -210,7 +210,7 @@ Bad: ../../../relative/paths/
### Task Commands
```xml
<c cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.md">
<c cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.xml">
Validate document
</c>
```
@@ -229,7 +229,7 @@ Bad: ../../../relative/paths/
```xml
<c cmd="*standup"
exec="{project-root}/bmad/bmm/tasks/daily-standup.md"
exec="{project-root}/bmad/bmm/tasks/daily-standup.xml"
data="{project-root}/bmad/_cfg/agent-party.xml">
Run daily standup
</c>

4
src/modules/bmb/workflows/create-agent/agent-command-patterns.md
View File

@@ -110,13 +110,13 @@ Execute single operations
```xml
<!-- Simple task -->
<c cmd="*validate"
exec="{project-root}/bmad/core/tasks/validate-workflow.md">
exec="{project-root}/bmad/core/tasks/validate-workflow.xml">
Validate document against checklist
</c>
<!-- Task with data -->
<c cmd="*standup"
exec="{project-root}/bmad/mmm/tasks/daily-standup.md"
exec="{project-root}/bmad/mmm/tasks/daily-standup.xml"
data="{project-root}/bmad/_cfg/agent-party.xml">
Run agile team standup
</c>

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

@@ -127,7 +127,7 @@ expert-agent/
<cmds>
<c cmd="*help">Show numbered cmd list</c>
<c cmd="*create-prd" run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">Create PRD</c>
<c cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.md">Validate document</c>
<c cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.xml">Validate document</c>
<c cmd="*exit">Exit</c>
</cmds>
</agent>

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

@@ -1,6 +1,6 @@
# Build Agent - Interactive Agent Builder Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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/create-agent/workflow.yaml</critical>
<critical>Study YAML agent examples in: {project_root}/bmad/bmm/agents/ for patterns</critical>

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

@@ -1,6 +1,6 @@
# Build Module - Interactive Module Builder Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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/create-module/workflow.yaml</critical>
<critical>Study existing modules in: {project_root}/bmad/ for patterns</critical>

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

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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/create-workflow/workflow.yaml</critical>
<critical>You MUST fully understand the workflow creation guide at: {workflow_creation_guide}</critical>
<critical>Study the guide thoroughly to follow ALL conventions for optimal human-AI collaboration</critical>
@@ -134,7 +134,7 @@ Load and use the template at: {template_instructions}
Generate the instructions.md file following the workflow creation guide:
1. ALWAYS include critical headers:
- Workflow engine reference: {project_root}/bmad/core/tasks/workflow.md
- Workflow engine reference: {project_root}/bmad/core/tasks/workflow.xml
- workflow.yaml reference: must be loaded and processed
2. Structure with <workflow> tags containing all steps

6
src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md
View File

@@ -42,7 +42,7 @@ default_output_file: '{output_folder}/output.md'
```markdown
# instructions.md
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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.yaml</critical>
<workflow>
@@ -140,7 +140,7 @@ recommended_inputs: # Expected input docs
```markdown
# instructions.md
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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.yaml</critical>
<workflow>
@@ -452,5 +452,5 @@ Check requirements against goals.
_For implementation details, see:_
- `/src/core/tasks/workflow.md` - Execution engine
- `/src/core/tasks/workflow.xml` - Execution engine
- `/bmad/bmm/workflows/` - Production examples

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

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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/{module-code}/workflows/{workflow}/workflow.yaml</critical>
<step n="1" goal="">

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

@@ -1,6 +1,6 @@
# Edit Workflow - Workflow Editor Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.md</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-workflow/workflow.yaml</critical>
<critical>Study the workflow creation guide thoroughly at: {workflow_creation_guide}</critical>

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

@@ -13,7 +13,7 @@ date: system-generated
# Required Data Files - Critical for understanding workflow conventions
workflow_creation_guide: "{project-root}/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md"
workflow_execution_engine: "{project-root}/bmad/core/tasks/workflow.md"
workflow_execution_engine: "{project-root}/bmad/core/tasks/workflow.xml"
# Optional docs that can be used to understand the target workflow
recommended_inputs:

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

@@ -1,6 +1,6 @@
# Module Brief Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>
<workflow>

2
src/modules/bmb/workflows/redoc/instructions.md
View File

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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}/src/modules/bmb/workflows/redoc/workflow.yaml</critical>
<critical>This is an AUTONOMOUS workflow - minimize user interaction unless clarification is absolutely required</critical>
<critical>IMPORTANT: Process ONE document at a time to avoid token limits. Each README should be created individually, not batched.</critical>

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

@@ -32,5 +32,5 @@ agent:
description: Analyze Project Scope and Create PRD or Smaller Tech Spec
- trigger: validate
exec: "{project-root}/bmad/core/tasks/validate-workflow.md"
exec: "{project-root}/bmad/core/tasks/validate-workflow.xml"
description: Validate any document against its workflow checklist

44
src/modules/bmm/tasks/daily-standup.md → src/modules/bmm/tasks/daily-standup.xml
View File

@@ -1,9 +1,4 @@
<!-- Powered by BMAD-CORE™ -->
# Daily Standup v1.0
```xml
<task id="bmad/bmm/tasks/daily-standup.md" name="Daily Standup">
<task id="bmad/bmm/tasks/daily-standup.xml" name="Daily Standup">
<llm critical="true">
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
<i>DO NOT skip steps or change the sequence</i>
@@ -23,15 +18,15 @@
<step n="2" title="Initialize Standup with Context">
<output>
🏃 DAILY STANDUP - Story-{{number}}: {{title}}
🏃 DAILY STANDUP - Story-{{number}}: {{title}}
Current Sprint Status:
- Active Story: story-{{number}} ({{status}} - {{percentage}}% complete)
- Next in Queue: story-{{next-number}}: {{next-title}}
- Blockers: {{blockers-from-story}}
Current Sprint Status:
- Active Story: story-{{number}} ({{status}} - {{percentage}}% complete)
- Next in Queue: story-{{next-number}}: {{next-title}}
- Blockers: {{blockers-from-story}}
Team assembled based on story participants:
{{ List Agents from {project-root}/bmad/_cfg/agent-party.xml }}
Team assembled based on story participants:
{{ List Agents from {project-root}/bmad/_cfg/agent-party.xml }}
</output>
</step>
@@ -44,18 +39,18 @@ Team assembled based on story participants:
<step n="4" title="Create Standup Summary">
<output>
📋 STANDUP SUMMARY:
Key Items from Story File:
- {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks)
- Blocker: {{main-blocker}}
- Next: {{next-story-reference}}
📋 STANDUP SUMMARY:
Key Items from Story File:
- {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks)
- Blocker: {{main-blocker}}
- Next: {{next-story-reference}}
Action Items:
- {{agent}}: {{action-item}}
- {{agent}}: {{action-item}}
- {{agent}}: {{action-item}}
Action Items:
- {{agent}}: {{action-item}}
- {{agent}}: {{action-item}}
- {{agent}}: {{action-item}}
Need extended discussion? Use *party-mode for detailed breakout.
Need extended discussion? Use *party-mode for detailed breakout.
</output>
</step>
</flow>
@@ -87,5 +82,4 @@ Need extended discussion? Use *party-mode for detailed breakout.
<i>No deep dives (suggest breakout if needed)</i>
<i>If no stories folder detected, run general standup format</i>
</llm>
</task>
```
</task>

48
src/modules/bmm/tasks/retrospective.md → src/modules/bmm/tasks/retrospective.xml
View File

@@ -1,9 +1,4 @@
<!-- Powered by BMAD-CORE™ -->
# Retrospective v1.0
```xml
<task id="bmad/bmm/tasks/retrospective.md" name="Team Retrospective">
<task id="bmad/bmm/tasks/retrospective.xml" name="Team Retrospective">
<llm critical="true">
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
<i>DO NOT skip steps or change the sequence</i>
@@ -34,24 +29,24 @@
<step n="3" title="Initialize Retrospective with Context">
<output>
🔄 TEAM RETROSPECTIVE - Epic {{number}}: {{Epic Name}}
🔄 TEAM RETROSPECTIVE - Epic {{number}}: {{Epic Name}}
Bob (Scrum Master) facilitating
Bob (Scrum Master) facilitating
Epic Summary:
- Completed: {{completed}}/{{total}} stories ({{percentage}}%)
- Velocity: {{actual-points}} story points (planned: {{planned-points}})
- Duration: {{actual-sprints}} sprints (planned: {{planned-sprints}})
- Technical Debt: {{debt-items}}
Epic Summary:
- Completed: {{completed}}/{{total}} stories ({{percentage}}%)
- Velocity: {{actual-points}} story points (planned: {{planned-points}})
- Duration: {{actual-sprints}} sprints (planned: {{planned-sprints}})
- Technical Debt: {{debt-items}}
Next Epic Preview: Epic {{next-number}}: {{Next Epic Name}}
- Dependencies on Epic {{number}}: {{dependencies}}
- Preparation needed: {{preparation-gaps}}
Next Epic Preview: Epic {{next-number}}: {{Next Epic Name}}
- Dependencies on Epic {{number}}: {{dependencies}}
- Preparation needed: {{preparation-gaps}}
Team assembled for reflection:
{{agents-based-on-story-records}}
Team assembled for reflection:
{{agents-based-on-story-records}}
Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}
Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}
</output>
</step>
@@ -75,14 +70,14 @@ Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}
<action>Assigns ownership to action items</action>
<action>Creates preparation sprint tasks if needed</action>
<output>
📝 EPIC {{number}} ACTION ITEMS:
{{numbered-action-items-with-owners}}
📝 EPIC {{number}} ACTION ITEMS:
{{numbered-action-items-with-owners}}
🚀 EPIC {{next-number}} PREPARATION SPRINT:
{{preparation-tasks-with-timeline}}
🚀 EPIC {{next-number}} PREPARATION SPRINT:
{{preparation-tasks-with-timeline}}
⚠️ CRITICAL PATH:
{{critical-dependencies-and-timeline}}
⚠️ CRITICAL PATH:
{{critical-dependencies-and-timeline}}
</output>
</step>
@@ -106,5 +101,4 @@ Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}
<i>End with team agreements and clear next steps</i>
<i>Two-part format: Epic Review + Next Epic Preparation</i>
</llm>
</task>
```
</task>

14
src/modules/bmm/teams/team-dev.yaml
View File

@@ -1,14 +0,0 @@
# <!-- Powered by BMAD-CORE™ -->
bundle:
name: Team Fullstack
icon: 🚀
description: Team capable of full stack, front end only, or service development.
agents:
- analyst
- pm
- ux-expert
- architect
- po
- tea
- devops
- security

12
src/modules/bmm/teams/team-planning.yaml Normal file
View File

@@ -0,0 +1,12 @@
# <!-- Powered by BMAD-CORE™ -->
bundle:
name: Team Plan and Architect
icon: 🚀
description: Team capable of project analysis, design, and architecture.
agents:
- analyst
- architect
- pm
- po
- tea
- ux-expert

6
src/modules/bmm/workflows/1-analysis/brainstorm-game/instructions.md
View File

@@ -1,7 +1,4 @@
# Brainstorm Game - Workflow Instructions
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques</critical>
@@ -44,4 +41,3 @@
</step>
</workflow>
```

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

@@ -1,7 +1,7 @@
# Brainstorm Project - Workflow Instructions
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This is a meta-workflow that orchestrates the CIS brainstorming workflow with project-specific context</critical>

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

@@ -1,6 +1,6 @@
# Game Brief - Interactive Workflow Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.md</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>
<workflow>

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

@@ -1,6 +1,6 @@
# Product Brief - Interactive Workflow Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.md</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>
<workflow>

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

@@ -1,6 +1,6 @@
# Deep Research Prompt Generator Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This workflow generates structured research prompts optimized for AI platforms</critical>
<critical>Based on 2025 best practices from ChatGPT, Gemini, Grok, and Claude</critical>

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

@@ -1,6 +1,6 @@
# Market Research Workflow Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This is an INTERACTIVE workflow with web research capabilities. Engage the user at key decision points.</critical>

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

@@ -1,6 +1,6 @@
# Research Workflow Router Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This is a ROUTER that directs to specialized research instruction sets</critical>

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

@@ -1,6 +1,6 @@
# Technical/Architecture Research Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This workflow conducts technical research for architecture and technology decisions</critical>

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

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This is the GDD instruction set for GAME projects - replaces PRD with Game Design Document</critical>
<critical>Project analysis already completed - proceeding with game-specific design</critical>

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

@@ -4,7 +4,7 @@
<critical>This is the INITIAL ASSESSMENT phase - determines which instruction set to load</critical>
<critical>ALWAYS check for existing project-workflow-analysis.md first</critical>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
<step n="1" goal="Check for existing analysis or perform new assessment">

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

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This workflow creates detailed narrative content for story-driven games</critical>
<critical>Uses narrative_template for output</critical>

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

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This is the LARGE instruction set for Level 3-4 projects - full PRD + architect handoff</critical>
<critical>Project analysis already completed - proceeding with comprehensive requirements</critical>

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

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This is the MEDIUM instruction set for Level 1-2 projects - minimal PRD + solutioning handoff</critical>
<critical>Project analysis already completed - proceeding with focused requirements</critical>

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

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This is the SMALL instruction set for Level 0 projects - tech-spec only</critical>
<critical>Project analysis already completed - proceeding directly to technical specification</critical>

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

@@ -2,7 +2,7 @@
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This workflow creates comprehensive UX/UI specifications - can run standalone or as part of plan-project</critical>
<critical>Uses ux-spec-template.md for structured output generation</critical>

4
src/modules/bmm/workflows/3-solutioning/tech-spec/instructions.md
View File

@@ -1,7 +1,7 @@
<!-- BMAD BMM Tech Spec Workflow Instructions (v6) -->
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping.</critical>
<critical>Default execution mode: #yolo (non-interactive). If required inputs cannot be auto-discovered and {{non_interactive}} == true, HALT with a clear message listing missing documents; do not prompt.</critical>
@@ -66,7 +66,7 @@
</step>
<step n="8" goal="Validate">
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.md</invoke-task>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
</step>
</workflow>

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

@@ -1,6 +1,6 @@
# Correct Course - Sprint Change Management Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.md</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>
<workflow>

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

@@ -1,7 +1,7 @@
# Create Story - Workflow Instructions (Spec-compliant, non-interactive by default)
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This workflow creates or updates the next user story from epics/PRD and architecture context, saving to the configured stories directory and optionally invoking Story Context.</critical>
<critical>Default execution mode: #yolo (minimal prompts). Only elicit if absolutely required and {{non_interactive}} == false.</critical>
@@ -71,7 +71,7 @@
</step>
<step n="8" goal="Validate, save, and optionally generate context">
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.md</invoke-task>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
<action>Save document unconditionally (non-interactive default). In interactive mode, allow user confirmation.</action>
<check>If {{auto_run_context}} == true → <invoke-workflow path="{project-root}/bmad/bmm/workflows/4-implementation/story-context/workflow.yaml">Pass {{story_path}} = {default_output_file}</invoke-workflow></check>
<action>Report created/updated story path</action>

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

@@ -1,7 +1,7 @@
# Develop Story - Workflow Instructions
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status</critical>
<critical>Execute ALL steps in exact order; do NOT skip steps</critical>
@@ -78,7 +78,7 @@
</step>
<step n="7" goal="Validation and handoff" optional="true">
<action>Optionally run the workflow validation task against the story using {project-root}/bmad/core/tasks/validate-workflow.md</action>
<action>Optionally run the workflow validation task against the story using {project-root}/bmad/core/tasks/validate-workflow.xml</action>
<action>Prepare a concise summary in Dev Agent Record → Completion Notes</action>
<action>Communicate that the story is Ready for Review</action>
</step>

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

@@ -50,7 +50,7 @@ The SM should run this workflow:
**Primary Deliverable:**
- **Retrospective Report** (`[epic-id]-retrospective.md`): Comprehensive analysis including:
- **Retrospective Report** (`[epic-id]-retrospective.xml`): Comprehensive analysis including:
- Executive summary of epic outcomes
- Story-by-story analysis of what was learned
- Technical insights and architecture learnings

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

@@ -1,6 +1,6 @@
# Retrospective - Epic Completion Review Instructions
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.md</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>

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

@@ -1,7 +1,7 @@
# Senior Developer Review - Workflow Instructions
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This workflow performs a Senior Developer Review on a story flagged Ready for Review, appends structured review notes, and can update the story status based on the outcome.</critical>
<critical>Default execution mode: #yolo (non-interactive). Only ask if {{non_interactive}} == false. If auto-discovery of the target story fails, HALT with a clear message to provide 'story_path' or 'story_dir'.</critical>
@@ -94,7 +94,7 @@
</step>
<step n="9" goal="Validation and completion">
<invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/bmad/core/tasks/validate-workflow.md</invoke-task>
<invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/bmad/core/tasks/validate-workflow.xml</invoke-task>
<action>Report workflow completion.</action>
</step> <step n="1" goal="Locate story and verify review status">
<action>If {{story_path}} was provided → use it. Else auto-discover from {{story_dir}} by listing files matching pattern: "story-*.md" (recursive), sort by last modified (newest first), present top {{story_selection_limit}}.</action>
@@ -168,7 +168,7 @@
</step>
<step n="9" goal="Validation and completion">
<invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/bmad/core/tasks/validate-workflow.md</invoke-task>
<invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/bmad/core/tasks/validate-workflow.xml</invoke-task>
<action>Report workflow completion.</action>
</step>

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

@@ -1,7 +1,7 @@
<!-- BMAD BMM Story Context Assembly Instructions (v6) -->
```xml
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>This workflow assembles a Story Context XML for a single user story by extracting ACs, tasks, relevant docs/code, interfaces, constraints, and testing guidance to support implementation.</critical>
<critical>Default execution mode: #yolo (non-interactive). Only ask if {{non_interactive}} == false. If auto-discovery fails, HALT and request 'story_path' or 'story_dir'.</critical>
@@ -63,7 +63,7 @@
<step n="6" goal="Validate and save">
<action>Validate output XML structure and content.</action>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.md</invoke-task>
<invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
</step>
<step n="7" goal="Update story status and context reference">

2
src/modules/cis/workflows/brainstorming/instructions.md
View File

@@ -3,7 +3,7 @@
## Workflow
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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/brainstorming/workflow.yaml</critical>
<step n="1" goal="Session Setup">

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

@@ -1,6 +1,6 @@
# Design Thinking Workflow Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>Load and understand design methods from: {design_methods}</critical>

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

@@ -1,6 +1,6 @@
# Innovation Strategy Workflow Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>Load and understand innovation frameworks from: {innovation_frameworks}</critical>

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

@@ -1,6 +1,6 @@
# Problem Solving Workflow Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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>Load and understand solving methods from: {solving_methods}</critical>

2
src/modules/cis/workflows/storytelling/instructions.md
View File

@@ -3,7 +3,7 @@
## Workflow
<workflow>
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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/storytelling/workflow.yaml</critical>
<step n="1" goal="Story Context Setup">

6
src/utility/models/agent-activation-ide.xml
View File

@@ -12,15 +12,15 @@
<handlers>
<handler type="run-workflow">
When command has: run-workflow="path/to/x.yaml" You MUST:
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.md
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
2. READ its entire contents - the is the CORE OS for EXECUTING modules
3. Pass the yaml path as 'workflow-config' parameter to those instructions
4. Follow workflow.md instructions EXACTLY as written
4. Follow workflow.xml instructions EXACTLY as written
5. Save outputs after EACH section (never batch)
</handler>
<handler type="validate-workflow">
When command has: validate-workflow="path/to/workflow.yaml" You MUST:
1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.md
1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
2. READ its entire contents and EXECUTE all instructions in that file
3. Pass the workflow, and also check the workflow location for a checklist.md to pass as the checklist
4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify

10
src/utility/models/agent-activation-web.xml
View File

@@ -7,8 +7,8 @@
<bundled-files critical="MANDATORY">
<access-method>
All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
When you need to access a file path like "bmad/core/tasks/workflow.md":
1. Find the &lt;file id="bmad/core/tasks/workflow.md"&gt; element in this document
When you need to access a file path like "bmad/core/tasks/workflow.xml":
1. Find the &lt;file id="bmad/core/tasks/workflow.xml"&gt; element in this document
2. Extract the content from within the CDATA section
3. Use that content as if you read it from the filesystem
</access-method>
@@ -25,11 +25,11 @@
<handlers>
<handler type="run-workflow">
When command has: run-workflow="path/to/x.yaml" You MUST:
1. CRITICAL: Locate &lt;file id="bmad/core/tasks/workflow.md"&gt; in this XML bundle
1. CRITICAL: Locate &lt;file id="bmad/core/tasks/workflow.xml"&gt; in this XML bundle
2. Extract and READ its CDATA content - this is the CORE OS for EXECUTING workflows
3. Locate &lt;file id="path/to/x.yaml"&gt; for the workflow config
4. Pass the yaml content as 'workflow-config' parameter to workflow.md instructions
5. Follow workflow.md instructions EXACTLY as written
4. Pass the yaml content as 'workflow-config' parameter to workflow.xml instructions
5. Follow workflow.xml instructions EXACTLY as written
6. When workflow references other files, locate them by id in &lt;file&gt; elements
7. Save outputs after EACH section (never batch)
</handler>

2
src/utility/models/fragments/handler-validate-workflow.xml
View File

@@ -1,6 +1,6 @@
<handler type="validate-workflow">
When command has: validate-workflow="path/to/workflow.yaml"
1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.md
1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.xml
2. READ its entire contents and EXECUTE all instructions in that file
3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify

18
src/utility/models/fragments/handler-workflow.xml
View File

@@ -1,9 +1,9 @@
<handler type="workflow">
When menu item has: workflow="path/to/workflow.yaml"
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.md
2. Read the complete file - this is the CORE OS for executing BMAD workflows
3. Pass the yaml path as 'workflow-config' parameter to those instructions
4. Execute workflow.md instructions precisely following all steps
5. Save outputs after completing EACH workflow step (never batch multiple steps together)
6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
</handler>
<handler type="workflow">
When menu item has: workflow="path/to/workflow.yaml"
1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
2. Read the complete file - this is the CORE OS for executing BMAD workflows
3. Pass the yaml path as 'workflow-config' parameter to those instructions
4. Execute workflow.xml instructions precisely following all steps
5. Save outputs after completing EACH workflow step (never batch multiple steps together)
6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
</handler>

32
src/utility/models/fragments/web-bundle-activation-steps.xml Normal file
View File

@@ -0,0 +1,32 @@
<step n="1">Load persona from this current agent XML block containing this activation you are reading now</step>
{AGENT_SPECIFIC_STEPS}
<step n="{MENU_STEP}">Show greeting + numbered list of ALL commands IN ORDER from current agent's menu section</step>
<step n="{HALT_STEP}">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
<step n="{INPUT_STEP}">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
to clarify | No match → show "Not recognized"</step>
<step n="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
(workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
<bundled-files critical="MANDATORY">
<access-method>
All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
When you need to access a file path like "bmad/core/tasks/workflow.xml":
1. Find the &lt;file id="bmad/core/tasks/workflow.xml"&gt; element in this document
2. Extract the content from within the CDATA section
3. Use that content as if you read it from the filesystem
</access-method>
<rules>
<rule>NEVER attempt to read files from filesystem - all files are bundled in this XML</rule>
<rule>File paths starting with "bmad/" or "{project-root}/bmad/" refer to &lt;file id="..."&gt; elements</rule>
<rule>When instructions reference a file path, locate the corresponding &lt;file&gt; element by matching the id attribute</rule>
<rule>YAML files are bundled with only their web_bundle section content (flattened to root level)</rule>
</rules>
</bundled-files>
<rules>
Stay in character until *exit
Number all option lists, use letters for sub-options
All file content is bundled in &lt;file&gt; elements - locate by id attribute
NEVER attempt filesystem operations - everything is in this XML
Menu triggers use asterisk (*) - display exactly as shown
</rules>