mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
update inquirer to v9.x for better windows support
This commit is contained in:
Brian Madison
14
q1/.clinerules/workflows/bmad-bmb-agents-agent-builder.md
Normal file
14
q1/.clinerules/workflows/bmad-bmb-agents-agent-builder.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'agent-builder'
|
||||
description: 'agent-builder agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmb-agents-module-builder.md
Normal file
14
q1/.clinerules/workflows/bmad-bmb-agents-module-builder.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'module-builder'
|
||||
description: 'module-builder agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmb-agents-workflow-builder.md
Normal file
14
q1/.clinerules/workflows/bmad-bmb-agents-workflow-builder.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'workflow-builder'
|
||||
description: 'workflow-builder agent'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Creates personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.'
|
||||
---
|
||||
|
||||
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!
|
||||
52
q1/.clinerules/workflows/bmad-bmb-workflows-README.md
Normal file
52
q1/.clinerules/workflows/bmad-bmb-workflows-README.md
Normal file
@@ -0,0 +1,52 @@
|
||||
# BMB Workflows
|
||||
|
||||
## Available Workflows in bmb
|
||||
|
||||
**Meal Prep & Nutrition Plan**
|
||||
|
||||
- Path: `_bmad/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md`
|
||||
- Creates personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.
|
||||
|
||||
**create-agent**
|
||||
|
||||
- Path: `_bmad/bmb/workflows/create-agent/workflow.md`
|
||||
- Interactive workflow to build BMAD Core compliant agents with optional brainstorming, persona development, and command structure
|
||||
|
||||
**create-module**
|
||||
|
||||
- Path: `_bmad/bmb/workflows/create-module/workflow.md`
|
||||
- Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure
|
||||
|
||||
**create-workflow**
|
||||
|
||||
- Path: `_bmad/bmb/workflows/create-workflow/workflow.md`
|
||||
- Create structured standalone workflows using markdown-based step architecture
|
||||
|
||||
**edit-agent**
|
||||
|
||||
- Path: `_bmad/bmb/workflows/edit-agent/workflow.md`
|
||||
- Edit existing BMAD agents while following all best practices and conventions
|
||||
|
||||
**edit-workflow**
|
||||
|
||||
- Path: `_bmad/bmb/workflows/edit-workflow/workflow.md`
|
||||
- Intelligent workflow editor that helps modify existing workflows while following best practices
|
||||
|
||||
**workflow-compliance-check**
|
||||
|
||||
- Path: `_bmad/bmb/workflows/workflow-compliance-check/workflow.md`
|
||||
- Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting
|
||||
|
||||
## Execution
|
||||
|
||||
When running any workflow:
|
||||
|
||||
1. LOAD {project-root}/\_bmad/core/tasks/workflow.xml
|
||||
2. Pass the workflow path as 'workflow-config' parameter
|
||||
3. Follow workflow.xml instructions EXACTLY
|
||||
4. Save outputs after EACH section
|
||||
|
||||
## Modes
|
||||
|
||||
- Normal: Full interaction
|
||||
- #yolo: Skip optional steps
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Interactive workflow to build BMAD Core compliant agents with optional brainstorming, persona development, and command structure'
|
||||
---
|
||||
|
||||
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!
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure'
|
||||
---
|
||||
|
||||
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!
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Create structured standalone workflows using markdown-based step architecture'
|
||||
---
|
||||
|
||||
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!
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Edit existing BMAD agents while following all best practices and conventions'
|
||||
---
|
||||
|
||||
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!
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Intelligent workflow editor that helps modify existing workflows while following best practices'
|
||||
---
|
||||
|
||||
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!
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting'
|
||||
---
|
||||
|
||||
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!
|
||||
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-architect.md
Normal file
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-architect.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'game-architect'
|
||||
description: 'game-architect agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-designer.md
Normal file
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-designer.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'game-designer'
|
||||
description: 'game-designer agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-dev.md
Normal file
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-dev.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'game-dev'
|
||||
description: 'game-dev agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-qa.md
Normal file
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-qa.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'game-qa'
|
||||
description: 'game-qa agent'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'game-scrum-master'
|
||||
description: 'game-scrum-master agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-solo-dev.md
Normal file
14
q1/.clinerules/workflows/bmad-bmgd-agents-game-solo-dev.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'game-solo-dev'
|
||||
description: 'game-solo-dev agent'
|
||||
---
|
||||
|
||||
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>
|
||||
147
q1/.clinerules/workflows/bmad-bmgd-workflows-README.md
Normal file
147
q1/.clinerules/workflows/bmad-bmgd-workflows-README.md
Normal file
@@ -0,0 +1,147 @@
|
||||
# BMGD Workflows
|
||||
|
||||
## Available Workflows in bmgd
|
||||
|
||||
**brainstorm-game**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml`
|
||||
- Facilitate game brainstorming sessions with game-specific context, guidance, and game design techniques.
|
||||
|
||||
**create-game-brief**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.md`
|
||||
- Creates a comprehensive Game Brief through collaborative step-by-step discovery to capture game vision before detailed design.
|
||||
|
||||
**game-brief**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml`
|
||||
- Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration
|
||||
|
||||
**create-gdd**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/2-design/gdd/workflow.md`
|
||||
- Creates a comprehensive Game Design Document through collaborative step-by-step discovery between game designer and user.
|
||||
|
||||
**gdd**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/2-design/gdd/workflow.yaml`
|
||||
- Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance.
|
||||
|
||||
**narrative**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/2-design/narrative/workflow.yaml`
|
||||
- Narrative design workflow for story-driven games. Creates comprehensive narrative documentation including story structure, character arcs, world-building, dialogue systems, and production planning.
|
||||
|
||||
**game-architecture**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml`
|
||||
- Collaborative game architecture workflow for AI-agent consistency. Intelligent, adaptive conversation that produces a decision-focused game architecture document covering engine, systems, networking, and technical design optimized for game development.
|
||||
|
||||
**generate-project-context**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/3-technical/generate-project-context/workflow.md`
|
||||
- Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing game code. Optimized for LLM context efficiency.
|
||||
|
||||
**code-review**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/4-production/code-review/workflow.yaml`
|
||||
- Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval. Game-specific focus on 60fps, feel, and platform considerations.
|
||||
|
||||
**correct-course**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml`
|
||||
- Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation
|
||||
|
||||
**create-story**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/4-production/create-story/workflow.yaml`
|
||||
- Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder
|
||||
|
||||
**dev-story**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/4-production/dev-story/workflow.yaml`
|
||||
- Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria
|
||||
|
||||
**retrospective**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/4-production/retrospective/workflow.yaml`
|
||||
- Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic
|
||||
|
||||
**sprint-planning**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml`
|
||||
- Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle
|
||||
|
||||
**sprint-status**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml`
|
||||
- Summarize sprint-status.yaml for game project, surface risks, and route to the right implementation workflow.
|
||||
|
||||
**create-tech-spec**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml`
|
||||
- Conversational spec engineering for games - ask questions, investigate code, produce implementation-ready tech-spec.
|
||||
|
||||
**quick-dev**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml`
|
||||
- Flexible game development - execute tech-specs, implement features, or refactor code with game-specific considerations.
|
||||
|
||||
**quick-prototype**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml`
|
||||
- Rapid game prototyping - quickly test gameplay ideas, mechanics, or features with minimal setup.
|
||||
|
||||
**gametest-automate**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/gametest/automate/workflow.yaml`
|
||||
- Generate automated game tests for Unity, Unreal, or Godot based on test design scenarios
|
||||
|
||||
**gametest-performance**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/gametest/performance/workflow.yaml`
|
||||
- Design performance testing strategy for frame rate, memory, and loading times
|
||||
|
||||
**gametest-playtest-plan**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/gametest/playtest-plan/workflow.yaml`
|
||||
- Create structured playtesting sessions for gameplay validation and user feedback
|
||||
|
||||
**gametest-test-design**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/gametest/test-design/workflow.yaml`
|
||||
- Create comprehensive game test scenarios covering gameplay, progression, and quality requirements
|
||||
|
||||
**gametest-framework**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/gametest/test-framework/workflow.yaml`
|
||||
- Initialize game test framework architecture for Unity, Unreal Engine, or Godot projects
|
||||
|
||||
**gametest-test-review**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/gametest/test-review/workflow.yaml`
|
||||
- Review test quality, coverage, and identify gaps in game testing
|
||||
|
||||
**workflow-init**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/workflow-status/init/workflow.yaml`
|
||||
- Initialize a new BMGD game project by determining level, type, and creating workflow path
|
||||
|
||||
**workflow-status**
|
||||
|
||||
- Path: `_bmad/bmgd/workflows/workflow-status/workflow.yaml`
|
||||
- Lightweight status checker - answers ""what should I do now?"" for any game dev agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.
|
||||
|
||||
## Execution
|
||||
|
||||
When running any workflow:
|
||||
|
||||
1. LOAD {project-root}/\_bmad/core/tasks/workflow.xml
|
||||
2. Pass the workflow path as 'workflow-config' parameter
|
||||
3. Follow workflow.xml instructions EXACTLY
|
||||
4. Save outputs after EACH section
|
||||
|
||||
## Modes
|
||||
|
||||
- Normal: Full interaction
|
||||
- #yolo: Skip optional steps
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Facilitate game brainstorming sessions with game-specific context, guidance, and game design techniques.'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmgd-workflows-code-review.md
Normal file
13
q1/.clinerules/workflows/bmad-bmgd-workflows-code-review.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval. Game-specific focus on 60fps, feel, and platform considerations.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Creates a comprehensive Game Brief through collaborative step-by-step discovery to capture game vision before detailed design.'
|
||||
---
|
||||
|
||||
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!
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Creates a comprehensive Game Design Document through collaborative step-by-step discovery between game designer and user.'
|
||||
---
|
||||
|
||||
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!
|
||||
13
q1/.clinerules/workflows/bmad-bmgd-workflows-create-story.md
Normal file
13
q1/.clinerules/workflows/bmad-bmgd-workflows-create-story.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Conversational spec engineering for games - ask questions, investigate code, produce implementation-ready tech-spec.'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmgd-workflows-dev-story.md
Normal file
13
q1/.clinerules/workflows/bmad-bmgd-workflows-dev-story.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Collaborative game architecture workflow for AI-agent consistency. Intelligent, adaptive conversation that produces a decision-focused game architecture document covering engine, systems, networking, and technical design optimized for game development.'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmgd-workflows-game-brief.md
Normal file
13
q1/.clinerules/workflows/bmad-bmgd-workflows-game-brief.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Generate automated game tests for Unity, Unreal, or Godot based on test design scenarios'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Initialize game test framework architecture for Unity, Unreal Engine, or Godot projects'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Design performance testing strategy for frame rate, memory, and loading times'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Create structured playtesting sessions for gameplay validation and user feedback'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Create comprehensive game test scenarios covering gameplay, progression, and quality requirements'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Review test quality, coverage, and identify gaps in game testing'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmgd-workflows-gdd.md
Normal file
13
q1/.clinerules/workflows/bmad-bmgd-workflows-gdd.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing game code. Optimized for LLM context efficiency.'
|
||||
---
|
||||
|
||||
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!
|
||||
13
q1/.clinerules/workflows/bmad-bmgd-workflows-narrative.md
Normal file
13
q1/.clinerules/workflows/bmad-bmgd-workflows-narrative.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Narrative design workflow for story-driven games. Creates comprehensive narrative documentation including story structure, character arcs, world-building, dialogue systems, and production planning.'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmgd-workflows-quick-dev.md
Normal file
13
q1/.clinerules/workflows/bmad-bmgd-workflows-quick-dev.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Flexible game development - execute tech-specs, implement features, or refactor code with game-specific considerations.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Rapid game prototyping - quickly test gameplay ideas, mechanics, or features with minimal setup.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Summarize sprint-status.yaml for game project, surface risks, and route to the right implementation workflow.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Initialize a new BMGD game project by determining level, type, and creating workflow path'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Lightweight status checker - answers ""what should I do now?"" for any game dev agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmm-agents-analyst.md
Normal file
14
q1/.clinerules/workflows/bmad-bmm-agents-analyst.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'analyst'
|
||||
description: 'analyst agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmm-agents-architect.md
Normal file
14
q1/.clinerules/workflows/bmad-bmm-agents-architect.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'architect'
|
||||
description: 'architect agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmm-agents-dev.md
Normal file
14
q1/.clinerules/workflows/bmad-bmm-agents-dev.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'dev'
|
||||
description: 'dev agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmm-agents-pm.md
Normal file
14
q1/.clinerules/workflows/bmad-bmm-agents-pm.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'pm'
|
||||
description: 'pm agent'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'quick-flow-solo-dev'
|
||||
description: 'quick-flow-solo-dev agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmm-agents-sm.md
Normal file
14
q1/.clinerules/workflows/bmad-bmm-agents-sm.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'sm'
|
||||
description: 'sm agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmm-agents-tea.md
Normal file
14
q1/.clinerules/workflows/bmad-bmm-agents-tea.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'tea'
|
||||
description: 'tea agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmm-agents-tech-writer.md
Normal file
14
q1/.clinerules/workflows/bmad-bmm-agents-tech-writer.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'tech-writer'
|
||||
description: 'tech-writer agent'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-bmm-agents-ux-designer.md
Normal file
14
q1/.clinerules/workflows/bmad-bmm-agents-ux-designer.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'ux-designer'
|
||||
description: 'ux-designer agent'
|
||||
---
|
||||
|
||||
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>
|
||||
177
q1/.clinerules/workflows/bmad-bmm-workflows-README.md
Normal file
177
q1/.clinerules/workflows/bmad-bmm-workflows-README.md
Normal file
@@ -0,0 +1,177 @@
|
||||
# BMM Workflows
|
||||
|
||||
## Available Workflows in bmm
|
||||
|
||||
**create-product-brief**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md`
|
||||
- Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
|
||||
|
||||
**research**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/1-analysis/research/workflow.md`
|
||||
- Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.
|
||||
|
||||
**create-ux-design**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md`
|
||||
- Work with a peer UX Design expert to plan your applications UX patterns, look and feel.
|
||||
|
||||
**create-prd**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md`
|
||||
- Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.
|
||||
|
||||
**check-implementation-readiness**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md`
|
||||
- Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.
|
||||
|
||||
**create-architecture**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md`
|
||||
- Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.
|
||||
|
||||
**create-epics-and-stories**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md`
|
||||
- Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.
|
||||
|
||||
**code-review**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml`
|
||||
- Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.
|
||||
|
||||
**correct-course**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml`
|
||||
- Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation
|
||||
|
||||
**create-story**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml`
|
||||
- Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking
|
||||
|
||||
**dev-story**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml`
|
||||
- Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria
|
||||
|
||||
**retrospective**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml`
|
||||
- Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic
|
||||
|
||||
**sprint-planning**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml`
|
||||
- Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle
|
||||
|
||||
**sprint-status**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml`
|
||||
- Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.
|
||||
|
||||
**create-tech-spec**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml`
|
||||
- Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.
|
||||
|
||||
**quick-dev**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml`
|
||||
- Flexible development - execute tech-specs OR direct instructions with optional planning.
|
||||
|
||||
**document-project**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/document-project/workflow.yaml`
|
||||
- Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development
|
||||
|
||||
**create-excalidraw-dataflow**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml`
|
||||
- Create data flow diagrams (DFD) in Excalidraw format
|
||||
|
||||
**create-excalidraw-diagram**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml`
|
||||
- Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format
|
||||
|
||||
**create-excalidraw-flowchart**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml`
|
||||
- Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows
|
||||
|
||||
**create-excalidraw-wireframe**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml`
|
||||
- Create website or app wireframes in Excalidraw format
|
||||
|
||||
**generate-project-context**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/generate-project-context/workflow.md`
|
||||
- Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.
|
||||
|
||||
**testarch-atdd**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/testarch/atdd/workflow.yaml`
|
||||
- Generate failing acceptance tests before implementation using TDD red-green-refactor cycle
|
||||
|
||||
**testarch-automate**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/testarch/automate/workflow.yaml`
|
||||
- Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite
|
||||
|
||||
**testarch-ci**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/testarch/ci/workflow.yaml`
|
||||
- Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection
|
||||
|
||||
**testarch-framework**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/testarch/framework/workflow.yaml`
|
||||
- Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration
|
||||
|
||||
**testarch-nfr**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml`
|
||||
- Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation
|
||||
|
||||
**testarch-test-design**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/testarch/test-design/workflow.yaml`
|
||||
- Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.
|
||||
|
||||
**testarch-test-review**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/testarch/test-review/workflow.yaml`
|
||||
- Review test quality using comprehensive knowledge base and best practices validation
|
||||
|
||||
**testarch-trace**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/testarch/trace/workflow.yaml`
|
||||
- Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)
|
||||
|
||||
**workflow-init**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/workflow-status/init/workflow.yaml`
|
||||
- Initialize a new BMM project by determining level, type, and creating workflow path
|
||||
|
||||
**workflow-status**
|
||||
|
||||
- Path: `_bmad/bmm/workflows/workflow-status/workflow.yaml`
|
||||
- Lightweight status checker - answers ""what should I do now?"" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.
|
||||
|
||||
## Execution
|
||||
|
||||
When running any workflow:
|
||||
|
||||
1. LOAD {project-root}/\_bmad/core/tasks/workflow.xml
|
||||
2. Pass the workflow path as 'workflow-config' parameter
|
||||
3. Follow workflow.xml instructions EXACTLY
|
||||
4. Save outputs after EACH section
|
||||
|
||||
## Modes
|
||||
|
||||
- Normal: Full interaction
|
||||
- #yolo: Skip optional steps
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.'
|
||||
---
|
||||
|
||||
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!
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-code-review.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-code-review.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.'
|
||||
---
|
||||
|
||||
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!
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.'
|
||||
---
|
||||
|
||||
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!
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Create data flow diagrams (DFD) in Excalidraw format'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Create website or app wireframes in Excalidraw format'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.'
|
||||
---
|
||||
|
||||
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!
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.'
|
||||
---
|
||||
|
||||
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!
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-create-story.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-create-story.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Work with a peer UX Design expert to plan your applications UX patterns, look and feel.'
|
||||
---
|
||||
|
||||
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!
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-dev-story.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-dev-story.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.'
|
||||
---
|
||||
|
||||
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!
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-quick-dev.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-quick-dev.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
|
||||
---
|
||||
|
||||
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>
|
||||
5
q1/.clinerules/workflows/bmad-bmm-workflows-research.md
Normal file
5
q1/.clinerules/workflows/bmad-bmm-workflows-research.md
Normal file
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.'
|
||||
---
|
||||
|
||||
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!
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-retrospective.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-retrospective.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-sprint-status.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-sprint-status.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-testarch-atdd.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-testarch-atdd.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Generate failing acceptance tests before implementation using TDD red-green-refactor cycle'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-testarch-ci.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-testarch-ci.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-testarch-nfr.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-testarch-nfr.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Review test quality using comprehensive knowledge base and best practices validation'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-bmm-workflows-workflow-init.md
Normal file
13
q1/.clinerules/workflows/bmad-bmm-workflows-workflow-init.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Initialize a new BMM project by determining level, type, and creating workflow path'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Lightweight status checker - answers ""what should I do now?"" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'brainstorming-coach'
|
||||
description: 'brainstorming-coach agent'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'creative-problem-solver'
|
||||
description: 'creative-problem-solver agent'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'design-thinking-coach'
|
||||
description: 'design-thinking-coach agent'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'innovation-strategist'
|
||||
description: 'innovation-strategist agent'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'presentation-master'
|
||||
description: 'presentation-master agent'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'storyteller'
|
||||
description: 'storyteller agent'
|
||||
---
|
||||
|
||||
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>
|
||||
37
q1/.clinerules/workflows/bmad-cis-workflows-README.md
Normal file
37
q1/.clinerules/workflows/bmad-cis-workflows-README.md
Normal file
@@ -0,0 +1,37 @@
|
||||
# CIS Workflows
|
||||
|
||||
## Available Workflows in cis
|
||||
|
||||
**design-thinking**
|
||||
|
||||
- Path: `_bmad/cis/workflows/design-thinking/workflow.yaml`
|
||||
- Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.
|
||||
|
||||
**innovation-strategy**
|
||||
|
||||
- Path: `_bmad/cis/workflows/innovation-strategy/workflow.yaml`
|
||||
- Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.
|
||||
|
||||
**problem-solving**
|
||||
|
||||
- Path: `_bmad/cis/workflows/problem-solving/workflow.yaml`
|
||||
- Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.
|
||||
|
||||
**storytelling**
|
||||
|
||||
- Path: `_bmad/cis/workflows/storytelling/workflow.yaml`
|
||||
- Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.
|
||||
|
||||
## Execution
|
||||
|
||||
When running any workflow:
|
||||
|
||||
1. LOAD {project-root}/\_bmad/core/tasks/workflow.xml
|
||||
2. Pass the workflow path as 'workflow-config' parameter
|
||||
3. Follow workflow.xml instructions EXACTLY
|
||||
4. Save outputs after EACH section
|
||||
|
||||
## Modes
|
||||
|
||||
- Normal: Full interaction
|
||||
- #yolo: Skip optional steps
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.'
|
||||
---
|
||||
|
||||
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>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.'
|
||||
---
|
||||
|
||||
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>
|
||||
13
q1/.clinerules/workflows/bmad-cis-workflows-storytelling.md
Normal file
13
q1/.clinerules/workflows/bmad-cis-workflows-storytelling.md
Normal file
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: 'Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.'
|
||||
---
|
||||
|
||||
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>
|
||||
14
q1/.clinerules/workflows/bmad-core-agents-bmad-master.md
Normal file
14
q1/.clinerules/workflows/bmad-core-agents-bmad-master.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
name: 'bmad-master'
|
||||
description: 'bmad-master agent'
|
||||
---
|
||||
|
||||
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>
|
||||
27
q1/.clinerules/workflows/bmad-core-workflows-README.md
Normal file
27
q1/.clinerules/workflows/bmad-core-workflows-README.md
Normal file
@@ -0,0 +1,27 @@
|
||||
# CORE Workflows
|
||||
|
||||
## Available Workflows in core
|
||||
|
||||
**brainstorming**
|
||||
|
||||
- Path: `_bmad/core/workflows/brainstorming/workflow.md`
|
||||
- Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
|
||||
|
||||
**party-mode**
|
||||
|
||||
- Path: `_bmad/core/workflows/party-mode/workflow.md`
|
||||
- Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
|
||||
|
||||
## Execution
|
||||
|
||||
When running any workflow:
|
||||
|
||||
1. LOAD {project-root}/\_bmad/core/tasks/workflow.xml
|
||||
2. Pass the workflow path as 'workflow-config' parameter
|
||||
3. Follow workflow.xml instructions EXACTLY
|
||||
4. Save outputs after EACH section
|
||||
|
||||
## Modes
|
||||
|
||||
- Normal: Full interaction
|
||||
- #yolo: Skip optional steps
|
||||
@@ -0,0 +1,5 @@
|
||||
---
|
||||
description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods'
|
||||
---
|
||||
|
||||
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!
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user