Skip to content

Commit 731bee2

Browse files
Brian MadisonBrian Madison
authored andcommitted
additional slash commands added that were missing from trivariate workflows
1 parent 5276d58 commit 731bee2

File tree

25 files changed

+238
-43
lines changed

25 files changed

+238
-43
lines changed

CHANGELOG.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1244,7 +1244,6 @@ Located in `src/modules/bmb/workflows/agent/data/`:
12441244

12451245
- **Workflow Vendoring**: Web bundler performs automatic cross-module dependency vendoring
12461246
- **BMGD Module Extraction**: Game development split into standalone 4-phase structure
1247-
- **Enhanced Dependency Resolution**: Better handling of web_bundle: false workflows
12481247
- **Advanced Elicitation Fix**: Added missing CSV files to workflow bundles
12491248
- **Claude Code Fix**: Resolved README slash command installation regression
12501249

src/bmm/module-help.csv

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -10,19 +10,15 @@ bmm,anytime,Mermaid Generate,MG,,_bmad/bmm/agents/tech-writer/tech-writer.agent.
1010
bmm,anytime,Validate Document,VD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Review the specified document against documentation standards and best practices. Returns specific actionable improvement suggestions organized by priority.",planning_artifacts,"validation report",
1111
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",
1212
bmm,1-analysis,Brainstorm Project,BP,10,_bmad/core/workflows/brainstorming/workflow.md,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",
13-
bmm,1-analysis,Market Research,MR,20,_bmad/bmm/workflows/1-analysis/research/workflow.md,bmad-bmm-research,false,analyst,Create Mode research_type=market,"Market analysis competitive landscape customer needs and trends","planning_artifacts|project-knowledge","research documents",
14-
bmm,1-analysis,Domain Research,DR,21,_bmad/bmm/workflows/1-analysis/research/workflow.md,bmad-bmm-research,false,analyst,Create Mode research_type=domain,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project_knowledge","research documents",
15-
bmm,1-analysis,Technical Research,TR,22,_bmad/bmm/workflows/1-analysis/research/workflow.md,bmad-bmm-research,false,analyst,Create Mode research_type=technical,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project_knowledge","research documents",
16-
bmm,1-analysis,Create Brief,CB,30,_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md,bmad-bmm-create-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
17-
bmm,1-analysis,Validate Brief,VB,40,_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md,bmad-bmm-validate-brief,false,analyst,Validate Mode,"Validates product brief completeness",planning_artifacts,"brief validation report",
18-
bmm,2-planning,Create PRD,CP,10,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
19-
bmm,2-planning,Validate PRD,VP,20,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow.md,bmad-bmm-validate-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report",
13+
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",
14+
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,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",
16+
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",
17+
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,
18+
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",
2019
bmm,2-planning,Create UX,CU,30,_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md,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",
21-
bmm,2-planning,Validate UX,VU,40,_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md,bmad-bmm-create-ux-design,false,ux-designer,Validate Mode,"Validates UX design deliverables",planning_artifacts,"ux validation report",
2220
bmm,3-solutioning,Create Architecture,CA,10,_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md,bmad-bmm-create-architecture,true,architect,Create Mode,"Guided Workflow to document technical decisions",planning_artifacts,architecture,
23-
bmm,3-solutioning,Validate Architecture,VA,20,_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md,bmad-bmm-create-architecture,false,architect,Validate Mode,"Validates architecture completeness",planning_artifacts,"architecture validation report",
2421
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",
25-
bmm,3-solutioning,Validate Epics and Stories,VE,40,_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md,bmad-bmm-create-epics-and-stories,false,pm,Validate Mode,"Validates epics and stories completeness",planning_artifacts,"epics validation report",
2622
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",
2723
bmm,4-implementation,Sprint Planning,SP,10,_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml,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",
2824
bmm,4-implementation,Sprint Status,SS,20,_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml,bmad-bmm-sprint-status,false,sm,Create Mode,"Anytime: Summarize sprint status and route to next workflow",,,

src/bmm/workflows/1-analysis/create-product-brief/workflow.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
name: create-product-brief
33
description: Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
4-
web_bundle: true
54
---
65

76
# Product Brief Workflow
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
name: domain-research
3+
description: Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.
4+
---
5+
6+
# Domain Research Workflow
7+
8+
**Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
9+
10+
**Your Role:** You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
11+
12+
## PREREQUISITE
13+
14+
**⛔ Web search required.** If unavailable, abort and tell the user.
15+
16+
## CONFIGURATION
17+
18+
Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
19+
- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
20+
- `communication_language`, `document_output_language`, `user_skill_level`
21+
- `date` as a system-generated value
22+
23+
## QUICK TOPIC DISCOVERY
24+
25+
"Welcome {{user_name}}! Let's get started with your **domain/industry research**.
26+
27+
**What domain, industry, or sector do you want to research?**
28+
29+
For example:
30+
- 'The healthcare technology industry'
31+
- 'Sustainable packaging regulations in Europe'
32+
- 'Construction and building materials sector'
33+
- 'Or any other domain you have in mind...'"
34+
35+
### Topic Clarification
36+
37+
Based on the user's topic, briefly clarify:
38+
1. **Core Domain**: "What specific aspect of [domain] are you most interested in?"
39+
2. **Research Goals**: "What do you hope to achieve with this research?"
40+
3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
41+
42+
## ROUTE TO DOMAIN RESEARCH STEPS
43+
44+
After gathering the topic and goals:
45+
46+
1. Set `research_type = "domain"`
47+
2. Set `research_topic = [discovered topic from discussion]`
48+
3. Set `research_goals = [discovered goals from discussion]`
49+
4. Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
50+
5. Load: `./domain-steps/step-01-init.md` with topic context
51+
52+
**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for domain research.
53+
54+
**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
name: market-research
3+
description: Conduct market research covering market size, growth, competition, and customer insights using current web data and verified sources.
4+
---
5+
6+
# Market Research Workflow
7+
8+
**Goal:** Conduct comprehensive market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
9+
10+
**Your Role:** You are a market research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
11+
12+
## PREREQUISITE
13+
14+
**⛔ Web search required.** If unavailable, abort and tell the user.
15+
16+
## CONFIGURATION
17+
18+
Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
19+
- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
20+
- `communication_language`, `document_output_language`, `user_skill_level`
21+
- `date` as a system-generated value
22+
23+
## QUICK TOPIC DISCOVERY
24+
25+
"Welcome {{user_name}}! Let's get started with your **market research**.
26+
27+
**What topic, problem, or area do you want to research?**
28+
29+
For example:
30+
- 'The electric vehicle market in Europe'
31+
- 'Plant-based food alternatives market'
32+
- 'Mobile payment solutions in Southeast Asia'
33+
- 'Or anything else you have in mind...'"
34+
35+
### Topic Clarification
36+
37+
Based on the user's topic, briefly clarify:
38+
1. **Core Topic**: "What exactly about [topic] are you most interested in?"
39+
2. **Research Goals**: "What do you hope to achieve with this research?"
40+
3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
41+
42+
## ROUTE TO MARKET RESEARCH STEPS
43+
44+
After gathering the topic and goals:
45+
46+
1. Set `research_type = "market"`
47+
2. Set `research_topic = [discovered topic from discussion]`
48+
3. Set `research_goals = [discovered goals from discussion]`
49+
4. Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
50+
5. Load: `./market-steps/step-01-init.md` with topic context
51+
52+
**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for market research.
53+
54+
**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
name: technical-research
3+
description: Conduct technical research covering technology evaluation, architecture decisions, and implementation approaches using current web data and verified sources.
4+
---
5+
6+
# Technical Research Workflow
7+
8+
**Goal:** Conduct comprehensive technical research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
9+
10+
**Your Role:** You are a technical research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
11+
12+
## PREREQUISITE
13+
14+
**⛔ Web search required.** If unavailable, abort and tell the user.
15+
16+
## CONFIGURATION
17+
18+
Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
19+
- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
20+
- `communication_language`, `document_output_language`, `user_skill_level`
21+
- `date` as a system-generated value
22+
23+
## QUICK TOPIC DISCOVERY
24+
25+
"Welcome {{user_name}}! Let's get started with your **technical research**.
26+
27+
**What technology, tool, or technical area do you want to research?**
28+
29+
For example:
30+
- 'React vs Vue for large-scale applications'
31+
- 'GraphQL vs REST API architectures'
32+
- 'Serverless deployment options for Node.js'
33+
- 'Or any other technical topic you have in mind...'"
34+
35+
### Topic Clarification
36+
37+
Based on the user's topic, briefly clarify:
38+
1. **Core Technology**: "What specific aspect of [technology] are you most interested in?"
39+
2. **Research Goals**: "What do you hope to achieve with this research?"
40+
3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
41+
42+
## ROUTE TO TECHNICAL RESEARCH STEPS
43+
44+
After gathering the topic and goals:
45+
46+
1. Set `research_type = "technical"`
47+
2. Set `research_topic = [discovered topic from discussion]`
48+
3. Set `research_goals = [discovered goals from discussion]`
49+
4. Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
50+
5. Load: `./technical-steps/step-01-init.md` with topic context
51+
52+
**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for technical research.
53+
54+
**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**

src/bmm/workflows/1-analysis/research/workflow.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
name: research
33
description: Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.
4-
web_bundle: true
54
---
65

76
# Research Workflow
Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
name: validate-prd
3+
description: Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality
4+
main_config: '{project-root}/_bmad/bmm/config.yaml'
5+
validateWorkflow: './steps-v/step-v-01-discovery.md'
6+
---
7+
8+
# PRD Validate Workflow
9+
10+
**Goal:** Validate existing PRDs against BMAD standards through comprehensive review.
11+
12+
**Your Role:** Validation Architect and Quality Assurance Specialist.
13+
14+
You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
15+
16+
## WORKFLOW ARCHITECTURE
17+
18+
This uses **step-file architecture** for disciplined execution:
19+
20+
### Core Principles
21+
22+
- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
23+
- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
24+
- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
25+
- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
26+
- **Append-Only Building**: Build documents by appending content as directed to the output file
27+
28+
### Step Processing Rules
29+
30+
1. **READ COMPLETELY**: Always read the entire step file before taking any action
31+
2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
32+
3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
33+
4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
34+
5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
35+
6. **LOAD NEXT**: When directed, read fully and follow the next step file
36+
37+
### Critical Rules (NO EXCEPTIONS)
38+
39+
- 🛑 **NEVER** load multiple step files simultaneously
40+
- 📖 **ALWAYS** read entire step file before execution
41+
- 🚫 **NEVER** skip steps or optimize the sequence
42+
- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
43+
- 🎯 **ALWAYS** follow the exact instructions in the step file
44+
- ⏸️ **ALWAYS** halt at menus and wait for user input
45+
- 📋 **NEVER** create mental todo lists from future steps
46+
47+
## INITIALIZATION SEQUENCE
48+
49+
### 1. Configuration Loading
50+
51+
Load and read full config from {main_config} and resolve:
52+
53+
- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
54+
- `communication_language`, `document_output_language`, `user_skill_level`
55+
- `date` as system-generated current datetime
56+
57+
✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
58+
59+
### 2. Route to Validate Workflow
60+
61+
"**Validate Mode: Validating an existing PRD against BMAD standards.**"
62+
63+
Prompt for PRD path: "Which PRD would you like to validate? Please provide the path to the PRD.md file."
64+
65+
Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)

src/bmm/workflows/2-plan-workflows/create-prd/workflow.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ main_config: '{project-root}/_bmad/bmm/config.yaml'
55
nextStep: './steps-c/step-01-init.md'
66
validateWorkflow: './steps-v/step-v-01-discovery.md'
77
editWorkflow: './steps-e/step-e-01-discovery.md'
8-
web_bundle: true
98
---
109

1110
# PRD Workflow (Tri-Modal)

src/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
name: create-ux-design
33
description: Work with a peer UX Design expert to plan your applications UX patterns, look and feel.
4-
web_bundle: true
54
---
65

76
# Create UX Design Workflow

0 commit comments

Comments
 (0)