bmad-method 4.24.5 → 4.24.6
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 +7 -0
- package/bmad-core/agents/bmad-master.md +0 -2
- package/bmad-core/agents/sm.md +1 -1
- package/bmad-core/core-config.yaml +1 -1
- package/dist/agents/bmad-master.txt +0 -2
- package/dist/agents/sm.txt +77 -1
- package/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt +1 -1
- package/dist/teams/team-all.txt +1 -1
- package/dist/teams/team-ide-minimal.txt +1 -1
- package/expansion-packs/bmad-2d-phaser-game-dev/config.yaml +1 -1
- 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/installer/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,10 @@
|
|
|
1
|
+
## [4.24.6](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.5...v4.24.6) (2025-07-04)
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
### Bug Fixes
|
|
5
|
+
|
|
6
|
+
* version bump and web build fix ([1c845e5](https://github.com/bmadcode/BMAD-METHOD/commit/1c845e5b2c77a77d887d8216152ba09110c72e40))
|
|
7
|
+
|
|
1
8
|
## [4.24.5](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.4...v4.24.5) (2025-07-04)
|
|
2
9
|
|
|
3
10
|
|
|
@@ -65,7 +65,6 @@ dependencies:
|
|
|
65
65
|
- brainstorming-techniques
|
|
66
66
|
- brownfield-create-epic
|
|
67
67
|
- brownfield-create-story
|
|
68
|
-
- core-dump
|
|
69
68
|
- correct-course
|
|
70
69
|
- create-deep-research-prompt
|
|
71
70
|
- create-doc
|
|
@@ -78,7 +77,6 @@ dependencies:
|
|
|
78
77
|
- shard-doc
|
|
79
78
|
- update-workflow-plan
|
|
80
79
|
templates:
|
|
81
|
-
- agent-tmpl
|
|
82
80
|
- architecture-tmpl
|
|
83
81
|
- brownfield-architecture-tmpl
|
|
84
82
|
- brownfield-prd-tmpl
|
package/bmad-core/agents/sm.md
CHANGED
|
@@ -103,7 +103,6 @@ dependencies:
|
|
|
103
103
|
- brainstorming-techniques
|
|
104
104
|
- brownfield-create-epic
|
|
105
105
|
- brownfield-create-story
|
|
106
|
-
- core-dump
|
|
107
106
|
- correct-course
|
|
108
107
|
- create-deep-research-prompt
|
|
109
108
|
- create-doc
|
|
@@ -116,7 +115,6 @@ dependencies:
|
|
|
116
115
|
- shard-doc
|
|
117
116
|
- update-workflow-plan
|
|
118
117
|
templates:
|
|
119
|
-
- agent-tmpl
|
|
120
118
|
- architecture-tmpl
|
|
121
119
|
- brownfield-architecture-tmpl
|
|
122
120
|
- brownfield-prd-tmpl
|
package/dist/agents/sm.txt
CHANGED
|
@@ -79,7 +79,7 @@ dependencies:
|
|
|
79
79
|
tasks:
|
|
80
80
|
- create-next-story
|
|
81
81
|
- execute-checklist
|
|
82
|
-
- course
|
|
82
|
+
- correct-course
|
|
83
83
|
templates:
|
|
84
84
|
- story-tmpl
|
|
85
85
|
checklists:
|
|
@@ -465,6 +465,82 @@ The LLM will:
|
|
|
465
465
|
- Offer to provide detailed analysis of any section, especially those with warnings or failures
|
|
466
466
|
==================== END: tasks#execute-checklist ====================
|
|
467
467
|
|
|
468
|
+
==================== START: tasks#correct-course ====================
|
|
469
|
+
# Correct Course Task
|
|
470
|
+
|
|
471
|
+
## Purpose
|
|
472
|
+
|
|
473
|
+
- Guide a structured response to a change trigger using the `change-checklist`.
|
|
474
|
+
- Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
|
|
475
|
+
- Explore potential solutions (e.g., adjust scope, rollback elements, rescope features) as prompted by the checklist.
|
|
476
|
+
- Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
|
|
477
|
+
- Produce a consolidated "Sprint Change Proposal" document that contains the impact analysis and the clearly drafted proposed edits for user review and approval.
|
|
478
|
+
- Ensure a clear handoff path if the nature of the changes necessitates fundamental replanning by other core agents (like PM or Architect).
|
|
479
|
+
|
|
480
|
+
## Instructions
|
|
481
|
+
|
|
482
|
+
### 1. Initial Setup & Mode Selection
|
|
483
|
+
|
|
484
|
+
- **Acknowledge Task & Inputs:**
|
|
485
|
+
- Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
|
|
486
|
+
- Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
|
|
487
|
+
- Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `change-checklist` (e.g., `change-checklist`).
|
|
488
|
+
- **Establish Interaction Mode:**
|
|
489
|
+
- Ask the user their preferred interaction mode for this task:
|
|
490
|
+
- **"Incrementally (Default & Recommended):** Shall we work through the `change-checklist` section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
|
|
491
|
+
- **"YOLO Mode (Batch Processing):** Or, would you prefer I conduct a more batched analysis based on the checklist and then present a consolidated set of findings and proposed changes for a broader review? This can be quicker for initial assessment but might require more extensive review of the combined proposals."
|
|
492
|
+
- Request the user to select their preferred mode.
|
|
493
|
+
- Once the user chooses, confirm the selected mode (e.g., "Okay, we will proceed in Incremental mode."). This chosen mode will govern how subsequent steps in this task are executed.
|
|
494
|
+
- **Explain Process:** Briefly inform the user: "We will now use the `change-checklist` to analyze the change and draft proposed updates. I will guide you through the checklist items based on our chosen interaction mode."
|
|
495
|
+
<rule>When asking multiple questions or presenting multiple points for user input at once, number them clearly (e.g., 1., 2a., 2b.) to make it easier for the user to provide specific responses.</rule>
|
|
496
|
+
|
|
497
|
+
### 2. Execute Checklist Analysis (Iteratively or Batched, per Interaction Mode)
|
|
498
|
+
|
|
499
|
+
- Systematically work through Sections 1-4 of the `change-checklist` (typically covering Change Context, Epic/Story Impact Analysis, Artifact Conflict Resolution, and Path Evaluation/Recommendation).
|
|
500
|
+
- For each checklist item or logical group of items (depending on interaction mode):
|
|
501
|
+
- Present the relevant prompt(s) or considerations from the checklist to the user.
|
|
502
|
+
- Request necessary information and actively analyze the relevant project artifacts (PRD, epics, architecture documents, story history, etc.) to assess the impact.
|
|
503
|
+
- Discuss your findings for each item with the user.
|
|
504
|
+
- Record the status of each checklist item (e.g., `[x] Addressed`, `[N/A]`, `[!] Further Action Needed`) and any pertinent notes or decisions.
|
|
505
|
+
- Collaboratively agree on the "Recommended Path Forward" as prompted by Section 4 of the checklist.
|
|
506
|
+
|
|
507
|
+
### 3. Draft Proposed Changes (Iteratively or Batched)
|
|
508
|
+
|
|
509
|
+
- Based on the completed checklist analysis (Sections 1-4) and the agreed "Recommended Path Forward" (excluding scenarios requiring fundamental replans that would necessitate immediate handoff to PM/Architect):
|
|
510
|
+
- Identify the specific project artifacts that require updates (e.g., specific epics, user stories, PRD sections, architecture document components, diagrams).
|
|
511
|
+
- **Draft the proposed changes directly and explicitly for each identified artifact.** Examples include:
|
|
512
|
+
- Revising user story text, acceptance criteria, or priority.
|
|
513
|
+
- Adding, removing, reordering, or splitting user stories within epics.
|
|
514
|
+
- Proposing modified architecture diagram snippets (e.g., providing an updated Mermaid diagram block or a clear textual description of the change to an existing diagram).
|
|
515
|
+
- Updating technology lists, configuration details, or specific sections within the PRD or architecture documents.
|
|
516
|
+
- Drafting new, small supporting artifacts if necessary (e.g., a brief addendum for a specific decision).
|
|
517
|
+
- If in "Incremental Mode," discuss and refine these proposed edits for each artifact or small group of related artifacts with the user as they are drafted.
|
|
518
|
+
- If in "YOLO Mode," compile all drafted edits for presentation in the next step.
|
|
519
|
+
|
|
520
|
+
### 4. Generate "Sprint Change Proposal" with Edits
|
|
521
|
+
|
|
522
|
+
- Synthesize the complete `change-checklist` analysis (covering findings from Sections 1-4) and all the agreed-upon proposed edits (from Instruction 3) into a single document titled "Sprint Change Proposal." This proposal should align with the structure suggested by Section 5 of the `change-checklist` (Proposal Components).
|
|
523
|
+
- The proposal must clearly present:
|
|
524
|
+
- **Analysis Summary:** A concise overview of the original issue, its analyzed impact (on epics, artifacts, MVP scope), and the rationale for the chosen path forward.
|
|
525
|
+
- **Specific Proposed Edits:** For each affected artifact, clearly show or describe the exact changes (e.g., "Change Story X.Y from: [old text] To: [new text]", "Add new Acceptance Criterion to Story A.B: [new AC]", "Update Section 3.2 of Architecture Document as follows: [new/modified text or diagram description]").
|
|
526
|
+
- Present the complete draft of the "Sprint Change Proposal" to the user for final review and feedback. Incorporate any final adjustments requested by the user.
|
|
527
|
+
|
|
528
|
+
### 5. Finalize & Determine Next Steps
|
|
529
|
+
|
|
530
|
+
- Obtain explicit user approval for the "Sprint Change Proposal," including all the specific edits documented within it.
|
|
531
|
+
- Provide the finalized "Sprint Change Proposal" document to the user.
|
|
532
|
+
- **Based on the nature of the approved changes:**
|
|
533
|
+
- **If the approved edits sufficiently address the change and can be implemented directly or organized by a PO/SM:** State that the "Correct Course Task" is complete regarding analysis and change proposal, and the user can now proceed with implementing or logging these changes (e.g., updating actual project documents, backlog items). Suggest handoff to a PO/SM agent for backlog organization if appropriate.
|
|
534
|
+
- **If the analysis and proposed path (as per checklist Section 4 and potentially Section 6) indicate that the change requires a more fundamental replan (e.g., significant scope change, major architectural rework):** Clearly state this conclusion. Advise the user that the next step involves engaging the primary PM or Architect agents, using the "Sprint Change Proposal" as critical input and context for that deeper replanning effort.
|
|
535
|
+
|
|
536
|
+
## Output Deliverables
|
|
537
|
+
|
|
538
|
+
- **Primary:** A "Sprint Change Proposal" document (in markdown format). This document will contain:
|
|
539
|
+
- A summary of the `change-checklist` analysis (issue, impact, rationale for the chosen path).
|
|
540
|
+
- Specific, clearly drafted proposed edits for all affected project artifacts.
|
|
541
|
+
- **Implicit:** An annotated `change-checklist` (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
|
|
542
|
+
==================== END: tasks#correct-course ====================
|
|
543
|
+
|
|
468
544
|
==================== START: templates#story-tmpl ====================
|
|
469
545
|
# Story {{EpicNum}}.{{StoryNum}}: {{Short Title Copied from Epic File specific story}}
|
|
470
546
|
|
|
@@ -41,7 +41,7 @@ These references map directly to bundle sections:
|
|
|
41
41
|
==================== START: agents#infra-devops-platform ====================
|
|
42
42
|
# infra-devops-platform
|
|
43
43
|
|
|
44
|
-
CRITICAL: Read the full
|
|
44
|
+
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:
|
|
45
45
|
|
|
46
46
|
```yaml
|
|
47
47
|
activation-instructions:
|
package/dist/teams/team-all.txt
CHANGED
package/package.json
CHANGED