bmad-method 6.1.1-next.25 → 6.1.1-next.26
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/package.json +1 -1
- package/src/bmm/workflows/3-solutioning/bmad-check-implementation-readiness/steps/step-01-document-discovery.md +3 -8
- package/src/bmm/workflows/3-solutioning/bmad-check-implementation-readiness/steps/step-02-prd-analysis.md +1 -5
- package/src/bmm/workflows/3-solutioning/bmad-check-implementation-readiness/steps/step-03-epic-coverage-validation.md +1 -5
- package/src/bmm/workflows/3-solutioning/bmad-check-implementation-readiness/steps/step-04-ux-alignment.md +1 -5
- package/src/bmm/workflows/3-solutioning/bmad-check-implementation-readiness/steps/step-05-epic-quality-review.md +2 -6
- package/src/bmm/workflows/3-solutioning/bmad-check-implementation-readiness/steps/step-06-final-assessment.md +0 -3
package/package.json
CHANGED
|
@@ -1,10 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: 'step-01-document-discovery'
|
|
3
|
-
description: 'Discover and inventory all project documents, handling duplicates and organizing file structure'
|
|
4
|
-
|
|
5
|
-
nextStepFile: './step-02-prd-analysis.md'
|
|
6
2
|
outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
|
|
7
|
-
templateFile: '../templates/readiness-report-template.md'
|
|
8
3
|
---
|
|
9
4
|
|
|
10
5
|
# Step 1: Document Discovery
|
|
@@ -122,7 +117,7 @@ If required documents not found:
|
|
|
122
117
|
|
|
123
118
|
### 5. Add Initial Report Section
|
|
124
119
|
|
|
125
|
-
Initialize {outputFile} with
|
|
120
|
+
Initialize {outputFile} with ../templates/readiness-report-template.md.
|
|
126
121
|
|
|
127
122
|
### 6. Present Findings and Get Confirmation
|
|
128
123
|
|
|
@@ -156,12 +151,12 @@ Display: **Select an Option:** [C] Continue to File Validation
|
|
|
156
151
|
|
|
157
152
|
#### Menu Handling Logic:
|
|
158
153
|
|
|
159
|
-
- IF C: Save document inventory to {outputFile}, update frontmatter with completed step and files being included, and then read fully and follow:
|
|
154
|
+
- IF C: Save document inventory to {outputFile}, update frontmatter with completed step and files being included, and then read fully and follow: ./step-02-prd-analysis.md
|
|
160
155
|
- IF Any other comments or queries: help user respond then redisplay menu
|
|
161
156
|
|
|
162
157
|
## CRITICAL STEP COMPLETION NOTE
|
|
163
158
|
|
|
164
|
-
ONLY WHEN C is selected and document inventory is saved will you load
|
|
159
|
+
ONLY WHEN C is selected and document inventory is saved will you load ./step-02-prd-analysis.md to begin file validation.
|
|
165
160
|
|
|
166
161
|
---
|
|
167
162
|
|
|
@@ -1,8 +1,4 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: 'step-02-prd-analysis'
|
|
3
|
-
description: 'Read and analyze PRD to extract all FRs and NFRs for coverage validation'
|
|
4
|
-
|
|
5
|
-
nextStepFile: './step-03-epic-coverage-validation.md'
|
|
6
2
|
outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
|
|
7
3
|
epicsFile: '{planning_artifacts}/*epic*.md' # Will be resolved to actual file
|
|
8
4
|
---
|
|
@@ -149,7 +145,7 @@ After PRD analysis complete, immediately load next step for epic coverage valida
|
|
|
149
145
|
|
|
150
146
|
## PROCEEDING TO EPIC COVERAGE VALIDATION
|
|
151
147
|
|
|
152
|
-
PRD analysis complete.
|
|
148
|
+
PRD analysis complete. Read fully and follow: `./step-03-epic-coverage-validation.md`
|
|
153
149
|
|
|
154
150
|
---
|
|
155
151
|
|
|
@@ -1,8 +1,4 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: 'step-03-epic-coverage-validation'
|
|
3
|
-
description: 'Validate that all PRD FRs are covered in epics and stories'
|
|
4
|
-
|
|
5
|
-
nextStepFile: './step-04-ux-alignment.md'
|
|
6
2
|
outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
|
|
7
3
|
---
|
|
8
4
|
|
|
@@ -150,7 +146,7 @@ After coverage validation complete, immediately load next step.
|
|
|
150
146
|
|
|
151
147
|
## PROCEEDING TO UX ALIGNMENT
|
|
152
148
|
|
|
153
|
-
Epic coverage validation complete.
|
|
149
|
+
Epic coverage validation complete. Read fully and follow: `./step-04-ux-alignment.md`
|
|
154
150
|
|
|
155
151
|
---
|
|
156
152
|
|
|
@@ -1,8 +1,4 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: 'step-04-ux-alignment'
|
|
3
|
-
description: 'Check for UX document and validate alignment with PRD and Architecture'
|
|
4
|
-
|
|
5
|
-
nextStepFile: './step-05-epic-quality-review.md'
|
|
6
2
|
outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
|
|
7
3
|
---
|
|
8
4
|
|
|
@@ -113,7 +109,7 @@ After UX assessment complete, immediately load next step.
|
|
|
113
109
|
|
|
114
110
|
## PROCEEDING TO EPIC QUALITY REVIEW
|
|
115
111
|
|
|
116
|
-
UX alignment assessment complete.
|
|
112
|
+
UX alignment assessment complete. Read fully and follow: `./step-05-epic-quality-review.md`
|
|
117
113
|
|
|
118
114
|
---
|
|
119
115
|
|
|
@@ -1,8 +1,4 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: 'step-05-epic-quality-review'
|
|
3
|
-
description: 'Validate epics and stories against create-epics-and-stories best practices'
|
|
4
|
-
|
|
5
|
-
nextStepFile: './step-06-final-assessment.md'
|
|
6
2
|
outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
|
|
7
3
|
---
|
|
8
4
|
|
|
@@ -217,11 +213,11 @@ After completing epic quality review:
|
|
|
217
213
|
- Update {outputFile} with all quality findings
|
|
218
214
|
- Document specific best practices violations
|
|
219
215
|
- Provide actionable recommendations
|
|
220
|
-
- Load
|
|
216
|
+
- Load ./step-06-final-assessment.md for final readiness assessment
|
|
221
217
|
|
|
222
218
|
## CRITICAL STEP COMPLETION NOTE
|
|
223
219
|
|
|
224
|
-
This step executes autonomously. Load
|
|
220
|
+
This step executes autonomously. Load ./step-06-final-assessment.md only after complete epic quality review is documented.
|
|
225
221
|
|
|
226
222
|
---
|
|
227
223
|
|