bmad-method 4.26.0 → 4.27.0
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/.vscode/settings.json +2 -0
- package/CHANGELOG.md +15 -0
- package/README.md +29 -282
- package/bmad-core/agents/analyst.md +3 -1
- package/bmad-core/agents/bmad-master.md +5 -1
- package/bmad-core/agents/bmad-orchestrator.md +1 -1
- package/bmad-core/core-config.yaml +1 -1
- package/bmad-core/data/bmad-kb.md +74 -15
- package/bmad-core/data/brainstorming-techniques.md +36 -0
- package/bmad-core/data/elicitation-methods.md +134 -0
- package/bmad-core/tasks/advanced-elicitation.md +82 -57
- package/bmad-core/tasks/facilitate-brainstorming-session.md +136 -0
- package/bmad-core/templates/architecture-tmpl.md +23 -23
- package/bmad-core/templates/brainstorming-output-tmpl.md +149 -0
- package/bmad-core/templates/prd-tmpl.md +6 -6
- package/bmad-core/templates/prd-tmpl2.yaml +202 -0
- package/bmad-core/utils/plan-management.md +9 -13
- package/bmad-core/workflows/greenfield-service.yaml +1 -1
- package/common/tasks/create-doc.md +4 -4
- package/common/tasks/create-doc2.md +65 -0
- package/common/utils/bmad-doc-template.md +296 -0
- package/dist/agents/analyst.txt +481 -305
- package/dist/agents/architect.txt +60 -59
- package/dist/agents/bmad-master.txt +694 -399
- package/dist/agents/bmad-orchestrator.txt +197 -116
- package/dist/agents/dev.txt +18 -17
- package/dist/agents/pm.txt +47 -46
- package/dist/agents/po.txt +31 -30
- package/dist/agents/qa.txt +15 -14
- package/dist/agents/sm.txt +23 -22
- package/dist/agents/ux-expert.txt +29 -28
- package/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt +33 -32
- package/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt +19 -18
- package/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt +21 -20
- package/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt +385 -297
- package/dist/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.txt +103 -77
- package/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt +29 -28
- package/dist/teams/team-all.txt +610 -438
- package/dist/teams/team-fullstack.txt +597 -425
- package/dist/teams/team-ide-minimal.txt +238 -157
- package/dist/teams/team-no-ui.txt +583 -411
- package/docs/agentic-tools/github-copilot-guide.md +29 -9
- package/docs/bmad-workflow-guide.md +2 -2
- package/expansion-packs/bmad-2d-phaser-game-dev/config.yaml +1 -1
- package/expansion-packs/bmad-2d-phaser-game-dev/tasks/create-game-story.md +2 -2
- package/expansion-packs/bmad-creator-tools/config.yaml +1 -1
- package/expansion-packs/bmad-infrastructure-devops/config.yaml +1 -1
- package/package.json +1 -1
- package/tools/builders/web-builder.js +117 -22
- package/tools/installer/config/install.config.yaml +2 -2
- package/tools/installer/lib/ide-setup.js +2 -2
- package/tools/installer/package.json +1 -1
- package/tools/lib/dependency-resolver.js +3 -3
- package/tools/md-assets/web-agent-startup-instructions.md +10 -10
- package/bmad-core/tasks/brainstorming-techniques.md +0 -238
|
@@ -8,14 +8,14 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
|
|
|
8
8
|
|
|
9
9
|
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
|
|
10
10
|
|
|
11
|
-
- `==================== START: folder
|
|
12
|
-
- `==================== END: folder
|
|
11
|
+
- `==================== START: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
|
|
12
|
+
- `==================== END: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
|
|
13
13
|
|
|
14
14
|
When you need to reference a resource mentioned in your instructions:
|
|
15
15
|
|
|
16
16
|
- Look for the corresponding START/END tags
|
|
17
|
-
- The format is always
|
|
18
|
-
- If a section is specified (e.g., `tasks
|
|
17
|
+
- The format is always the full path with dot prefix (e.g., `.bmad-2d-phaser-game-dev/personas/analyst.md`, `.bmad-2d-phaser-game-dev/tasks/create-story.md`)
|
|
18
|
+
- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
|
|
19
19
|
|
|
20
20
|
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
|
|
21
21
|
|
|
@@ -29,8 +29,8 @@ dependencies:
|
|
|
29
29
|
|
|
30
30
|
These references map directly to bundle sections:
|
|
31
31
|
|
|
32
|
-
- `utils: template-format` → Look for `==================== START: utils
|
|
33
|
-
- `tasks: create-story` → Look for `==================== START: tasks
|
|
32
|
+
- `utils: template-format` → Look for `==================== START: .bmad-2d-phaser-game-dev/utils/template-format.md ====================`
|
|
33
|
+
- `tasks: create-story` → Look for `==================== START: .bmad-2d-phaser-game-dev/tasks/create-story.md ====================`
|
|
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
|
|
|
@@ -38,7 +38,8 @@ These references map directly to bundle sections:
|
|
|
38
38
|
|
|
39
39
|
---
|
|
40
40
|
|
|
41
|
-
|
|
41
|
+
|
|
42
|
+
==================== START: .bmad-2d-phaser-game-dev/agents/game-developer.md ====================
|
|
42
43
|
# game-developer
|
|
43
44
|
|
|
44
45
|
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
|
|
@@ -105,16 +106,16 @@ dependencies:
|
|
|
105
106
|
data:
|
|
106
107
|
- development-guidelines
|
|
107
108
|
```
|
|
108
|
-
==================== END: agents
|
|
109
|
+
==================== END: .bmad-2d-phaser-game-dev/agents/game-developer.md ====================
|
|
109
110
|
|
|
110
|
-
==================== START: tasks
|
|
111
|
+
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
|
111
112
|
# Checklist Validation Task
|
|
112
113
|
|
|
113
114
|
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
|
114
115
|
|
|
115
116
|
## Available Checklists
|
|
116
117
|
|
|
117
|
-
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the
|
|
118
|
+
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the .bmad-2d-phaser-game-dev/checklists folder to select the appropriate one to run.
|
|
118
119
|
|
|
119
120
|
## Instructions
|
|
120
121
|
|
|
@@ -123,7 +124,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
|
|
123
124
|
- If user or the task being run provides a checklist name:
|
|
124
125
|
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
|
|
125
126
|
- If multiple matches found, ask user to clarify
|
|
126
|
-
- Load the appropriate checklist from
|
|
127
|
+
- Load the appropriate checklist from .bmad-2d-phaser-game-dev/checklists/
|
|
127
128
|
- If no checklist specified:
|
|
128
129
|
- Ask the user which checklist they want to use
|
|
129
130
|
- Present the available options from the files in the checklists folder
|
|
@@ -201,9 +202,9 @@ The LLM will:
|
|
|
201
202
|
- Execute the complete checklist validation
|
|
202
203
|
- Present a final report with pass/fail rates and key findings
|
|
203
204
|
- Offer to provide detailed analysis of any section, especially those with warnings or failures
|
|
204
|
-
==================== END: tasks
|
|
205
|
+
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
|
205
206
|
|
|
206
|
-
==================== START: templates
|
|
207
|
+
==================== START: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.md ====================
|
|
207
208
|
# {{Game Title}} Game Architecture Document
|
|
208
209
|
|
|
209
210
|
[[LLM: This template creates a comprehensive game architecture document specifically for Phaser 3 + TypeScript projects. This should provide the technical foundation for all game development stories and epics.
|
|
@@ -764,9 +765,9 @@ export const GameBalance = {
|
|
|
764
765
|
- Zero TypeScript errors in strict mode
|
|
765
766
|
- Consistent adherence to coding standards
|
|
766
767
|
- Comprehensive documentation coverage
|
|
767
|
-
==================== END: templates
|
|
768
|
+
==================== END: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.md ====================
|
|
768
769
|
|
|
769
|
-
==================== START: checklists
|
|
770
|
+
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
|
770
771
|
# Game Development Story Definition of Done Checklist
|
|
771
772
|
|
|
772
773
|
## Story Completeness
|
|
@@ -927,9 +928,9 @@ export const GameBalance = {
|
|
|
927
928
|
|
|
928
929
|
**Additional Notes:**
|
|
929
930
|
_Any specific concerns, recommendations, or clarifications needed before development begins._
|
|
930
|
-
==================== END: checklists
|
|
931
|
+
==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
|
931
932
|
|
|
932
|
-
==================== START: data
|
|
933
|
+
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
|
933
934
|
# Game Development Guidelines
|
|
934
935
|
|
|
935
936
|
## Overview
|
|
@@ -1581,4 +1582,4 @@ src/
|
|
|
1581
1582
|
- **Asset Streaming**: Background loading for upcoming content
|
|
1582
1583
|
|
|
1583
1584
|
These guidelines ensure consistent, high-quality game development that meets performance targets and maintains code quality across all implementation stories.
|
|
1584
|
-
==================== END: data
|
|
1585
|
+
==================== END: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
|
@@ -8,14 +8,14 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
|
|
|
8
8
|
|
|
9
9
|
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
|
|
10
10
|
|
|
11
|
-
- `==================== START: folder
|
|
12
|
-
- `==================== END: folder
|
|
11
|
+
- `==================== START: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
|
|
12
|
+
- `==================== END: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
|
|
13
13
|
|
|
14
14
|
When you need to reference a resource mentioned in your instructions:
|
|
15
15
|
|
|
16
16
|
- Look for the corresponding START/END tags
|
|
17
|
-
- The format is always
|
|
18
|
-
- If a section is specified (e.g., `tasks
|
|
17
|
+
- The format is always the full path with dot prefix (e.g., `.bmad-2d-phaser-game-dev/personas/analyst.md`, `.bmad-2d-phaser-game-dev/tasks/create-story.md`)
|
|
18
|
+
- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
|
|
19
19
|
|
|
20
20
|
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
|
|
21
21
|
|
|
@@ -29,8 +29,8 @@ dependencies:
|
|
|
29
29
|
|
|
30
30
|
These references map directly to bundle sections:
|
|
31
31
|
|
|
32
|
-
- `utils: template-format` → Look for `==================== START: utils
|
|
33
|
-
- `tasks: create-story` → Look for `==================== START: tasks
|
|
32
|
+
- `utils: template-format` → Look for `==================== START: .bmad-2d-phaser-game-dev/utils/template-format.md ====================`
|
|
33
|
+
- `tasks: create-story` → Look for `==================== START: .bmad-2d-phaser-game-dev/tasks/create-story.md ====================`
|
|
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
|
|
|
@@ -38,7 +38,8 @@ These references map directly to bundle sections:
|
|
|
38
38
|
|
|
39
39
|
---
|
|
40
40
|
|
|
41
|
-
|
|
41
|
+
|
|
42
|
+
==================== START: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
|
|
42
43
|
# game-sm
|
|
43
44
|
|
|
44
45
|
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
|
|
@@ -90,9 +91,9 @@ dependencies:
|
|
|
90
91
|
checklists:
|
|
91
92
|
- game-story-dod-checklist
|
|
92
93
|
```
|
|
93
|
-
==================== END: agents
|
|
94
|
+
==================== END: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
|
|
94
95
|
|
|
95
|
-
==================== START: tasks
|
|
96
|
+
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
|
96
97
|
# Create Game Development Story Task
|
|
97
98
|
|
|
98
99
|
## Purpose
|
|
@@ -152,7 +153,7 @@ Before creating stories, ensure you have:
|
|
|
152
153
|
### 3. Template Execution
|
|
153
154
|
|
|
154
155
|
**Load Template:**
|
|
155
|
-
Use
|
|
156
|
+
Use `.bmad-2d-phaser-game-dev/templates/game-story-tmpl.md` following all embedded LLM instructions
|
|
156
157
|
|
|
157
158
|
**Key Focus Areas:**
|
|
158
159
|
|
|
@@ -188,7 +189,7 @@ Use `templates#game-story-tmpl` following all embedded LLM instructions
|
|
|
188
189
|
### 5. Quality Assurance
|
|
189
190
|
|
|
190
191
|
**Apply Checklist:**
|
|
191
|
-
Execute
|
|
192
|
+
Execute `.bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md` against completed story
|
|
192
193
|
|
|
193
194
|
**Story Criteria:**
|
|
194
195
|
|
|
@@ -309,16 +310,16 @@ Execute `checklists#game-story-dod-checklist` against completed story
|
|
|
309
310
|
- Testing → Done
|
|
310
311
|
|
|
311
312
|
This task ensures game development stories are immediately actionable and enable efficient AI-driven development of game features.
|
|
312
|
-
==================== END: tasks
|
|
313
|
+
==================== END: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
|
313
314
|
|
|
314
|
-
==================== START: tasks
|
|
315
|
+
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
|
315
316
|
# Checklist Validation Task
|
|
316
317
|
|
|
317
318
|
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
|
318
319
|
|
|
319
320
|
## Available Checklists
|
|
320
321
|
|
|
321
|
-
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the
|
|
322
|
+
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the .bmad-2d-phaser-game-dev/checklists folder to select the appropriate one to run.
|
|
322
323
|
|
|
323
324
|
## Instructions
|
|
324
325
|
|
|
@@ -327,7 +328,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
|
|
327
328
|
- If user or the task being run provides a checklist name:
|
|
328
329
|
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
|
|
329
330
|
- If multiple matches found, ask user to clarify
|
|
330
|
-
- Load the appropriate checklist from
|
|
331
|
+
- Load the appropriate checklist from .bmad-2d-phaser-game-dev/checklists/
|
|
331
332
|
- If no checklist specified:
|
|
332
333
|
- Ask the user which checklist they want to use
|
|
333
334
|
- Present the available options from the files in the checklists folder
|
|
@@ -405,9 +406,9 @@ The LLM will:
|
|
|
405
406
|
- Execute the complete checklist validation
|
|
406
407
|
- Present a final report with pass/fail rates and key findings
|
|
407
408
|
- Offer to provide detailed analysis of any section, especially those with warnings or failures
|
|
408
|
-
==================== END: tasks
|
|
409
|
+
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
|
409
410
|
|
|
410
|
-
==================== START: templates
|
|
411
|
+
==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.md ====================
|
|
411
412
|
# Story: {{Story Title}}
|
|
412
413
|
|
|
413
414
|
**Epic:** {{Epic Name}}
|
|
@@ -643,9 +644,9 @@ class {{ClassName}} extends {{PhaseClass}} {
|
|
|
643
644
|
|
|
644
645
|
- {{future_enhancement_1}}
|
|
645
646
|
- {{future_optimization_1}}
|
|
646
|
-
==================== END: templates
|
|
647
|
+
==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.md ====================
|
|
647
648
|
|
|
648
|
-
==================== START: checklists
|
|
649
|
+
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
|
649
650
|
# Game Development Story Definition of Done Checklist
|
|
650
651
|
|
|
651
652
|
## Story Completeness
|
|
@@ -806,4 +807,4 @@ class {{ClassName}} extends {{PhaseClass}} {
|
|
|
806
807
|
|
|
807
808
|
**Additional Notes:**
|
|
808
809
|
_Any specific concerns, recommendations, or clarifications needed before development begins._
|
|
809
|
-
==================== END: checklists
|
|
810
|
+
==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|