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

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

@@ -1,86 +1,86 @@
----
-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 [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
-
-✅ User personas defined
-✅ User journey story told
-✅ User can visualize how their module will be used
+---
+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 [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
+
+✅ User personas defined
+✅ User journey story told
+✅ User can visualize how their module will be used

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

@@ -1,76 +1,76 @@
----
-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 [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
-
-✅ Unique value proposition articulated
-✅ Differentiation from alternatives clear
-✅ User can explain why someone would choose this module
+---
+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 [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
+
+✅ Unique value proposition articulated
+✅ Differentiation from alternatives clear
+✅ User can explain why someone would choose this module

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

@@ -1,97 +1,97 @@
----
-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 [AR] Adversarial Review [C] Continue
-
-- IF A: Execute `{advancedElicitationTask}`
-- IF P: Execute `{partyModeWorkflow}` — great for agent interaction simulation
-- 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
-
-✅ Single vs multi-agent decided
-✅ Agent roles defined
-✅ Agent-workflow mappings clear
-✅ Agent interactions explored (via party mode if used)
+---
+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 [AR] Adversarial Review [C] Continue
+
+- IF A: Execute `{advancedElicitationTask}`
+- IF P: Execute `{partyModeWorkflow}` — great for agent interaction simulation
+- 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
+
+✅ Single vs multi-agent decided
+✅ Agent roles defined
+✅ Agent-workflow mappings clear
+✅ Agent interactions explored (via party mode if used)