bmad-method 4.5.0 → 4.6.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/CHANGELOG.md +19 -0
- package/bmad-core/agents/bmad-orchestrator.md +55 -66
- package/bmad-core/agents/pm.md +0 -1
- package/bmad-core/tasks/doc-migration-task.md +9 -9
- package/bmad-core/tasks/index-docs.md +3 -7
- package/bmad-core/templates/front-end-spec-tmpl.md +1 -1
- package/bmad-core/templates/fullstack-architecture-tmpl.md +60 -60
- package/bmad-core/templates/prd-tmpl.md +2 -2
- package/bmad-core/workflows/brownfield-fullstack.yml +19 -58
- package/bmad-core/workflows/brownfield-service.yml +19 -58
- package/bmad-core/workflows/brownfield-ui.yml +20 -59
- package/bmad-core/workflows/greenfield-fullstack.yml +31 -77
- package/bmad-core/workflows/greenfield-service.yml +22 -68
- package/bmad-core/workflows/greenfield-ui.yml +30 -76
- package/dist/agents/architect.txt +60 -60
- package/dist/agents/bmad-master.txt +66 -70
- package/dist/agents/bmad-orchestrator.txt +55 -66
- package/dist/agents/pm.txt +2 -467
- package/dist/agents/ux-expert.txt +1 -1
- package/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt +55 -66
- package/dist/expansion-packs/expansion-creator/agents/bmad-the-creator.txt +39 -32
- package/dist/teams/team-all.txt +368 -1099
- package/dist/teams/team-fullstack.txt +286 -1017
- package/dist/teams/team-ide-minimal.txt +55 -66
- package/dist/teams/team-no-ui.txt +224 -785
- package/docs/claude-code-guide.md +6 -4
- package/docs/cursor-guide.md +8 -4
- package/docs/roo-code-guide.md +6 -4
- package/docs/versioning-and-releases.md +6 -6
- package/docs/windsurf-guide.md +6 -4
- package/expansion-packs/expansion-creator/tasks/generate-expansion-pack.md +17 -13
- package/package.json +1 -1
- package/tools/installer/package.json +1 -1
- package/bmad-core/templates/simple-project-prd-tmpl.md +0 -461
|
@@ -6,9 +6,11 @@ This guide walks you through the complete BMAD workflow using Claude Code as you
|
|
|
6
6
|
|
|
7
7
|
1. Navigate to your project directory
|
|
8
8
|
2. Run the BMAD installer:
|
|
9
|
+
|
|
9
10
|
```bash
|
|
10
11
|
npx bmad-method install
|
|
11
12
|
```
|
|
13
|
+
|
|
12
14
|
3. When prompted:
|
|
13
15
|
- **Installation Type**: Choose "Complete installation (recommended)"
|
|
14
16
|
- **IDE**: Select "Claude Code"
|
|
@@ -17,11 +19,11 @@ This creates a `.bmad-core` folder with all agents and a `.claude/commands` fold
|
|
|
17
19
|
|
|
18
20
|
## Step 2: Set Up Team Fullstack in Gemini
|
|
19
21
|
|
|
20
|
-
For ideation and planning, use Google's Gemini with the team-fullstack configuration:
|
|
22
|
+
For ideation and planning, use Google's Gemini Custom Gem with the team-fullstack configuration:
|
|
21
23
|
|
|
22
|
-
1. Open [Google
|
|
23
|
-
2. Create a new
|
|
24
|
-
3. Copy the contents of
|
|
24
|
+
1. Open [Google gems](https://gemini.google.com/gems/view)
|
|
25
|
+
2. Create a new Gem - give it a title and description
|
|
26
|
+
3. Copy the contents of `.<install location>/web-bundles/teams/team-fullstack.txt`
|
|
25
27
|
4. Paste this content into Gemini to set up the team
|
|
26
28
|
|
|
27
29
|
### Gemini Planning Phase
|
package/docs/cursor-guide.md
CHANGED
|
@@ -6,9 +6,11 @@ This guide walks you through the complete BMAD workflow using Cursor as your AI-
|
|
|
6
6
|
|
|
7
7
|
1. Navigate to your project directory
|
|
8
8
|
2. Run the BMAD installer:
|
|
9
|
+
|
|
9
10
|
```bash
|
|
10
11
|
npx bmad-method install
|
|
11
12
|
```
|
|
13
|
+
|
|
12
14
|
3. When prompted:
|
|
13
15
|
- **Installation Type**: Choose "Complete installation (recommended)"
|
|
14
16
|
- **IDE**: Select "Cursor"
|
|
@@ -17,11 +19,11 @@ This creates a `.bmad-core` folder with all agents and a `.cursor/rules` folder
|
|
|
17
19
|
|
|
18
20
|
## Step 2: Set Up Team Fullstack in Gemini
|
|
19
21
|
|
|
20
|
-
For ideation and planning, use Google's Gemini with the team-fullstack configuration:
|
|
22
|
+
For ideation and planning, use Google's Gemini Custom Gem with the team-fullstack configuration:
|
|
21
23
|
|
|
22
|
-
1. Open [Google
|
|
23
|
-
2. Create a new
|
|
24
|
-
3. Copy the contents of
|
|
24
|
+
1. Open [Google gems](https://gemini.google.com/gems/view)
|
|
25
|
+
2. Create a new Gem - give it a title and description
|
|
26
|
+
3. Copy the contents of `.<install location>/web-bundles/teams/team-fullstack.txt`
|
|
25
27
|
4. Paste this content into Gemini to set up the team
|
|
26
28
|
|
|
27
29
|
### Gemini Planning Phase
|
|
@@ -101,6 +103,8 @@ All BMAD agents are available as Cursor rules (use `@` prefix):
|
|
|
101
103
|
- `@po` - Product owner for prioritization
|
|
102
104
|
- `@ux-expert` - UX specialist for design
|
|
103
105
|
|
|
106
|
+
Alternatively, and more performance - you can copy the contents of an agent file into a custom mode - see the cursor docs on how to use custom agents.
|
|
107
|
+
|
|
104
108
|
## Cursor-Specific Features
|
|
105
109
|
|
|
106
110
|
- **Agent rules are stored in**: `.cursor/rules/` as `.mdc` files
|
package/docs/roo-code-guide.md
CHANGED
|
@@ -6,9 +6,11 @@ This guide walks you through the complete BMAD workflow using Roo Code as your A
|
|
|
6
6
|
|
|
7
7
|
1. Navigate to your project directory
|
|
8
8
|
2. Run the BMAD installer:
|
|
9
|
+
|
|
9
10
|
```bash
|
|
10
11
|
npx bmad-method install
|
|
11
12
|
```
|
|
13
|
+
|
|
12
14
|
3. When prompted:
|
|
13
15
|
- **Installation Type**: Choose "Complete installation (recommended)"
|
|
14
16
|
- **IDE**: Select "Roo Code"
|
|
@@ -17,11 +19,11 @@ This creates a `.bmad-core` folder with all agents and a `.roomodes` file (in th
|
|
|
17
19
|
|
|
18
20
|
## Step 2: Set Up Team Fullstack in Gemini
|
|
19
21
|
|
|
20
|
-
For ideation and planning, use Google's Gemini with the team-fullstack configuration:
|
|
22
|
+
For ideation and planning, use Google's Gemini Custom Gem with the team-fullstack configuration:
|
|
21
23
|
|
|
22
|
-
1. Open [Google
|
|
23
|
-
2. Create a new
|
|
24
|
-
3. Copy the contents of
|
|
24
|
+
1. Open [Google gems](https://gemini.google.com/gems/view)
|
|
25
|
+
2. Create a new Gem - give it a title and description
|
|
26
|
+
3. Copy the contents of `.<install location>/web-bundles/teams/team-fullstack.txt`
|
|
25
27
|
4. Paste this content into Gemini to set up the team
|
|
26
28
|
|
|
27
29
|
### Gemini Planning Phase
|
|
@@ -8,11 +8,11 @@ The easiest way to release new versions is through **automatic semantic releases
|
|
|
8
8
|
|
|
9
9
|
Use these prefixes to control what type of release happens:
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
```bash
|
|
12
12
|
fix: resolve CLI argument parsing bug # → patch release (4.1.0 → 4.1.1)
|
|
13
13
|
feat: add new agent orchestration mode # → minor release (4.1.0 → 4.2.0)
|
|
14
14
|
feat!: redesign CLI interface # → major release (4.1.0 → 5.0.0)
|
|
15
|
-
```
|
|
15
|
+
```
|
|
16
16
|
|
|
17
17
|
### What Happens Automatically
|
|
18
18
|
|
|
@@ -35,24 +35,24 @@ git push
|
|
|
35
35
|
|
|
36
36
|
# That's it! Release happens automatically 🎉
|
|
37
37
|
# Users can now run: npx bmad-method (and get the new version)
|
|
38
|
-
|
|
38
|
+
```
|
|
39
39
|
|
|
40
40
|
### Commits That DON'T Trigger Releases
|
|
41
41
|
|
|
42
42
|
These commit types won't create releases (use them for maintenance):
|
|
43
43
|
|
|
44
|
-
|
|
44
|
+
```bash
|
|
45
45
|
chore: update dependencies # No release
|
|
46
46
|
docs: fix typo in readme # No release
|
|
47
47
|
style: format code # No release
|
|
48
48
|
test: add unit tests # No release
|
|
49
|
-
```
|
|
49
|
+
```
|
|
50
50
|
|
|
51
51
|
### Test Your Setup
|
|
52
52
|
|
|
53
53
|
```bash
|
|
54
54
|
npm run release:test # Safe to run locally - tests the config
|
|
55
|
-
|
|
55
|
+
```
|
|
56
56
|
|
|
57
57
|
---
|
|
58
58
|
|
package/docs/windsurf-guide.md
CHANGED
|
@@ -6,9 +6,11 @@ This guide walks you through the complete BMAD workflow using Windsurf as your A
|
|
|
6
6
|
|
|
7
7
|
1. Navigate to your project directory
|
|
8
8
|
2. Run the BMAD installer:
|
|
9
|
+
|
|
9
10
|
```bash
|
|
10
11
|
npx bmad-method install
|
|
11
12
|
```
|
|
13
|
+
|
|
12
14
|
3. When prompted:
|
|
13
15
|
- **Installation Type**: Choose "Complete installation (recommended)"
|
|
14
16
|
- **IDE**: Select "Windsurf"
|
|
@@ -17,11 +19,11 @@ This creates a `.bmad-core` folder with all agents and a `.windsurf/rules` folde
|
|
|
17
19
|
|
|
18
20
|
## Step 2: Set Up Team Fullstack in Gemini
|
|
19
21
|
|
|
20
|
-
For ideation and planning, use Google's Gemini with the team-fullstack configuration:
|
|
22
|
+
For ideation and planning, use Google's Gemini Custom Gem with the team-fullstack configuration:
|
|
21
23
|
|
|
22
|
-
1. Open [Google
|
|
23
|
-
2. Create a new
|
|
24
|
-
3. Copy the contents of
|
|
24
|
+
1. Open [Google gems](https://gemini.google.com/gems/view)
|
|
25
|
+
2. Create a new Gem - give it a title and description
|
|
26
|
+
3. Copy the contents of `.<install location>/web-bundles/teams/team-fullstack.txt`
|
|
25
27
|
4. Paste this content into Gemini to set up the team
|
|
26
28
|
|
|
27
29
|
### Gemini Planning Phase
|
|
@@ -70,7 +70,7 @@ IMPORTANT: STOP HERE AND CREATE PLAN FIRST
|
|
|
70
70
|
|
|
71
71
|
Create `expansion-packs/{pack-name}/plan.md` with:
|
|
72
72
|
|
|
73
|
-
|
|
73
|
+
```markdown
|
|
74
74
|
# {Pack Name} Expansion Pack Plan
|
|
75
75
|
|
|
76
76
|
## Overview
|
|
@@ -149,8 +149,7 @@ Create `expansion-packs/{pack-name}/plan.md` with:
|
|
|
149
149
|
## Approval
|
|
150
150
|
|
|
151
151
|
User approval received: [ ] Yes
|
|
152
|
-
|
|
153
|
-
```text
|
|
152
|
+
```
|
|
154
153
|
|
|
155
154
|
Important: Wait for user approval before proceeding to Phase 2
|
|
156
155
|
|
|
@@ -281,8 +280,8 @@ For each checklist, implement comprehensive validation frameworks:
|
|
|
281
280
|
IMPORTANT: Only proceed after plan.md is approved
|
|
282
281
|
|
|
283
282
|
#### 3.1 Create Directory Structure
|
|
283
|
+
|
|
284
284
|
```
|
|
285
|
-
````
|
|
286
285
|
|
|
287
286
|
expansion-packs/
|
|
288
287
|
└── {pack-name}/
|
|
@@ -312,7 +311,7 @@ expansion-packs/
|
|
|
312
311
|
└── agent-teams/
|
|
313
312
|
└── {domain}-team.yml (REQUIRED if multiple agents)
|
|
314
313
|
|
|
315
|
-
|
|
314
|
+
```
|
|
316
315
|
|
|
317
316
|
#### 3.2 Create Manifest
|
|
318
317
|
|
|
@@ -415,7 +414,7 @@ post_install_message: |
|
|
|
415
414
|
- Domain best practices and terminology
|
|
416
415
|
- Quality standards and validation criteria
|
|
417
416
|
- Workflow orchestration with handoff protocols
|
|
418
|
-
|
|
417
|
+
```
|
|
419
418
|
|
|
420
419
|
### Phase 4: Content Creation
|
|
421
420
|
|
|
@@ -439,7 +438,7 @@ IMPORTANT: Work through plan.md checklist systematically!
|
|
|
439
438
|
|
|
440
439
|
Before proceeding, copy these essential files from bmad-core:
|
|
441
440
|
|
|
442
|
-
|
|
441
|
+
```bash
|
|
443
442
|
# Copy core task utilities
|
|
444
443
|
cp bmad-core/tasks/create-doc.md expansion-packs/{pack-name}/tasks/
|
|
445
444
|
cp bmad-core/tasks/execute-checklist.md expansion-packs/{pack-name}/tasks/
|
|
@@ -448,7 +447,7 @@ cp bmad-core/tasks/execute-checklist.md expansion-packs/{pack-name}/tasks/
|
|
|
448
447
|
mkdir -p expansion-packs/{pack-name}/utils
|
|
449
448
|
cp bmad-core/utils/template-format.md expansion-packs/{pack-name}/utils/
|
|
450
449
|
cp bmad-core/utils/workflow-management.md expansion-packs/{pack-name}/utils/
|
|
451
|
-
```
|
|
450
|
+
```
|
|
452
451
|
|
|
453
452
|
**Step 3: Technical Implementation**
|
|
454
453
|
|
|
@@ -488,7 +487,7 @@ cp bmad-core/utils/workflow-management.md expansion-packs/{pack-name}/utils/
|
|
|
488
487
|
tasks: {required task list}
|
|
489
488
|
templates: {required template list}
|
|
490
489
|
checklists: {quality checklist list}
|
|
491
|
-
|
|
490
|
+
```
|
|
492
491
|
|
|
493
492
|
**Step 4: Workflow and Team Integration**
|
|
494
493
|
|
|
@@ -698,10 +697,10 @@ _{Professional background and expertise}_
|
|
|
698
697
|
- `{file2}.{ext}` - {description}
|
|
699
698
|
|
|
700
699
|
2. **Launch Orchestrator**:
|
|
700
|
+
|
|
701
701
|
```bash
|
|
702
702
|
npm run agent {pack-name}-orchestrator
|
|
703
703
|
```
|
|
704
|
-
````
|
|
705
704
|
|
|
706
705
|
3. **Follow Numbered Options**: {Character Name} will present numbered choices for each decision
|
|
707
706
|
|
|
@@ -731,14 +730,12 @@ _{Professional background and expertise}_
|
|
|
731
730
|
### Knowledge Base
|
|
732
731
|
|
|
733
732
|
[Embedded domain expertise]
|
|
734
|
-
|
|
735
733
|
````
|
|
736
734
|
|
|
737
735
|
#### 6.3 Advanced Data File Documentation with Validation
|
|
738
736
|
|
|
739
737
|
For each required data file, provide comprehensive guidance:
|
|
740
738
|
|
|
741
|
-
```markdown
|
|
742
739
|
## Required User Data Files
|
|
743
740
|
|
|
744
741
|
### {filename}.{ext}
|
|
@@ -748,7 +745,6 @@ For each required data file, provide comprehensive guidance:
|
|
|
748
745
|
- **Location**: Place in `bmad-core/data/`
|
|
749
746
|
- **Validation**: {how agents will verify the file is correct}
|
|
750
747
|
- **Example Structure**:
|
|
751
|
-
````
|
|
752
748
|
|
|
753
749
|
{sample content showing exact format}
|
|
754
750
|
|
|
@@ -1024,3 +1020,11 @@ Embedded knowledge (automatic):
|
|
|
1024
1020
|
- [ ] Template conditional content tested with different scenarios
|
|
1025
1021
|
- [ ] Workflow decision trees validated with sample use cases
|
|
1026
1022
|
- [ ] Character interactions tested for consistency and professional authenticity
|
|
1023
|
+
|
|
1024
|
+
```
|
|
1025
|
+
|
|
1026
|
+
```
|
|
1027
|
+
|
|
1028
|
+
```
|
|
1029
|
+
|
|
1030
|
+
```
|
package/package.json
CHANGED