@devo-bmad-custom/agent-orchestration 1.0.2 → 1.0.4

package/src/bmb/workflows/module/steps-b/step-01-welcome.md

@@ -1,148 +1,148 @@
----
-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 [AR] Adversarial Review [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 AR: Execute {project-root}/_bmad/core/tasks/review-adversarial-general.xml — pass the current editPlan (or plan document in context) as the content to review; display findings with recommendations; then redisplay this 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.
+---
+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 [AR] Adversarial Review [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 AR: Execute {project-root}/_bmad/core/tasks/review-adversarial-general.xml — pass the current editPlan (or plan document in context) as the content to review; display findings with recommendations; then redisplay this 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.

package/src/bmb/workflows/module/steps-b/step-02-spark.md

@@ -1,141 +1,141 @@
----
-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 [AR] Adversarial Review [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 AR: Execute {project-root}/_bmad/core/tasks/review-adversarial-general.xml — pass the current editPlan (or plan document in context) as the content to review; display findings with recommendations; then redisplay this menu
-- 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.
+---
+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 [AR] Adversarial Review [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 AR: Execute {project-root}/_bmad/core/tasks/review-adversarial-general.xml — pass the current editPlan (or plan document in context) as the content to review; display findings with recommendations; then redisplay this menu
+- 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.