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

update inquirer to v9.x for better windows support

Browse Source
This commit is contained in:
Brian Madison
2025-12-22 18:18:16 +08:00
parent da21790531
commit 021936eaa9
783 changed files with 13034 additions and 413 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
q1/.cursor/rules/bmad/bmb/agents/agent-builder.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMB Agent: agent-builder
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmb/agents/agent-builder.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmb/agents/module-builder.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMB Agent: module-builder
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmb/agents/module-builder.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmb/agents/workflow-builder.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMB Agent: workflow-builder
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmb/agents/workflow-builder.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

7
q1/.cursor/rules/bmad/bmb/workflows/Meal Prep & Nutrition Plan.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMB Agent: Meal Prep & Nutrition Plan
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/bmb/workflows/create-agent.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMB Agent: create-agent
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/create-agent/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/bmb/workflows/create-module.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMB Agent: create-module
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/create-module/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/bmb/workflows/create-workflow.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMB Agent: create-workflow
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/create-workflow/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/bmb/workflows/edit-agent.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMB Agent: edit-agent
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/edit-agent/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/bmb/workflows/edit-workflow.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMB Agent: edit-workflow
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/edit-workflow/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/bmb/workflows/workflow-compliance-check.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMB Agent: workflow-compliance-check
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/workflow-compliance-check/workflow.md, READ its entire contents and follow its directions exactly!

15
q1/.cursor/rules/bmad/bmgd/agents/game-architect.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: game-architect
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-architect.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmgd/agents/game-designer.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: game-designer
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-designer.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmgd/agents/game-dev.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: game-dev
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmgd/agents/game-qa.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: game-qa
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-qa.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmgd/agents/game-scrum-master.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: game-scrum-master
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-scrum-master.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmgd/agents/game-solo-dev.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: game-solo-dev
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmgd/agents/game-solo-dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmgd/workflows/brainstorm-game.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: brainstorm-game
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/code-review.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: code-review
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/code-review/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/4-production/code-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/correct-course.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: correct-course
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/4-production/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

7
q1/.cursor/rules/bmad/bmgd/workflows/create-game-brief.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMGD Agent: create-game-brief
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/bmgd/workflows/create-gdd.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMGD Agent: create-gdd
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmgd/workflows/2-design/gdd/workflow.md, READ its entire contents and follow its directions exactly!

15
q1/.cursor/rules/bmad/bmgd/workflows/create-story.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: create-story
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/create-story/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/4-production/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/create-tech-spec.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: create-tech-spec
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/dev-story.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: dev-story
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/dev-story/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/4-production/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/game-architecture.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: game-architecture
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/game-brief.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: game-brief
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/gametest-automate.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: gametest-automate
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/automate/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/gametest/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/gametest-framework.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: gametest-framework
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/test-framework/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/gametest/test-framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/gametest-performance.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: gametest-performance
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/performance/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/gametest/performance/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/gametest-playtest-plan.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: gametest-playtest-plan
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/playtest-plan/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/gametest/playtest-plan/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/gametest-test-design.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: gametest-test-design
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/test-design/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/gametest/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/gametest-test-review.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: gametest-test-review
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/gametest/test-review/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/gametest/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/gdd.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: gdd
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/2-design/gdd/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/2-design/gdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

7
q1/.cursor/rules/bmad/bmgd/workflows/generate-project-context.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMGD Agent: generate-project-context
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmgd/workflows/3-technical/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!

15
q1/.cursor/rules/bmad/bmgd/workflows/narrative.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: narrative
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/2-design/narrative/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/2-design/narrative/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/quick-dev.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: quick-dev
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/quick-prototype.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: quick-prototype
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/retrospective.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: retrospective
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/retrospective/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/4-production/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/sprint-planning.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: sprint-planning
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/sprint-status.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: sprint-status
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/workflow-init.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: workflow-init
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/workflow-status/init/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmgd/workflows/workflow-status.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMGD Agent: workflow-status
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmgd/workflows/workflow-status/workflow.yaml
3. Pass the yaml path _bmad/bmgd/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/agents/analyst.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: analyst
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/analyst.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmm/agents/architect.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: architect
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/architect.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmm/agents/dev.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: dev
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmm/agents/pm.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: pm
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/pm.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmm/agents/quick-flow-solo-dev.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: quick-flow-solo-dev
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/quick-flow-solo-dev.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmm/agents/sm.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: sm
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/sm.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmm/agents/tea.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: tea
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/tea.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmm/agents/tech-writer.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: tech-writer
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/tech-writer.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/bmm/agents/ux-designer.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: ux-designer
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/bmm/agents/ux-designer.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

7
q1/.cursor/rules/bmad/bmm/workflows/check-implementation-readiness.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMM Agent: check-implementation-readiness
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!

15
q1/.cursor/rules/bmad/bmm/workflows/code-review.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: code-review
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/code-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/correct-course.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: correct-course
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

7
q1/.cursor/rules/bmad/bmm/workflows/create-architecture.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMM Agent: create-architecture
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/bmm/workflows/create-epics-and-stories.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMM Agent: create-epics-and-stories
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md, READ its entire contents and follow its directions exactly!

15
q1/.cursor/rules/bmad/bmm/workflows/create-excalidraw-dataflow.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: create-excalidraw-dataflow
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/create-excalidraw-diagram.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: create-excalidraw-diagram
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/create-excalidraw-flowchart.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: create-excalidraw-flowchart
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/create-excalidraw-wireframe.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: create-excalidraw-wireframe
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

7
q1/.cursor/rules/bmad/bmm/workflows/create-prd.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMM Agent: create-prd
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/bmm/workflows/create-product-brief.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMM Agent: create-product-brief
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md, READ its entire contents and follow its directions exactly!

15
q1/.cursor/rules/bmad/bmm/workflows/create-story.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: create-story
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/create-tech-spec.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: create-tech-spec
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

7
q1/.cursor/rules/bmad/bmm/workflows/create-ux-design.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMM Agent: create-ux-design
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!

15
q1/.cursor/rules/bmad/bmm/workflows/dev-story.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: dev-story
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/document-project.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: document-project
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/document-project/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/document-project/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

7
q1/.cursor/rules/bmad/bmm/workflows/generate-project-context.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMM Agent: generate-project-context
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!

15
q1/.cursor/rules/bmad/bmm/workflows/quick-dev.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: quick-dev
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

7
q1/.cursor/rules/bmad/bmm/workflows/research.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD BMM Agent: research
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/1-analysis/research/workflow.md, READ its entire contents and follow its directions exactly!

15
q1/.cursor/rules/bmad/bmm/workflows/retrospective.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: retrospective
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/sprint-planning.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: sprint-planning
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/sprint-status.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: sprint-status
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/testarch-atdd.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: testarch-atdd
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/atdd/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/atdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/testarch-automate.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: testarch-automate
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/automate/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/testarch-ci.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: testarch-ci
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/ci/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/ci/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/testarch-framework.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: testarch-framework
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/framework/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/testarch-nfr.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: testarch-nfr
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/testarch-test-design.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: testarch-test-design
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-design/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/testarch-test-review.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: testarch-test-review
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-review/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/testarch-trace.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: testarch-trace
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/trace/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/testarch/trace/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/workflow-init.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: workflow-init
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/init/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/bmm/workflows/workflow-status.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD BMM Agent: workflow-status
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/workflow.yaml
3. Pass the yaml path _bmad/bmm/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/cis/agents/brainstorming-coach.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: brainstorming-coach
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/cis/agents/brainstorming-coach.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/cis/agents/creative-problem-solver.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: creative-problem-solver
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/cis/agents/creative-problem-solver.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/cis/agents/design-thinking-coach.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: design-thinking-coach
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/cis/agents/design-thinking-coach.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/cis/agents/innovation-strategist.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: innovation-strategist
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/cis/agents/innovation-strategist.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/cis/agents/presentation-master.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: presentation-master
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/cis/agents/presentation-master.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/cis/agents/storyteller.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: storyteller
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/cis/agents/storyteller/storyteller.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

15
q1/.cursor/rules/bmad/cis/workflows/design-thinking.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: design-thinking
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/design-thinking/workflow.yaml
3. Pass the yaml path _bmad/cis/workflows/design-thinking/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/cis/workflows/innovation-strategy.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: innovation-strategy
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/innovation-strategy/workflow.yaml
3. Pass the yaml path _bmad/cis/workflows/innovation-strategy/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/cis/workflows/problem-solving.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: problem-solving
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/problem-solving/workflow.yaml
3. Pass the yaml path _bmad/cis/workflows/problem-solving/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/cis/workflows/storytelling.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CIS Agent: storytelling
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/cis/workflows/storytelling/workflow.yaml
3. Pass the yaml path _bmad/cis/workflows/storytelling/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
5. Save outputs after EACH section when generating any documents from templates
</steps>

15
q1/.cursor/rules/bmad/core/agents/bmad-master.mdc Normal file
View File

@@ -0,0 +1,15 @@
---
description: BMAD CORE Agent: bmad-master
globs:
alwaysApply: false
---
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
<agent-activation CRITICAL="TRUE">
1. LOAD the FULL agent file from @_bmad/core/agents/bmad-master.md
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
3. Execute ALL activation steps exactly as written in the agent file
4. Follow the agent's persona and menu system precisely
5. Stay in character throughout the session
</agent-activation>

122
q1/.cursor/rules/bmad/core/tasks/advanced-elicitation.mdc Normal file
View File

@@ -0,0 +1,122 @@
---
description: BMAD CORE Task: Advanced Elicitation
globs:
alwaysApply: false
---
<task id="_bmad/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
methods="{project-root}/_bmad/core/tasks/advanced-elicitation-methods.csv"
agent-party="{project-root}/_bmad/_config/agent-manifest.csv">
<llm critical="true">
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
<i>DO NOT skip steps or change the sequence</i>
<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>
<integration description="When called from workflow">
<desc>When called during template workflow processing:</desc>
<i>1. Receive or review the current section content that was just generated or</i>
<i>2. Apply elicitation methods iteratively to enhance that specific content</i>
<i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
<i>4. The enhanced content replaces the original section content in the output document</i>
</integration>
<flow>
<step n="1" title="Method Registry Loading">
<action>Load and read {{methods}} and {{agent-party}}</action>
<csv-structure>
<i>category: Method grouping (core, structural, risk, etc.)</i>
<i>method_name: Display name for the method</i>
<i>description: Rich explanation of what the method does, when to use it, and why it's valuable</i>
<i>output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action")</i>
</csv-structure>
<context-analysis>
<i>Use conversation history</i>
<i>Analyze: content type, complexity, stakeholder needs, risk level, and creative potential</i>
</context-analysis>
<smart-selection>
<i>1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential</i>
<i>2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV</i>
<i>3. Select 5 methods: Choose methods that best match the context based on their descriptions</i>
<i>4. Balance approach: Include mix of foundational and specialized techniques as appropriate</i>
</smart-selection>
</step>
<step n="2" title="Present Options and Handle Responses">
<format>
**Advanced Elicitation Options (If you launched Party Mode, they will participate randomly)**
Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed:
1. [Method Name]
2. [Method Name]
3. [Method Name]
4. [Method Name]
5. [Method Name]
r. Reshuffle the list with 5 new options
a. List all methods with descriptions
x. Proceed / No Further Actions
</format>
<response-handling>
<case n="1-5">
<i>Execute the selected method using its description from the CSV</i>
<i>Adapt the method's complexity and output format based on the current context</i>
<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: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
</case>
<case n="r">
<i>Select 5 random methods from advanced-elicitation-methods.csv, present new list with same prompt format</i>
<i>When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being
potentially the most useful for the document or section being discovered</i>
</case>
<case n="x">
<i>Complete elicitation and proceed</i>
<i>Return the fully enhanced content back to create-doc.md</i>
<i>The enhanced content becomes the final version for that section</i>
<i>Signal completion back to create-doc.md to continue with next section</i>
</case>
<case n="a">
<i>List all methods with their descriptions from the CSV in a compact table</i>
<i>Allow user to select any method by name or number from the full list</i>
<i>After selection, execute the method as described in the n="1-5" case above</i>
</case>
<case n="direct-feedback">
<i>Apply changes to current section content and re-present choices</i>
</case>
<case n="multiple-numbers">
<i>Execute methods in sequence on the content, then re-offer choices</i>
</case>
</response-handling>
</step>
<step n="3" title="Execution Guidelines">
<i>Method execution: Use the description from CSV to understand and apply each method</i>
<i>Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")</i>
<i>Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)</i>
<i>Creative application: Interpret methods flexibly based on context while maintaining pattern consistency</i>
<i>Focus on actionable insights</i>
<i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user
indicates otherwise)</i>
<i>Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory
already</i>
<i>Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution</i>
<i>Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session</i>
<i>Each method application builds upon previous enhancements</i>
<i>Content preservation: Track all enhancements made during elicitation</i>
<i>Iterative enhancement: Each selected method (1-5) should:</i>
<i> 1. Apply to the current enhanced version of the content</i>
<i> 2. Show the improvements made</i>
<i> 3. Return to the prompt for additional elicitations or completion</i>
</step>
</flow>
</task>

71
q1/.cursor/rules/bmad/core/tasks/index-docs.mdc Normal file
View File

@@ -0,0 +1,71 @@
---
description: BMAD CORE Task: Index Docs
globs:
alwaysApply: false
---
<task id="_bmad/core/tasks/index-docs" name="Index Docs"
description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
<llm critical="true">
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
<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="Scan Directory">
<i>List all files and subdirectories in the target location</i>
</step>
<step n="2" title="Group Content">
<i>Organize files by type, purpose, or subdirectory</i>
</step>
<step n="3" title="Generate Descriptions">
<i>Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the
filename</i>
</step>
<step n="4" title="Create/Update Index">
<i>Write or update index.md with organized file listings</i>
</step>
</flow>
<output-format>
<example>
# Directory Index
## Files
- **[filename.ext](./filename.ext)** - Brief description
- **[another-file.ext](./another-file.ext)** - Brief description
## Subdirectories
### subfolder/
- **[file1.ext](./subfolder/file1.ext)** - Brief description
- **[file2.ext](./subfolder/file2.ext)** - Brief description
### another-folder/
- **[file3.ext](./another-folder/file3.ext)** - Brief description
</example>
</output-format>
<halt-conditions critical="true">
<i>HALT if target directory does not exist or is inaccessible</i>
<i>HALT if user does not have write permissions to create index.md</i>
</halt-conditions>
<validation>
<i>Use relative paths starting with ./</i>
<i>Group similar files together</i>
<i>Read file contents to generate accurate descriptions - don't guess from filenames</i>
<i>Keep descriptions concise but informative (3-10 words)</i>
<i>Sort alphabetically within groups</i>
<i>Skip hidden files (starting with .) unless specified</i>
</validation>
</task>

115
q1/.cursor/rules/bmad/core/tools/shard-doc.mdc Normal file
View File

@@ -0,0 +1,115 @@
---
description: BMAD CORE Tool: Shard Document
globs:
alwaysApply: false
---
<tool id="_bmad/core/tasks/shard-doc" name="Shard Document"
description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
standalone="true">
<objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>
<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>
<critical-context>
<i>Uses `npx @kayvan/markdown-tree-parser` to automatically shard documents by level 2 headings and generate an index</i>
</critical-context>
<flow>
<step n="1" title="Get Source Document">
<action>Ask user for the source document path if not provided already</action>
<action>Verify file exists and is accessible</action>
<action>Verify file is markdown format (.md extension)</action>
<action if="file not found or not markdown">HALT with error message</action>
</step>
<step n="2" title="Get Destination Folder">
<action>Determine default destination: same location as source file, folder named after source file without .md extension</action>
<action>Example: /path/to/architecture.md → /path/to/architecture/</action>
<action>Ask user for the destination folder path ([y] to confirm use of default: [suggested-path], else enter a new path)</action>
<action if="user accepts default">Use the suggested destination path</action>
<action if="user provides custom path">Use the custom destination path</action>
<action>Verify destination folder exists or can be created</action>
<action>Check write permissions for destination</action>
<action if="permission denied">HALT with error message</action>
</step>
<step n="3" title="Execute Sharding">
<action>Inform user that sharding is beginning</action>
<action>Execute command: `npx @kayvan/markdown-tree-parser explode [source-document] [destination-folder]`</action>
<action>Capture command output and any errors</action>
<action if="command fails">HALT and display error to user</action>
</step>
<step n="4" title="Verify Output">
<action>Check that destination folder contains sharded files</action>
<action>Verify index.md was created in destination folder</action>
<action>Count the number of files created</action>
<action if="no files created">HALT with error message</action>
</step>
<step n="5" title="Report Completion">
<action>Display completion report to user including:</action>
<i>- Source document path and name</i>
<i>- Destination folder path</i>
<i>- Number of section files created</i>
<i>- Confirmation that index.md was created</i>
<i>- Any tool output or warnings</i>
<action>Inform user that sharding completed successfully</action>
</step>
<step n="6" title="Handle Original Document">
<critical>Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion</critical>
<action>Present user with options for the original document:</action>
<ask>What would you like to do with the original document `[source-document-name]`?
Options:
[d] Delete - Remove the original (recommended - shards can always be recombined)
[m] Move to archive - Move original to a backup/archive location
[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
Your choice (d/m/k):</ask>
<check if="user selects 'd' (delete)">
<action>Delete the original source document file</action>
<action>Confirm deletion to user: "✓ Original document deleted: [source-document-path]"</action>
<note>The document can be reconstructed from shards by concatenating all section files in order</note>
</check>
<check if="user selects 'm' (move)">
<action>Determine default archive location: same directory as source, in an "archive" subfolder</action>
<action>Example: /path/to/architecture.md → /path/to/archive/architecture.md</action>
<ask>Archive location ([y] to use default: [default-archive-path], or provide custom path):</ask>
<action if="user accepts default">Use default archive path</action>
<action if="user provides custom path">Use custom archive path</action>
<action>Create archive directory if it doesn't exist</action>
<action>Move original document to archive location</action>
<action>Confirm move to user: "✓ Original document moved to: [archive-path]"</action>
</check>
<check if="user selects 'k' (keep)">
<action>Display warning to user:</action>
<output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
This creates confusion because:
- The discover_inputs protocol may load the wrong version
- Updates to one won't reflect in the other
- You'll have duplicate content taking up space
Consider deleting or archiving the original document.</output>
<action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
</check>
</step>
</flow>
<halt-conditions critical="true">
<i>HALT if npx command fails or produces no output files</i>
</halt-conditions>
</tool>

7
q1/.cursor/rules/bmad/core/workflows/brainstorming.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD CORE Agent: brainstorming
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!

7
q1/.cursor/rules/bmad/core/workflows/party-mode.mdc Normal file
View File

@@ -0,0 +1,7 @@
---
description: BMAD CORE Agent: party-mode
globs:
alwaysApply: false
---
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/party-mode/workflow.md, READ its entire contents and follow its directions exactly!

175
q1/.cursor/rules/bmad/index.mdc Normal file
View File

@@ -0,0 +1,175 @@
---
description: BMAD Method - Master Index
globs:
alwaysApply: true
---
# BMAD Method - Cursor Rules Index
This is the master index for all BMAD agents, tasks, tools, and workflows available in your project.
## Installation Complete!
BMAD rules have been installed to: `.cursor/rules/bmad/`
**Note:** BMAD does not modify your `.cursorrules` file. You manage that separately.
## How to Use
- Reference specific agents: @bmad/{module}/agents/{agent-name}
- Reference specific tasks: @bmad/{module}/tasks/{task-name}
- Reference specific tools: @bmad/{module}/tools/{tool-name}
- Reference specific workflows: @bmad/{module}/workflows/{workflow-name}
- Reference entire modules: @bmad/{module}
- Reference this index: @bmad/index
## Available Modules
### CORE
**Agents:**
- @bmad/core/agents/bmad-master - bmad-master
**Tasks:**
- @bmad/core/tasks/advanced-elicitation - advanced-elicitation
- @bmad/core/tasks/index-docs - index-docs
**Tools:**
- @bmad/core/tools/shard-doc - shard-doc
**Workflows:**
- @bmad/core/workflows/brainstorming - brainstorming
- @bmad/core/workflows/party-mode - party-mode
### BMB
**Agents:**
- @bmad/bmb/agents/agent-builder - agent-builder
- @bmad/bmb/agents/module-builder - module-builder
- @bmad/bmb/agents/workflow-builder - workflow-builder
**Workflows:**
- @bmad/bmb/workflows/Meal Prep & Nutrition Plan - Meal Prep & Nutrition Plan
- @bmad/bmb/workflows/create-agent - create-agent
- @bmad/bmb/workflows/create-module - create-module
- @bmad/bmb/workflows/create-workflow - create-workflow
- @bmad/bmb/workflows/edit-agent - edit-agent
- @bmad/bmb/workflows/edit-workflow - edit-workflow
- @bmad/bmb/workflows/workflow-compliance-check - workflow-compliance-check
### BMGD
**Agents:**
- @bmad/bmgd/agents/game-architect - game-architect
- @bmad/bmgd/agents/game-designer - game-designer
- @bmad/bmgd/agents/game-dev - game-dev
- @bmad/bmgd/agents/game-qa - game-qa
- @bmad/bmgd/agents/game-scrum-master - game-scrum-master
- @bmad/bmgd/agents/game-solo-dev - game-solo-dev
**Workflows:**
- @bmad/bmgd/workflows/brainstorm-game - brainstorm-game
- @bmad/bmgd/workflows/create-game-brief - create-game-brief
- @bmad/bmgd/workflows/game-brief - game-brief
- @bmad/bmgd/workflows/create-gdd - create-gdd
- @bmad/bmgd/workflows/gdd - gdd
- @bmad/bmgd/workflows/narrative - narrative
- @bmad/bmgd/workflows/game-architecture - game-architecture
- @bmad/bmgd/workflows/generate-project-context - generate-project-context
- @bmad/bmgd/workflows/code-review - code-review
- @bmad/bmgd/workflows/correct-course - correct-course
- @bmad/bmgd/workflows/create-story - create-story
- @bmad/bmgd/workflows/dev-story - dev-story
- @bmad/bmgd/workflows/retrospective - retrospective
- @bmad/bmgd/workflows/sprint-planning - sprint-planning
- @bmad/bmgd/workflows/sprint-status - sprint-status
- @bmad/bmgd/workflows/create-tech-spec - create-tech-spec
- @bmad/bmgd/workflows/quick-dev - quick-dev
- @bmad/bmgd/workflows/quick-prototype - quick-prototype
- @bmad/bmgd/workflows/gametest-automate - gametest-automate
- @bmad/bmgd/workflows/gametest-performance - gametest-performance
- @bmad/bmgd/workflows/gametest-playtest-plan - gametest-playtest-plan
- @bmad/bmgd/workflows/gametest-test-design - gametest-test-design
- @bmad/bmgd/workflows/gametest-framework - gametest-framework
- @bmad/bmgd/workflows/gametest-test-review - gametest-test-review
- @bmad/bmgd/workflows/workflow-init - workflow-init
- @bmad/bmgd/workflows/workflow-status - workflow-status
### BMM
**Agents:**
- @bmad/bmm/agents/analyst - analyst
- @bmad/bmm/agents/architect - architect
- @bmad/bmm/agents/dev - dev
- @bmad/bmm/agents/pm - pm
- @bmad/bmm/agents/quick-flow-solo-dev - quick-flow-solo-dev
- @bmad/bmm/agents/sm - sm
- @bmad/bmm/agents/tea - tea
- @bmad/bmm/agents/tech-writer - tech-writer
- @bmad/bmm/agents/ux-designer - ux-designer
**Workflows:**
- @bmad/bmm/workflows/create-product-brief - create-product-brief
- @bmad/bmm/workflows/research - research
- @bmad/bmm/workflows/create-ux-design - create-ux-design
- @bmad/bmm/workflows/create-prd - create-prd
- @bmad/bmm/workflows/check-implementation-readiness - check-implementation-readiness
- @bmad/bmm/workflows/create-architecture - create-architecture
- @bmad/bmm/workflows/create-epics-and-stories - create-epics-and-stories
- @bmad/bmm/workflows/code-review - code-review
- @bmad/bmm/workflows/correct-course - correct-course
- @bmad/bmm/workflows/create-story - create-story
- @bmad/bmm/workflows/dev-story - dev-story
- @bmad/bmm/workflows/retrospective - retrospective
- @bmad/bmm/workflows/sprint-planning - sprint-planning
- @bmad/bmm/workflows/sprint-status - sprint-status
- @bmad/bmm/workflows/create-tech-spec - create-tech-spec
- @bmad/bmm/workflows/quick-dev - quick-dev
- @bmad/bmm/workflows/document-project - document-project
- @bmad/bmm/workflows/create-excalidraw-dataflow - create-excalidraw-dataflow
- @bmad/bmm/workflows/create-excalidraw-diagram - create-excalidraw-diagram
- @bmad/bmm/workflows/create-excalidraw-flowchart - create-excalidraw-flowchart
- @bmad/bmm/workflows/create-excalidraw-wireframe - create-excalidraw-wireframe
- @bmad/bmm/workflows/generate-project-context - generate-project-context
- @bmad/bmm/workflows/testarch-atdd - testarch-atdd
- @bmad/bmm/workflows/testarch-automate - testarch-automate
- @bmad/bmm/workflows/testarch-ci - testarch-ci
- @bmad/bmm/workflows/testarch-framework - testarch-framework
- @bmad/bmm/workflows/testarch-nfr - testarch-nfr
- @bmad/bmm/workflows/testarch-test-design - testarch-test-design
- @bmad/bmm/workflows/testarch-test-review - testarch-test-review
- @bmad/bmm/workflows/testarch-trace - testarch-trace
- @bmad/bmm/workflows/workflow-init - workflow-init
- @bmad/bmm/workflows/workflow-status - workflow-status
### CIS
**Agents:**
- @bmad/cis/agents/brainstorming-coach - brainstorming-coach
- @bmad/cis/agents/creative-problem-solver - creative-problem-solver
- @bmad/cis/agents/design-thinking-coach - design-thinking-coach
- @bmad/cis/agents/innovation-strategist - innovation-strategist
- @bmad/cis/agents/presentation-master - presentation-master
- @bmad/cis/agents/storyteller - storyteller
**Workflows:**
- @bmad/cis/workflows/design-thinking - design-thinking
- @bmad/cis/workflows/innovation-strategy - innovation-strategy
- @bmad/cis/workflows/problem-solving - problem-solving
- @bmad/cis/workflows/storytelling - storytelling
## Quick Reference
- All BMAD rules are Manual type - reference them explicitly when needed
- Agents provide persona-based assistance with specific expertise
- Tasks are reusable workflows for common operations
- Tools provide specialized functionality
- Workflows orchestrate multi-step processes
- Each agent includes an activation block for proper initialization
## Configuration
BMAD rules are configured as Manual rules (alwaysApply: false) to give you control
over when they're included in your context. Reference them explicitly when you need
specific agent expertise, task workflows, tools, or guided workflows.