bmad-method 6.1.1-next.3 → 6.1.1-next.5

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.
Files changed (20) hide show
  1. package/package.json +1 -1
  2. package/src/bmm/agents/analyst.agent.yaml +1 -1
  3. package/src/bmm/agents/dev.agent.yaml +1 -1
  4. package/src/bmm/module-help.csv +2 -2
  5. package/src/bmm/workflows/1-analysis/research/bmad-domain-research/SKILL.md +6 -0
  6. package/src/bmm/workflows/1-analysis/research/bmad-domain-research/bmad-skill-manifest.yaml +1 -0
  7. package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-01-init.md +2 -2
  8. package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-02-domain-analysis.md +2 -2
  9. package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-03-competitive-landscape.md +2 -2
  10. package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-04-regulatory-focus.md +2 -2
  11. package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-05-technical-trends.md +1 -1
  12. package/src/bmm/workflows/1-analysis/research/bmad-domain-research/research.template.md +29 -0
  13. package/src/bmm/workflows/1-analysis/research/{workflow-domain-research.md → bmad-domain-research/workflow.md} +0 -5
  14. package/src/bmm/workflows/1-analysis/research/bmad-skill-manifest.yaml +0 -5
  15. package/src/bmm/workflows/4-implementation/bmad-dev-story/SKILL.md +6 -0
  16. package/src/bmm/workflows/4-implementation/bmad-dev-story/bmad-skill-manifest.yaml +1 -0
  17. package/src/bmm/workflows/4-implementation/{dev-story → bmad-dev-story}/workflow.md +1 -7
  18. package/src/bmm/workflows/4-implementation/dev-story/bmad-skill-manifest.yaml +0 -3
  19. /package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-06-research-synthesis.md +0 -0
  20. /package/src/bmm/workflows/4-implementation/{dev-story → bmad-dev-story}/checklist.md +0 -0
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/package.json",
3
3
  "name": "bmad-method",
4
- "version": "6.1.1-next.3",
4
+ "version": "6.1.1-next.5",
5
5
  "description": "Breakthrough Method of Agile AI-driven Development",
6
6
  "keywords": [
7
7
  "agile",
@@ -27,7 +27,7 @@ agent:
27
27
  description: "[MR] Market Research: Market analysis, competitive landscape, customer needs and trends"
28
28
 
29
29
  - trigger: DR or fuzzy match on domain-research
30
- exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md"
30
+ exec: "skill:bmad-domain-research"
31
31
  description: "[DR] Domain Research: Industry domain deep dive, subject matter expertise and terminology"
32
32
 
33
33
  - trigger: TR or fuzzy match on technical-research
@@ -30,7 +30,7 @@ agent:
30
30
 
31
31
  menu:
32
32
  - trigger: DS or fuzzy match on dev-story
33
- exec: "{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.md"
33
+ exec: "skill:bmad-dev-story"
34
34
  description: "[DS] Dev Story: Write the next or specified stories tests and code."
35
35
 
36
36
  - trigger: CR or fuzzy match on code-review
@@ -12,7 +12,7 @@ bmm,anytime,Validate Document,VD,,_bmad/bmm/agents/tech-writer/tech-writer.agent
12
12
  bmm,anytime,Explain Concept,EC,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Create clear technical explanations with examples and diagrams for complex concepts. Breaks down into digestible sections using task-oriented approach.",project_knowledge,"explanation",
13
13
  bmm,1-analysis,Brainstorm Project,BP,10,skill:bmad-brainstorming,bmad-brainstorming,false,analyst,data=_bmad/bmm/data/project-context-template.md,"Expert Guided Facilitation through a single or multiple techniques",planning_artifacts,"brainstorming session",
14
14
  bmm,1-analysis,Market Research,MR,20,_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md,bmad-bmm-market-research,false,analyst,Create Mode,"Market analysis competitive landscape customer needs and trends","planning_artifacts|project-knowledge","research documents",
15
- bmm,1-analysis,Domain Research,DR,21,_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md,bmad-bmm-domain-research,false,analyst,Create Mode,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project_knowledge","research documents",
15
+ bmm,1-analysis,Domain Research,DR,21,skill:bmad-domain-research,bmad-bmm-domain-research,false,analyst,Create Mode,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project_knowledge","research documents",
16
16
  bmm,1-analysis,Technical Research,TR,22,_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md,bmad-bmm-technical-research,false,analyst,Create Mode,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project_knowledge","research documents",
17
17
  bmm,1-analysis,Create Brief,CB,30,_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md,bmad-bmm-create-product-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
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,
@@ -26,7 +26,7 @@ bmm,4-implementation,Sprint Planning,SP,10,_bmad/bmm/workflows/4-implementation/
26
26
  bmm,4-implementation,Sprint Status,SS,20,_bmad/bmm/workflows/4-implementation/sprint-status/workflow.md,bmad-bmm-sprint-status,false,sm,Create Mode,"Anytime: Summarize sprint status and route to next workflow",,,
27
27
  bmm,4-implementation,Validate Story,VS,35,skill:bmad-create-story,bmad-bmm-create-story,false,sm,Validate Mode,"Validates story readiness and completeness before development work begins",implementation_artifacts,"story validation report",
28
28
  bmm,4-implementation,Create Story,CS,30,skill:bmad-create-story,bmad-bmm-create-story,true,sm,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story,
29
- bmm,4-implementation,Dev Story,DS,40,_bmad/bmm/workflows/4-implementation/dev-story/workflow.md,bmad-bmm-dev-story,true,dev,Create Mode,"Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed",,,
29
+ bmm,4-implementation,Dev Story,DS,40,skill:bmad-dev-story,bmad-bmm-dev-story,true,dev,Create Mode,"Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed",,,
30
30
  bmm,4-implementation,Code Review,CR,50,_bmad/bmm/workflows/4-implementation/code-review/workflow.md,bmad-bmm-code-review,false,dev,Create Mode,"Story cycle: If issues back to DS if approved then next CS or ER if epic complete",,,
31
31
  bmm,4-implementation,QA Automation Test,QA,45,_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.md,bmad-bmm-qa-automate,false,qa,Create Mode,"Generate automated API and E2E tests for implemented code using the project's existing test framework (detects existing well known in use test frameworks). Use after implementation to add test coverage. NOT for code review or story validation - use CR for that.",implementation_artifacts,"test suite",
32
32
  bmm,4-implementation,Retrospective,ER,60,_bmad/bmm/workflows/4-implementation/retrospective/workflow.md,bmad-bmm-retrospective,false,sm,Create Mode,"Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC",implementation_artifacts,retrospective,
@@ -0,0 +1,6 @@
1
+ ---
2
+ name: bmad-domain-research
3
+ description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
4
+ ---
5
+
6
+ Follow the instructions in [workflow.md](workflow.md).
@@ -78,7 +78,7 @@ For **{{research_topic}}**, I will research:
78
78
 
79
79
  - Document scope confirmation in research file
80
80
  - Update frontmatter: `stepsCompleted: [1]`
81
- - Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md`
81
+ - Load: `./step-02-domain-analysis.md`
82
82
 
83
83
  ## APPEND TO DOCUMENT:
84
84
 
@@ -132,6 +132,6 @@ When user selects 'C', append scope confirmation:
132
132
 
133
133
  ## NEXT STEP:
134
134
 
135
- After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md` to begin industry analysis.
135
+ After user selects 'C', load `./step-02-domain-analysis.md` to begin industry analysis.
136
136
 
137
137
  Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!
@@ -171,7 +171,7 @@ _Source: [URL]_
171
171
 
172
172
  - **CONTENT ALREADY WRITTEN TO DOCUMENT**
173
173
  - Update frontmatter: `stepsCompleted: [1, 2]`
174
- - Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md`
174
+ - Load: `./step-03-competitive-landscape.md`
175
175
 
176
176
  ## APPEND TO DOCUMENT:
177
177
 
@@ -224,6 +224,6 @@ Content is already written to document when generated in step 4. No additional a
224
224
 
225
225
  ## NEXT STEP:
226
226
 
227
- After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
227
+ After user selects 'C', load `./step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
228
228
 
229
229
  Remember: Always write research content to document immediately and search the web to verify facts!
@@ -180,7 +180,7 @@ _Source: [URL]_
180
180
 
181
181
  - **CONTENT ALREADY WRITTEN TO DOCUMENT**
182
182
  - Update frontmatter: `stepsCompleted: [1, 2, 3]`
183
- - Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md`
183
+ - Load: `./step-04-regulatory-focus.md`
184
184
 
185
185
  ## APPEND TO DOCUMENT:
186
186
 
@@ -233,6 +233,6 @@ Content is already written to document when generated in step 4. No additional a
233
233
 
234
234
  ## NEXT STEP:
235
235
 
236
- After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}.
236
+ After user selects 'C', load `./step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}.
237
237
 
238
238
  Remember: Always write research content to document immediately and search the web to verify facts!
@@ -155,7 +155,7 @@ Show the generated regulatory analysis and present continue option:
155
155
 
156
156
  - **CONTENT ALREADY WRITTEN TO DOCUMENT**
157
157
  - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
158
- - Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md`
158
+ - Load: `./step-05-technical-trends.md`
159
159
 
160
160
  ## APPEND TO DOCUMENT:
161
161
 
@@ -201,6 +201,6 @@ Content is already written to document when generated in step 5. No additional a
201
201
 
202
202
  ## NEXT STEP:
203
203
 
204
- After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md` to analyze technical trends and innovations in the domain.
204
+ After user selects 'C' and content is saved to document, load `./step-05-technical-trends.md` to analyze technical trends and innovations in the domain.
205
205
 
206
206
  Remember: Search the web to verify regulatory facts and provide practical implementation considerations!
@@ -174,7 +174,7 @@ Show the generated technical analysis and present complete option:
174
174
 
175
175
  - **CONTENT ALREADY WRITTEN TO DOCUMENT**
176
176
  - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
177
- - Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md`
177
+ - Load: `./step-06-research-synthesis.md`
178
178
 
179
179
  ## APPEND TO DOCUMENT:
180
180
 
@@ -0,0 +1,29 @@
1
+ ---
2
+ stepsCompleted: []
3
+ inputDocuments: []
4
+ workflowType: 'research'
5
+ lastStep: 1
6
+ research_type: '{{research_type}}'
7
+ research_topic: '{{research_topic}}'
8
+ research_goals: '{{research_goals}}'
9
+ user_name: '{{user_name}}'
10
+ date: '{{date}}'
11
+ web_research_enabled: true
12
+ source_verification: true
13
+ ---
14
+
15
+ # Research Report: {{research_type}}
16
+
17
+ **Date:** {{date}}
18
+ **Author:** {{user_name}}
19
+ **Research Type:** {{research_type}}
20
+
21
+ ---
22
+
23
+ ## Research Overview
24
+
25
+ [Research overview and methodology will be appended here]
26
+
27
+ ---
28
+
29
+ <!-- Content will be appended sequentially through research workflow steps -->
@@ -1,8 +1,3 @@
1
- ---
2
- name: domain-research
3
- description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
4
- ---
5
-
6
1
  # Domain Research Workflow
7
2
 
8
3
  **Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
@@ -1,8 +1,3 @@
1
- workflow-domain-research.md:
2
- canonicalId: bmad-domain-research
3
- type: workflow
4
- description: "Conduct domain and industry research. Use when the user says 'lets create a research report on [domain or industry]'"
5
-
6
1
  workflow-market-research.md:
7
2
  canonicalId: bmad-market-research
8
3
  type: workflow
@@ -0,0 +1,6 @@
1
+ ---
2
+ name: bmad-dev-story
3
+ description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
4
+ ---
5
+
6
+ Follow the instructions in [workflow.md](workflow.md).
@@ -1,8 +1,3 @@
1
- ---
2
- name: dev-story
3
- description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
4
- ---
5
-
6
1
  # Dev Story Workflow
7
2
 
8
3
  **Goal:** Execute story implementation following a context filled story spec file.
@@ -32,8 +27,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
32
27
 
33
28
  ### Paths
34
29
 
35
- - `installed_path` = `{project-root}/_bmad/bmm/workflows/4-implementation/dev-story`
36
- - `validation` = `{installed_path}/checklist.md`
30
+ - `validation` = `./checklist.md`
37
31
  - `story_file` = `` (explicit story path; auto-discovered if empty)
38
32
  - `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
39
33
 
@@ -1,3 +0,0 @@
1
- canonicalId: bmad-dev-story
2
- type: workflow
3
- description: "Execute story implementation following a context-filled story spec file"