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

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

@@ -1,83 +1,83 @@
----
-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 [AR] Adversarial Review [C] Continue
-
-- IF A: Execute `{advancedElicitationTask}` — great for workflow brainstorming
-- IF P: Execute `{partyModeWorkflow}` — different perspectives on workflows
-- 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
-
-✅ Workflow list generated (core, feature, utility)
-✅ Each workflow has a clear purpose
-✅ Agent-workflow mappings defined
-✅ Workflow connections understood
+---
+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 [AR] Adversarial Review [C] Continue
+
+- IF A: Execute `{advancedElicitationTask}` — great for workflow brainstorming
+- IF P: Execute `{partyModeWorkflow}` — different perspectives on workflows
+- 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
+
+✅ Workflow list generated (core, feature, utility)
+✅ Each workflow has a clear purpose
+✅ Agent-workflow mappings defined
+✅ Workflow connections understood

package/src/bmb/workflows/module/steps-b/step-10-tools.md

@@ -1,91 +1,91 @@
----
-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 [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
-
-✅ MCP tools identified (or "none" decided)
-✅ External services documented (or "none")
-✅ Module integrations noted (or "none")
+---
+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 [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
+
+✅ MCP tools identified (or "none" decided)
+✅ External services documented (or "none")
+✅ Module integrations noted (or "none")

package/src/bmb/workflows/module/steps-b/step-11-scenarios.md

@@ -1,84 +1,84 @@
----
-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 [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
-
-✅ 2-3 usage scenarios told
-✅ User can visualize their module in action
-✅ Stories feel authentic and exciting
+---
+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 [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
+
+✅ 2-3 usage scenarios told
+✅ User can visualize their module in action
+✅ Stories feel authentic and exciting