create-byan-agent 2.1.1 → 2.2.2

package/install/templates/_byan/bmb/workflows/module/steps-b/step-07-value.md

@@ -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

package/install/templates/_byan/bmb/workflows/module/steps-b/step-08-agents.md

@@ -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)

package/install/templates/_byan/bmb/workflows/module/steps-b/step-09-workflows.md

@@ -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

package/install/templates/_byan/bmb/workflows/module/steps-b/step-10-tools.md

@@ -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")

package/install/templates/_byan/bmb/workflows/module/steps-b/step-11-scenarios.md

@@ -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

package/install/templates/_byan/bmb/workflows/module/steps-b/step-12-creative.md

@@ -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

package/install/templates/_byan/bmb/workflows/module/steps-b/step-13-review.md

@@ -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