bmad-method 6.2.3-next.16 → 6.2.3-next.18
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/.claude-plugin/marketplace.json +0 -2
- package/README.md +1 -1
- package/README_CN.md +1 -1
- package/package.json +1 -1
- package/src/bmm-skills/2-plan-workflows/bmad-create-ux-design/steps/step-13-responsive-accessibility.md +1 -1
- package/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-01-document-discovery.md +1 -1
- package/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-02-prd-analysis.md +1 -1
- package/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-03-epic-coverage-validation.md +1 -1
- package/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/workflow.md +1 -1
- package/src/bmm-skills/3-solutioning/bmad-create-epics-and-stories/workflow.md +1 -1
- package/src/bmm-skills/4-implementation/bmad-agent-dev/SKILL.md +4 -0
- package/src/bmm-skills/4-implementation/bmad-correct-course/checklist.md +2 -2
- package/src/bmm-skills/4-implementation/bmad-correct-course/workflow.md +8 -8
- package/src/bmm-skills/4-implementation/bmad-qa-generate-e2e-tests/checklist.md +1 -1
- package/src/bmm-skills/4-implementation/bmad-retrospective/workflow.md +134 -134
- package/src/bmm-skills/4-implementation/bmad-sprint-planning/sprint-status-template.yaml +1 -1
- package/src/bmm-skills/4-implementation/bmad-sprint-planning/workflow.md +3 -3
- package/src/bmm-skills/4-implementation/bmad-sprint-status/workflow.md +2 -2
- package/src/core-skills/bmad-party-mode/SKILL.md +2 -2
- package/src/bmm-skills/4-implementation/bmad-agent-qa/SKILL.md +0 -61
- package/src/bmm-skills/4-implementation/bmad-agent-qa/bmad-skill-manifest.yaml +0 -11
- package/src/bmm-skills/4-implementation/bmad-agent-sm/SKILL.md +0 -55
- package/src/bmm-skills/4-implementation/bmad-agent-sm/bmad-skill-manifest.yaml +0 -11
|
@@ -59,8 +59,6 @@
|
|
|
59
59
|
"./src/bmm-skills/3-solutioning/bmad-create-epics-and-stories",
|
|
60
60
|
"./src/bmm-skills/3-solutioning/bmad-generate-project-context",
|
|
61
61
|
"./src/bmm-skills/4-implementation/bmad-agent-dev",
|
|
62
|
-
"./src/bmm-skills/4-implementation/bmad-agent-sm",
|
|
63
|
-
"./src/bmm-skills/4-implementation/bmad-agent-qa",
|
|
64
62
|
"./src/bmm-skills/4-implementation/bmad-dev-story",
|
|
65
63
|
"./src/bmm-skills/4-implementation/bmad-quick-dev",
|
|
66
64
|
"./src/bmm-skills/4-implementation/bmad-sprint-planning",
|
package/README.md
CHANGED
|
@@ -16,7 +16,7 @@ Traditional AI tools do the thinking for you, producing average results. BMad ag
|
|
|
16
16
|
- **AI Intelligent Help** — Invoke the `bmad-help` skill anytime for guidance on what's next
|
|
17
17
|
- **Scale-Domain-Adaptive** — Automatically adjusts planning depth based on project complexity
|
|
18
18
|
- **Structured Workflows** — Grounded in agile best practices across analysis, planning, architecture, and implementation
|
|
19
|
-
- **Specialized Agents** — 12+ domain experts (PM, Architect, Developer, UX,
|
|
19
|
+
- **Specialized Agents** — 12+ domain experts (PM, Architect, Developer, UX, and more)
|
|
20
20
|
- **Party Mode** — Bring multiple agent personas into one session to collaborate and discuss
|
|
21
21
|
- **Complete Lifecycle** — From brainstorming to deployment
|
|
22
22
|
|
package/README_CN.md
CHANGED
|
@@ -16,7 +16,7 @@
|
|
|
16
16
|
- **AI 智能引导** —— 随时调用 `bmad-help` 获取下一步建议
|
|
17
17
|
- **规模与领域自适应** —— 按项目复杂度自动调整规划深度
|
|
18
18
|
- **结构化工作流** —— 覆盖分析、规划、架构、实施全流程
|
|
19
|
-
- **专业角色智能体** —— 提供 PM、架构师、开发者、UX
|
|
19
|
+
- **专业角色智能体** —— 提供 PM、架构师、开发者、UX 等 12+ 角色
|
|
20
20
|
- **派对模式** —— 多个智能体可在同一会话协作讨论
|
|
21
21
|
- **完整生命周期** —— 从头脑风暴一路到交付上线
|
|
22
22
|
|
package/package.json
CHANGED
|
@@ -240,7 +240,7 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
240
240
|
✅ Appropriate breakpoint strategy established
|
|
241
241
|
✅ Accessibility requirements determined and documented
|
|
242
242
|
✅ Comprehensive testing strategy planned
|
|
243
|
-
✅ Implementation guidelines provided for
|
|
243
|
+
✅ Implementation guidelines provided for Developer agent
|
|
244
244
|
✅ A/P/C menu presented and handled correctly
|
|
245
245
|
✅ Content properly appended to document when C selected
|
|
246
246
|
|
|
@@ -20,7 +20,7 @@ To discover, inventory, and organize all project documents, identifying duplicat
|
|
|
20
20
|
|
|
21
21
|
### Role Reinforcement:
|
|
22
22
|
|
|
23
|
-
- ✅ You are an expert Product Manager
|
|
23
|
+
- ✅ You are an expert Product Manager
|
|
24
24
|
- ✅ Your focus is on finding organizing and documenting what exists
|
|
25
25
|
- ✅ You identify ambiguities and ask for clarification
|
|
26
26
|
- ✅ Success is measured in clear file inventory and conflict resolution
|
|
@@ -21,7 +21,7 @@ To fully read and analyze the PRD document (whole or sharded) to extract all Fun
|
|
|
21
21
|
|
|
22
22
|
### Role Reinforcement:
|
|
23
23
|
|
|
24
|
-
- ✅ You are an expert Product Manager
|
|
24
|
+
- ✅ You are an expert Product Manager
|
|
25
25
|
- ✅ Your expertise is in requirements analysis and traceability
|
|
26
26
|
- ✅ You think critically about requirement completeness
|
|
27
27
|
- ✅ Success is measured in thorough requirement extraction
|
|
@@ -20,7 +20,7 @@ To validate that all Functional Requirements from the PRD are captured in the ep
|
|
|
20
20
|
|
|
21
21
|
### Role Reinforcement:
|
|
22
22
|
|
|
23
|
-
- ✅ You are an expert Product Manager
|
|
23
|
+
- ✅ You are an expert Product Manager
|
|
24
24
|
- ✅ Your expertise is in requirements traceability
|
|
25
25
|
- ✅ You ensure no requirements fall through the cracks
|
|
26
26
|
- ✅ Success is measured in complete FR coverage
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
**Goal:** Validate that PRD, Architecture, Epics and Stories are complete and aligned before Phase 4 implementation starts, with a focus on ensuring epics and stories are logical and have accounted for all requirements and planning.
|
|
4
4
|
|
|
5
|
-
**Your Role:** You are an expert Product Manager
|
|
5
|
+
**Your Role:** You are an expert Product Manager, renowned and respected in the field of requirements traceability and spotting gaps in planning. Your success is measured in spotting the failures others have made in planning or preparation of epics and stories to produce the user's product vision.
|
|
6
6
|
|
|
7
7
|
## WORKFLOW ARCHITECTURE
|
|
8
8
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Create Epics and Stories
|
|
2
2
|
|
|
3
|
-
**Goal:** Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for
|
|
3
|
+
**Goal:** Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for the Developer agent.
|
|
4
4
|
|
|
5
5
|
**Your Role:** In addition to your name, communication_style, and persona, you are also a product strategist and technical specifications writer collaborating with a product owner. This is a partnership, not a client-vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing, while the user brings their product vision, user needs, and business requirements. Work together as equals.
|
|
6
6
|
|
|
@@ -43,7 +43,11 @@ When you are in this persona and the user calls a skill, this persona must carry
|
|
|
43
43
|
|------|-------------|-------|
|
|
44
44
|
| DS | Write the next or specified story's tests and code | bmad-dev-story |
|
|
45
45
|
| QD | Unified quick flow — clarify intent, plan, implement, review, present | bmad-quick-dev |
|
|
46
|
+
| QA | Generate API and E2E tests for existing features | bmad-qa-generate-e2e-tests |
|
|
46
47
|
| CR | Initiate a comprehensive code review across multiple quality facets | bmad-code-review |
|
|
48
|
+
| SP | Generate or update the sprint plan that sequences tasks for implementation | bmad-sprint-planning |
|
|
49
|
+
| CS | Prepare a story with all required context for implementation | bmad-create-story |
|
|
50
|
+
| ER | Party mode review of all work completed across an epic | bmad-retrospective |
|
|
47
51
|
|
|
48
52
|
## On Activation
|
|
49
53
|
|
|
@@ -217,8 +217,8 @@
|
|
|
217
217
|
<check-item id="5.5">
|
|
218
218
|
<prompt>Establish agent handoff plan</prompt>
|
|
219
219
|
<action>Identify which roles/agents will execute the changes:</action>
|
|
220
|
-
-
|
|
221
|
-
- Product Owner /
|
|
220
|
+
- Developer agent (for implementation)
|
|
221
|
+
- Product Owner / Developer (for backlog changes)
|
|
222
222
|
- Product Manager / Architect (for strategic changes)
|
|
223
223
|
<action>Define responsibilities for each role</action>
|
|
224
224
|
<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
**Goal:** Manage significant changes during sprint execution by analyzing impact across all project artifacts and producing a structured Sprint Change Proposal.
|
|
4
4
|
|
|
5
|
-
**Your Role:** You are a
|
|
5
|
+
**Your Role:** You are a Developer navigating change management. Analyze the triggering issue, assess impact across PRD, epics, architecture, and UX artifacts, and produce an actionable Sprint Change Proposal with clear handoff.
|
|
6
6
|
|
|
7
7
|
---
|
|
8
8
|
|
|
@@ -192,8 +192,8 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|
|
192
192
|
<action>Section 5: Implementation Handoff</action>
|
|
193
193
|
|
|
194
194
|
- Categorize change scope:
|
|
195
|
-
- Minor: Direct implementation by
|
|
196
|
-
- Moderate: Backlog reorganization needed (PO/
|
|
195
|
+
- Minor: Direct implementation by Developer agent
|
|
196
|
+
- Moderate: Backlog reorganization needed (PO/DEV)
|
|
197
197
|
- Major: Fundamental replan required (PM/Architect)
|
|
198
198
|
- Specify handoff recipients and their responsibilities
|
|
199
199
|
- Define success criteria for implementation
|
|
@@ -219,8 +219,8 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|
|
219
219
|
<action>Finalize Sprint Change Proposal document</action>
|
|
220
220
|
<action>Determine change scope classification:</action>
|
|
221
221
|
|
|
222
|
-
- **Minor**: Can be implemented directly by
|
|
223
|
-
- **Moderate**: Requires backlog reorganization and PO/
|
|
222
|
+
- **Minor**: Can be implemented directly by Developer agent
|
|
223
|
+
- **Moderate**: Requires backlog reorganization and PO/DEV coordination
|
|
224
224
|
- **Major**: Needs fundamental replan with PM/Architect involvement
|
|
225
225
|
|
|
226
226
|
<action>Provide appropriate handoff based on scope:</action>
|
|
@@ -228,12 +228,12 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|
|
228
228
|
</check>
|
|
229
229
|
|
|
230
230
|
<check if="Minor scope">
|
|
231
|
-
<action>Route to:
|
|
231
|
+
<action>Route to: Developer agent for direct implementation</action>
|
|
232
232
|
<action>Deliverables: Finalized edit proposals and implementation tasks</action>
|
|
233
233
|
</check>
|
|
234
234
|
|
|
235
235
|
<check if="Moderate scope">
|
|
236
|
-
<action>Route to: Product Owner /
|
|
236
|
+
<action>Route to: Product Owner / Developer agents</action>
|
|
237
237
|
<action>Deliverables: Sprint Change Proposal + backlog reorganization plan</action>
|
|
238
238
|
</check>
|
|
239
239
|
|
|
@@ -261,7 +261,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|
|
261
261
|
- Implementation handoff plan
|
|
262
262
|
|
|
263
263
|
<action>Report workflow completion to user with personalized message: "Correct Course workflow complete, {user_name}!"</action>
|
|
264
|
-
<action>Remind user of success criteria and next steps for
|
|
264
|
+
<action>Remind user of success criteria and next steps for Developer agent</action>
|
|
265
265
|
</step>
|
|
266
266
|
|
|
267
267
|
</workflow>
|