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

package/src/bmb/workflows/module/steps-b/step-03-module-type.md

@@ -1,149 +1,149 @@
----
-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 [AR] Adversarial Review [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 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: 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.
+---
+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 [AR] Adversarial Review [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 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: 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.

package/src/bmb/workflows/module/steps-b/step-04-vision.md

@@ -1,83 +1,83 @@
----
-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 [AR] Adversarial Review [C] Continue
-
-- IF A: Execute `{advancedElicitationTask}`
-- IF P: Execute `{partyModeWorkflow}`
-- 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, then redisplay
-
----
-
-## Success Metrics
-
-✅ Vision feels inspiring and clear
-✅ "Extraordinary" elements identified
-✅ User excited about the possibility
+---
+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 [AR] Adversarial Review [C] Continue
+
+- IF A: Execute `{advancedElicitationTask}`
+- IF P: Execute `{partyModeWorkflow}`
+- 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, then redisplay
+
+---
+
+## Success Metrics
+
+✅ Vision feels inspiring and clear
+✅ "Extraordinary" elements identified
+✅ User excited about the possibility

package/src/bmb/workflows/module/steps-b/step-05-identity.md

@@ -1,97 +1,97 @@
----
-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 [AR] Adversarial Review [C] Continue
-
-- IF A: Execute `{advancedElicitationTask}`
-- IF P: Execute `{partyModeWorkflow}`
-- 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, then redisplay
-
----
-
-## Success Metrics
-
-✅ Module code decided and validated
-✅ Module name defined
-✅ Personality theme decided (even if "none")
+---
+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 [AR] Adversarial Review [C] Continue
+
+- IF A: Execute `{advancedElicitationTask}`
+- IF P: Execute `{partyModeWorkflow}`
+- 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, then redisplay
+
+---
+
+## Success Metrics
+
+✅ Module code decided and validated
+✅ Module name defined
+✅ Personality theme decided (even if "none")