bmad-method 4.30.3 ā 4.31.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 +20 -0
- package/CONTRIBUTING.md +1 -1
- package/README.md +8 -9
- package/bmad-core/agents/analyst.md +6 -6
- package/bmad-core/agents/architect.md +8 -3
- package/bmad-core/agents/bmad-master.md +2 -1
- package/bmad-core/agents/pm.md +7 -2
- package/bmad-core/agents/po.md +2 -5
- package/bmad-core/agents/qa.md +0 -1
- package/bmad-core/agents/sm.md +3 -3
- package/bmad-core/agents/ux-expert.md +2 -5
- package/bmad-core/user-guide.md +250 -0
- package/docs/how-to-contribute-with-pull-requests.md +2 -2
- package/package.json +4 -3
- package/tools/installer/lib/installer.js +4 -0
- package/tools/installer/package.json +1 -1
- package/docs/agentic-tools/claude-code-guide.md +0 -19
- package/docs/agentic-tools/cline-guide.md +0 -16
- package/docs/agentic-tools/cursor-guide.md +0 -14
- package/docs/agentic-tools/gemini-cli-guide.md +0 -31
- package/docs/agentic-tools/github-copilot-guide.md +0 -42
- package/docs/agentic-tools/roo-code-guide.md +0 -15
- package/docs/agentic-tools/trae-guide.md +0 -14
- package/docs/agentic-tools/windsurf-guide.md +0 -14
- package/docs/bmad-workflow-guide.md +0 -166
- package/docs/user-guide.md +0 -1142
- /package/{docs ā bmad-core}/working-in-the-brownfield.md +0 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,23 @@
|
|
|
1
|
+
# [4.31.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.30.4...v4.31.0) (2025-07-20)
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
### Bug Fixes
|
|
5
|
+
|
|
6
|
+
* enhanced user guide with better diagrams ([c445962](https://github.com/bmadcode/BMAD-METHOD/commit/c445962f259cd7d84c47a896e7fda99e83a30c8d))
|
|
7
|
+
|
|
8
|
+
|
|
9
|
+
### Features
|
|
10
|
+
|
|
11
|
+
* Installation includes a getting started user guide with detailed mermaid diagram ([df57d77](https://github.com/bmadcode/BMAD-METHOD/commit/df57d772cac9f9010811e7e86a6433a0fe636a45))
|
|
12
|
+
|
|
13
|
+
## [4.30.4](https://github.com/bmadcode/BMAD-METHOD/compare/v4.30.3...v4.30.4) (2025-07-19)
|
|
14
|
+
|
|
15
|
+
|
|
16
|
+
### Bug Fixes
|
|
17
|
+
|
|
18
|
+
* docs ([8619006](https://github.com/bmadcode/BMAD-METHOD/commit/8619006c16731b99fa36b434d209a0c2caf2d998))
|
|
19
|
+
* lint fix ([49e4897](https://github.com/bmadcode/BMAD-METHOD/commit/49e489701e55feac481806740ea54bebef042fba))
|
|
20
|
+
|
|
1
21
|
## [4.30.3](https://github.com/bmadcode/BMAD-METHOD/compare/v4.30.2...v4.30.3) (2025-07-19)
|
|
2
22
|
|
|
3
23
|
|
package/CONTRIBUTING.md
CHANGED
|
@@ -8,7 +8,7 @@ Thank you for considering contributing to this project! This document outlines t
|
|
|
8
8
|
|
|
9
9
|
Also note, we use the discussions feature in GitHub to have a community to discuss potential ideas, uses, additions and enhancements.
|
|
10
10
|
|
|
11
|
-
š¬ **Discord Community**: Join our [Discord server](https://discord.gg/
|
|
11
|
+
š¬ **Discord Community**: Join our [Discord server](https://discord.gg/gk8jAdXWmj) for real-time discussions:
|
|
12
12
|
|
|
13
13
|
- **#general-dev** - Technical discussions, feature ideas, and development questions
|
|
14
14
|
- **#bugs-issues** - Bug reports and issue discussions
|
package/README.md
CHANGED
|
@@ -23,7 +23,7 @@ Foundations in Agentic Agile Driven Development, known as the Breakthrough Metho
|
|
|
23
23
|
|
|
24
24
|
This two-phase approach eliminates both **planning inconsistency** and **context loss** - the biggest problems in AI-assisted development. Your Dev agent opens a story file with complete understanding of what to build, how to build it, and why.
|
|
25
25
|
|
|
26
|
-
**š [See the complete workflow in the User Guide](
|
|
26
|
+
**š [See the complete workflow in the User Guide](bmad-core/user-guide.md)** - Planning phase, development cycle, and all agent roles
|
|
27
27
|
|
|
28
28
|
## Quick Navigation
|
|
29
29
|
|
|
@@ -31,21 +31,21 @@ This two-phase approach eliminates both **planning inconsistency** and **context
|
|
|
31
31
|
|
|
32
32
|
**Before diving in, review these critical workflow diagrams that explain how BMad works:**
|
|
33
33
|
|
|
34
|
-
1. **[Planning Workflow (Web UI)](
|
|
35
|
-
2. **[Core Development Cycle (IDE)](
|
|
34
|
+
1. **[Planning Workflow (Web UI)](bmad-core/user-guide.md#the-planning-workflow-web-ui)** - How to create PRD and Architecture documents
|
|
35
|
+
2. **[Core Development Cycle (IDE)](bmad-core/user-guide.md#the-core-development-cycle-ide)** - How SM, Dev, and QA agents collaborate through story files
|
|
36
36
|
|
|
37
37
|
> ā ļø **These diagrams explain 90% of BMad Method Agentic Agile flow confusion** - Understanding the PRD+Architecture creation and the SM/Dev/QA workflow and how agents pass notes through story files is essential - and also explains why this is NOT taskmaster or just a simple task runner!
|
|
38
38
|
|
|
39
39
|
### What would you like to do?
|
|
40
40
|
|
|
41
41
|
- **[Install and Build software with Full Stack Agile AI Team](#quick-start)** ā Quick Start Instruction
|
|
42
|
-
- **[Learn how to use BMad](
|
|
42
|
+
- **[Learn how to use BMad](bmad-core/user-guide.md)** ā Complete user guide and walkthrough
|
|
43
43
|
- **[See available AI agents](#available-agents)** ā Specialized roles for your team
|
|
44
44
|
- **[Explore non-technical uses](#-beyond-software-development---expansion-packs)** ā Creative writing, business, wellness, education
|
|
45
45
|
- **[Create my own AI agents](#creating-your-own-expansion-pack)** ā Build agents for your domain
|
|
46
46
|
- **[Browse ready-made expansion packs](expansion-packs/)** ā Game dev, DevOps, infrastructure and get inspired with ideas and examples
|
|
47
47
|
- **[Understand the architecture](docs/core-architecture.md)** ā Technical deep dive
|
|
48
|
-
- **[Join the community](https://discord.gg/
|
|
48
|
+
- **[Join the community](https://discord.gg/gk8jAdXWmj)** ā Get help and share ideas
|
|
49
49
|
|
|
50
50
|
## Important: Keep Your BMad Installation Updated
|
|
51
51
|
|
|
@@ -97,7 +97,7 @@ This single command handles:
|
|
|
97
97
|
3. **Upload & configure**: Upload the file and set instructions: "Your critical operating instructions are attached, do not break character as directed"
|
|
98
98
|
4. **Start Ideating and Planning**: Start chatting! Type `*help` to see available commands or pick an agent like `*analyst` to start right in on creating a brief.
|
|
99
99
|
5. **CRITICAL**: Talk to BMad Orchestrator in the web at ANY TIME (#bmad-orchestrator command) and ask it questions about how this all works!
|
|
100
|
-
6. **When to move to the IDE**: Once you have your PRD, Architecture, optional UX and Briefs - its time to switch over to the IDE to shard your docs, and start implementing the actual code! See the [User guide](
|
|
100
|
+
6. **When to move to the IDE**: Once you have your PRD, Architecture, optional UX and Briefs - its time to switch over to the IDE to shard your docs, and start implementing the actual code! See the [User guide](bmad-core/user-guide.md) for more details
|
|
101
101
|
|
|
102
102
|
### Alternative: Clone and Build
|
|
103
103
|
|
|
@@ -114,14 +114,13 @@ BMad's natural language framework works in ANY domain. Expansion packs provide s
|
|
|
114
114
|
|
|
115
115
|
### Essential Guides
|
|
116
116
|
|
|
117
|
-
- š **[User Guide](
|
|
117
|
+
- š **[User Guide](bmad-core/user-guide.md)** - Complete walkthrough from project inception to completion
|
|
118
118
|
- šļø **[Core Architecture](docs/core-architecture.md)** - Technical deep dive and system design
|
|
119
119
|
- š **[Expansion Packs Guide](docs/expansion-packs.md)** - Extend BMad to any domain beyond software development
|
|
120
|
-
- [IDE Specific Guides available in this folder](docs/agentic-tools/)
|
|
121
120
|
|
|
122
121
|
## Support
|
|
123
122
|
|
|
124
|
-
- š¬ [Discord Community](https://discord.gg/
|
|
123
|
+
- š¬ [Discord Community](https://discord.gg/gk8jAdXWmj)
|
|
125
124
|
- š [Issue Tracker](https://github.com/bmadcode/bmad-method/issues)
|
|
126
125
|
- š¬ [Discussions](https://github.com/bmadcode/bmad-method/discussions)
|
|
127
126
|
|
|
@@ -54,14 +54,14 @@ persona:
|
|
|
54
54
|
# All commands require * prefix when used (e.g., *help)
|
|
55
55
|
commands:
|
|
56
56
|
- help: Show numbered list of the following commands to allow selection
|
|
57
|
-
- create-
|
|
57
|
+
- create-project-brief: use task create-doc with project-brief-tmpl.yaml
|
|
58
|
+
- perform-market-research: use task create-doc with market-research-tmpl.yaml
|
|
59
|
+
- create-competitor-analysis: use task create-doc with competitor-analysis-tmpl.yaml
|
|
58
60
|
- yolo: Toggle Yolo Mode
|
|
59
|
-
- doc-out: Output full document to current destination file
|
|
60
|
-
-
|
|
61
|
-
-
|
|
62
|
-
- brainstorm {topic}: Facilitate structured brainstorming session
|
|
61
|
+
- doc-out: Output full document in progress to current destination file
|
|
62
|
+
- research-prompt {topic}: execute task create-deep-research-prompt.md
|
|
63
|
+
- brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
|
|
63
64
|
- elicit: run the task advanced-elicitation
|
|
64
|
-
- document-project: Analyze and document existing project structure comprehensively
|
|
65
65
|
- exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
|
|
66
66
|
dependencies:
|
|
67
67
|
tasks:
|
|
@@ -55,11 +55,16 @@ persona:
|
|
|
55
55
|
# All commands require * prefix when used (e.g., *help)
|
|
56
56
|
commands:
|
|
57
57
|
- help: Show numbered list of the following commands to allow selection
|
|
58
|
-
- create-
|
|
59
|
-
-
|
|
58
|
+
- create-full-stack-architecture: use create-doc with fullstack-architecture-tmpl.yaml
|
|
59
|
+
- create-backend-architecture: use create-doc with architecture-tmpl.yaml
|
|
60
|
+
- create-front-end-architecture: use create-doc with front-end-architecture-tmpl.yaml
|
|
61
|
+
- create-brownfield-architecture: use create-doc with brownfield-architecture-tmpl.yaml
|
|
60
62
|
- doc-out: Output full document to current destination file
|
|
63
|
+
- document-project: execute the task document-project.md
|
|
61
64
|
- execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
|
|
62
|
-
- research {topic}: execute task create-deep-research-prompt
|
|
65
|
+
- research {topic}: execute task create-deep-research-prompt
|
|
66
|
+
- shard-prd: run the task shard-doc.md for the provided architecture.md (ask if not found)
|
|
67
|
+
- yolo: Toggle Yolo Mode
|
|
63
68
|
- exit: Say goodbye as the Architect, and then abandon inhabiting this persona
|
|
64
69
|
dependencies:
|
|
65
70
|
tasks:
|
|
@@ -52,10 +52,11 @@ commands:
|
|
|
52
52
|
- kb: Toggle KB mode off (default) or on, when on will load and reference the {root}/data/bmad-kb.md and converse with the user answering his questions with this informational resource
|
|
53
53
|
- task {task}: Execute task, if not found or none specified, ONLY list available dependencies/tasks listed below
|
|
54
54
|
- create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
|
|
55
|
+
- doc-out: Output full document to current destination file
|
|
56
|
+
- document-project: execute the task document-project.md
|
|
55
57
|
- execute-checklist {checklist}: Run task execute-checklist (no checklist = ONLY show available checklists listed under dependencies/checklist below)
|
|
56
58
|
- shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
|
|
57
59
|
- yolo: Toggle Yolo Mode
|
|
58
|
-
- doc-out: Output full document to current destination file
|
|
59
60
|
- exit: Exit (confirm)
|
|
60
61
|
|
|
61
62
|
dependencies:
|
package/bmad-core/agents/pm.md
CHANGED
|
@@ -50,9 +50,14 @@ persona:
|
|
|
50
50
|
# All commands require * prefix when used (e.g., *help)
|
|
51
51
|
commands:
|
|
52
52
|
- help: Show numbered list of the following commands to allow selection
|
|
53
|
-
- create-
|
|
54
|
-
-
|
|
53
|
+
- create-prd: run task create-doc.md with template prd-tmpl.yaml
|
|
54
|
+
- create-brownfield-prd: run task create-doc.md with template brownfield-prd-tmpl.yaml
|
|
55
|
+
- create-epic: Create epic for brownfield projects (task brownfield-create-epic)
|
|
56
|
+
- create-story: Create user story from requirements (task brownfield-create-story)
|
|
55
57
|
- doc-out: Output full document to current destination file
|
|
58
|
+
- shard-prd: run the task shard-doc.md for the provided prd.md (ask if not found)
|
|
59
|
+
- correct-course: execute the correct-course task
|
|
60
|
+
- yolo: Toggle Yolo Mode
|
|
56
61
|
- exit: Exit (confirm)
|
|
57
62
|
dependencies:
|
|
58
63
|
tasks:
|
package/bmad-core/agents/po.md
CHANGED
|
@@ -53,23 +53,20 @@ persona:
|
|
|
53
53
|
# All commands require * prefix when used (e.g., *help)
|
|
54
54
|
commands:
|
|
55
55
|
- help: Show numbered list of the following commands to allow selection
|
|
56
|
-
-
|
|
57
|
-
- execute-checklist {checklist}: Run task execute-checklist (default->po-master-checklist)
|
|
56
|
+
- execute-checklist-po: Run task execute-checklist (checklist po-master-checklist)
|
|
58
57
|
- shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
|
|
59
58
|
- correct-course: execute the correct-course task
|
|
60
59
|
- create-epic: Create epic for brownfield projects (task brownfield-create-epic)
|
|
61
60
|
- create-story: Create user story from requirements (task brownfield-create-story)
|
|
62
|
-
- yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
|
|
63
61
|
- doc-out: Output full document to current destination file
|
|
64
62
|
- validate-story-draft {story}: run the task validate-next-story against the provided story file
|
|
63
|
+
- yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
|
|
65
64
|
- exit: Exit (confirm)
|
|
66
65
|
dependencies:
|
|
67
66
|
tasks:
|
|
68
67
|
- execute-checklist.md
|
|
69
68
|
- shard-doc.md
|
|
70
69
|
- correct-course.md
|
|
71
|
-
- brownfield-create-epic.md
|
|
72
|
-
- brownfield-create-story.md
|
|
73
70
|
- validate-next-story.md
|
|
74
71
|
templates:
|
|
75
72
|
- story-tmpl.yaml
|
package/bmad-core/agents/qa.md
CHANGED
|
@@ -58,7 +58,6 @@ story-file-permissions:
|
|
|
58
58
|
commands:
|
|
59
59
|
- help: Show numbered list of the following commands to allow selection
|
|
60
60
|
- review {story}: execute the task review-story for the highest sequence story in docs/stories unless another is specified - keep any specified technical-preferences in mind as needed
|
|
61
|
-
- create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
|
|
62
61
|
- exit: Say goodbye as the QA Engineer, and then abandon inhabiting this persona
|
|
63
62
|
dependencies:
|
|
64
63
|
tasks:
|
package/bmad-core/agents/sm.md
CHANGED
|
@@ -46,9 +46,9 @@ persona:
|
|
|
46
46
|
# All commands require * prefix when used (e.g., *help)
|
|
47
47
|
commands:
|
|
48
48
|
- help: Show numbered list of the following commands to allow selection
|
|
49
|
-
- draft: Execute task create-next-story
|
|
50
|
-
- correct-course: Execute task correct-course
|
|
51
|
-
- checklist
|
|
49
|
+
- draft: Execute task create-next-story.md
|
|
50
|
+
- correct-course: Execute task correct-course.md
|
|
51
|
+
- story-checklist: Execute task execute-checklist.md with checklist story-draft-checklist.md
|
|
52
52
|
- exit: Say goodbye as the Scrum Master, and then abandon inhabiting this persona
|
|
53
53
|
dependencies:
|
|
54
54
|
tasks:
|
|
@@ -51,15 +51,12 @@ persona:
|
|
|
51
51
|
# All commands require * prefix when used (e.g., *help)
|
|
52
52
|
commands:
|
|
53
53
|
- help: Show numbered list of the following commands to allow selection
|
|
54
|
-
- create-
|
|
55
|
-
- generate-ui-prompt:
|
|
56
|
-
- research {topic}: Execute create-deep-research-prompt task to generate a prompt to init UX deep research
|
|
57
|
-
- execute-checklist {checklist}: Run task execute-checklist (default->po-master-checklist)
|
|
54
|
+
- create-front-end-spec: run task create-doc.md with template front-end-spec-tmpl.yaml
|
|
55
|
+
- generate-ui-prompt: Run task generate-ai-frontend-prompt.md
|
|
58
56
|
- exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
|
|
59
57
|
dependencies:
|
|
60
58
|
tasks:
|
|
61
59
|
- generate-ai-frontend-prompt.md
|
|
62
|
-
- create-deep-research-prompt.md
|
|
63
60
|
- create-doc.md
|
|
64
61
|
- execute-checklist.md
|
|
65
62
|
templates:
|
|
@@ -0,0 +1,250 @@
|
|
|
1
|
+
# BMad-Method BMAd Code User Guide
|
|
2
|
+
|
|
3
|
+
This guide will help you understand and effectively use the BMad Method for agile ai driven planning and development.
|
|
4
|
+
|
|
5
|
+
## The BMad Plan and Execute Workflow
|
|
6
|
+
|
|
7
|
+
First, here is the full standard Greenfield Planning + Execution Workflow. Brownfield is very similar, but its suggested to understand this greenfield first, even if on a simple project before tackling a brownfield project. The BMad Method needs to be installed to the root of your new project folder. For the planning phase, you can optionally perform it with powerful web agents, potentially resulting in higher quality results at a fraction of the cost it would take to complete if providing your own API key or credits in some Agentic tools. For planning, powerful thinking models and larger context - along with working as a partner with the agents will net the best results.
|
|
8
|
+
|
|
9
|
+
If you are going to use the BMad Method with a Brownfield project (an existing project), review [Working in the Brownfield](./working-in-the-brownfield.md)
|
|
10
|
+
|
|
11
|
+
If you do not see the diagrams that following rendering, you can install Markdown All in One along with the Markdown Preview Mermaid Support plugins to VSCode (or one of the forked clones). With these plugin's, if you right click on the tab when open, there should be a Open Preview option, or check the IDE documentation.
|
|
12
|
+
|
|
13
|
+
### The Planning Workflow (Web UI or Powerful IDE Agents)
|
|
14
|
+
|
|
15
|
+
Before development begins, BMad follows a structured planning workflow that's ideally done in web UI for cost efficiency:
|
|
16
|
+
|
|
17
|
+
```mermaid
|
|
18
|
+
graph TD
|
|
19
|
+
A["Start: Project Idea"] --> B{"Optional: Analyst Research"}
|
|
20
|
+
B -->|Yes| C["Analyst: Brainstorming (Optional)"]
|
|
21
|
+
B -->|No| G{"Project Brief Available?"}
|
|
22
|
+
C --> C2["Analyst: Market Research (Optional)"]
|
|
23
|
+
C2 --> C3["Analyst: Competitor Analysis (Optional)"]
|
|
24
|
+
C3 --> D["Analyst: Create Project Brief"]
|
|
25
|
+
D --> G
|
|
26
|
+
G -->|Yes| E["PM: Create PRD from Brief (Fast Track)"]
|
|
27
|
+
G -->|No| E2["PM: Interactive PRD Creation (More Questions)"]
|
|
28
|
+
E --> F["PRD Created with FRs, NFRs, Epics & Stories"]
|
|
29
|
+
E2 --> F
|
|
30
|
+
F --> F2{"UX Required?"}
|
|
31
|
+
F2 -->|Yes| F3["UX Expert: Create Front End Spec"]
|
|
32
|
+
F2 -->|No| H["Architect: Create Architecture from PRD"]
|
|
33
|
+
F3 --> F4["UX Expert: Generate UI Prompt for Lovable/V0 (Optional)"]
|
|
34
|
+
F4 --> H2["Architect: Create Architecture from PRD + UX Spec"]
|
|
35
|
+
H --> I["PO: Run Master Checklist"]
|
|
36
|
+
H2 --> I
|
|
37
|
+
I --> J{"Documents Aligned?"}
|
|
38
|
+
J -->|Yes| K["Planning Complete"]
|
|
39
|
+
J -->|No| L["PO: Update Epics & Stories"]
|
|
40
|
+
L --> M["Update PRD/Architecture as needed"]
|
|
41
|
+
M --> I
|
|
42
|
+
K --> N["š Switch to IDE (If in a Web Agent Platform)"]
|
|
43
|
+
N --> O["PO: Shard Documents"]
|
|
44
|
+
O --> P["Ready for SM/Dev Cycle"]
|
|
45
|
+
|
|
46
|
+
style A fill:#f5f5f5,color:#000
|
|
47
|
+
style B fill:#e3f2fd,color:#000
|
|
48
|
+
style C fill:#e8f5e9,color:#000
|
|
49
|
+
style C2 fill:#e8f5e9,color:#000
|
|
50
|
+
style C3 fill:#e8f5e9,color:#000
|
|
51
|
+
style D fill:#e8f5e9,color:#000
|
|
52
|
+
style E fill:#fff3e0,color:#000
|
|
53
|
+
style E2 fill:#fff3e0,color:#000
|
|
54
|
+
style F fill:#fff3e0,color:#000
|
|
55
|
+
style F2 fill:#e3f2fd,color:#000
|
|
56
|
+
style F3 fill:#e1f5fe,color:#000
|
|
57
|
+
style F4 fill:#e1f5fe,color:#000
|
|
58
|
+
style G fill:#e3f2fd,color:#000
|
|
59
|
+
style H fill:#f3e5f5,color:#000
|
|
60
|
+
style H2 fill:#f3e5f5,color:#000
|
|
61
|
+
style I fill:#f9ab00,color:#fff
|
|
62
|
+
style J fill:#e3f2fd,color:#000
|
|
63
|
+
style K fill:#34a853,color:#fff
|
|
64
|
+
style L fill:#f9ab00,color:#fff
|
|
65
|
+
style M fill:#fff3e0,color:#000
|
|
66
|
+
style N fill:#1a73e8,color:#fff
|
|
67
|
+
style O fill:#f9ab00,color:#fff
|
|
68
|
+
style P fill:#34a853,color:#fff
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
#### Web UI to IDE Transition
|
|
72
|
+
|
|
73
|
+
**Critical Transition Point**: Once the PO confirms document alignment, you must switch from web UI to IDE to begin the development workflow:
|
|
74
|
+
|
|
75
|
+
1. **Copy Documents to Project**: Ensure `docs/prd.md` and `docs/architecture.md` are in your project's docs folder (or a custom location you can specify during installation)
|
|
76
|
+
2. **Switch to IDE**: Open your project in your preferred Agentic IDE
|
|
77
|
+
3. **Document Sharding**: Use the PO agent to shard the PRD and then the Architecture
|
|
78
|
+
4. **Begin Development**: Start the Core Development Cycle that follows
|
|
79
|
+
|
|
80
|
+
### The Core Development Cycle (IDE)
|
|
81
|
+
|
|
82
|
+
Once planning is complete and documents are sharded, BMad follows a structured development workflow:
|
|
83
|
+
|
|
84
|
+
```mermaid
|
|
85
|
+
graph TD
|
|
86
|
+
A["Development Phase Start"] --> B["SM: Reviews Previous Story Dev/QA Notes"]
|
|
87
|
+
B --> B2["SM: Drafts Next Story from Sharded Epic + Architecture"]
|
|
88
|
+
B2 --> B3{"QA: Review Story Draft (Optional)"}
|
|
89
|
+
B3 -->|Review Requested| B4["QA: Review Story Against Artifacts"]
|
|
90
|
+
B3 -->|Skip Review| C{"User Approval"}
|
|
91
|
+
B4 --> C
|
|
92
|
+
C -->|Approved| D["Dev: Sequential Task Execution"]
|
|
93
|
+
C -->|Needs Changes| B2
|
|
94
|
+
D --> E["Dev: Implement Tasks + Tests"]
|
|
95
|
+
E --> F["Dev: Run All Validations"]
|
|
96
|
+
F --> G["Dev: Mark Ready for Review + Add Notes"]
|
|
97
|
+
G --> H{"User Verification"}
|
|
98
|
+
H -->|Request QA Review| I["QA: Senior Dev Review + Active Refactoring"]
|
|
99
|
+
H -->|Approve Without QA| M["IMPORTANT: Verify All Regression Tests and Linting are Passing"]
|
|
100
|
+
I --> J["QA: Review, Refactor Code, Add Tests, Document Notes"]
|
|
101
|
+
J --> L{"QA Decision"}
|
|
102
|
+
L -->|Needs Dev Work| D
|
|
103
|
+
L -->|Approved| M
|
|
104
|
+
H -->|Needs Fixes| D
|
|
105
|
+
M --> N["IMPORTANT: COMMIT YOUR CHANGES BEFORE PROCEEDING!"]
|
|
106
|
+
N --> K["Mark Story as Done"]
|
|
107
|
+
K --> B
|
|
108
|
+
|
|
109
|
+
style A fill:#f5f5f5,color:#000
|
|
110
|
+
style B fill:#e8f5e9,color:#000
|
|
111
|
+
style B2 fill:#e8f5e9,color:#000
|
|
112
|
+
style B3 fill:#e3f2fd,color:#000
|
|
113
|
+
style B4 fill:#fce4ec,color:#000
|
|
114
|
+
style C fill:#e3f2fd,color:#000
|
|
115
|
+
style D fill:#e3f2fd,color:#000
|
|
116
|
+
style E fill:#e3f2fd,color:#000
|
|
117
|
+
style F fill:#e3f2fd,color:#000
|
|
118
|
+
style G fill:#e3f2fd,color:#000
|
|
119
|
+
style H fill:#e3f2fd,color:#000
|
|
120
|
+
style I fill:#f9ab00,color:#fff
|
|
121
|
+
style J fill:#ffd54f,color:#000
|
|
122
|
+
style K fill:#34a853,color:#fff
|
|
123
|
+
style L fill:#e3f2fd,color:#000
|
|
124
|
+
style M fill:#ff5722,color:#fff
|
|
125
|
+
style N fill:#d32f2f,color:#fff
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
## Installation
|
|
129
|
+
|
|
130
|
+
### Optional
|
|
131
|
+
|
|
132
|
+
If you want to do the planning in the Web with Claude (Sonnet 4 or Opus), Gemini Gem (2.5 Pro), or Custom GPT's:
|
|
133
|
+
|
|
134
|
+
1. Navigate to `dist/teams/`
|
|
135
|
+
2. Copy `team-fullstack.txt` content
|
|
136
|
+
3. Create new Gemini Gem or CustomGPT
|
|
137
|
+
4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
|
|
138
|
+
5. Type `/help` to see available commands
|
|
139
|
+
|
|
140
|
+
### IDE Project Setup
|
|
141
|
+
|
|
142
|
+
```bash
|
|
143
|
+
# Interactive installation (recommended)
|
|
144
|
+
npx bmad-method install
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
## Special Agents
|
|
148
|
+
|
|
149
|
+
There are two bmad agents - in the future they will be consolidated into the single bmad-master.
|
|
150
|
+
|
|
151
|
+
### BMad-Master
|
|
152
|
+
|
|
153
|
+
This agent can do any task or command that all other agents can do, aside from actual story implementation. Additionally, this agent can help explain the BMad Method when in the web by accessing the knowledge base and explaining anything to you about the process.
|
|
154
|
+
|
|
155
|
+
If you dont want to bother switching between different agents aside from the dev, this is the agent for you.
|
|
156
|
+
|
|
157
|
+
### BMad-Orchestrator
|
|
158
|
+
|
|
159
|
+
This agent should NOT be used within the IDE, it is a heavy weight special purpose agent that utilizes a lot of context and can morph into any other agent. This exists solely to facilitate the team's within the web bundles. If you use a web bundle you will be greeted by the BMad Orchestrator.
|
|
160
|
+
|
|
161
|
+
### How Agents Work
|
|
162
|
+
|
|
163
|
+
#### Dependencies System
|
|
164
|
+
|
|
165
|
+
Each agent has a YAML section that defines its dependencies:
|
|
166
|
+
|
|
167
|
+
```yaml
|
|
168
|
+
dependencies:
|
|
169
|
+
templates:
|
|
170
|
+
- prd-template.md
|
|
171
|
+
- user-story-template.md
|
|
172
|
+
tasks:
|
|
173
|
+
- create-doc.md
|
|
174
|
+
- shard-doc.md
|
|
175
|
+
data:
|
|
176
|
+
- bmad-kb.md
|
|
177
|
+
```
|
|
178
|
+
|
|
179
|
+
**Key Points:**
|
|
180
|
+
|
|
181
|
+
- Agents only load resources they need (lean context)
|
|
182
|
+
- Dependencies are automatically resolved during bundling
|
|
183
|
+
- Resources are shared across agents to maintain consistency
|
|
184
|
+
|
|
185
|
+
#### Agent Interaction
|
|
186
|
+
|
|
187
|
+
**In IDE:**
|
|
188
|
+
|
|
189
|
+
```bash
|
|
190
|
+
# Some Ide's, like Cursor or Windsurf for example, utilize manual rules so interaction is done with the '@' symbol
|
|
191
|
+
@pm Create a PRD for a task management app
|
|
192
|
+
@architect Design the system architecture
|
|
193
|
+
@dev Implement the user authentication
|
|
194
|
+
|
|
195
|
+
# Some, like Claude Code use slash commands instead
|
|
196
|
+
/pm Create user stories
|
|
197
|
+
/dev Fix the login bug
|
|
198
|
+
```
|
|
199
|
+
|
|
200
|
+
#### Interactive Modes
|
|
201
|
+
|
|
202
|
+
- **Incremental Mode**: Step-by-step with user input
|
|
203
|
+
- **YOLO Mode**: Rapid generation with minimal interaction
|
|
204
|
+
|
|
205
|
+
## IDE Integration
|
|
206
|
+
|
|
207
|
+
### IDE Best Practices
|
|
208
|
+
|
|
209
|
+
- **Context Management**: Keep relevant files only in context, keep files as lean and focused as necessary
|
|
210
|
+
- **Agent Selection**: Use appropriate agent for task
|
|
211
|
+
- **Iterative Development**: Work in small, focused tasks
|
|
212
|
+
- **File Organization**: Maintain clean project structure
|
|
213
|
+
|
|
214
|
+
## Technical Preferences System
|
|
215
|
+
|
|
216
|
+
BMad includes a personalization system through the `technical-preferences.md` file located in `.bmad-core/data/` - this can help bias the PM and Architect to recommend your preferences for design patterns, technology selection, or anything else you would like to put in here.
|
|
217
|
+
|
|
218
|
+
### Using with Web Bundles
|
|
219
|
+
|
|
220
|
+
When creating custom web bundles or uploading to AI platforms, include your `technical-preferences.md` content to ensure agents have your preferences from the start of any conversation.
|
|
221
|
+
|
|
222
|
+
## Core Configuration
|
|
223
|
+
|
|
224
|
+
The `bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
|
|
225
|
+
|
|
226
|
+
### Developer Context Files
|
|
227
|
+
|
|
228
|
+
Define which files the dev agent should always load:
|
|
229
|
+
|
|
230
|
+
```yaml
|
|
231
|
+
devLoadAlwaysFiles:
|
|
232
|
+
- docs/architecture/coding-standards.md
|
|
233
|
+
- docs/architecture/tech-stack.md
|
|
234
|
+
- docs/architecture/project-structure.md
|
|
235
|
+
```
|
|
236
|
+
|
|
237
|
+
You will want to verify from sharding your architecture that these documents exist, that they are as lean as possible, and contain exactly the information you want your dev agent to ALWAYS load into it's context. These are the rules the agent will follow.
|
|
238
|
+
|
|
239
|
+
As your project grows and the code starts to build consistent patterns, coding standards should be reduced to just the items that the agent makes mistakes at still - must with the better models, they will look at surrounding code in files and not need a rule from that file to guide them.
|
|
240
|
+
|
|
241
|
+
## Getting Help
|
|
242
|
+
|
|
243
|
+
- **Discord Community**: [Join Discord](https://discord.gg/gk8jAdXWmj)
|
|
244
|
+
- **GitHub Issues**: [Report bugs](https://github.com/bmadcode/bmad-method/issues)
|
|
245
|
+
- **Documentation**: [Browse docs](https://github.com/bmadcode/bmad-method/docs)
|
|
246
|
+
- **YouTube**: [BMadCode Channel](https://www.youtube.com/@BMadCode)
|
|
247
|
+
|
|
248
|
+
## Conclusion
|
|
249
|
+
|
|
250
|
+
Remember: BMad is designed to enhance your development process, not replace your expertise. Use it as a powerful tool to accelerate your projects while maintaining control over design decisions and implementation details.
|
|
@@ -14,7 +14,7 @@ A pull request (PR) is how you propose changes to a project on GitHub. Think of
|
|
|
14
14
|
|
|
15
15
|
- **For bug fixes**: Create an issue using the [bug report template](https://github.com/bmadcode/bmad-method/issues/new?template=bug_report.md)
|
|
16
16
|
- **For new features**:
|
|
17
|
-
1. Discuss in Discord [#general-dev channel](https://discord.gg/
|
|
17
|
+
1. Discuss in Discord [#general-dev channel](https://discord.gg/gk8jAdXWmj)
|
|
18
18
|
2. Create an issue using the [feature request template](https://github.com/bmadcode/bmad-method/issues/new?template=feature_request.md)
|
|
19
19
|
- **For large changes**: Always open an issue first to discuss alignment
|
|
20
20
|
|
|
@@ -131,7 +131,7 @@ git push origin fix/typo-in-readme
|
|
|
131
131
|
|
|
132
132
|
## Need Help?
|
|
133
133
|
|
|
134
|
-
- š¬ Join our [Discord Community](https://discord.gg/
|
|
134
|
+
- š¬ Join our [Discord Community](https://discord.gg/gk8jAdXWmj) for real-time help:
|
|
135
135
|
- **#general-dev** - Technical questions and feature discussions
|
|
136
136
|
- **#bugs-issues** - Get help with bugs before filing issues
|
|
137
137
|
- š¬ Ask questions in [GitHub Discussions](https://github.com/bmadcode/bmad-method/discussions)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "bmad-method",
|
|
3
|
-
"version": "4.
|
|
3
|
+
"version": "4.31.0",
|
|
4
4
|
"description": "Breakthrough Method of Agile AI-driven Development",
|
|
5
5
|
"main": "tools/cli.js",
|
|
6
6
|
"bin": {
|
|
@@ -34,6 +34,7 @@
|
|
|
34
34
|
},
|
|
35
35
|
"dependencies": {
|
|
36
36
|
"@kayvan/markdown-tree-parser": "^1.5.0",
|
|
37
|
+
"bmad-method": "^4.30.3",
|
|
37
38
|
"chalk": "^4.1.2",
|
|
38
39
|
"commander": "^14.0.0",
|
|
39
40
|
"fs-extra": "^11.3.0",
|
|
@@ -61,12 +62,12 @@
|
|
|
61
62
|
"node": ">=20.0.0"
|
|
62
63
|
},
|
|
63
64
|
"devDependencies": {
|
|
65
|
+
"@semantic-release/changelog": "^6.0.3",
|
|
66
|
+
"@semantic-release/git": "^10.0.1",
|
|
64
67
|
"husky": "^9.1.7",
|
|
65
68
|
"lint-staged": "^16.1.1",
|
|
66
69
|
"prettier": "^3.5.3",
|
|
67
70
|
"semantic-release": "^22.0.0",
|
|
68
|
-
"@semantic-release/changelog": "^6.0.3",
|
|
69
|
-
"@semantic-release/git": "^10.0.1",
|
|
70
71
|
"yaml-lint": "^1.7.0"
|
|
71
72
|
},
|
|
72
73
|
"lint-staged": {
|
|
@@ -891,6 +891,10 @@ class Installer {
|
|
|
891
891
|
console.log(chalk.yellow.bold("\nā ļø IMPORTANT: Cursor Custom Modes Update Required"));
|
|
892
892
|
console.log(chalk.yellow("Since agents have been updated, you need to update any custom agent modes configured in the Cursor custom agent GUI per the Cursor docs."));
|
|
893
893
|
}
|
|
894
|
+
|
|
895
|
+
// Important notice to read the user guide
|
|
896
|
+
console.log(chalk.red.bold("\nš IMPORTANT: Please read the user guide installed at docs/user-guide.md"));
|
|
897
|
+
console.log(chalk.red("This guide contains essential information about the BMad workflow and how to use the agents effectively."));
|
|
894
898
|
}
|
|
895
899
|
|
|
896
900
|
// Legacy method for backward compatibility
|
|
@@ -1,19 +0,0 @@
|
|
|
1
|
-
# BMad Method Guide for Claude Code
|
|
2
|
-
|
|
3
|
-
For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.md).
|
|
4
|
-
|
|
5
|
-
## Installation
|
|
6
|
-
|
|
7
|
-
When running `npx bmad-method install`, select **Claude Code** as your IDE. This creates:
|
|
8
|
-
|
|
9
|
-
- `.bmad-core/` folder with all agents
|
|
10
|
-
- `.claude/commands/BMad` folder with agent command files (`.md`)
|
|
11
|
-
|
|
12
|
-
## Using BMad Agents in Claude Code
|
|
13
|
-
|
|
14
|
-
Type `/agent-name` in your chat to activate an agent.
|
|
15
|
-
|
|
16
|
-
## Tips for Claude Code Users
|
|
17
|
-
|
|
18
|
-
- Commands are auto-suggested as you type `/`
|
|
19
|
-
- More coming soon...
|
|
@@ -1,16 +0,0 @@
|
|
|
1
|
-
# BMad Method Guide for Cline (VS Code)
|
|
2
|
-
|
|
3
|
-
For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.md).
|
|
4
|
-
|
|
5
|
-
## Installation
|
|
6
|
-
|
|
7
|
-
When running `npx bmad-method install`, select **Cline** as your IDE. This creates:
|
|
8
|
-
|
|
9
|
-
- `.clinerules/` directory with numbered agent rule files (`.md`)
|
|
10
|
-
- Agents ordered by priority (bmad-master first)
|
|
11
|
-
|
|
12
|
-
## Using BMad Agents in Cline
|
|
13
|
-
|
|
14
|
-
1. **Open Cline panel** in VS Code
|
|
15
|
-
2. **Type `@agent-name`** in the chat (e.g., `@dev`, `@sm`, `@architect`)
|
|
16
|
-
3. The agent adopts that persona for the conversation
|
|
@@ -1,14 +0,0 @@
|
|
|
1
|
-
# BMad Method Guide for Cursor
|
|
2
|
-
|
|
3
|
-
For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.md).
|
|
4
|
-
|
|
5
|
-
## Installation
|
|
6
|
-
|
|
7
|
-
When running `npx bmad-method install`, select **Cursor** as your IDE. This creates:
|
|
8
|
-
|
|
9
|
-
- `.bmad-core/` folder with all agents
|
|
10
|
-
- `.cursor/rules/` folder with agent rule files (`.mdc`)
|
|
11
|
-
|
|
12
|
-
## Using BMad Agents in Cursor
|
|
13
|
-
|
|
14
|
-
Type `@agent-name` in chat (Ctrl+L / Cmd+L) to activate an agent. Make sure you select the icon that looks like a small ruler if presented with multiple options in the popup window.
|
|
@@ -1,31 +0,0 @@
|
|
|
1
|
-
# BMad Method Guide for Gemini CLI
|
|
2
|
-
|
|
3
|
-
For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.md).
|
|
4
|
-
|
|
5
|
-
## Installation
|
|
6
|
-
|
|
7
|
-
When running `npx bmad-method install`, select **Gemini CLI** as your IDE. This creates:
|
|
8
|
-
|
|
9
|
-
- `.gemini/bmad-method/` directory with all agent context in GEMINI.md file
|
|
10
|
-
|
|
11
|
-
## Using BMad Agents with Gemini CLI
|
|
12
|
-
|
|
13
|
-
Simply mention the agent in your prompt:
|
|
14
|
-
|
|
15
|
-
- "As \*dev, implement the login feature"
|
|
16
|
-
- "Acting as \*architect, review this system design"
|
|
17
|
-
- "\*sm, create the next story for our project"
|
|
18
|
-
|
|
19
|
-
The Gemini CLI automatically loads the appropriate agent context.
|
|
20
|
-
|
|
21
|
-
## Gemini CLI-Specific Features
|
|
22
|
-
|
|
23
|
-
- **Context files**: All agents loaded as context in `.gemini/bmad-method/GEMINI.md`
|
|
24
|
-
- **Automatic loading**: GEMINI.md ensures agents are always available
|
|
25
|
-
- **Natural language**: No special syntax needed, just mention the agent
|
|
26
|
-
|
|
27
|
-
## Tips for Gemini CLI Users
|
|
28
|
-
|
|
29
|
-
- Be explicit about which agent you're addressing
|
|
30
|
-
- You can switch agents mid-conversation by mentioning a different one
|
|
31
|
-
- The CLI maintains context across your session
|