bmad-method 6.1.1-next.6 → 6.1.1-next.8
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/agents/architect.agent.yaml +1 -1
- package/src/bmm/agents/ux-designer.agent.yaml +1 -1
- package/src/bmm/module-help.csv +2 -2
- package/src/bmm/workflows/2-plan-workflows/bmad-create-ux-design/SKILL.md +6 -0
- package/src/bmm/workflows/2-plan-workflows/bmad-create-ux-design/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-01-init.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-01b-continue.md +3 -3
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-02-discovery.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-03-core-experience.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-04-emotional-response.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-05-inspiration.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-06-design-system.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-07-defining-experience.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-08-visual-foundation.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-09-design-directions.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-10-user-journeys.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-11-component-strategy.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-12-ux-patterns.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-13-responsive-accessibility.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/workflow.md +2 -7
- package/src/bmm/workflows/3-solutioning/bmad-create-architecture/SKILL.md +6 -0
- package/src/bmm/workflows/3-solutioning/bmad-create-architecture/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-01-init.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-01b-continue.md +9 -9
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-02-context.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-03-starter.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-04-decisions.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-05-patterns.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-06-structure.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-07-validation.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/workflow.md +2 -7
- package/src/bmm/workflows/2-plan-workflows/create-ux-design/bmad-skill-manifest.yaml +0 -3
- package/src/bmm/workflows/3-solutioning/create-architecture/bmad-skill-manifest.yaml +0 -3
- /package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-14-complete.md +0 -0
- /package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/ux-design-template.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/architecture-decision-template.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/data/domain-complexity.csv +0 -0
- /package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/data/project-types.csv +0 -0
- /package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-08-complete.md +0 -0
package/package.json
CHANGED
|
@@ -21,7 +21,7 @@ agent:
|
|
|
21
21
|
|
|
22
22
|
menu:
|
|
23
23
|
- trigger: CA or fuzzy match on create-architecture
|
|
24
|
-
exec: "
|
|
24
|
+
exec: "skill:bmad-create-architecture"
|
|
25
25
|
description: "[CA] Create Architecture: Guided Workflow to document technical decisions to keep implementation on track"
|
|
26
26
|
|
|
27
27
|
- trigger: IR or fuzzy match on implementation-readiness
|
|
@@ -23,5 +23,5 @@ agent:
|
|
|
23
23
|
|
|
24
24
|
menu:
|
|
25
25
|
- trigger: CU or fuzzy match on ux-design
|
|
26
|
-
exec: "
|
|
26
|
+
exec: "skill:bmad-create-ux-design"
|
|
27
27
|
description: "[CU] Create UX: Guidance through realizing the plan for your UX to inform architecture and implementation. Provides more details than what was discovered in the PRD"
|
package/src/bmm/module-help.csv
CHANGED
|
@@ -18,8 +18,8 @@ bmm,1-analysis,Create Brief,CB,30,skill:bmad-create-product-brief,bmad-bmm-creat
|
|
|
18
18
|
bmm,2-planning,Create PRD,CP,10,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
|
|
19
19
|
bmm,2-planning,Validate PRD,VP,20,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md,bmad-bmm-validate-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report",
|
|
20
20
|
bmm,2-planning,Edit PRD,EP,25,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md,bmad-bmm-edit-prd,false,pm,Edit Mode,"Improve and enhance an existing PRD",planning_artifacts,"updated prd",
|
|
21
|
-
bmm,2-planning,Create UX,CU,30,
|
|
22
|
-
bmm,3-solutioning,Create Architecture,CA,10,
|
|
21
|
+
bmm,2-planning,Create UX,CU,30,skill:bmad-create-ux-design,bmad-bmm-create-ux-design,false,ux-designer,Create Mode,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project",planning_artifacts,"ux design",
|
|
22
|
+
bmm,3-solutioning,Create Architecture,CA,10,skill:bmad-create-architecture,bmad-bmm-create-architecture,true,architect,Create Mode,"Guided Workflow to document technical decisions",planning_artifacts,architecture,
|
|
23
23
|
bmm,3-solutioning,Create Epics and Stories,CE,30,_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md,bmad-bmm-create-epics-and-stories,true,pm,Create Mode,"Create the Epics and Stories Listing",planning_artifacts,"epics and stories",
|
|
24
24
|
bmm,3-solutioning,Check Implementation Readiness,IR,70,_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md,bmad-bmm-check-implementation-readiness,true,architect,Validate Mode,"Ensure PRD UX Architecture and Epics Stories are aligned",planning_artifacts,"readiness report",
|
|
25
25
|
bmm,4-implementation,Sprint Planning,SP,10,_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.md,bmad-bmm-sprint-planning,true,sm,Create Mode,"Generate sprint plan for development tasks - this kicks off the implementation phase by producing a plan the implementation agents will follow in sequence for every story in the plan.",implementation_artifacts,"sprint status",
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
type: skill
|
|
@@ -44,7 +44,7 @@ First, check if the output document already exists:
|
|
|
44
44
|
|
|
45
45
|
If the document exists and has frontmatter with `stepsCompleted`:
|
|
46
46
|
|
|
47
|
-
- **STOP here** and load
|
|
47
|
+
- **STOP here** and load `./step-01b-continue.md` immediately
|
|
48
48
|
- Do not proceed with any initialization tasks
|
|
49
49
|
- Let step-01b handle the continuation logic
|
|
50
50
|
|
|
@@ -110,7 +110,7 @@ Do you have any other documents you'd like me to include, or shall we continue t
|
|
|
110
110
|
|
|
111
111
|
## NEXT STEP:
|
|
112
112
|
|
|
113
|
-
After user selects [C] to continue, ensure the file `{planning_artifacts}/ux-design-specification.md` has been created and saved, and then load
|
|
113
|
+
After user selects [C] to continue, ensure the file `{planning_artifacts}/ux-design-specification.md` has been created and saved, and then load `./step-02-discovery.md` to begin the UX discovery phase.
|
|
114
114
|
|
|
115
115
|
Remember: Do NOT proceed to step-02 until output file has been updated and user explicitly selects [C] to continue!
|
|
116
116
|
|
|
@@ -72,9 +72,9 @@ Does this look right, or do you want to make any adjustments before we proceed?"
|
|
|
72
72
|
|
|
73
73
|
Based on `lastStep` value, determine which step to load next:
|
|
74
74
|
|
|
75
|
-
- If `lastStep = 1` → Load
|
|
76
|
-
- If `lastStep = 2` → Load
|
|
77
|
-
- If `lastStep = 3` → Load
|
|
75
|
+
- If `lastStep = 1` → Load `./step-02-discovery.md`
|
|
76
|
+
- If `lastStep = 2` → Load `./step-03-core-experience.md`
|
|
77
|
+
- If `lastStep = 3` → Load `./step-04-emotional-response.md`
|
|
78
78
|
- Continue this pattern for all steps
|
|
79
79
|
- If `lastStep` indicates final step → Workflow already complete
|
|
80
80
|
|
|
@@ -155,11 +155,11 @@ Show the generated project understanding content and present choices:
|
|
|
155
155
|
|
|
156
156
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
157
157
|
- Update frontmatter: `stepsCompleted: [1, 2]`
|
|
158
|
-
- Load
|
|
158
|
+
- Load `./step-03-core-experience.md`
|
|
159
159
|
|
|
160
160
|
## APPEND TO DOCUMENT:
|
|
161
161
|
|
|
162
|
-
When user selects 'C', append the content directly to the document. Only after the content is saved to document, read fully and follow:
|
|
162
|
+
When user selects 'C', append the content directly to the document. Only after the content is saved to document, read fully and follow: `./step-03-core-experience.md`.
|
|
163
163
|
|
|
164
164
|
## SUCCESS METRICS:
|
|
165
165
|
|
|
@@ -179,7 +179,7 @@ Show the generated core experience content and present choices:
|
|
|
179
179
|
|
|
180
180
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
181
181
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
182
|
-
- Load
|
|
182
|
+
- Load `./step-04-emotional-response.md`
|
|
183
183
|
|
|
184
184
|
## APPEND TO DOCUMENT:
|
|
185
185
|
|
|
@@ -211,6 +211,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
211
211
|
|
|
212
212
|
## NEXT STEP:
|
|
213
213
|
|
|
214
|
-
After user selects 'C' and content is saved to document, load
|
|
214
|
+
After user selects 'C' and content is saved to document, load `./step-04-emotional-response.md` to define desired emotional responses.
|
|
215
215
|
|
|
216
216
|
Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -182,7 +182,7 @@ Show the generated emotional response content and present choices:
|
|
|
182
182
|
|
|
183
183
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
184
184
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
185
|
-
- Load
|
|
185
|
+
- Load `./step-05-inspiration.md`
|
|
186
186
|
|
|
187
187
|
## APPEND TO DOCUMENT:
|
|
188
188
|
|
|
@@ -214,6 +214,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
214
214
|
|
|
215
215
|
## NEXT STEP:
|
|
216
216
|
|
|
217
|
-
After user selects 'C' and content is saved to document, load
|
|
217
|
+
After user selects 'C' and content is saved to document, load `./step-05-inspiration.md` to analyze UX patterns from inspiring products.
|
|
218
218
|
|
|
219
219
|
Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -197,7 +197,7 @@ Show the generated inspiration analysis content and present choices:
|
|
|
197
197
|
|
|
198
198
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
199
199
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
200
|
-
- Read fully and follow:
|
|
200
|
+
- Read fully and follow: `./step-06-design-system.md`
|
|
201
201
|
|
|
202
202
|
## APPEND TO DOCUMENT:
|
|
203
203
|
|
|
@@ -229,6 +229,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
229
229
|
|
|
230
230
|
## NEXT STEP:
|
|
231
231
|
|
|
232
|
-
After user selects 'C' and content is saved to document, load
|
|
232
|
+
After user selects 'C' and content is saved to document, load `./step-06-design-system.md` to choose the appropriate design system approach.
|
|
233
233
|
|
|
234
234
|
Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -215,7 +215,7 @@ Show the generated design system content and present choices:
|
|
|
215
215
|
|
|
216
216
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
217
217
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
218
|
-
- Load
|
|
218
|
+
- Load `./step-07-defining-experience.md`
|
|
219
219
|
|
|
220
220
|
## APPEND TO DOCUMENT:
|
|
221
221
|
|
|
@@ -247,6 +247,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
247
247
|
|
|
248
248
|
## NEXT STEP:
|
|
249
249
|
|
|
250
|
-
After user selects 'C' and content is saved to document, load
|
|
250
|
+
After user selects 'C' and content is saved to document, load `./step-07-defining-experience.md` to define the core user interaction.
|
|
251
251
|
|
|
252
252
|
Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -217,7 +217,7 @@ Show the generated defining experience content and present choices:
|
|
|
217
217
|
|
|
218
218
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
219
219
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
220
|
-
- Load
|
|
220
|
+
- Load `./step-08-visual-foundation.md`
|
|
221
221
|
|
|
222
222
|
## APPEND TO DOCUMENT:
|
|
223
223
|
|
|
@@ -249,6 +249,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
249
249
|
|
|
250
250
|
## NEXT STEP:
|
|
251
251
|
|
|
252
|
-
After user selects 'C' and content is saved to document, load
|
|
252
|
+
After user selects 'C' and content is saved to document, load `./step-08-visual-foundation.md` to establish visual design foundation.
|
|
253
253
|
|
|
254
254
|
Remember: Do NOT proceed to step-08 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -187,7 +187,7 @@ Show the generated visual foundation content and present choices:
|
|
|
187
187
|
|
|
188
188
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
189
189
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
190
|
-
- Load
|
|
190
|
+
- Load `./step-09-design-directions.md`
|
|
191
191
|
|
|
192
192
|
## APPEND TO DOCUMENT:
|
|
193
193
|
|
|
@@ -219,6 +219,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
219
219
|
|
|
220
220
|
## NEXT STEP:
|
|
221
221
|
|
|
222
|
-
After user selects 'C' and content is saved to document, load
|
|
222
|
+
After user selects 'C' and content is saved to document, load `./step-09-design-directions.md` to generate design direction mockups.
|
|
223
223
|
|
|
224
224
|
Remember: Do NOT proceed to step-09 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -187,7 +187,7 @@ Show the generated design direction content and present choices:
|
|
|
187
187
|
|
|
188
188
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
189
189
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
190
|
-
- Load
|
|
190
|
+
- Load `./step-10-user-journeys.md`
|
|
191
191
|
|
|
192
192
|
## APPEND TO DOCUMENT:
|
|
193
193
|
|
|
@@ -219,6 +219,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
219
219
|
|
|
220
220
|
## NEXT STEP:
|
|
221
221
|
|
|
222
|
-
After user selects 'C' and content is saved to document, load
|
|
222
|
+
After user selects 'C' and content is saved to document, load `./step-10-user-journeys.md` to design user journey flows.
|
|
223
223
|
|
|
224
224
|
Remember: Do NOT proceed to step-10 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -205,7 +205,7 @@ Show the generated user journey content and present choices:
|
|
|
205
205
|
|
|
206
206
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
207
207
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
208
|
-
- Load
|
|
208
|
+
- Load `./step-11-component-strategy.md`
|
|
209
209
|
|
|
210
210
|
## APPEND TO DOCUMENT:
|
|
211
211
|
|
|
@@ -236,6 +236,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
236
236
|
|
|
237
237
|
## NEXT STEP:
|
|
238
238
|
|
|
239
|
-
After user selects 'C' and content is saved to document, load
|
|
239
|
+
After user selects 'C' and content is saved to document, load `./step-11-component-strategy.md` to define component library strategy.
|
|
240
240
|
|
|
241
241
|
Remember: Do NOT proceed to step-11 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -211,7 +211,7 @@ Show the generated component strategy content and present choices:
|
|
|
211
211
|
|
|
212
212
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
213
213
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
214
|
-
- Load
|
|
214
|
+
- Load `./step-12-ux-patterns.md`
|
|
215
215
|
|
|
216
216
|
## APPEND TO DOCUMENT:
|
|
217
217
|
|
|
@@ -243,6 +243,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
243
243
|
|
|
244
244
|
## NEXT STEP:
|
|
245
245
|
|
|
246
|
-
After user selects 'C' and content is saved to document, load
|
|
246
|
+
After user selects 'C' and content is saved to document, load `./step-12-ux-patterns.md` to define UX consistency patterns.
|
|
247
247
|
|
|
248
248
|
Remember: Do NOT proceed to step-12 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -200,7 +200,7 @@ Show the generated UX patterns content and present choices:
|
|
|
200
200
|
|
|
201
201
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
202
202
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
203
|
-
- Load
|
|
203
|
+
- Load `./step-13-responsive-accessibility.md`
|
|
204
204
|
|
|
205
205
|
## APPEND TO DOCUMENT:
|
|
206
206
|
|
|
@@ -232,6 +232,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
232
232
|
|
|
233
233
|
## NEXT STEP:
|
|
234
234
|
|
|
235
|
-
After user selects 'C' and content is saved to document, load
|
|
235
|
+
After user selects 'C' and content is saved to document, load `./step-13-responsive-accessibility.md` to define responsive design and accessibility strategy.
|
|
236
236
|
|
|
237
237
|
Remember: Do NOT proceed to step-13 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -227,7 +227,7 @@ Show the generated responsive and accessibility content and present choices:
|
|
|
227
227
|
|
|
228
228
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
229
229
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
230
|
-
- Load
|
|
230
|
+
- Load `./step-14-complete.md`
|
|
231
231
|
|
|
232
232
|
## APPEND TO DOCUMENT:
|
|
233
233
|
|
|
@@ -259,6 +259,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
259
259
|
|
|
260
260
|
## NEXT STEP:
|
|
261
261
|
|
|
262
|
-
After user selects 'C' and content is saved to document, load
|
|
262
|
+
After user selects 'C' and content is saved to document, load `./step-14-complete.md` to finalize the UX design workflow.
|
|
263
263
|
|
|
264
264
|
Remember: Do NOT proceed to step-14 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/workflow.md
RENAMED
|
@@ -1,8 +1,3 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: create-ux-design
|
|
3
|
-
description: 'Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"'
|
|
4
|
-
---
|
|
5
|
-
|
|
6
1
|
# Create UX Design Workflow
|
|
7
2
|
|
|
8
3
|
**Goal:** Create comprehensive UX design specifications through collaborative visual exploration and informed decision-making where you act as a UX facilitator working with a product stakeholder.
|
|
@@ -32,11 +27,11 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|
|
32
27
|
|
|
33
28
|
### Paths
|
|
34
29
|
|
|
35
|
-
- `installed_path` =
|
|
30
|
+
- `installed_path` = `.`
|
|
36
31
|
- `template_path` = `{installed_path}/ux-design-template.md`
|
|
37
32
|
- `default_output_file` = `{planning_artifacts}/ux-design-specification.md`
|
|
38
33
|
|
|
39
34
|
## EXECUTION
|
|
40
35
|
|
|
41
36
|
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
|
42
|
-
- Read fully and follow:
|
|
37
|
+
- Read fully and follow: `./steps/step-01-init.md` to begin the UX design workflow.
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: bmad-create-architecture
|
|
3
|
+
description: 'Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"'
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Follow the instructions in [workflow.md](workflow.md).
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
type: skill
|
|
@@ -44,7 +44,7 @@ First, check if the output document already exists:
|
|
|
44
44
|
|
|
45
45
|
If the document exists and has frontmatter with `stepsCompleted`:
|
|
46
46
|
|
|
47
|
-
- **STOP here** and load
|
|
47
|
+
- **STOP here** and load `./step-01b-continue.md` immediately
|
|
48
48
|
- Do not proceed with any initialization tasks
|
|
49
49
|
- Let step-01b handle the continuation logic
|
|
50
50
|
|
|
@@ -148,6 +148,6 @@ Ready to begin architectural decision making. Do you have any other documents yo
|
|
|
148
148
|
|
|
149
149
|
## NEXT STEP:
|
|
150
150
|
|
|
151
|
-
After user selects [C] to continue, only after ensuring all the template output has been created, then load
|
|
151
|
+
After user selects [C] to continue, only after ensuring all the template output has been created, then load `./step-02-context.md` to analyze the project context and begin architectural decision making.
|
|
152
152
|
|
|
153
153
|
Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and setup is confirmed!
|
|
@@ -85,7 +85,7 @@ Show the user their current progress:
|
|
|
85
85
|
|
|
86
86
|
- Identify the next step based on `stepsCompleted`
|
|
87
87
|
- Load the appropriate step file to continue
|
|
88
|
-
- Example: If `stepsCompleted: [1, 2, 3]`, load
|
|
88
|
+
- Example: If `stepsCompleted: [1, 2, 3]`, load `./step-04-decisions.md`
|
|
89
89
|
|
|
90
90
|
#### If 'C' (Continue to next logical step):
|
|
91
91
|
|
|
@@ -103,7 +103,7 @@ Show the user their current progress:
|
|
|
103
103
|
#### If 'X' (Start over):
|
|
104
104
|
|
|
105
105
|
- Confirm: "This will delete all existing architectural decisions. Are you sure? (y/n)"
|
|
106
|
-
- If confirmed: Delete existing document and read fully and follow:
|
|
106
|
+
- If confirmed: Delete existing document and read fully and follow: `./step-01-init.md`
|
|
107
107
|
- If not confirmed: Return to continuation menu
|
|
108
108
|
|
|
109
109
|
### 4. Navigate to Selected Step
|
|
@@ -162,12 +162,12 @@ After user makes choice:
|
|
|
162
162
|
After user selects their continuation option, load the appropriate step file based on their choice. The step file will handle the detailed work from that point forward.
|
|
163
163
|
|
|
164
164
|
Valid step files to load:
|
|
165
|
-
-
|
|
166
|
-
-
|
|
167
|
-
-
|
|
168
|
-
-
|
|
169
|
-
-
|
|
170
|
-
-
|
|
171
|
-
-
|
|
165
|
+
- `./step-02-context.md`
|
|
166
|
+
- `./step-03-starter.md`
|
|
167
|
+
- `./step-04-decisions.md`
|
|
168
|
+
- `./step-05-patterns.md`
|
|
169
|
+
- `./step-06-structure.md`
|
|
170
|
+
- `./step-07-validation.md`
|
|
171
|
+
- `./step-08-complete.md`
|
|
172
172
|
|
|
173
173
|
Remember: The goal is smooth, transparent resumption that respects the work already done while giving the user control over how to proceed.
|
|
@@ -188,7 +188,7 @@ Show the generated content and present choices:
|
|
|
188
188
|
|
|
189
189
|
- Append the final content to `{planning_artifacts}/architecture.md`
|
|
190
190
|
- Update frontmatter: `stepsCompleted: [1, 2]`
|
|
191
|
-
- Load
|
|
191
|
+
- Load `./step-03-starter.md`
|
|
192
192
|
|
|
193
193
|
## APPEND TO DOCUMENT:
|
|
194
194
|
|
|
@@ -219,6 +219,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
219
219
|
|
|
220
220
|
## NEXT STEP:
|
|
221
221
|
|
|
222
|
-
After user selects 'C' and content is saved to document, load
|
|
222
|
+
After user selects 'C' and content is saved to document, load `./step-03-starter.md` to evaluate starter template options.
|
|
223
223
|
|
|
224
224
|
Remember: Do NOT proceed to step-03 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -294,7 +294,7 @@ Show the generated content and present choices:
|
|
|
294
294
|
|
|
295
295
|
- Append the final content to `{planning_artifacts}/architecture.md`
|
|
296
296
|
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
|
297
|
-
- Load
|
|
297
|
+
- Load `./step-04-decisions.md`
|
|
298
298
|
|
|
299
299
|
## APPEND TO DOCUMENT:
|
|
300
300
|
|
|
@@ -324,6 +324,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
324
324
|
|
|
325
325
|
## NEXT STEP:
|
|
326
326
|
|
|
327
|
-
After user selects 'C' and content is saved to document, load
|
|
327
|
+
After user selects 'C' and content is saved to document, load `./step-04-decisions.md` to begin making specific architectural decisions.
|
|
328
328
|
|
|
329
329
|
Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -282,7 +282,7 @@ Show the generated decisions content and present choices:
|
|
|
282
282
|
|
|
283
283
|
- Append the final content to `{planning_artifacts}/architecture.md`
|
|
284
284
|
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
|
|
285
|
-
- Load
|
|
285
|
+
- Load `./step-05-patterns.md`
|
|
286
286
|
|
|
287
287
|
## APPEND TO DOCUMENT:
|
|
288
288
|
|
|
@@ -313,6 +313,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
313
313
|
|
|
314
314
|
## NEXT STEP:
|
|
315
315
|
|
|
316
|
-
After user selects 'C' and content is saved to document, load
|
|
316
|
+
After user selects 'C' and content is saved to document, load `./step-05-patterns.md` to define implementation patterns that ensure consistency across AI agents.
|
|
317
317
|
|
|
318
318
|
Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -323,7 +323,7 @@ Show the generated patterns content and present choices:
|
|
|
323
323
|
|
|
324
324
|
- Append the final content to `{planning_artifacts}/architecture.md`
|
|
325
325
|
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
|
|
326
|
-
- Load
|
|
326
|
+
- Load `./step-06-structure.md`
|
|
327
327
|
|
|
328
328
|
## APPEND TO DOCUMENT:
|
|
329
329
|
|
|
@@ -354,6 +354,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
354
354
|
|
|
355
355
|
## NEXT STEP:
|
|
356
356
|
|
|
357
|
-
After user selects 'C' and content is saved to document, load
|
|
357
|
+
After user selects 'C' and content is saved to document, load `./step-06-structure.md` to define the complete project structure.
|
|
358
358
|
|
|
359
359
|
Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -343,7 +343,7 @@ Show the generated project structure content and present choices:
|
|
|
343
343
|
|
|
344
344
|
- Append the final content to `{planning_artifacts}/architecture.md`
|
|
345
345
|
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
|
|
346
|
-
- Load
|
|
346
|
+
- Load `./step-07-validation.md`
|
|
347
347
|
|
|
348
348
|
## APPEND TO DOCUMENT:
|
|
349
349
|
|
|
@@ -374,6 +374,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
374
374
|
|
|
375
375
|
## NEXT STEP:
|
|
376
376
|
|
|
377
|
-
After user selects 'C' and content is saved to document, load
|
|
377
|
+
After user selects 'C' and content is saved to document, load `./step-07-validation.md` to validate architectural coherence and completeness.
|
|
378
378
|
|
|
379
379
|
Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -323,7 +323,7 @@ Show the validation results and present choices:
|
|
|
323
323
|
|
|
324
324
|
- Append the final content to `{planning_artifacts}/architecture.md`
|
|
325
325
|
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`
|
|
326
|
-
- Load
|
|
326
|
+
- Load `./step-08-complete.md`
|
|
327
327
|
|
|
328
328
|
## APPEND TO DOCUMENT:
|
|
329
329
|
|
|
@@ -354,6 +354,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
354
354
|
|
|
355
355
|
## NEXT STEP:
|
|
356
356
|
|
|
357
|
-
After user selects 'C' and content is saved to document, load
|
|
357
|
+
After user selects 'C' and content is saved to document, load `./step-08-complete.md` to complete the workflow and provide implementation guidance.
|
|
358
358
|
|
|
359
359
|
Remember: Do NOT proceed to step-08 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/workflow.md
RENAMED
|
@@ -1,8 +1,3 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: create-architecture
|
|
3
|
-
description: 'Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"'
|
|
4
|
-
---
|
|
5
|
-
|
|
6
1
|
# Architecture Workflow
|
|
7
2
|
|
|
8
3
|
**Goal:** Create comprehensive architecture decisions through collaborative step-by-step discovery that ensures AI agents implement consistently.
|
|
@@ -36,7 +31,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|
|
36
31
|
|
|
37
32
|
### Paths
|
|
38
33
|
|
|
39
|
-
- `installed_path` =
|
|
34
|
+
- `installed_path` = `.`
|
|
40
35
|
- `template_path` = `{installed_path}/architecture-decision-template.md`
|
|
41
36
|
- `data_files_path` = `{installed_path}/data/`
|
|
42
37
|
|
|
@@ -44,6 +39,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|
|
44
39
|
|
|
45
40
|
## EXECUTION
|
|
46
41
|
|
|
47
|
-
Read fully and follow:
|
|
42
|
+
Read fully and follow: `./steps/step-01-init.md` to begin the workflow.
|
|
48
43
|
|
|
49
44
|
**Note:** Input document discovery and all initialization protocols are handled in step-01-init.md.
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|