create-byan-agent 2.1.0 → 2.1.1

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

@@ -1,147 +0,0 @@
----
-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 [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 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/_bmad/bmb/workflows/module/steps-b/step-02-spark.md

@@ -1,140 +0,0 @@
----
-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 [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 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.

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

@@ -1,148 +0,0 @@
----
-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 [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 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/_bmad/bmb/workflows/module/steps-b/step-04-vision.md

@@ -1,82 +0,0 @@
----
-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 [C] Continue
-
-- IF A: Execute `{advancedElicitationTask}`
-- IF P: Execute `{partyModeWorkflow}`
-- 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/_bmad/bmb/workflows/module/steps-b/step-05-identity.md

@@ -1,96 +0,0 @@
----
-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 [C] Continue
-
-- IF A: Execute `{advancedElicitationTask}`
-- IF P: Execute `{partyModeWorkflow}`
-- 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")

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

@@ -1,85 +0,0 @@
----
-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 [C] Continue
-
-- IF A: Execute `{advancedElicitationTask}`
-- IF P: Execute `{partyModeWorkflow}`
-- 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