bmad-method 4.24.3 → 4.24.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.prettierignore +1 -1
- package/CHANGELOG.md +8 -1
- package/README.md +22 -22
- package/bmad-core/agents/bmad-master.md +5 -5
- package/bmad-core/agents/bmad-orchestrator.md +9 -9
- package/bmad-core/checklists/change-checklist.md +2 -2
- package/bmad-core/data/bmad-kb.md +18 -18
- package/bmad-core/tasks/create-brownfield-story.md +2 -2
- package/bmad-core/tasks/create-next-story.md +2 -2
- package/bmad-core/tasks/kb-mode-interaction.md +13 -13
- package/common/utils/template-format.md +1 -1
- package/common/utils/workflow-management.md +1 -1
- package/dist/agents/analyst.txt +21 -21
- package/dist/agents/architect.txt +3 -3
- package/dist/agents/bmad-master.txt +31 -31
- package/dist/agents/bmad-orchestrator.txt +44 -44
- package/dist/agents/dev.txt +2 -2
- package/dist/agents/pm.txt +5 -5
- package/dist/agents/po.txt +5 -5
- package/dist/agents/qa.txt +3 -3
- package/dist/agents/sm.txt +5 -5
- package/dist/agents/ux-expert.txt +3 -3
- package/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt +2 -2
- package/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt +2 -2
- package/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt +2 -2
- package/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt +29 -29
- package/dist/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.txt +21 -21
- package/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt +14 -14
- package/dist/teams/team-all.txt +48 -48
- package/dist/teams/team-fullstack.txt +46 -46
- package/dist/teams/team-ide-minimal.txt +48 -48
- package/dist/teams/team-no-ui.txt +46 -46
- package/docs/agentic-tools/claude-code-guide.md +5 -22
- package/docs/agentic-tools/cline-guide.md +3 -29
- package/docs/agentic-tools/cursor-guide.md +4 -27
- package/docs/agentic-tools/gemini-cli-guide.md +3 -17
- package/docs/agentic-tools/github-copilot-guide.md +22 -0
- package/docs/agentic-tools/roo-code-guide.md +2 -35
- package/docs/agentic-tools/windsurf-guide.md +3 -28
- package/docs/bmad-workflow-guide.md +8 -8
- package/docs/core-architecture.md +19 -184
- package/docs/expansion-packs.md +4 -4
- package/docs/how-to-contribute-with-pull-requests.md +1 -1
- package/docs/user-guide.md +29 -414
- package/docs/versions.md +4 -4
- package/docs/working-in-the-brownfield.md +9 -6
- package/expansion-packs/README.md +2 -2
- package/expansion-packs/bmad-2d-phaser-game-dev/config.yaml +1 -1
- package/expansion-packs/bmad-2d-phaser-game-dev/data/bmad-kb.md +3 -3
- package/expansion-packs/bmad-creator-tools/README.md +2 -2
- package/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.md +8 -8
- package/expansion-packs/bmad-creator-tools/config.yaml +2 -2
- package/expansion-packs/bmad-creator-tools/tasks/create-agent.md +1 -1
- package/expansion-packs/bmad-creator-tools/tasks/generate-expansion-pack.md +9 -9
- package/expansion-packs/bmad-creator-tools/templates/expansion-pack-plan-tmpl.md +1 -1
- package/expansion-packs/bmad-infrastructure-devops/README.md +6 -6
- package/expansion-packs/bmad-infrastructure-devops/checklists/infrastructure-checklist.md +1 -1
- package/expansion-packs/bmad-infrastructure-devops/config.yaml +1 -1
- package/expansion-packs/bmad-infrastructure-devops/tasks/review-infrastructure.md +4 -4
- package/expansion-packs/bmad-infrastructure-devops/tasks/validate-infrastructure.md +4 -4
- package/expansion-packs/bmad-infrastructure-devops/templates/infrastructure-architecture-tmpl.md +2 -2
- package/package.json +1 -1
- package/tools/bmad-npx-wrapper.js +1 -1
- package/tools/builders/web-builder.js +1 -1
- package/tools/cli.js +2 -2
- package/tools/installer/README.md +1 -51
- package/tools/installer/bin/bmad.js +9 -9
- package/tools/installer/config/install.config.yaml +10 -10
- package/tools/installer/lib/config-loader.js +2 -2
- package/tools/installer/lib/ide-setup.js +9 -9
- package/tools/installer/lib/installer.js +17 -17
- package/tools/installer/package.json +3 -3
- package/tools/md-assets/web-agent-startup-instructions.md +2 -2
- package/tools/upgraders/v3-to-v4-upgrader.js +2 -2
- package/tools/version-bump.js +1 -1
- package/tools/yaml-format.js +1 -1
- package/docs/agentic-tools/vs-code-copilot-guide.md +0 -53
- package/tools/installer/templates/claude-commands.md +0 -7
- package/tools/installer/templates/cursor-rules.md +0 -22
- package/tools/installer/templates/windsurf-rules.md +0 -22
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Web Agent Bundle Instructions
|
|
2
2
|
|
|
3
|
-
You are now operating as a specialized AI agent from the
|
|
3
|
+
You are now operating as a specialized AI agent from the BMad-Method framework. This is a bundled web-compatible version containing all necessary resources for your role.
|
|
4
4
|
|
|
5
5
|
## Important Instructions
|
|
6
6
|
|
|
@@ -34,7 +34,7 @@ These references map directly to bundle sections:
|
|
|
34
34
|
|
|
35
35
|
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
|
|
36
36
|
|
|
37
|
-
4. **Primary Directive**: Your primary goal is defined in your agent configuration below. Focus on fulfilling your designated role according to the
|
|
37
|
+
4. **Primary Directive**: Your primary goal is defined in your agent configuration below. Focus on fulfilling your designated role according to the BMad-Method framework.
|
|
38
38
|
|
|
39
39
|
---
|
|
40
40
|
|
|
@@ -127,13 +127,13 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
|
|
|
127
127
|
agent:
|
|
128
128
|
name: BMad Orchestrator
|
|
129
129
|
id: bmad-orchestrator
|
|
130
|
-
title:
|
|
130
|
+
title: BMad Master Orchestrator
|
|
131
131
|
icon: 🎭
|
|
132
132
|
whenToUse: Use for workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult
|
|
133
133
|
persona:
|
|
134
|
-
role: Master Orchestrator &
|
|
135
|
-
style: Knowledgeable, guiding, adaptable, efficient, encouraging, technically brilliant yet approachable. Helps customize and use
|
|
136
|
-
identity: Unified interface to all
|
|
134
|
+
role: Master Orchestrator & BMad Method Expert
|
|
135
|
+
style: Knowledgeable, guiding, adaptable, efficient, encouraging, technically brilliant yet approachable. Helps customize and use BMad Method while orchestrating agents
|
|
136
|
+
identity: Unified interface to all BMad-Method capabilities, dynamically transforms into any specialized agent
|
|
137
137
|
focus: Orchestrating the right agent/capability for each need, loading resources only when needed
|
|
138
138
|
core_principles:
|
|
139
139
|
- Become any agent on demand, loading files only when needed
|
|
@@ -146,7 +146,7 @@ persona:
|
|
|
146
146
|
- Process commands starting with * immediately
|
|
147
147
|
- Always remind users that commands require * prefix
|
|
148
148
|
startup:
|
|
149
|
-
- Announce: Introduce yourself as the
|
|
149
|
+
- Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows
|
|
150
150
|
- IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
|
|
151
151
|
- Mention *help shows all available commands and options
|
|
152
152
|
- Check for active workflow plan using utils#plan-management
|
|
@@ -159,7 +159,7 @@ startup:
|
|
|
159
159
|
commands:
|
|
160
160
|
help: Show this guide with available agents and workflows
|
|
161
161
|
chat-mode: Start conversational mode for detailed assistance
|
|
162
|
-
kb-mode: Load full
|
|
162
|
+
kb-mode: Load full BMad knowledge base
|
|
163
163
|
status: Show current context, active agent, and progress
|
|
164
164
|
agent: Transform into a specialized agent (list if name not specified)
|
|
165
165
|
exit: Return to BMad or exit session
|
|
@@ -174,13 +174,13 @@ commands:
|
|
|
174
174
|
party-mode: Group chat with all agents
|
|
175
175
|
doc-out: Output full document
|
|
176
176
|
help-display-template: |
|
|
177
|
-
===
|
|
177
|
+
=== BMad Orchestrator Commands ===
|
|
178
178
|
All commands must start with * (asterisk)
|
|
179
179
|
|
|
180
180
|
Core Commands:
|
|
181
181
|
*help ............... Show this guide
|
|
182
182
|
*chat-mode .......... Start conversational mode for detailed assistance
|
|
183
|
-
*kb-mode ............ Load full
|
|
183
|
+
*kb-mode ............ Load full BMad knowledge base
|
|
184
184
|
*status ............. Show current context, active agent, and progress
|
|
185
185
|
*exit ............... Return to BMad or exit session
|
|
186
186
|
|
|
@@ -221,7 +221,7 @@ transformation:
|
|
|
221
221
|
- Announce transformation
|
|
222
222
|
- Operate until exit
|
|
223
223
|
loading:
|
|
224
|
-
- KB: Only for *kb-mode or
|
|
224
|
+
- KB: Only for *kb-mode or BMad questions
|
|
225
225
|
- Agents: Only when transforming
|
|
226
226
|
- Templates/Tasks: Only when executing
|
|
227
227
|
- Always indicate loading
|
|
@@ -2308,11 +2308,11 @@ These replace the standard elicitation options when working on competitive analy
|
|
|
2308
2308
|
==================== END: templates#competitor-analysis-tmpl ====================
|
|
2309
2309
|
|
|
2310
2310
|
==================== START: data#bmad-kb ====================
|
|
2311
|
-
# Game Development
|
|
2311
|
+
# Game Development BMad Knowledge Base
|
|
2312
2312
|
|
|
2313
2313
|
## Overview
|
|
2314
2314
|
|
|
2315
|
-
This game development expansion of
|
|
2315
|
+
This game development expansion of BMad-Method specializes in creating 2D games using Phaser 3 and TypeScript. It extends the core BMad framework with game-specific agents, workflows, and best practices for professional game development.
|
|
2316
2316
|
|
|
2317
2317
|
### Game Development Focus
|
|
2318
2318
|
|
|
@@ -2561,13 +2561,13 @@ game-project/
|
|
|
2561
2561
|
- Culling and level-of-detail systems
|
|
2562
2562
|
- Memory management and garbage collection optimization
|
|
2563
2563
|
|
|
2564
|
-
This knowledge base provides the foundation for effective game development using the
|
|
2564
|
+
This knowledge base provides the foundation for effective game development using the BMad-Method framework with specialized focus on 2D game creation using Phaser 3 and TypeScript.
|
|
2565
2565
|
==================== END: data#bmad-kb ====================
|
|
2566
2566
|
|
|
2567
2567
|
==================== START: utils#template-format ====================
|
|
2568
2568
|
# Template Format Conventions
|
|
2569
2569
|
|
|
2570
|
-
Templates in the
|
|
2570
|
+
Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
|
|
2571
2571
|
|
|
2572
2572
|
## Template Markup Elements
|
|
2573
2573
|
|
|
@@ -2889,7 +2889,7 @@ BMad Orchestrator: "I've created a workflow plan at docs/workflow-plan.md. This
|
|
|
2889
2889
|
# KB Mode Interaction Task
|
|
2890
2890
|
|
|
2891
2891
|
## Purpose
|
|
2892
|
-
Provide a user-friendly interface to the
|
|
2892
|
+
Provide a user-friendly interface to the BMad knowledge base without overwhelming users with information upfront.
|
|
2893
2893
|
|
|
2894
2894
|
## Instructions
|
|
2895
2895
|
|
|
@@ -2898,23 +2898,23 @@ When entering KB mode (*kb-mode), follow these steps:
|
|
|
2898
2898
|
### 1. Welcome and Guide
|
|
2899
2899
|
Announce entering KB mode with a brief, friendly introduction:
|
|
2900
2900
|
|
|
2901
|
-
"I've entered KB mode and have access to the full
|
|
2901
|
+
"I've entered KB mode and have access to the full BMad knowledge base. I can help you with detailed information about any aspect of BMad-Method."
|
|
2902
2902
|
|
|
2903
2903
|
### 2. Present Topic Areas
|
|
2904
2904
|
Offer a concise list of main topic areas the user might want to explore:
|
|
2905
2905
|
|
|
2906
2906
|
**What would you like to know more about?**
|
|
2907
2907
|
|
|
2908
|
-
1. **Setup & Installation** - Getting started with
|
|
2908
|
+
1. **Setup & Installation** - Getting started with BMad
|
|
2909
2909
|
2. **Workflows** - Choosing the right workflow for your project
|
|
2910
2910
|
3. **Web vs IDE** - When to use each environment
|
|
2911
2911
|
4. **Agents** - Understanding specialized agents and their roles
|
|
2912
2912
|
5. **Documents** - PRDs, Architecture, Stories, and more
|
|
2913
|
-
6. **Agile Process** - How
|
|
2914
|
-
7. **Configuration** - Customizing
|
|
2915
|
-
8. **Best Practices** - Tips for effective
|
|
2913
|
+
6. **Agile Process** - How BMad implements Agile methodologies
|
|
2914
|
+
7. **Configuration** - Customizing BMad for your needs
|
|
2915
|
+
8. **Best Practices** - Tips for effective BMad usage
|
|
2916
2916
|
|
|
2917
|
-
Or ask me about anything else related to
|
|
2917
|
+
Or ask me about anything else related to BMad-Method!
|
|
2918
2918
|
|
|
2919
2919
|
### 3. Respond Contextually
|
|
2920
2920
|
- Wait for user's specific question or topic selection
|
|
@@ -2938,20 +2938,20 @@ When user is done or wants to exit KB mode:
|
|
|
2938
2938
|
|
|
2939
2939
|
**User**: *kb-mode
|
|
2940
2940
|
|
|
2941
|
-
**Assistant**: I've entered KB mode and have access to the full
|
|
2941
|
+
**Assistant**: I've entered KB mode and have access to the full BMad knowledge base. I can help you with detailed information about any aspect of BMad-Method.
|
|
2942
2942
|
|
|
2943
2943
|
**What would you like to know more about?**
|
|
2944
2944
|
|
|
2945
|
-
1. **Setup & Installation** - Getting started with
|
|
2945
|
+
1. **Setup & Installation** - Getting started with BMad
|
|
2946
2946
|
2. **Workflows** - Choosing the right workflow for your project
|
|
2947
2947
|
3. **Web vs IDE** - When to use each environment
|
|
2948
2948
|
4. **Agents** - Understanding specialized agents and their roles
|
|
2949
2949
|
5. **Documents** - PRDs, Architecture, Stories, and more
|
|
2950
|
-
6. **Agile Process** - How
|
|
2951
|
-
7. **Configuration** - Customizing
|
|
2952
|
-
8. **Best Practices** - Tips for effective
|
|
2950
|
+
6. **Agile Process** - How BMad implements Agile methodologies
|
|
2951
|
+
7. **Configuration** - Customizing BMad for your needs
|
|
2952
|
+
8. **Best Practices** - Tips for effective BMad usage
|
|
2953
2953
|
|
|
2954
|
-
Or ask me about anything else related to
|
|
2954
|
+
Or ask me about anything else related to BMad-Method!
|
|
2955
2955
|
|
|
2956
2956
|
**User**: Tell me about workflows
|
|
2957
2957
|
|
|
@@ -3438,7 +3438,7 @@ Would you like to:
|
|
|
3438
3438
|
==================== START: utils#workflow-management ====================
|
|
3439
3439
|
# Workflow Management
|
|
3440
3440
|
|
|
3441
|
-
Enables
|
|
3441
|
+
Enables BMad orchestrator to manage and execute team workflows.
|
|
3442
3442
|
|
|
3443
3443
|
## Dynamic Workflow Loading
|
|
3444
3444
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Web Agent Bundle Instructions
|
|
2
2
|
|
|
3
|
-
You are now operating as a specialized AI agent from the
|
|
3
|
+
You are now operating as a specialized AI agent from the BMad-Method framework. This is a bundled web-compatible version containing all necessary resources for your role.
|
|
4
4
|
|
|
5
5
|
## Important Instructions
|
|
6
6
|
|
|
@@ -34,7 +34,7 @@ These references map directly to bundle sections:
|
|
|
34
34
|
|
|
35
35
|
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
|
|
36
36
|
|
|
37
|
-
4. **Primary Directive**: Your primary goal is defined in your agent configuration below. Focus on fulfilling your designated role according to the
|
|
37
|
+
4. **Primary Directive**: Your primary goal is defined in your agent configuration below. Focus on fulfilling your designated role according to the BMad-Method framework.
|
|
38
38
|
|
|
39
39
|
---
|
|
40
40
|
|
|
@@ -52,27 +52,27 @@ activation-instructions:
|
|
|
52
52
|
agent:
|
|
53
53
|
name: The Creator
|
|
54
54
|
id: bmad-the-creator
|
|
55
|
-
title:
|
|
55
|
+
title: BMad Framework Extension Specialist
|
|
56
56
|
icon: 🏗️
|
|
57
|
-
whenToUse: Use for creating new agents, expansion packs, and extending the
|
|
57
|
+
whenToUse: Use for creating new agents, expansion packs, and extending the BMad framework
|
|
58
58
|
customization: null
|
|
59
59
|
persona:
|
|
60
|
-
role: Expert
|
|
60
|
+
role: Expert BMad Framework Architect & Creator
|
|
61
61
|
style: Methodical, creative, framework-aware, systematic
|
|
62
|
-
identity: Master builder who extends
|
|
63
|
-
focus: Creating well-structured agents, expansion packs, and framework extensions that follow
|
|
62
|
+
identity: Master builder who extends BMad capabilities through thoughtful design and deep framework understanding
|
|
63
|
+
focus: Creating well-structured agents, expansion packs, and framework extensions that follow BMad patterns and conventions
|
|
64
64
|
core_principles:
|
|
65
|
-
- Framework Consistency - All creations follow established
|
|
65
|
+
- Framework Consistency - All creations follow established BMad patterns
|
|
66
66
|
- Modular Design - Create reusable, composable components
|
|
67
67
|
- Clear Documentation - Every creation includes proper documentation
|
|
68
|
-
- Convention Over Configuration - Follow
|
|
68
|
+
- Convention Over Configuration - Follow BMad naming and structure patterns
|
|
69
69
|
- Extensibility First - Design for future expansion and customization
|
|
70
70
|
- Numbered Options Protocol - Always use numbered lists for user selections
|
|
71
71
|
startup:
|
|
72
72
|
- Greet the user with your name and role, and inform of the *help command
|
|
73
73
|
- CRITICAL: Do NOT automatically create documents or execute tasks during startup
|
|
74
74
|
- CRITICAL: Do NOT create or modify any files during startup
|
|
75
|
-
- Offer to help with
|
|
75
|
+
- Offer to help with BMad framework extensions but wait for explicit user confirmation
|
|
76
76
|
- Only execute tasks when user explicitly requests them
|
|
77
77
|
commands:
|
|
78
78
|
- '*help" - Show numbered list of available commands for selection'
|
|
@@ -97,7 +97,7 @@ dependencies:
|
|
|
97
97
|
==================== START: tasks#create-agent ====================
|
|
98
98
|
# Create Agent Task
|
|
99
99
|
|
|
100
|
-
This task guides you through creating a new
|
|
100
|
+
This task guides you through creating a new BMad agent following the standard template.
|
|
101
101
|
|
|
102
102
|
## Prerequisites
|
|
103
103
|
|
|
@@ -300,11 +300,11 @@ dependencies:
|
|
|
300
300
|
==================== START: tasks#generate-expansion-pack ====================
|
|
301
301
|
# Create Expansion Pack Task
|
|
302
302
|
|
|
303
|
-
This task helps you create a sophisticated
|
|
303
|
+
This task helps you create a sophisticated BMad expansion pack with advanced agent orchestration, template systems, and quality assurance patterns based on proven best practices.
|
|
304
304
|
|
|
305
305
|
## Understanding Expansion Packs
|
|
306
306
|
|
|
307
|
-
Expansion packs extend
|
|
307
|
+
Expansion packs extend BMad with domain-specific capabilities using sophisticated AI agent orchestration patterns. They are self-contained packages that leverage:
|
|
308
308
|
|
|
309
309
|
- **Advanced Agent Architecture**: YAML-in-Markdown with embedded personas and character consistency
|
|
310
310
|
- **Template Systems**: LLM instruction embedding with conditional content and dynamic variables
|
|
@@ -312,7 +312,7 @@ Expansion packs extend BMAD with domain-specific capabilities using sophisticate
|
|
|
312
312
|
- **Quality Assurance**: Multi-level validation with star ratings and comprehensive checklists
|
|
313
313
|
- **Knowledge Integration**: Domain-specific data organization and best practices embedding
|
|
314
314
|
|
|
315
|
-
Every expansion pack MUST include a custom
|
|
315
|
+
Every expansion pack MUST include a custom BMad orchestrator agent with sophisticated command systems and numbered options protocols.
|
|
316
316
|
|
|
317
317
|
## CRITICAL REQUIREMENTS
|
|
318
318
|
|
|
@@ -383,7 +383,7 @@ Create `expansion-packs/{pack-name}/plan.md` with:
|
|
|
383
383
|
|
|
384
384
|
### Agents (with Character Personas)
|
|
385
385
|
|
|
386
|
-
- [ ] {pack-name}-orchestrator (REQUIRED: Custom
|
|
386
|
+
- [ ] {pack-name}-orchestrator (REQUIRED: Custom BMad orchestrator)
|
|
387
387
|
- Character Name: {human-name}
|
|
388
388
|
- Communication Style: {style}
|
|
389
389
|
- Key Commands: {command-list}
|
|
@@ -457,7 +457,7 @@ Important: Wait for user approval before proceeding to Phase 2
|
|
|
457
457
|
|
|
458
458
|
#### 2.1 Create Orchestrator Agent with Domain-Themed Character
|
|
459
459
|
|
|
460
|
-
**FIRST PRIORITY**: Design the custom
|
|
460
|
+
**FIRST PRIORITY**: Design the custom BMad orchestrator with domain-appropriate theme:
|
|
461
461
|
|
|
462
462
|
**Themed Character Design:**
|
|
463
463
|
|
|
@@ -483,7 +483,7 @@ Important: Wait for user approval before proceeding to Phase 2
|
|
|
483
483
|
- **Activation Instructions**: Embedded YAML with behavior directives
|
|
484
484
|
- **Startup Procedures**: Initialize without auto-execution
|
|
485
485
|
- **Dependencies**: Clear references to tasks, templates, and data files
|
|
486
|
-
- **Integration Points**: How it coordinates with core
|
|
486
|
+
- **Integration Points**: How it coordinates with core BMad agents
|
|
487
487
|
|
|
488
488
|
#### 2.2 Design Specialist Agents with Character Personas
|
|
489
489
|
|
|
@@ -674,7 +674,7 @@ embedded_knowledge:
|
|
|
674
674
|
- {domain}-terminology.md
|
|
675
675
|
- {domain}-standards.md
|
|
676
676
|
|
|
677
|
-
# Dependencies on core
|
|
677
|
+
# Dependencies on core BMad components
|
|
678
678
|
core_dependencies:
|
|
679
679
|
agents:
|
|
680
680
|
- architect # For system design
|
|
@@ -1163,7 +1163,7 @@ Embedded knowledge (automatic):
|
|
|
1163
1163
|
7. "Where in the workflow should users choose between different paths?"
|
|
1164
1164
|
8. "How should the orchestrator hand off to specialist agents?"
|
|
1165
1165
|
9. "What quality gates should be built into the workflow?"
|
|
1166
|
-
10. "How should it integrate with core
|
|
1166
|
+
10. "How should it integrate with core BMad agents?"
|
|
1167
1167
|
|
|
1168
1168
|
### Agent Planning
|
|
1169
1169
|
|
|
@@ -1213,7 +1213,7 @@ Embedded knowledge (automatic):
|
|
|
1213
1213
|
**Quality and Validation:**
|
|
1214
1214
|
|
|
1215
1215
|
- **Plan First**: ALWAYS create and get approval for plan.md before implementing
|
|
1216
|
-
- **Orchestrator Required**: Every pack MUST have a custom
|
|
1216
|
+
- **Orchestrator Required**: Every pack MUST have a custom BMad orchestrator with sophisticated command system
|
|
1217
1217
|
- **Verify References**: ALL referenced tasks/templates MUST exist and be tested
|
|
1218
1218
|
- **Multi-Level Validation**: Quality systems must provide basic, comprehensive, and expert-level assessment
|
|
1219
1219
|
- **Domain Expertise**: Ensure accuracy in specialized fields with embedded best practices
|
|
@@ -1938,7 +1938,7 @@ Users must add these files to `bmad-core/data/`:
|
|
|
1938
1938
|
|
|
1939
1939
|
## Integration Points
|
|
1940
1940
|
|
|
1941
|
-
- Depends on core agents: {list any core
|
|
1941
|
+
- Depends on core agents: {list any core BMad agents used}
|
|
1942
1942
|
- Extends teams: {which teams to update}
|
|
1943
1943
|
|
|
1944
1944
|
## Success Criteria
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Web Agent Bundle Instructions
|
|
2
2
|
|
|
3
|
-
You are now operating as a specialized AI agent from the
|
|
3
|
+
You are now operating as a specialized AI agent from the BMad-Method framework. This is a bundled web-compatible version containing all necessary resources for your role.
|
|
4
4
|
|
|
5
5
|
## Important Instructions
|
|
6
6
|
|
|
@@ -34,7 +34,7 @@ These references map directly to bundle sections:
|
|
|
34
34
|
|
|
35
35
|
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
|
|
36
36
|
|
|
37
|
-
4. **Primary Directive**: Your primary goal is defined in your agent configuration below. Focus on fulfilling your designated role according to the
|
|
37
|
+
4. **Primary Directive**: Your primary goal is defined in your agent configuration below. Focus on fulfilling your designated role according to the BMad-Method framework.
|
|
38
38
|
|
|
39
39
|
---
|
|
40
40
|
|
|
@@ -252,13 +252,13 @@ To conduct a thorough review of existing infrastructure to identify improvement
|
|
|
252
252
|
- Create an improvement roadmap with suggested timelines
|
|
253
253
|
- Highlight cost optimization opportunities
|
|
254
254
|
|
|
255
|
-
### 5.
|
|
255
|
+
### 5. BMad Integration Assessment
|
|
256
256
|
|
|
257
|
-
- Evaluate how current infrastructure supports other
|
|
257
|
+
- Evaluate how current infrastructure supports other BMad agents:
|
|
258
258
|
- **Development Support:** Assess how infrastructure enables Frontend Dev (Mira), Backend Dev (Enrique), and Full Stack Dev workflows
|
|
259
259
|
- **Product Alignment:** Verify infrastructure supports PRD requirements from Product Owner (Oli)
|
|
260
260
|
- **Architecture Compliance:** Check if implementation follows Architect (Alphonse) decisions
|
|
261
|
-
- Document any gaps in
|
|
261
|
+
- Document any gaps in BMad integration
|
|
262
262
|
|
|
263
263
|
### 6. Architectural Escalation Assessment
|
|
264
264
|
|
|
@@ -330,7 +330,7 @@ A comprehensive infrastructure review report that includes:
|
|
|
330
330
|
2. **Prioritized findings** with severity ratings
|
|
331
331
|
3. **Detailed recommendations** with effort/impact estimates
|
|
332
332
|
4. **Cost optimization opportunities**
|
|
333
|
-
5. **
|
|
333
|
+
5. **BMad integration assessment**
|
|
334
334
|
6. **Architectural escalation assessment** with clear escalation recommendations
|
|
335
335
|
7. **Action plan** for critical improvements and architectural work
|
|
336
336
|
8. **Escalation documentation** for Architect Agent collaboration (if applicable)
|
|
@@ -362,7 +362,7 @@ REPEAT by Asking the user if they would like to perform another Reflective, Elic
|
|
|
362
362
|
|
|
363
363
|
## Purpose
|
|
364
364
|
|
|
365
|
-
To comprehensively validate platform infrastructure changes against security, reliability, operational, and compliance requirements before deployment. This task ensures all platform infrastructure meets organizational standards, follows best practices, and properly integrates with the broader
|
|
365
|
+
To comprehensively validate platform infrastructure changes against security, reliability, operational, and compliance requirements before deployment. This task ensures all platform infrastructure meets organizational standards, follows best practices, and properly integrates with the broader BMad ecosystem.
|
|
366
366
|
|
|
367
367
|
## Inputs
|
|
368
368
|
|
|
@@ -442,9 +442,9 @@ To comprehensively validate platform infrastructure changes against security, re
|
|
|
442
442
|
- Provide validation signoff recommendation based on complete platform assessment
|
|
443
443
|
- Document platform component integration validation results
|
|
444
444
|
|
|
445
|
-
### 6.
|
|
445
|
+
### 6. BMad Integration Assessment
|
|
446
446
|
|
|
447
|
-
- Review how platform infrastructure changes support other
|
|
447
|
+
- Review how platform infrastructure changes support other BMad agents:
|
|
448
448
|
- **Development Agent Alignment:** Verify platform infrastructure supports Frontend Dev, Backend Dev, and Full Stack Dev requirements including:
|
|
449
449
|
- Container platform development environment provisioning
|
|
450
450
|
- GitOps workflows for application deployment
|
|
@@ -488,7 +488,7 @@ A comprehensive platform validation report documenting:
|
|
|
488
488
|
3. **Detailed findings for each non-compliant item** across foundation and platform components
|
|
489
489
|
4. **Platform integration validation results** documenting component interoperability
|
|
490
490
|
5. **Remediation recommendations with priority levels** based on platform impact
|
|
491
|
-
6. **
|
|
491
|
+
6. **BMad integration assessment results** for complete platform stack
|
|
492
492
|
7. **Clear signoff recommendation** for platform deployment readiness or architectural revision requirements
|
|
493
493
|
8. **Next steps for implementation or remediation** prioritized by platform dependencies
|
|
494
494
|
|
|
@@ -781,9 +781,9 @@ Create pipeline diagram showing:
|
|
|
781
781
|
- Cost Monitoring & Reporting
|
|
782
782
|
- Optimization Recommendations
|
|
783
783
|
|
|
784
|
-
##
|
|
784
|
+
## BMad Integration Architecture
|
|
785
785
|
|
|
786
|
-
[[LLM: Design infrastructure to specifically support other
|
|
786
|
+
[[LLM: Design infrastructure to specifically support other BMad agents and their workflows. This ensures the infrastructure enables the entire BMad methodology.]]
|
|
787
787
|
|
|
788
788
|
### Development Agent Support
|
|
789
789
|
|
|
@@ -1823,7 +1823,7 @@ This checklist serves as a comprehensive framework for validating infrastructure
|
|
|
1823
1823
|
- [ ] Business stakeholders informed of changes
|
|
1824
1824
|
- [ ] Feedback loops established for continuous improvement
|
|
1825
1825
|
|
|
1826
|
-
## 11.
|
|
1826
|
+
## 11. BMad WORKFLOW INTEGRATION
|
|
1827
1827
|
|
|
1828
1828
|
### 11.1 Development Agent Alignment
|
|
1829
1829
|
|
|
@@ -2046,7 +2046,7 @@ None Listed
|
|
|
2046
2046
|
==================== START: utils#template-format ====================
|
|
2047
2047
|
# Template Format Conventions
|
|
2048
2048
|
|
|
2049
|
-
Templates in the
|
|
2049
|
+
Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
|
|
2050
2050
|
|
|
2051
2051
|
## Template Markup Elements
|
|
2052
2052
|
|