ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc and text cleanup

Browse Source
This commit is contained in:
Brian Madison
2025-07-04 07:47:57 -05:00
parent be4fcd8668
commit f440d14565
77 changed files with 243 additions and 78705 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bmad-core/checklists/change-checklist.md
View File

@@ -1,6 +1,6 @@
# Change Navigation Checklist
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMAD workflow.
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
**Instructions:** Review each item with the user. Mark `[x]` for completed/confirmed, `[N/A]` if not applicable, or add notes for discussion points.
@@ -75,7 +75,7 @@ Think about both immediate and downstream effects.]]
## 3. Artifact Conflict & Impact Analysis
[[LLM: Documentation drives development in BMAD. Check each artifact:
[[LLM: Documentation drives development in BMad. Check each artifact:
1. Does this change invalidate documented decisions?
2. Are architectural assumptions still valid?