bmad-method 6.8.1-next.2 → 6.8.1-next.3
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
CHANGED
|
@@ -48,7 +48,7 @@ Verify required documents exist and are complete:
|
|
|
48
48
|
|
|
49
49
|
1. **PRD.md** - Contains requirements (FRs and NFRs) and product scope
|
|
50
50
|
2. **Architecture.md** - Contains technical decisions, API contracts, data models
|
|
51
|
-
3. **UX
|
|
51
|
+
3. **UX design contract** (if UI exists) - Contains visual identity, interaction patterns, mockups, and user flows
|
|
52
52
|
|
|
53
53
|
### 2. Document Discovery and Validation
|
|
54
54
|
|
|
@@ -66,8 +66,16 @@ Search for required documents using these patterns (sharded means a large docume
|
|
|
66
66
|
|
|
67
67
|
**UX Design Document Search (Optional):**
|
|
68
68
|
|
|
69
|
-
1. `{planning_artifacts}
|
|
70
|
-
2. `{planning_artifacts}/*ux
|
|
69
|
+
1. `{planning_artifacts}/ux-designs/ux-*/DESIGN.md` and `{planning_artifacts}/ux-designs/ux-*/EXPERIENCE.md` (bmad-ux spine pair)
|
|
70
|
+
2. `{planning_artifacts}/*ux*.md` (legacy whole document)
|
|
71
|
+
3. `{planning_artifacts}/*ux*/index.md` (legacy sharded version)
|
|
72
|
+
|
|
73
|
+
For each matching bmad-ux run folder, treat `DESIGN.md` and `EXPERIENCE.md` as one UX design contract:
|
|
74
|
+
|
|
75
|
+
- Confirm and load both files together. `DESIGN.md` owns visual identity and design tokens; `EXPERIENCE.md` owns information architecture, behavior, states, interactions, accessibility, and journeys.
|
|
76
|
+
- Add both files to the `inputDocuments: []` frontmatter array.
|
|
77
|
+
- If only one spine exists, report the incomplete pair and ask whether the user wants to include the partial UX handoff.
|
|
78
|
+
- If multiple run folders match, show each run folder with the spine frontmatter `status` and `updated` values when available, then ask the user which UX design contract to include.
|
|
71
79
|
|
|
72
80
|
Before proceeding, Ask the user if there are any other documents to include for analysis, and if anything found should be excluded. Wait for user confirmation. Once confirmed, create the {planning_artifacts}/epics.md from the ../templates/epics-template.md and in the front matter list the files in the array of `inputDocuments: []`.
|
|
73
81
|
|
|
@@ -136,7 +144,7 @@ Review the Architecture document for technical requirements that impact epic and
|
|
|
136
144
|
|
|
137
145
|
**IMPORTANT**: The UX Design Specification is a first-class input document, not supplementary material. Requirements from the UX spec must be extracted with the same rigor as PRD functional requirements.
|
|
138
146
|
|
|
139
|
-
Read the FULL UX
|
|
147
|
+
Read the FULL UX design contract and extract ALL actionable work items. For a bmad-ux spine pair, read both `DESIGN.md` and `EXPERIENCE.md`:
|
|
140
148
|
|
|
141
149
|
**Look for:**
|
|
142
150
|
|