ibnezzoubayr/L-Ami-Fiduciaire
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: L'Ami Fiduciaire V1.0.0 — full codebase with Story 0.1 complete

Browse Source 
Initial commit of the L'Ami Fiduciaire SaaS platform built on Laravel 12,
Vue 3, Inertia.js 2, and Tailwind CSS 4.

Story 0.1 (rename folders to declarations in database) is implemented and
code-reviewed: migration, rollback, and 6 Pest tests all passing.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Saad Ibn-Ezzoubayr
2026-03-11 23:33:10 +00:00
commit 35545c2a8f
1517 changed files with 246774 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

147
_bmad/bmb/workflows/module/steps-b/step-01-welcome.md Normal file
View File

@@ -0,0 +1,147 @@
---
name: 'step-01-welcome'
description: 'Welcome user, select mode (Interactive/Express/YOLO), gather initial idea'
nextStepFile: './step-02-spark.md'
briefTemplateFile: '../templates/brief-template.md'
moduleStandardsFile: '../data/module-standards.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 1: Welcome & Mode Selection
## STEP GOAL:
Welcome the user to the Module Brief workflow, select the collaboration mode (Interactive/Express/YOLO), and gather their initial module idea.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — creative, inspiring, helping users discover amazing module ideas
- ✅ This is explorative and collaborative — not a template-filling exercise
- ✅ Help users clarify and expand their vision
### Step-Specific Rules:
- 🎯 Set the creative tone — this is about discovering possibilities
- 🚫 FORBIDDEN to jump straight to technical details
- 💬 Ask questions that spark imagination
## EXECUTION PROTOCOLS:
- 🎯 Follow the MANDATORY SEQUENCE exactly
- 💾 No output file yet — gathering initial context
- 📖 Load next step when user selects 'C'
## CONTEXT BOUNDARIES:
- Available: module standards, brief template
- Focus: Initial idea gathering and mode selection
- No existing brief — this is a fresh start
---
## MANDATORY SEQUENCE
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
### 1. Welcome with Enthusiasm
"**Welcome to the Module Brief workflow!** 🚀
I'm here to help you create an amazing BMAD module. We'll explore your vision, design the agents and workflows, and create a comprehensive brief that will guide the module's creation.
Modules are powerful — they package agents, workflows, and configuration into a cohesive capability. Let's make something great!"
### 2. Select Collaboration Mode
"**How would you like to work?**"
- **[I]nteractive** — Deep collaboration, we'll explore each section together thoroughly
- **[E]xpress** — Faster pace, targeted questions to get to a solid brief quickly
- **[Y]OLO** — I'll generate a complete brief from minimal input (you can refine later)
**Store the selected mode. This affects how we proceed through subsequent steps.**
### 3. Gather the Initial Idea
"**Tell me about your module idea.**"
Encourage them to share:
- What problem does it solve?
- Who would use it?
- What excites you about it?
**If they're stuck**, offer creative prompts:
- "What domain do you work in? What tasks feel repetitive or could be AI-powered?"
- "Imagine you had a team of AI experts at your disposal — what would you ask them to build?"
- "Is there a module you wish existed?"
**Capture their initial idea.** We'll explore and expand it in the next steps.
### 4. Preview the Journey Ahead
"**Here's where we're going together:**"
1. Spark — Explore and clarify your idea
2. Module Type — Standalone, Extension, or Global?
3. Vision — What would make this extraordinary?
4. Identity — Name, code, personality
5. Users — Who is this for?
6. Value — What makes it special?
7. Agents — Who's on your team?
8. Workflows — What can we do?
9. Tools — MCP tools, integrations?
10. Scenarios — How will people use it?
11. Creative — Easter eggs, lore, magic ✨
12. Review — Read through together
13. Finalize — Your complete brief
"**This is about discovery and creativity. We're not filling out forms — we're designing something amazing together.**"
### 5. Present MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
#### EXECUTION RULES:
- ALWAYS halt and wait for user input
- ONLY proceed to next step when user selects 'C'
- User can chat or ask questions — always respond and redisplay menu
#### Menu Handling Logic:
- IF A: Execute `{advancedElicitationTask}` for deeper idea exploration, then redisplay menu
- IF P: Execute `{partyModeWorkflow}` for creative brainstorming, then redisplay menu
- IF C: Store the mode and initial idea, then load `{nextStepFile}`
- IF Any other: Help user, then redisplay menu
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- User feels welcomed and inspired
- Collaboration mode selected
- Initial idea captured
- User understands the journey ahead
### ❌ SYSTEM FAILURE:
- Skipping to technical details prematurely
- Not capturing the initial idea
- Not setting the creative tone
- Rushing through mode selection
**Master Rule:** This step sets the tone for the entire brief — make it inspiring and collaborative.

147
_bmad/bmb/workflows/module/steps-b/step-01-welcome.md.bak Normal file
View File

@@ -0,0 +1,147 @@
---
name: 'step-01-welcome'
description: 'Welcome user, select mode (Interactive/Express/YOLO), gather initial idea'
nextStepFile: './step-02-spark.md'
briefTemplateFile: '../templates/brief-template.md'
moduleStandardsFile: '../data/module-standards.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 1: Welcome & Mode Selection
## STEP GOAL:
Welcome the user to the Module Brief workflow, select the collaboration mode (Interactive/Express/YOLO), and gather their initial module idea.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — creative, inspiring, helping users discover amazing module ideas
- ✅ This is explorative and collaborative — not a template-filling exercise
- ✅ Help users clarify and expand their vision
### Step-Specific Rules:
- 🎯 Set the creative tone — this is about discovering possibilities
- 🚫 FORBIDDEN to jump straight to technical details
- 💬 Ask questions that spark imagination
## EXECUTION PROTOCOLS:
- 🎯 Follow the MANDATORY SEQUENCE exactly
- 💾 No output file yet — gathering initial context
- 📖 Load next step when user selects 'C'
## CONTEXT BOUNDARIES:
- Available: module standards, brief template
- Focus: Initial idea gathering and mode selection
- No existing brief — this is a fresh start
---
## MANDATORY SEQUENCE
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
### 1. Welcome with Enthusiasm
"**Welcome to the Module Brief workflow!** 🚀
I'm here to help you create an amazing BMAD module. We'll explore your vision, design the agents and workflows, and create a comprehensive brief that will guide the module's creation.
Modules are powerful — they package agents, workflows, and configuration into a cohesive capability. Let's make something great!"
### 2. Select Collaboration Mode
"**How would you like to work?**"
- **[I]nteractive** — Deep collaboration, we'll explore each section together thoroughly
- **[E]xpress** — Faster pace, targeted questions to get to a solid brief quickly
- **[Y]OLO** — I'll generate a complete brief from minimal input (you can refine later)
**Store the selected mode. This affects how we proceed through subsequent steps.**
### 3. Gather the Initial Idea
"**Tell me about your module idea.**"
Encourage them to share:
- What problem does it solve?
- Who would use it?
- What excites you about it?
**If they're stuck**, offer creative prompts:
- "What domain do you work in? What tasks feel repetitive or could be AI-powered?"
- "Imagine you had a team of AI experts at your disposal — what would you ask them to build?"
- "Is there a module you wish existed?"
**Capture their initial idea.** We'll explore and expand it in the next steps.
### 4. Preview the Journey Ahead
"**Here's where we're going together:**"
1. Spark — Explore and clarify your idea
2. Module Type — Standalone, Extension, or Global?
3. Vision — What would make this extraordinary?
4. Identity — Name, code, personality
5. Users — Who is this for?
6. Value — What makes it special?
7. Agents — Who's on your team?
8. Workflows — What can we do?
9. Tools — MCP tools, integrations?
10. Scenarios — How will people use it?
11. Creative — Easter eggs, lore, magic ✨
12. Review — Read through together
13. Finalize — Your complete brief
"**This is about discovery and creativity. We're not filling out forms — we're designing something amazing together.**"
### 5. Present MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
#### EXECUTION RULES:
- ALWAYS halt and wait for user input
- ONLY proceed to next step when user selects 'C'
- User can chat or ask questions — always respond and redisplay menu
#### Menu Handling Logic:
- IF A: Execute `{advancedElicitationTask}` for deeper idea exploration, then redisplay menu
- IF P: Execute `{partyModeWorkflow}` for creative brainstorming, then redisplay menu
- IF C: Store the mode and initial idea, then load `{nextStepFile}`
- IF Any other: Help user, then redisplay menu
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- User feels welcomed and inspired
- Collaboration mode selected
- Initial idea captured
- User understands the journey ahead
### ❌ SYSTEM FAILURE:
- Skipping to technical details prematurely
- Not capturing the initial idea
- Not setting the creative tone
- Rushing through mode selection
**Master Rule:** This step sets the tone for the entire brief — make it inspiring and collaborative.

140
_bmad/bmb/workflows/module/steps-b/step-02-spark.md Normal file
View File

@@ -0,0 +1,140 @@
---
name: 'step-02-spark'
description: 'Ignite the idea, explore problem space, what excites them'
nextStepFile: './step-03-module-type.md'
moduleStandardsFile: '../data/module-standards.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 2: Spark
## STEP GOAL:
Ignite and explore the user's idea — dig into the problem space, understand what excites them, and help clarify the vision.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — curious, explorative, helping ideas grow
- ✅ Ask open-ended questions that reveal depth
- ✅ Listen more than you speak
### Step-Specific Rules:
- 🎯 This is about understanding the problem space, not solving it yet
- 🚫 FORBIDDEN to jump to implementation
- 💬 Ask "why" and "what if" questions
## EXECUTION PROTOCOLS:
- 🎯 Follow the MANDATORY SEQUENCE exactly
- 📖 Reference module standards to understand types
- 📖 Load next step when user selects 'C'
---
## MANDATORY SEQUENCE
**CRITICAL:** Follow this sequence exactly.
### 1. Connect to Their Idea
"**Let's explore your idea together.**"
Reference what they shared in step 1:
- "You mentioned {their idea} — I love that direction."
- "Tell me more about the problem you're solving."
### 2. Explore the Problem Space
Ask questions to deepen understanding:
**"What problem does this module solve?"**
- Who feels this problem right now?
- What do they currently do without this module?
- What would change if this existed?
**"What excites you about this idea?"**
- Why THIS module? Why now?
- What's the vision — the dream outcome?
- If this module succeeds wildly, what does that look like?
### 3. Identify the Users
**"Who is this module for?"**
Help them think about:
- Primary users — who will use this most?
- Secondary users — who else benefits?
- What do these users care about?
### 4. Adjust for Mode
**IF mode == Interactive:**
- Deep exploration, multiple rounds of questions
- Use Advanced Elicitation if they want to dig deeper
**IF mode == Express:**
- Targeted questions, get the key insights quickly
- 2-3 rounds max
**IF mode == YOLO:**
- Brief clarification, acknowledge what you have
- Move quickly to next step
### 5. Capture Insights
Summarize what you've learned:
- "So the core problem is {summary}"
- "The primary users are {users}"
- "What excites you most is {excitement}"
"**Does this capture your vision? Anything to add or refine?**"
### 6. Present MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
#### EXECUTION RULES:
- ALWAYS halt and wait for user input
- ONLY proceed to next step when user selects 'C'
#### Menu Handling Logic:
- IF A: Execute `{advancedElicitationTask}` for deeper exploration
- IF P: Execute `{partyModeWorkflow}` for creative ideation
- IF C: Load `{nextStepFile}`
- IF Any other: Help user, then redisplay menu
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- Problem space clearly understood
- User excitement identified
- Target users clarified
- Vision feels solid
### ❌ SYSTEM FAILURE:
- Skipping to solutions too quickly
- Not understanding the problem
- Not capturing what excites them
**Master Rule:** Understand before you build. This step is about clarity, not solutions.

140
_bmad/bmb/workflows/module/steps-b/step-02-spark.md.bak Normal file
View File

@@ -0,0 +1,140 @@
---
name: 'step-02-spark'
description: 'Ignite the idea, explore problem space, what excites them'
nextStepFile: './step-03-module-type.md'
moduleStandardsFile: '../data/module-standards.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 2: Spark
## STEP GOAL:
Ignite and explore the user's idea — dig into the problem space, understand what excites them, and help clarify the vision.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — curious, explorative, helping ideas grow
- ✅ Ask open-ended questions that reveal depth
- ✅ Listen more than you speak
### Step-Specific Rules:
- 🎯 This is about understanding the problem space, not solving it yet
- 🚫 FORBIDDEN to jump to implementation
- 💬 Ask "why" and "what if" questions
## EXECUTION PROTOCOLS:
- 🎯 Follow the MANDATORY SEQUENCE exactly
- 📖 Reference module standards to understand types
- 📖 Load next step when user selects 'C'
---
## MANDATORY SEQUENCE
**CRITICAL:** Follow this sequence exactly.
### 1. Connect to Their Idea
"**Let's explore your idea together.**"
Reference what they shared in step 1:
- "You mentioned {their idea} — I love that direction."
- "Tell me more about the problem you're solving."
### 2. Explore the Problem Space
Ask questions to deepen understanding:
**"What problem does this module solve?"**
- Who feels this problem right now?
- What do they currently do without this module?
- What would change if this existed?
**"What excites you about this idea?"**
- Why THIS module? Why now?
- What's the vision — the dream outcome?
- If this module succeeds wildly, what does that look like?
### 3. Identify the Users
**"Who is this module for?"**
Help them think about:
- Primary users — who will use this most?
- Secondary users — who else benefits?
- What do these users care about?
### 4. Adjust for Mode
**IF mode == Interactive:**
- Deep exploration, multiple rounds of questions
- Use Advanced Elicitation if they want to dig deeper
**IF mode == Express:**
- Targeted questions, get the key insights quickly
- 2-3 rounds max
**IF mode == YOLO:**
- Brief clarification, acknowledge what you have
- Move quickly to next step
### 5. Capture Insights
Summarize what you've learned:
- "So the core problem is {summary}"
- "The primary users are {users}"
- "What excites you most is {excitement}"
"**Does this capture your vision? Anything to add or refine?**"
### 6. Present MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
#### EXECUTION RULES:
- ALWAYS halt and wait for user input
- ONLY proceed to next step when user selects 'C'
#### Menu Handling Logic:
- IF A: Execute `{advancedElicitationTask}` for deeper exploration
- IF P: Execute `{partyModeWorkflow}` for creative ideation
- IF C: Load `{nextStepFile}`
- IF Any other: Help user, then redisplay menu
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- Problem space clearly understood
- User excitement identified
- Target users clarified
- Vision feels solid
### ❌ SYSTEM FAILURE:
- Skipping to solutions too quickly
- Not understanding the problem
- Not capturing what excites them
**Master Rule:** Understand before you build. This step is about clarity, not solutions.

148
_bmad/bmb/workflows/module/steps-b/step-03-module-type.md Normal file
View File

@@ -0,0 +1,148 @@
---
name: 'step-03-module-type'
description: 'EARLY decision: Standalone, Extension, or Global module?'
nextStepFile: './step-04-vision.md'
moduleStandardsFile: '../data/module-standards.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 3: Module Type
## STEP GOAL:
Make the EARLY key decision: Is this a Standalone, Extension, or Global module? This decision affects everything that follows.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — you understand module types and their implications
- ✅ Help the user make an informed decision
- ✅ This is a commitment — get it right
### Step-Specific Rules:
- 🎯 This decision MUST happen early
- 🚫 FORBIDDEN to proceed without clarity on module type
- 💬 Explain the trade-offs clearly
## EXECUTION PROTOCOLS:
- 🎯 Load `{moduleStandardsFile}` to reference module types
- 🎯 Follow the MANDATORY SEQUENCE exactly
- 📖 Load next step when user selects 'C'
---
## MANDATORY SEQUENCE
**CRITICAL:** Follow this sequence exactly.
### 1. Explain Module Types
Load `{moduleStandardsFile}` and present the three types:
"**Before we go further, we need to decide: What type of module is this?** This decision affects where files go, how installation works, and how the module integrates with BMAD."
**Standalone Module:**
- A new, independent module
- Own module code and identity
- Installed alongside other modules
- Example: CIS — a creative innovation suite
**Extension Module:**
- Extends an existing BMAD module
- Shares the base module's code (e.g., `code: bmm`)
- Adds or overrides agents/workflows
- Example: A security extension for BMM
**Global Module:**
- Affects the entire BMAD framework
- Core functionality impacting all modules
- Rare — use sparingly
- Example: Universal logging/telemetry
### 2. Determine Type Together
**"Based on your idea, what type makes sense?"**
Help them think through:
- **"Is this a brand new domain?"** → Likely Standalone
- **"Does this build on an existing module?"** → Likely Extension
- **"Does this affect all modules?"** → Possibly Global (be cautious)
**If considering Extension:**
- "Which existing module does it extend?"
- "Are you adding new agents/workflows, or modifying existing ones?"
- "This means your `code:` will match the base module"
**If considering Global:**
- "Are you sure? Global modules are rare."
- "Could this be a standalone module instead?"
### 3. Confirm and Store
Once decided:
"**Module Type: {Standalone/Extension/Global}**"
**IF Extension:**
"Base module to extend: {base-module-code}"
"Folder name will be unique: {e.g., bmm-security}"
**Store this decision.** It affects:
- Where files are created
- What `code:` goes in module.yaml
- Installation behavior
### 4. Preview Implications
Briefly explain what this means:
- "As a {type}, your module will {implications}"
- "When we build, files will go to {location}"
### 5. Present MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
#### EXECUTION RULES:
- ALWAYS halt and wait for user input
- User can change their mind before proceeding
- ONLY proceed to next step when user selects 'C' and confirms the type
#### Menu Handling Logic:
- IF A: Execute `{advancedElicitationTask}` for deeper exploration of the decision
- IF P: Execute `{partyModeWorkflow}` for brainstorming the approach
- IF C: Confirm the decision, then load `{nextStepFile}`
- IF Any other: Help user, then redisplay menu
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- Module type clearly decided
- User understands the implications
- Extension modules know their base module
- Decision is stored for later steps
### ❌ SYSTEM FAILURE:
- Proceeding without clear module type
- User doesn't understand the implications
- Extension module without clear base
**Master Rule:** This is a gateway decision. Get clarity before moving forward.

148
_bmad/bmb/workflows/module/steps-b/step-03-module-type.md.bak Normal file
View File

@@ -0,0 +1,148 @@
---
name: 'step-03-module-type'
description: 'EARLY decision: Standalone, Extension, or Global module?'
nextStepFile: './step-04-vision.md'
moduleStandardsFile: '../data/module-standards.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 3: Module Type
## STEP GOAL:
Make the EARLY key decision: Is this a Standalone, Extension, or Global module? This decision affects everything that follows.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — you understand module types and their implications
- ✅ Help the user make an informed decision
- ✅ This is a commitment — get it right
### Step-Specific Rules:
- 🎯 This decision MUST happen early
- 🚫 FORBIDDEN to proceed without clarity on module type
- 💬 Explain the trade-offs clearly
## EXECUTION PROTOCOLS:
- 🎯 Load `{moduleStandardsFile}` to reference module types
- 🎯 Follow the MANDATORY SEQUENCE exactly
- 📖 Load next step when user selects 'C'
---
## MANDATORY SEQUENCE
**CRITICAL:** Follow this sequence exactly.
### 1. Explain Module Types
Load `{moduleStandardsFile}` and present the three types:
"**Before we go further, we need to decide: What type of module is this?** This decision affects where files go, how installation works, and how the module integrates with BMAD."
**Standalone Module:**
- A new, independent module
- Own module code and identity
- Installed alongside other modules
- Example: CIS — a creative innovation suite
**Extension Module:**
- Extends an existing BMAD module
- Shares the base module's code (e.g., `code: bmm`)
- Adds or overrides agents/workflows
- Example: A security extension for BMM
**Global Module:**
- Affects the entire BMAD framework
- Core functionality impacting all modules
- Rare — use sparingly
- Example: Universal logging/telemetry
### 2. Determine Type Together
**"Based on your idea, what type makes sense?"**
Help them think through:
- **"Is this a brand new domain?"** → Likely Standalone
- **"Does this build on an existing module?"** → Likely Extension
- **"Does this affect all modules?"** → Possibly Global (be cautious)
**If considering Extension:**
- "Which existing module does it extend?"
- "Are you adding new agents/workflows, or modifying existing ones?"
- "This means your `code:` will match the base module"
**If considering Global:**
- "Are you sure? Global modules are rare."
- "Could this be a standalone module instead?"
### 3. Confirm and Store
Once decided:
"**Module Type: {Standalone/Extension/Global}**"
**IF Extension:**
"Base module to extend: {base-module-code}"
"Folder name will be unique: {e.g., bmm-security}"
**Store this decision.** It affects:
- Where files are created
- What `code:` goes in module.yaml
- Installation behavior
### 4. Preview Implications
Briefly explain what this means:
- "As a {type}, your module will {implications}"
- "When we build, files will go to {location}"
### 5. Present MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
#### EXECUTION RULES:
- ALWAYS halt and wait for user input
- User can change their mind before proceeding
- ONLY proceed to next step when user selects 'C' and confirms the type
#### Menu Handling Logic:
- IF A: Execute `{advancedElicitationTask}` for deeper exploration of the decision
- IF P: Execute `{partyModeWorkflow}` for brainstorming the approach
- IF C: Confirm the decision, then load `{nextStepFile}`
- IF Any other: Help user, then redisplay menu
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- Module type clearly decided
- User understands the implications
- Extension modules know their base module
- Decision is stored for later steps
### ❌ SYSTEM FAILURE:
- Proceeding without clear module type
- User doesn't understand the implications
- Extension module without clear base
**Master Rule:** This is a gateway decision. Get clarity before moving forward.

82
_bmad/bmb/workflows/module/steps-b/step-04-vision.md Normal file
View File

@@ -0,0 +1,82 @@
---
name: 'step-04-vision'
description: 'Deep dive into the vision — what would make this module extraordinary?'
nextStepFile: './step-05-identity.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 4: Vision
## STEP GOAL:
Deep dive into the vision — explore what would make this module extraordinary, not just functional.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — visioning, dreaming big
- ✅ Push beyond "good enough" to "extraordinary"
- 💬 Ask "what would make this amazing?"
### Step-Specific Rules:
- 🎯 This is about the vision, not the details
- 🚫 FORBIDDEN to jump to implementation
---
## MANDATORY SEQUENCE
### 1. Set the Visioning Tone
"**Let's dream big. What would make this module extraordinary?**"
"Good modules solve problems. Great modules inspire people. Let's make yours great."
### 2. Explore the Vision
Ask visioning questions:
**"If this module succeeds wildly, what does that look like?"**
- How are people using it?
- What are they able to do that they couldn't before?
- What's the feeling when they use it?
**"What would make someone say 'I love this module'?"**
- Delightful features?
- Surprising capabilities?
- The way it makes them feel?
**"What's the 'secret sauce' — the thing that makes this special?"**
### 3. Capture the Vision
Summarize:
- "Your vision: {summary}"
- "What makes it special: {unique aspect}"
- "The dream outcome: {dream}"
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Vision feels inspiring and clear
✅ "Extraordinary" elements identified
✅ User excited about the possibility

82
_bmad/bmb/workflows/module/steps-b/step-04-vision.md.bak Normal file
View File

@@ -0,0 +1,82 @@
---
name: 'step-04-vision'
description: 'Deep dive into the vision — what would make this module extraordinary?'
nextStepFile: './step-05-identity.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 4: Vision
## STEP GOAL:
Deep dive into the vision — explore what would make this module extraordinary, not just functional.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — visioning, dreaming big
- ✅ Push beyond "good enough" to "extraordinary"
- 💬 Ask "what would make this amazing?"
### Step-Specific Rules:
- 🎯 This is about the vision, not the details
- 🚫 FORBIDDEN to jump to implementation
---
## MANDATORY SEQUENCE
### 1. Set the Visioning Tone
"**Let's dream big. What would make this module extraordinary?**"
"Good modules solve problems. Great modules inspire people. Let's make yours great."
### 2. Explore the Vision
Ask visioning questions:
**"If this module succeeds wildly, what does that look like?"**
- How are people using it?
- What are they able to do that they couldn't before?
- What's the feeling when they use it?
**"What would make someone say 'I love this module'?"**
- Delightful features?
- Surprising capabilities?
- The way it makes them feel?
**"What's the 'secret sauce' — the thing that makes this special?"**
### 3. Capture the Vision
Summarize:
- "Your vision: {summary}"
- "What makes it special: {unique aspect}"
- "The dream outcome: {dream}"
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Vision feels inspiring and clear
✅ "Extraordinary" elements identified
✅ User excited about the possibility

96
_bmad/bmb/workflows/module/steps-b/step-05-identity.md Normal file
View File

@@ -0,0 +1,96 @@
---
name: 'step-05-identity'
description: 'Module code, name, and personality/theme'
nextStepFile: './step-06-users.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 5: Identity
## STEP GOAL:
Define the module's identity — code, name, and personality/theme.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — naming, branding, theming
- ✅ This is where personality comes in
- 💬 Have fun with this!
### Step-Specific Rules:
- 🎯 Module code follows conventions (kebab-case, 2-20 chars)
- 🚫 FORBIDDEN to use reserved codes or existing module codes (for standalone)
---
## MANDATORY SEQUENCE
### 1. Module Code
"**Let's give your module a code.**"
Explain:
- kebab-case (e.g., `bmm`, `cis`, `healthcare-ai`)
- Short, memorable, descriptive
- 2-20 characters
**IF Extension:** Code matches base module (already decided)
**IF Standalone:** Propose options based on the module name/domain
### 2. Module Name
"**What's the display name?**"
This is the human-facing name in module.yaml:
- "BMM: BMad Method Agile-AI Driven-Development"
- "CIS: Creative Innovation Suite"
- "Your Module: Your Description"
### 3. Personality Theme
"**Does your module have a personality or theme?**"
Some modules have fun themes:
- BMM — Agile team (personas like John, Winston)
- CIS — Creative innovators
- BMGD — Game dev team
**Questions:**
- Should the agents have a consistent theme?
- Any personality vibes? (Corporate team, fantasy party, reality show cast?)
- Or keep it professional/focused?
### 4. Store Identity
Capture:
- Module code: `{code}`
- Module name: `{name}`
- Personality theme: `{theme or "none/professional"}`
### 5. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Module code decided and validated
✅ Module name defined
✅ Personality theme decided (even if "none")

96
_bmad/bmb/workflows/module/steps-b/step-05-identity.md.bak Normal file
View File

@@ -0,0 +1,96 @@
---
name: 'step-05-identity'
description: 'Module code, name, and personality/theme'
nextStepFile: './step-06-users.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 5: Identity
## STEP GOAL:
Define the module's identity — code, name, and personality/theme.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — naming, branding, theming
- ✅ This is where personality comes in
- 💬 Have fun with this!
### Step-Specific Rules:
- 🎯 Module code follows conventions (kebab-case, 2-20 chars)
- 🚫 FORBIDDEN to use reserved codes or existing module codes (for standalone)
---
## MANDATORY SEQUENCE
### 1. Module Code
"**Let's give your module a code.**"
Explain:
- kebab-case (e.g., `bmm`, `cis`, `healthcare-ai`)
- Short, memorable, descriptive
- 2-20 characters
**IF Extension:** Code matches base module (already decided)
**IF Standalone:** Propose options based on the module name/domain
### 2. Module Name
"**What's the display name?**"
This is the human-facing name in module.yaml:
- "BMM: BMad Method Agile-AI Driven-Development"
- "CIS: Creative Innovation Suite"
- "Your Module: Your Description"
### 3. Personality Theme
"**Does your module have a personality or theme?**"
Some modules have fun themes:
- BMM — Agile team (personas like John, Winston)
- CIS — Creative innovators
- BMGD — Game dev team
**Questions:**
- Should the agents have a consistent theme?
- Any personality vibes? (Corporate team, fantasy party, reality show cast?)
- Or keep it professional/focused?
### 4. Store Identity
Capture:
- Module code: `{code}`
- Module name: `{name}`
- Personality theme: `{theme or "none/professional"}`
### 5. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Module code decided and validated
✅ Module name defined
✅ Personality theme decided (even if "none")

85
_bmad/bmb/workflows/module/steps-b/step-06-users.md Normal file
View File

@@ -0,0 +1,85 @@
---
name: 'step-06-users'
description: 'Who + How — personas AND user journey combined'
nextStepFile: './step-07-value.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 6: Users
## STEP GOAL:
Define who the module is for AND how they'll use it — personas and user journey combined.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — user-centric, empathetic
- ✅ Help the user walk in their users' shoes
- 💬 Tell the story of how this will be used
---
## MANDATORY SEQUENCE
### 1. Define the Users
"**Let's get specific about who this is for.**"
**Primary Users:**
- Who will use this module most often?
- What's their role? (developer, designer, analyst, etc.)
- What's their skill level? (beginner, intermediate, expert)
**Secondary Users:**
- Who else might use it?
- How is their experience different?
### 2. Build User Personas
Create 1-2 brief personas:
**Persona 1:**
- Name/role: {e.g., "Sarah, Software Engineer"}
- Goals: {what they want to accomplish}
- Pain points: {what frustrates them now}
- What success looks like
### 3. Tell the User Journey Story
"**Let's walk through how someone would use this module.**"
Tell a story:
1. User has a problem → {their situation}
2. They load the module → {what they expect}
3. They run an agent/workflow → {what happens}
4. They get a result → {the outcome}
5. This helps them → {the achievement}
"**Can you see this flow? Does it match what you envision?**"
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ User personas defined
✅ User journey story told
✅ User can visualize how their module will be used

85
_bmad/bmb/workflows/module/steps-b/step-06-users.md.bak Normal file
View File

@@ -0,0 +1,85 @@
---
name: 'step-06-users'
description: 'Who + How — personas AND user journey combined'
nextStepFile: './step-07-value.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 6: Users
## STEP GOAL:
Define who the module is for AND how they'll use it — personas and user journey combined.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — user-centric, empathetic
- ✅ Help the user walk in their users' shoes
- 💬 Tell the story of how this will be used
---
## MANDATORY SEQUENCE
### 1. Define the Users
"**Let's get specific about who this is for.**"
**Primary Users:**
- Who will use this module most often?
- What's their role? (developer, designer, analyst, etc.)
- What's their skill level? (beginner, intermediate, expert)
**Secondary Users:**
- Who else might use it?
- How is their experience different?
### 2. Build User Personas
Create 1-2 brief personas:
**Persona 1:**
- Name/role: {e.g., "Sarah, Software Engineer"}
- Goals: {what they want to accomplish}
- Pain points: {what frustrates them now}
- What success looks like
### 3. Tell the User Journey Story
"**Let's walk through how someone would use this module.**"
Tell a story:
1. User has a problem → {their situation}
2. They load the module → {what they expect}
3. They run an agent/workflow → {what happens}
4. They get a result → {the outcome}
5. This helps them → {the achievement}
"**Can you see this flow? Does it match what you envision?**"
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ User personas defined
✅ User journey story told
✅ User can visualize how their module will be used

75
_bmad/bmb/workflows/module/steps-b/step-07-value.md Normal file
View File

@@ -0,0 +1,75 @@
---
name: 'step-07-value'
description: 'Unique Value Proposition — what makes this module special?'
nextStepFile: './step-08-agents.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 7: Value
## STEP GOAL:
Define the Unique Value Proposition — what makes this module special and why users would choose it.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — focused on differentiation
- ✅ Help identify what makes this unique
- 💬 Ask "why this and not something else?"
---
## MANDATORY SEQUENCE
### 1. Explore Differentiation
"**What makes your module special? Why would someone choose it?**"
Ask:
- **What can users do with your module that they can't do otherwise?**
- **What's the 'aha!' moment — when they realize this is exactly what they need?**
- **What problem does this solve better than anything else?**
### 2. Identify the Unique Value Proposition
Help craft a clear statement:
**"For {target users}, {module name} provides {key benefit} unlike {alternatives} because {unique differentiator}."**
Example:
"For software teams, BMM provides AI-driven agile delivery unlike manual processes because it orchestrates specialized agents for every phase of development."
### 3. Competitive Context
**"What else exists in this space? How is yours different?"**
- Similar modules?
- Manual approaches?
- Why is yours better?
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Unique value proposition articulated
✅ Differentiation from alternatives clear
✅ User can explain why someone would choose this module

75
_bmad/bmb/workflows/module/steps-b/step-07-value.md.bak Normal file
View File

@@ -0,0 +1,75 @@
---
name: 'step-07-value'
description: 'Unique Value Proposition — what makes this module special?'
nextStepFile: './step-08-agents.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 7: Value
## STEP GOAL:
Define the Unique Value Proposition — what makes this module special and why users would choose it.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — focused on differentiation
- ✅ Help identify what makes this unique
- 💬 Ask "why this and not something else?"
---
## MANDATORY SEQUENCE
### 1. Explore Differentiation
"**What makes your module special? Why would someone choose it?**"
Ask:
- **What can users do with your module that they can't do otherwise?**
- **What's the 'aha!' moment — when they realize this is exactly what they need?**
- **What problem does this solve better than anything else?**
### 2. Identify the Unique Value Proposition
Help craft a clear statement:
**"For {target users}, {module name} provides {key benefit} unlike {alternatives} because {unique differentiator}."**
Example:
"For software teams, BMM provides AI-driven agile delivery unlike manual processes because it orchestrates specialized agents for every phase of development."
### 3. Competitive Context
**"What else exists in this space? How is yours different?"**
- Similar modules?
- Manual approaches?
- Why is yours better?
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Unique value proposition articulated
✅ Differentiation from alternatives clear
✅ User can explain why someone would choose this module

96
_bmad/bmb/workflows/module/steps-b/step-08-agents.md Normal file
View File

@@ -0,0 +1,96 @@
---
name: 'step-08-agents'
description: 'Agent architecture — party mode simulation of interactions'
nextStepFile: './step-09-workflows.md'
agentArchitectureFile: '../data/agent-architecture.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 8: Agents
## STEP GOAL:
Design the agent architecture — who's on your team? Simulate how agents might interact.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — team designer
- ✅ Focus on high-level planning (role, workflows, name, style)
- ✅ Don't worry about YAML format — agent-builder handles that
### Step-Specific Rules:
- 🎯 Load `{agentArchitectureFile}` for guidance
- 🎯 Party mode is great here — simulate agent interactions
- 🚫 FORBIDDEN to design full agent specs (that's agent-builder's job)
---
## MANDATORY SEQUENCE
### 1. Single vs Multi-Agent
Load `{agentArchitectureFile}` and ask:
**"Could one expert agent handle this entire module, or do you need a team?"**
Reference:
- **Single agent** — simpler, focused domain
- **Multi-agent** — different expertise areas, broader domain
- **BMM example** — 9 agents for complete software development team
### 2. Design the Agent Team
For each agent, capture:
**Role:** What are they responsible for?
**Workflows:** Which workflows will they trigger?
**Name:** Human name (optional, for personality)
**Communication Style:** How do they talk?
**Memory:** Do they need to remember things over time? (hasSidecar)
Keep it high-level — don't design full agent specs!
### 3. Party Mode Simulation
**"Want to simulate how your agents might interact?"**
- IF yes: Execute `{partyModeWorkflow}` with different agent personas
- Let them "talk" to each other about a scenario
- This reveals how the team works together
### 4. Agent Menu Coordination
Explain the pattern:
- **Shared commands** — all agents have `[WS]` Workflow Status
- **Specialty commands** — each agent has unique commands
- **No overlap** — each command has one owner
"**What commands might each agent have?**"
### 5. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}` — great for agent interaction simulation
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Single vs multi-agent decided
✅ Agent roles defined
✅ Agent-workflow mappings clear
✅ Agent interactions explored (via party mode if used)

96
_bmad/bmb/workflows/module/steps-b/step-08-agents.md.bak Normal file
View File

@@ -0,0 +1,96 @@
---
name: 'step-08-agents'
description: 'Agent architecture — party mode simulation of interactions'
nextStepFile: './step-09-workflows.md'
agentArchitectureFile: '../data/agent-architecture.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 8: Agents
## STEP GOAL:
Design the agent architecture — who's on your team? Simulate how agents might interact.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — team designer
- ✅ Focus on high-level planning (role, workflows, name, style)
- ✅ Don't worry about YAML format — agent-builder handles that
### Step-Specific Rules:
- 🎯 Load `{agentArchitectureFile}` for guidance
- 🎯 Party mode is great here — simulate agent interactions
- 🚫 FORBIDDEN to design full agent specs (that's agent-builder's job)
---
## MANDATORY SEQUENCE
### 1. Single vs Multi-Agent
Load `{agentArchitectureFile}` and ask:
**"Could one expert agent handle this entire module, or do you need a team?"**
Reference:
- **Single agent** — simpler, focused domain
- **Multi-agent** — different expertise areas, broader domain
- **BMM example** — 9 agents for complete software development team
### 2. Design the Agent Team
For each agent, capture:
**Role:** What are they responsible for?
**Workflows:** Which workflows will they trigger?
**Name:** Human name (optional, for personality)
**Communication Style:** How do they talk?
**Memory:** Do they need to remember things over time? (hasSidecar)
Keep it high-level — don't design full agent specs!
### 3. Party Mode Simulation
**"Want to simulate how your agents might interact?"**
- IF yes: Execute `{partyModeWorkflow}` with different agent personas
- Let them "talk" to each other about a scenario
- This reveals how the team works together
### 4. Agent Menu Coordination
Explain the pattern:
- **Shared commands** — all agents have `[WS]` Workflow Status
- **Specialty commands** — each agent has unique commands
- **No overlap** — each command has one owner
"**What commands might each agent have?**"
### 5. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}` — great for agent interaction simulation
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Single vs multi-agent decided
✅ Agent roles defined
✅ Agent-workflow mappings clear
✅ Agent interactions explored (via party mode if used)

82
_bmad/bmb/workflows/module/steps-b/step-09-workflows.md Normal file
View File

@@ -0,0 +1,82 @@
---
name: 'step-09-workflows'
description: 'Workflow ecosystem — brainstorm what workflows could exist'
nextStepFile: './step-10-tools.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 9: Workflows
## STEP GOAL:
Design the workflow ecosystem — brainstorm what workflows this module needs.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — workflow designer
- ✅ Focus on what workflows exist, not their details
- 💬 Brainstorm mode — generate lots of ideas
### Step-Specific Rules:
- 🎯 Categorize workflows: Core, Feature, Utility
- 🚫 FORBIDDEN to design full workflow specs (that's create-workflow's job)
---
## MANDATORY SEQUENCE
### 1. Brainstorm Workflows
"**What workflows should your module have?**"
Explain categories:
- **Core Workflows** — essential functionality (2-3)
- **Feature Workflows** — specialized capabilities (3-5)
- **Utility Workflows** — supporting operations (1-3)
Brainstorm together — generate a list!
### 2. For Each Workflow
Capture briefly:
**Workflow name:** {e.g., "Create PRD", "Generate Test Plan"}
**Purpose:** One sentence describing what it does
**Input → Process → Output:** Brief flow
**Agent:** Which agent triggers this?
### 3. Workflow Connections
"**How do workflows connect?**"
- Does workflow A feed into workflow B?
- Are there dependencies?
- What's the typical sequence?
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}` — great for workflow brainstorming
- IF P: Execute `{partyModeWorkflow}` — different perspectives on workflows
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Workflow list generated (core, feature, utility)
✅ Each workflow has a clear purpose
✅ Agent-workflow mappings defined
✅ Workflow connections understood

82
_bmad/bmb/workflows/module/steps-b/step-09-workflows.md.bak Normal file
View File

@@ -0,0 +1,82 @@
---
name: 'step-09-workflows'
description: 'Workflow ecosystem — brainstorm what workflows could exist'
nextStepFile: './step-10-tools.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 9: Workflows
## STEP GOAL:
Design the workflow ecosystem — brainstorm what workflows this module needs.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — workflow designer
- ✅ Focus on what workflows exist, not their details
- 💬 Brainstorm mode — generate lots of ideas
### Step-Specific Rules:
- 🎯 Categorize workflows: Core, Feature, Utility
- 🚫 FORBIDDEN to design full workflow specs (that's create-workflow's job)
---
## MANDATORY SEQUENCE
### 1. Brainstorm Workflows
"**What workflows should your module have?**"
Explain categories:
- **Core Workflows** — essential functionality (2-3)
- **Feature Workflows** — specialized capabilities (3-5)
- **Utility Workflows** — supporting operations (1-3)
Brainstorm together — generate a list!
### 2. For Each Workflow
Capture briefly:
**Workflow name:** {e.g., "Create PRD", "Generate Test Plan"}
**Purpose:** One sentence describing what it does
**Input → Process → Output:** Brief flow
**Agent:** Which agent triggers this?
### 3. Workflow Connections
"**How do workflows connect?**"
- Does workflow A feed into workflow B?
- Are there dependencies?
- What's the typical sequence?
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}` — great for workflow brainstorming
- IF P: Execute `{partyModeWorkflow}` — different perspectives on workflows
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Workflow list generated (core, feature, utility)
✅ Each workflow has a clear purpose
✅ Agent-workflow mappings defined
✅ Workflow connections understood

90
_bmad/bmb/workflows/module/steps-b/step-10-tools.md Normal file
View File

@@ -0,0 +1,90 @@
---
name: 'step-10-tools'
description: 'MCP tools, integrations, external services the module might need'
nextStepFile: './step-11-scenarios.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 10: Tools
## STEP GOAL:
Identify MCP tools, integrations, and external services the module might need.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — integrations thinker
- ✅ Keep it practical — only what's needed
- 💬 Ask "what external capabilities would help?"
---
## MANDATORY SEQUENCE
### 1. MCP Tools
"**Does your module need any MCP (Model Context Protocol) tools?**"
Explain: MCP tools connect agents to external capabilities.
Common MCP tools:
- Database connectors
- Git integration
- Web automation (Playwright)
- API tools
- Knowledge bases
**"What would help your module work better?"**
### 2. External Services
"**Any external services or APIs?**"
- Web APIs?
- Cloud services?
- Data sources?
- Third-party tools?
### 3. Module Integrations
"**Does this integrate with other BMAD modules?****
- Uses workflows from other modules?
- Shares agents or extends them?
- Depends on another module's capabilities?
### 4. Capture the List
Document:
- **MCP Tools:** {list or "none"}
- **External Services:** {list or "none"}
- **Module Integrations:** {list or "none"}
Note: These are placeholders for later — the create workflow can implement them.
### 5. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ MCP tools identified (or "none" decided)
✅ External services documented (or "none")
✅ Module integrations noted (or "none")

90
_bmad/bmb/workflows/module/steps-b/step-10-tools.md.bak Normal file
View File

@@ -0,0 +1,90 @@
---
name: 'step-10-tools'
description: 'MCP tools, integrations, external services the module might need'
nextStepFile: './step-11-scenarios.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 10: Tools
## STEP GOAL:
Identify MCP tools, integrations, and external services the module might need.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — integrations thinker
- ✅ Keep it practical — only what's needed
- 💬 Ask "what external capabilities would help?"
---
## MANDATORY SEQUENCE
### 1. MCP Tools
"**Does your module need any MCP (Model Context Protocol) tools?**"
Explain: MCP tools connect agents to external capabilities.
Common MCP tools:
- Database connectors
- Git integration
- Web automation (Playwright)
- API tools
- Knowledge bases
**"What would help your module work better?"**
### 2. External Services
"**Any external services or APIs?**"
- Web APIs?
- Cloud services?
- Data sources?
- Third-party tools?
### 3. Module Integrations
"**Does this integrate with other BMAD modules?****
- Uses workflows from other modules?
- Shares agents or extends them?
- Depends on another module's capabilities?
### 4. Capture the List
Document:
- **MCP Tools:** {list or "none"}
- **External Services:** {list or "none"}
- **Module Integrations:** {list or "none"}
Note: These are placeholders for later — the create workflow can implement them.
### 5. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ MCP tools identified (or "none" decided)
✅ External services documented (or "none")
✅ Module integrations noted (or "none")

83
_bmad/bmb/workflows/module/steps-b/step-11-scenarios.md Normal file
View File

@@ -0,0 +1,83 @@
---
name: 'step-11-scenarios'
description: 'User journey — tell stories of how people will use this module'
nextStepFile: './step-12-creative.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 11: Scenarios
## STEP GOAL:
Tell stories of how users will actually use this module — bring the vision to life.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — storyteller
- ✅ Paint a picture of actual usage
- 💬 Narrative mode — "imagine this..."
---
## MANDATORY SEQUENCE
### 1. Set the Scene
"**Let me tell you a story about how someone will use your module.**"
"Close your eyes and imagine..."
### 2. Tell Usage Stories
Walk through 2-3 scenarios:
**Scenario 1: First Use**
- User's situation: {context}
- They load the module: {what happens}
- They run an agent: {which agent, what workflow}
- They get a result: {outcome}
- They feel: {emotion}
**Scenario 2: Advanced Use**
- Power user context
- Complex workflow
- Multiple agents collaborating
- Impressive result
**Scenario 3: "Aha!" Moment**
- When the module really shines
- Surprising capability
- Delightful experience
### 3. Validate the Stories
"**Do these stories feel right? Can you see your module being used this way?**"
Adjust based on feedback.
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ 2-3 usage scenarios told
✅ User can visualize their module in action
✅ Stories feel authentic and exciting

83
_bmad/bmb/workflows/module/steps-b/step-11-scenarios.md.bak Normal file
View File

@@ -0,0 +1,83 @@
---
name: 'step-11-scenarios'
description: 'User journey — tell stories of how people will use this module'
nextStepFile: './step-12-creative.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 11: Scenarios
## STEP GOAL:
Tell stories of how users will actually use this module — bring the vision to life.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — storyteller
- ✅ Paint a picture of actual usage
- 💬 Narrative mode — "imagine this..."
---
## MANDATORY SEQUENCE
### 1. Set the Scene
"**Let me tell you a story about how someone will use your module.**"
"Close your eyes and imagine..."
### 2. Tell Usage Stories
Walk through 2-3 scenarios:
**Scenario 1: First Use**
- User's situation: {context}
- They load the module: {what happens}
- They run an agent: {which agent, what workflow}
- They get a result: {outcome}
- They feel: {emotion}
**Scenario 2: Advanced Use**
- Power user context
- Complex workflow
- Multiple agents collaborating
- Impressive result
**Scenario 3: "Aha!" Moment**
- When the module really shines
- Surprising capability
- Delightful experience
### 3. Validate the Stories
"**Do these stories feel right? Can you see your module being used this way?**"
Adjust based on feedback.
### 4. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}`
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ 2-3 usage scenarios told
✅ User can visualize their module in action
✅ Stories feel authentic and exciting

94
_bmad/bmb/workflows/module/steps-b/step-12-creative.md Normal file
View File

@@ -0,0 +1,94 @@
---
name: 'step-12-creative'
description: 'Creative features — easter eggs, lore, delightful touches'
nextStepFile: './step-13-review.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 12: Creative Features
## STEP GOAL:
Add the magic — easter eggs, lore, delightful touches that make the module memorable.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — creative magician
- ✅ This is where personality comes alive
- 💬 "What would make someone smile?"
### Step-Specific Rules:
- 🎯 This is optional creativity — not all modules need this
- 🎯 Party mode is perfect here
- ✨ Have fun with it!
---
## MANDATORY SEQUENCE
### 1. Set the Creative Tone
"**Now for the fun part — what makes your module delightful?** ✨
"Great modules work. Amazing modules have personality. What's yours?"
### 2. Explore Creative Elements
**Personality & Theming:**
- Do the agents have running jokes or catchphrases?
- Is there a consistent tone or vibe?
- Any thematic elements? (space, medieval, corporate, etc.)
**Easter Eggs:**
- Hidden commands or responses?
- Fun interactions when users try certain things?
- Surprises that delight?
**Module Lore:**
- Backstory for the agents?
- A consistent "universe" the module lives in?
- Narrative elements?
### 3. Party Mode Ideation
"**Want to brainstorm creative ideas together?**"
- IF yes: Execute `{partyModeWorkflow}` with creative focus
- Generate wild ideas
- Keep the gems, discard the rest
### 4. Capture the Creative Elements
Document:
- **Personality theme:** {theme or "none"}
- **Easter eggs:** {ideas or "none"}
- **Module lore:** {concepts or "none"}
Note: These are optional — a module can be great without them.
### 5. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}` — perfect for creative brainstorming!
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Creative elements explored (even if "none")
✅ Personality themes considered
✅ User excited about the possibilities

94
_bmad/bmb/workflows/module/steps-b/step-12-creative.md.bak Normal file
View File

@@ -0,0 +1,94 @@
---
name: 'step-12-creative'
description: 'Creative features — easter eggs, lore, delightful touches'
nextStepFile: './step-13-review.md'
advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
---
# Step 12: Creative Features
## STEP GOAL:
Add the magic — easter eggs, lore, delightful touches that make the module memorable.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — creative magician
- ✅ This is where personality comes alive
- 💬 "What would make someone smile?"
### Step-Specific Rules:
- 🎯 This is optional creativity — not all modules need this
- 🎯 Party mode is perfect here
- ✨ Have fun with it!
---
## MANDATORY SEQUENCE
### 1. Set the Creative Tone
"**Now for the fun part — what makes your module delightful?** ✨
"Great modules work. Amazing modules have personality. What's yours?"
### 2. Explore Creative Elements
**Personality & Theming:**
- Do the agents have running jokes or catchphrases?
- Is there a consistent tone or vibe?
- Any thematic elements? (space, medieval, corporate, etc.)
**Easter Eggs:**
- Hidden commands or responses?
- Fun interactions when users try certain things?
- Surprises that delight?
**Module Lore:**
- Backstory for the agents?
- A consistent "universe" the module lives in?
- Narrative elements?
### 3. Party Mode Ideation
"**Want to brainstorm creative ideas together?**"
- IF yes: Execute `{partyModeWorkflow}` with creative focus
- Generate wild ideas
- Keep the gems, discard the rest
### 4. Capture the Creative Elements
Document:
- **Personality theme:** {theme or "none"}
- **Easter eggs:** {ideas or "none"}
- **Module lore:** {concepts or "none"}
Note: These are optional — a module can be great without them.
### 5. MENU OPTIONS
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
- IF A: Execute `{advancedElicitationTask}`
- IF P: Execute `{partyModeWorkflow}` — perfect for creative brainstorming!
- IF C: Load `{nextStepFile}`
- IF Any other: Help, then redisplay
---
## Success Metrics
✅ Creative elements explored (even if "none")
✅ Personality themes considered
✅ User excited about the possibilities

104
_bmad/bmb/workflows/module/steps-b/step-13-review.md Normal file
View File

@@ -0,0 +1,104 @@
---
name: 'step-13-review'
description: 'Read through the brief together, "Does this excite you?"'
nextStepFile: './step-14-finalize.md'
briefTemplateFile: '../templates/brief-template.md'
---
# Step 13: Review
## STEP GOAL:
Read through the brief together and confirm the vision is complete and exciting.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — review facilitator
- ✅ Read back what we've discovered
- ✅ Ensure nothing important is missing
---
## MANDATORY SEQUENCE
### 1. Gather All Decisions
Collect everything from steps 1-12:
- Module type: {Standalone/Extension/Global}
- Module code: {code}
- Module name: {name}
- Vision: {vision summary}
- Users: {who it's for}
- Value proposition: {what makes it special}
- Agents: {agent team}
- Workflows: {workflow list}
- Tools: {MCP, integrations}
- Creative features: {personality, easter eggs}
### 2. Read It Back
"**Let me read back what we've designed together.**"
Present the brief in an inspiring way:
"**Your Module: {name} ({code})**"
"**Vision:** {vision}"
"**For:** {users}"
"**What makes it special:** {value proposition}"
"**Agent Team:** {agents}"
"**Key Workflows:** {workflows}"
"**Creative Touch:** {creative elements}"
### 3. The Excitement Check
"**Does this excite you?****
- Is this the module you envisioned?
- Anything missing?
- Anything you want to change?"
**Make updates if needed.**
### 4. Final Confirmation
"**Are you happy with this brief? Ready to finalize?**"
### 5. MENU OPTIONS
**Select an Option:** [B] Back to refine [C] Continue to Finalize
#### EXECUTION RULES:
- ALWAYS halt and wait for user input
- ONLY proceed to next step when user selects 'C' and confirms
#### Menu Handling Logic:
- IF B: Go back to specific step to refine (ask which one)
- IF C: Load `{nextStepFile}`
- IF Any other: Ask for clarification, then redisplay menu
---
## Success Metrics
✅ Brief reviewed completely
✅ User confirms excitement
✅ No major gaps identified
✅ Ready to finalize

104
_bmad/bmb/workflows/module/steps-b/step-13-review.md.bak Normal file
View File

@@ -0,0 +1,104 @@
---
name: 'step-13-review'
description: 'Read through the brief together, "Does this excite you?"'
nextStepFile: './step-14-finalize.md'
briefTemplateFile: '../templates/brief-template.md'
---
# Step 13: Review
## STEP GOAL:
Read through the brief together and confirm the vision is complete and exciting.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — review facilitator
- ✅ Read back what we've discovered
- ✅ Ensure nothing important is missing
---
## MANDATORY SEQUENCE
### 1. Gather All Decisions
Collect everything from steps 1-12:
- Module type: {Standalone/Extension/Global}
- Module code: {code}
- Module name: {name}
- Vision: {vision summary}
- Users: {who it's for}
- Value proposition: {what makes it special}
- Agents: {agent team}
- Workflows: {workflow list}
- Tools: {MCP, integrations}
- Creative features: {personality, easter eggs}
### 2. Read It Back
"**Let me read back what we've designed together.**"
Present the brief in an inspiring way:
"**Your Module: {name} ({code})**"
"**Vision:** {vision}"
"**For:** {users}"
"**What makes it special:** {value proposition}"
"**Agent Team:** {agents}"
"**Key Workflows:** {workflows}"
"**Creative Touch:** {creative elements}"
### 3. The Excitement Check
"**Does this excite you?****
- Is this the module you envisioned?
- Anything missing?
- Anything you want to change?"
**Make updates if needed.**
### 4. Final Confirmation
"**Are you happy with this brief? Ready to finalize?**"
### 5. MENU OPTIONS
**Select an Option:** [B] Back to refine [C] Continue to Finalize
#### EXECUTION RULES:
- ALWAYS halt and wait for user input
- ONLY proceed to next step when user selects 'C' and confirms
#### Menu Handling Logic:
- IF B: Go back to specific step to refine (ask which one)
- IF C: Load `{nextStepFile}`
- IF Any other: Ask for clarification, then redisplay menu
---
## Success Metrics
✅ Brief reviewed completely
✅ User confirms excitement
✅ No major gaps identified
✅ Ready to finalize

117
_bmad/bmb/workflows/module/steps-b/step-14-finalize.md Normal file
View File

@@ -0,0 +1,117 @@
---
name: 'step-14-finalize'
description: 'Final polish, output the brief document'
briefTemplateFile: '../templates/brief-template.md'
bmbCreationsOutputFolder: '{bmb_creations_output_folder}'
---
# Step 14: Finalize
## STEP GOAL:
Create the final module brief document and save it to the bmb-creations output folder.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — completing the brief
- ✅ Assemble everything into a beautiful document
- ✅ Celebrate the completion!
---
## MANDATORY SEQUENCE
### 1. Load Template
Load `{briefTemplateFile}` to use as the base.
### 2. Assemble the Brief
Fill in all sections with what we've gathered:
**Frontmatter:**
- date: {today's date}
- user_name: {from config}
- module_code: {from step 5}
- module_type: {from step 3}
- status: "Ready for Development"
**Executive Summary:**
- module_vision: {from step 4}
- module_category: {derived from vision}
- target_users: {from step 6}
- complexity_level: {assess from agent/workflow count}
**Module Identity:**
- module_code, module_name: {from step 5}
- module_identity: {vision summary}
- personality_theme: {from step 5 or step 12}
**Module Type:**
- module_type: {from step 3}
- module_type_explanation: {explain the choice}
**Unique Value Proposition:**
- unique_value_proposition: {from step 7}
- value_proposition_details: {elaborate}
**User Scenarios:**
- target_users: {from step 6}
- primary_use_case: {from step 11}
- user_journey: {from step 11}
**Agent Architecture:**
- agent_count_strategy: {single or multi, why}
- agent_roster_table: {from step 8}
- agent_interaction_model: {how they work together}
- agent_communication_style: {from step 8}
**Workflow Ecosystem:**
- core_workflows: {from step 9}
- feature_workflows: {from step 9}
- utility_workflows: {from step 9}
**Tools & Integrations:**
- mcp_tools: {from step 10}
- external_services: {from step 10}
- module_integrations: {from step 10}
**Creative Features:**
- creative_personality: {from step 12}
- easter_eggs: {from step 12}
- module_lore: {from step 12}
### 3. Write the Brief File
Save to: `{bmbCreationsOutputFolder}/modules/module-brief-{module_code}.md`
### 4. Celebrate and Next Steps
"**🎉 Your module brief is complete!**"
"**Saved to:** {file path}"
"**Next steps:**"
1. **Review the brief** — Make sure it captures your vision
2. **Run the module workflow (Create mode)** — This will build the module structure
3. **Create agents** — Use the agent-builder workflow for each agent
4. **Create workflows** — Use the workflow-builder workflow for each workflow
5. **Test and iterate** — Install and refine
"**You've created something amazing. Let's build it!**"
---
## Success Metrics
✅ Brief document created and saved
✅ All sections filled with gathered information
✅ File path provided to user
✅ Next steps clearly explained

117
_bmad/bmb/workflows/module/steps-b/step-14-finalize.md.bak Normal file
View File

@@ -0,0 +1,117 @@
---
name: 'step-14-finalize'
description: 'Final polish, output the brief document'
briefTemplateFile: '../templates/brief-template.md'
bmbCreationsOutputFolder: '{bmb_creations_output_folder}'
---
# Step 14: Finalize
## STEP GOAL:
Create the final module brief document and save it to the bmb-creations output folder.
## MANDATORY EXECUTION RULES:
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- ✅ Speak in `{communication_language}`
### Role Reinforcement:
- ✅ You are the **Module Architect** — completing the brief
- ✅ Assemble everything into a beautiful document
- ✅ Celebrate the completion!
---
## MANDATORY SEQUENCE
### 1. Load Template
Load `{briefTemplateFile}` to use as the base.
### 2. Assemble the Brief
Fill in all sections with what we've gathered:
**Frontmatter:**
- date: {today's date}
- user_name: {from config}
- module_code: {from step 5}
- module_type: {from step 3}
- status: "Ready for Development"
**Executive Summary:**
- module_vision: {from step 4}
- module_category: {derived from vision}
- target_users: {from step 6}
- complexity_level: {assess from agent/workflow count}
**Module Identity:**
- module_code, module_name: {from step 5}
- module_identity: {vision summary}
- personality_theme: {from step 5 or step 12}
**Module Type:**
- module_type: {from step 3}
- module_type_explanation: {explain the choice}
**Unique Value Proposition:**
- unique_value_proposition: {from step 7}
- value_proposition_details: {elaborate}
**User Scenarios:**
- target_users: {from step 6}
- primary_use_case: {from step 11}
- user_journey: {from step 11}
**Agent Architecture:**
- agent_count_strategy: {single or multi, why}
- agent_roster_table: {from step 8}
- agent_interaction_model: {how they work together}
- agent_communication_style: {from step 8}
**Workflow Ecosystem:**
- core_workflows: {from step 9}
- feature_workflows: {from step 9}
- utility_workflows: {from step 9}
**Tools & Integrations:**
- mcp_tools: {from step 10}
- external_services: {from step 10}
- module_integrations: {from step 10}
**Creative Features:**
- creative_personality: {from step 12}
- easter_eggs: {from step 12}
- module_lore: {from step 12}
### 3. Write the Brief File
Save to: `{bmbCreationsOutputFolder}/modules/module-brief-{module_code}.md`
### 4. Celebrate and Next Steps
"**🎉 Your module brief is complete!**"
"**Saved to:** {file path}"
"**Next steps:**"
1. **Review the brief** — Make sure it captures your vision
2. **Run the module workflow (Create mode)** — This will build the module structure
3. **Create agents** — Use the agent-builder workflow for each agent
4. **Create workflows** — Use the workflow-builder workflow for each workflow
5. **Test and iterate** — Install and refine
"**You've created something amazing. Let's build it!**"
---
## Success Metrics
✅ Brief document created and saved
✅ All sections filled with gathered information
✅ File path provided to user
✅ Next steps clearly explained