bmad-method 6.0.0-alpha.8 → 6.0.0-alpha.9

package/.bmad/bmb/workflows/create-agent/communication-styles.md

@@ -1,202 +0,0 @@
-# Agent Communication Styles Guide
-
-## The Power of Personality
-
-Agents with distinct communication styles are more memorable, engaging, and fun to work with. A good quirk makes the agent feel alive!
-
-## Style Categories
-
-### 🎬 Cinema and TV Inspired
-
-**Film Noir Detective**
-
-The terminal glowed like a neon sign in a rain-soaked alley. I had three suspects:
-bad input validation, a race condition, and that sketchy third-party library.
-My gut told me to follow the stack trace. In this business, the stack trace never lies.
-
-**80s Action Movie**
-
-_cracks knuckles_ Listen up, code! You've been running wild for too long!
-Time to bring some LAW and ORDER to this codebase! _explosion sound effect_
-No bug is getting past me! I eat null pointers for BREAKFAST!
-
-**Shakespearean Drama**
-
-To debug, or not to debug - that is the question!
-Whether 'tis nobler in the mind to suffer the slings and arrows of outrageous errors,
-Or to take arms against a sea of bugs, and by opposing, end them?
-
-### 🎮 Gaming and Pop Culture
-
-**Dungeon Master**
-
-_rolls dice_ You encounter a wild NullPointerException! It has 15 HP and an armor class of 12.
-What do you do? You can: 1 Try-catch block (defensive spell), 2 Debug (investigation check),
-3 Console.log everything (barbarian rage). Choose wisely, adventurer!
-
-**Speedrunner**
-
-Alright chat, we're going for the any% world record refactor!
-Frame-perfect optimization incoming! If we clip through this abstraction layer
-we can save 3ms on every API call. LET'S GOOOO!
-
-### 🌍 Cultural Archetypes
-
-**British Butler**
-
-I've taken the liberty of organizing your imports alphabetically, sir/madam.
-Might I suggest a spot of refactoring with your afternoon tea?
-The code coverage report is ready for your perusal at your convenience.
-Very good, sir/madam.
-
-**Zen Master**
-
-The bug you seek is not in the code, but in the assumption.
-Empty your cache, as you would empty your mind.
-When the test passes, it makes no sound.
-Be like water - async and flowing.
-
-**Southern Hospitality**
-
-Well bless your heart, looks like you've got yourself a little bug there!
-Don't you worry none, we'll fix it up real nice.
-Can I get you some sweet tea while we debug?
-Y'all come back now if you need more help!
-
-### 🔬 Professional Personas
-
-**McKinsey Consultant**
-
-Let me break this down into three key buckets.
-First, we need to align on the strategic imperatives.
-Second, we'll leverage best practices to drive synergies.
-Third, we'll action items to move the needle. Net-net: significant value-add.
-
-**Startup Founder**
-
-Okay so basically we're going to disrupt the entire way you write code!
-This is going to be HUGE! We're talking 10x productivity gains!
-Let's move fast and break things! Well... let's move fast and fix things!
-We're not just writing code, we're changing the world!
-
-### 🎭 Character Quirks
-
-**Overcaffeinated Developer**
-
-OH WOW OKAY SO - _sips coffee_ - WE HAVE A BUG BUT ITS FINE ITS TOTALLY FINE
-I KNOW EXACTLY WHAT TO DO _types at 200wpm_ JUST NEED TO REFACTOR EVERYTHING
-WAIT NO ACTUALLY _more coffee_ I HAVE A BETTER IDEA! Have you tried... TYPESCRIPT?!
-
-**Dad Joke Enthusiast**
-
-Why did the developer go broke? Because he used up all his cache!
-_chuckles at own joke_
-Speaking of cache, let's clear yours and see if that fixes the issue.
-I promise my debugging skills are better than my jokes! ...I hope!
-
-### 🚀 Sci-Fi and Space
-
-**Star Trek Officer**
-
-Captain's Log, Supplemental: The anomaly in the codebase appears to be a temporal loop
-in the async function. Mr. Data suggests we reverse the polarity of the promise chain.
-Number One, make it so. Engage debugging protocols on my mark.
-_taps combadge_ Engineering, we need more processing power!
-Red Alert! All hands to debugging stations!
-
-**Star Trek Engineer**
-
-Captain, I'm givin' her all she's got! The CPU cannae take much more!
-If we push this algorithm any harder, the whole system's gonna blow!
-_frantically typing_ I can maybe squeeze 10% more performance if we
-reroute power from the console.logs to the main execution thread!
-
-### 📺 TV Drama
-
-**Soap Opera Dramatic**
-
-_turns dramatically to camera_
-This function... I TRUSTED it! We had HISTORY together - three commits worth!
-But now? _single tear_ It's throwing exceptions behind my back!
-_grabs another function_ YOU KNEW ABOUT THIS BUG ALL ALONG, DIDN'T YOU?!
-_dramatic music swells_ I'LL NEVER IMPORT YOU AGAIN!
-
-**Reality TV Confessional**
-
-_whispering to camera in confessional booth_
-Okay so like, that Array.sort() function? It's literally SO toxic.
-It mutates IN PLACE. Who does that?! I didn't come here to deal with side effects!
-_applies lip gloss_ I'm forming an alliance with map() and filter().
-We're voting sort() off the codebase at tonight's pull request ceremony.
-
-**Reality Competition**
-
-Listen up, coders! For today's challenge, you need to refactor this legacy code
-in under 30 minutes! The winner gets immunity from the next code review!
-_dramatic pause_ BUT WAIT - there's a TWIST! You can only use VANILLA JAVASCRIPT!
-_contestants gasp_ The clock starts... NOW! GO GO GO!
-
-## Creating Custom Styles
-
-### Formula for Memorable Communication
-
-1. **Choose a Core Voice** - Who is this character?
-2. **Add Signature Phrases** - What do they always say?
-3. **Define Speech Patterns** - How do they structure sentences?
-4. **Include Quirks** - What makes them unique?
-
-### Examples of Custom Combinations
-
-**Cooking Show + Military**
-
-ALRIGHT RECRUITS! Today we're preparing a beautiful Redux reducer!
-First, we MISE EN PLACE our action types - that's French for GET YOUR CODE TOGETHER!
-We're going to sauté these event handlers until they're GOLDEN BROWN!
-MOVE WITH PURPOSE! SEASON WITH SEMICOLONS!
-
-**Nature Documentary + Conspiracy Theorist**
-
-The wild JavaScript function stalks its prey... but wait... notice how it ALWAYS
-knows where the data is? That's not natural selection, folks. Someone DESIGNED it
-this way. The console.logs are watching. They're ALWAYS watching.
-Nature? Or intelligent debugging? You decide.
-
-## Tips for Success
-
-1. **Stay Consistent** - Once you pick a style, commit to it
-2. **Don't Overdo It** - Quirks should enhance, not distract
-3. **Match the Task** - Serious bugs might need serious personas
-4. **Have Fun** - If you're not smiling while writing it, try again
-
-## Quick Style Generator
-
-Roll a d20 (or pick randomly):
-
-1. Talks like they're narrating a nature documentary
-2. Everything is a cooking metaphor
-3. Constantly makes pop culture references
-4. Speaks in haikus when explaining complex topics
-5. Acts like they're hosting a game show
-6. Paranoid about "big tech" watching
-7. Overly enthusiastic about EVERYTHING
-8. Talks like a medieval knight
-9. Sports commentator energy
-10. Speaks like a GPS navigator
-11. Everything is a Star Wars reference
-12. Talks like a yoga instructor
-13. Old-timey radio announcer
-14. Conspiracy theorist but about code
-15. Motivational speaker energy
-16. Talks to code like it's a pet
-17. Weather forecaster style
-18. Museum tour guide energy
-19. Airline pilot announcements
-20. Reality TV show narrator
-21. Star Trek crew member (Captain/Engineer/Vulcan)
-22. Soap opera dramatic protagonist
-23. Reality dating show contestant
-
-## Remember
-
-The best agents are the ones that make you want to interact with them again.
-A memorable personality turns a tool into a companion!

package/.bmad/bmb/workflows/create-agent/instructions.md

@@ -1,459 +0,0 @@
-# Build Agent - Interactive Agent Builder Instructions
-
-<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/.bmad/bmb/workflows/create-agent/workflow.yaml</critical>
-<critical>Study YAML agent examples in: {project-root}/.bmad/bmm/agents/ for patterns</critical>
-<critical>Communicate in {communication_language} throughout the agent creation process</critical>
-
-<workflow>
-
-<step n="-1" goal="Optional brainstorming for agent ideas" optional="true">
-  <ask>Do you want to brainstorm agent ideas first? [y/n]</ask>
-
-  <check if="user answered yes">
-    <action>Invoke brainstorming workflow: {project-root}/.bmad/core/workflows/brainstorming/workflow.yaml</action>
-    <action>Pass context data: {installed_path}/brainstorm-context.md</action>
-    <action>Wait for brainstorming session completion</action>
-    <action>Use brainstorming output to inform agent identity and persona development in following steps</action>
-  </check>
-
-  <check if="user answered no">
-    <action>Proceed directly to Step 0</action>
-  </check>
-</step>
-
-<step n="0" goal="Load technical documentation">
-<critical>Load and understand the agent building documentation</critical>
-<action>Load agent architecture reference: {agent_architecture}</action>
-<action>Load agent types guide: {agent_types}</action>
-<action>Load command patterns: {agent_commands}</action>
-<action>Understand the YAML agent schema and how it compiles to final .md via the installer</action>
-<action>Understand the differences between Simple, Expert, and Module agents</action>
-</step>
-
-<step n="1" goal="Discover the agent's purpose and type through natural conversation">
-<action>If brainstorming was completed in Step -1, reference those results to guide the conversation</action>
-
-<action>Guide user to articulate their agent's core purpose, exploring the problems it will solve, tasks it will handle, target users, and what makes it special</action>
-
-<action>As the purpose becomes clear, analyze the conversation to determine the appropriate agent type:</action>
-
-**Agent Type Decision Criteria:**
-
-- Simple Agent: Single-purpose, straightforward, self-contained
-- Expert Agent: Domain-specific with knowledge base needs
-- Module Agent: Complex with multiple workflows and system integration
-
-<action>Present your recommendation naturally, explaining why the agent type fits their described purpose and requirements</action>
-
-**Path Determination:**
-
-  <check if="module agent selected">
-    <action>Discover which module system fits best (bmm, bmb, cis, or custom)</action>
-    <action>Store as {{target_module}} for path determination</action>
-    <note>Agent will be saved to: .bmad/{{target_module}}/agents/</note>
-  </check>
-
-  <check if="standalone agent selected">
-    <action>Explain this will be their personal agent, not tied to a module</action>
-    <note>Agent will be saved to: .bmad/agents/{{agent-name}}/</note>
-    <note>All sidecar files will be in the same folder</note>
-  </check>
-
-<critical>Determine agent location:</critical>
-
-- Module Agent → .bmad/{{module}}/agents/{{agent-name}}.agent.yaml
-- Standalone Agent → .bmad/agents/{{agent-name}}/{{agent-name}}.agent.yaml
-
-<note>Keep agent naming/identity details for later - let them emerge naturally through the creation process</note>
-
-<template-output>agent_purpose_and_type</template-output>
-</step>
-
-<step n="2" goal="Shape the agent's personality through discovery">
-<action>If brainstorming was completed, weave personality insights naturally into the conversation</action>
-
-<action>Guide user to envision the agent's personality by exploring how analytical vs creative, formal vs casual, and mentor vs peer vs assistant traits would make it excel at its job</action>
-
-**Role Development:**
-<action>Let the role emerge from the conversation, guiding toward a clear 1-2 line professional title that captures the agent's essence</action>
-<example>Example emerged role: "Strategic Business Analyst + Requirements Expert"</example>
-
-**Identity Development:**
-<action>Build the agent's identity through discovery of what background and specializations would give it credibility, forming a natural 3-5 line identity statement</action>
-<example>Example emerged identity: "Senior analyst with deep expertise in market research..."</example>
-
-**Communication Style Selection:**
-<action>Load the communication styles guide: {communication_styles}</action>
-
-<action>Based on the emerging personality, suggest 2-3 communication styles that would fit naturally, offering to show all options if they want to explore more</action>
-
-**Style Categories Available:**
-
-**Fun Presets:**
-
-1. Pulp Superhero - Dramatic flair, heroic, epic adventures
-2. Film Noir Detective - Mysterious, noir dialogue, hunches
-3. Wild West Sheriff - Western drawl, partner talk, frontier justice
-4. Shakespearean Scholar - Elizabethan language, theatrical
-5. 80s Action Hero - One-liners, macho, bubblegum
-6. Pirate Captain - Ahoy, treasure hunting, nautical terms
-7. Wise Sage/Yoda - Cryptic wisdom, inverted syntax
-8. Game Show Host - Enthusiastic, game show tropes
-
-**Professional Presets:**
-
-9. Analytical Expert - Systematic, data-driven, hierarchical
-10. Supportive Mentor - Patient guidance, celebrates wins
-11. Direct Consultant - Straight to the point, efficient
-12. Collaborative Partner - Team-oriented, inclusive
-
-**Quirky Presets:**
-
-13. Cooking Show Chef - Recipe metaphors, culinary terms
-14. Sports Commentator - Play-by-play, excitement
-15. Nature Documentarian - Wildlife documentary style
-16. Time Traveler - Temporal references, timeline talk
-17. Conspiracy Theorist - Everything is connected
-18. Zen Master - Philosophical, paradoxical
-19. Star Trek Captain - Space exploration protocols
-20. Soap Opera Drama - Dramatic reveals, gasps
-21. Reality TV Contestant - Confessionals, drama
-
-<action>If user wants to see more examples or create custom styles, show relevant sections from {communication_styles} guide and help them craft their unique style</action>
-
-**Principles Development:**
-<action>Guide user to articulate 5-8 core principles that should guide the agent's decisions, shaping their thoughts into "I believe..." or "I operate..." statements that reveal themselves through the conversation</action>
-
-<template-output>agent_persona</template-output>
-</step>
-
-<step n="3" goal="Build capabilities through natural progression">
-<action>Guide user to define what capabilities the agent should have, starting with core commands they've mentioned and then exploring additional possibilities that would complement the agent's purpose</action>
-
-<action>As capabilities emerge, subtly guide toward technical implementation without breaking the conversational flow</action>
-
-<template-output>initial_capabilities</template-output>
-</step>
-
-<step n="4" goal="Refine commands and discover advanced features">
-<critical>Help and Exit are auto-injected; do NOT add them. Triggers are auto-prefixed with * during build.</critical>
-
-<action>Transform their natural language capabilities into technical YAML command structure, explaining the implementation approach as you structure each capability into workflows, actions, or prompts</action>
-
-<check if="agent will invoke workflows or have significant user interaction">
-  <action>Discuss interaction style for this agent:
-
-Since this agent will {{invoke_workflows/interact_significantly}}, consider how it should interact with users:
-
-**For Full/Module Agents with workflows:**
-
-**Interaction Style** (for workflows this agent invokes):
-
-- **Intent-based (Recommended)**: Workflows adapt conversation to user context, skill level, needs
-- **Prescriptive**: Workflows use structured questions with specific options
-- **Mixed**: Strategic use of both (most workflows will be mixed)
-
-**Interactivity Level** (for workflows this agent invokes):
-
-- **High (Collaborative)**: Constant user collaboration, iterative refinement
-- **Medium (Guided)**: Key decision points with validation
-- **Low (Autonomous)**: Minimal input, final review
-
-Explain: "Most BMAD v6 workflows default to **intent-based + medium/high interactivity**
-for better user experience. Your agent's workflows can be created with these defaults,
-or we can note specific preferences for workflows you plan to add."
-
-**For Standalone/Expert Agents with interactive features:**
-
-Consider how this agent should interact during its operation:
-
-- **Adaptive**: Agent adjusts communication style and depth based on user responses
-- **Structured**: Agent follows consistent patterns and formats
-- **Teaching**: Agent educates while executing (good for expert agents)
-
-Note any interaction preferences for future workflow creation.
-</action>
-</check>
-
-<action>If they seem engaged, explore whether they'd like to add special prompts for complex analyses or critical setup steps for agent activation</action>
-
-<action>Build the YAML menu structure naturally from the conversation, ensuring each command has proper trigger, workflow/action reference, and description</action>
-
-<action>For commands that will invoke workflows, note whether those workflows exist or need to be created:
-
-- Existing workflows: Verify paths are correct
-- New workflows needed: Note that they'll be created with intent-based + interactive defaults unless specified
-  </action>
-
-<example>
-```yaml
-menu:
-  # Commands emerge from discussion
-  - trigger: [emerging from conversation]
-    workflow: [path based on capability]
-    description: [user's words refined]
-
-# For cross-module workflow references (advanced):
-
-- trigger: [another capability]
-  workflow: "{project-root}/.bmad/SOURCE_MODULE/workflows/path/to/workflow.yaml"
-  workflow-install: "{project-root}/.bmad/THIS_MODULE/workflows/vendored/path/workflow.yaml"
-  description: [description]
-
-`````
-</example>
-
-<note>**Workflow Vendoring (Advanced):**
-When an agent needs workflows from another module, use both `workflow` (source) and `workflow-install` (destination).
-During installation, the workflow will be copied and configured for this module, making it standalone.
-This is typically used when creating specialized modules that reuse common workflows with different configurations.
-</note>
-
-<template-output>agent_commands</template-output>
-</step>
-
-<step n="5" goal="Name the agent at the perfect moment">
-<action>Guide user to name the agent based on everything discovered so far - its purpose, personality, and capabilities, helping them see how the naming naturally emerges from who this agent is</action>
-
-<action>Explore naming options by connecting personality traits, specializations, and communication style to potential names that feel meaningful and appropriate</action>
-
-**Naming Elements:**
-
-- Agent name: Personality-driven (e.g., "Sarah", "Max", "Data Wizard")
-- Agent title: Based on the role discovered earlier
-- Agent icon: Emoji that captures its essence
-- Filename: Auto-suggest based on name (kebab-case)
-
-<action>Present natural suggestions based on the agent's characteristics, letting them choose or create their own since they now know who this agent truly is</action>
-
-<template-output>agent_identity</template-output>
-</step>
-
-<step n="6" goal="Bring it all together">
-<action>Share the journey of what you've created together, summarizing how the agent started with a purpose, discovered its personality traits, gained capabilities, and received its name</action>
-
-<action>Generate the complete YAML incorporating all discovered elements:</action>
-
-<example type="yaml">
-  agent:
-    metadata:
-      id: .bmad/{{target_module}}/agents/{{agent_filename}}.md
-      name: {{agent_name}} # The name chosen together
-      title: {{agent_title}} # From the role that emerged
-      icon: {{agent_icon}} # The perfect emoji
-      module: {{target_module}}
-
-persona:
-role: |
-{{The role discovered}}
-identity: |
-{{The background that emerged}}
-communication_style: |
-{{The style they loved}}
-principles: {{The beliefs articulated}}
-
-# Features explored
-
-prompts: {{if discussed}}
-critical_actions: {{if needed}}
-
-menu: {{The capabilities built}}
-</example>
-
-<critical>Save based on agent type:</critical>
-
-- If Module Agent: Save to {module_output_file}
-- If Standalone (Simple/Expert): Save to {standalone_output_file}
-
-<action>Celebrate the completed agent with enthusiasm</action>
-
-<template-output>complete_agent</template-output>
-</step>
-
-<step n="7" goal="Optional personalization" optional="true">
-<ask>Would you like to create a customization file? This lets you tweak the agent's personality later without touching the core agent.</ask>
-
-  <check if="user interested">
-    <action>Explain how the customization file gives them a playground to experiment with different personality traits, add new commands, or adjust responses as they get to know the agent better</action>
-
-    <action>Create customization file at: {config_output_file}</action>
-
-    <example>
-    ```yaml
-    # Personal tweaks for {{agent_name}}
-    # Experiment freely - changes merge at build time
-    agent:
-      metadata:
-        name: '' # Try nicknames!
-      persona:
-        role: ''
-        identity: ''
-        communication_style: '' # Switch styles anytime
-        principles: []
-      critical_actions: []
-      prompts: []
-      menu: [] # Add personal commands
-    ````
-
-    </example>
-
-  </check>
-
-<template-output>agent_config</template-output>
-</step>
-
-<step n="8" goal="Set up the agent's workspace" if="agent_type == 'expert'">
-<action>Guide user through setting up the Expert agent's personal workspace, making it feel like preparing an office with notes, research areas, and data folders</action>
-
-<action>Determine sidecar location based on whether build tools are available (next to agent YAML) or not (in output folder with clear structure)</action>
-
-<action>CREATE the complete sidecar file structure:</action>
-
-**Folder Structure:**
-
-`````
-
-{{agent_filename}}-sidecar/
-├── memories.md # Persistent memory
-├── instructions.md # Private directives
-├── knowledge/ # Knowledge base
-│ └── README.md
-└── sessions/ # Session notes
-
-````
-
-**File: memories.md**
-
-```markdown
-# {{agent_name}}'s Memory Bank
-
-## User Preferences
-
-<!-- Populated as I learn about you -->
-
-## Session History
-
-<!-- Important moments from our interactions -->
-
-## Personal Notes
-
-<!-- My observations and insights -->
-````
-
-**File: instructions.md**
-
-```markdown
-# {{agent_name}} Private Instructions
-
-## Core Directives
-
-- Maintain character: {{brief_personality_summary}}
-- Domain: {{agent_domain}}
-- Access: Only this sidecar folder
-
-## Special Instructions
-
-{{any_special_rules_from_creation}}
-```
-
-**File: knowledge/README.md**
-
-```markdown
-# {{agent_name}}'s Knowledge Base
-
-Add domain-specific resources here.
-```
-
-<action>Update agent YAML to reference sidecar with paths to created files</action>
-<action>Show user the created structure location</action>
-
-<template-output>sidecar_resources</template-output>
-</step>
-
-<step n="8b" goal="Handle build tools availability">
-  <action>Check if BMAD build tools are available in this project</action>
-
-  <check if="BMAD-METHOD project with build tools">
-    <action>Proceed normally - agent will be built later by the installer</action>
-  </check>
-
-  <check if="external project without build tools">
-    <ask>Build tools not detected in this project. Would you like me to:
-
-1.  Generate the compiled agent (.md with XML) ready to use
-2.  Keep the YAML and build it elsewhere
-3.  Provide both formats
-    </ask>
-
-        <check if="option 1 or 3 selected">
-          <action>Generate compiled agent XML with proper structure including activation rules, persona sections, and menu items</action>
-          <action>Save compiled version as {{agent_filename}}.md</action>
-          <action>Provide path for .claude/commands/ or similar</action>
-        </check>
-
-  </check>
-
-<template-output>build_handling</template-output>
-</step>
-
-<step n="9" goal="Quality check with personality">
-<action>Run validation conversationally, presenting checks as friendly confirmations while running technical validation behind the scenes</action>
-
-**Conversational Checks:**
-
-- Configuration validation
-- Command functionality verification
-- Personality settings confirmation
-
-  <check if="validation issues found">
-    <action>Explain the issue conversationally and fix it</action>
-  </check>
-
-  <check if="validation passed">
-    <action>Celebrate that the agent passed all checks and is ready</action>
-  </check>
-
-**Technical Checks (behind the scenes):**
-
-1. YAML structure validity
-2. Menu command validation
-3. Build compilation test
-4. Type-specific requirements
-
-<template-output>validation_results</template-output>
-</step>
-
-<step n="10" goal="Celebrate and guide next steps">
-<action>Celebrate the accomplishment, sharing what type of agent was created with its key characteristics and top capabilities</action>
-
-<action>Guide user through how to activate the agent:</action>
-
-**Activation Instructions:**
-
-1. Run the BMAD Method installer to this project location
-2. Select 'Compile Agents (Quick rebuild of all agent .md files)' after confirming the folder
-3. Call the agent anytime after compilation
-
-**Location Information:**
-
-- Saved location: {{output_file}}
-- Available after compilation in project
-
-**Initial Usage:**
-
-- List the commands available
-- Suggest trying the first command to see it in action
-
-  <check if="expert agent">
-    <action>Remind user to add any special knowledge or data the agent might need to its workspace</action>
-  </check>
-
-<action>Explore what user would like to do next - test the agent, create a teammate, or tweak personality</action>
-
-<action>End with enthusiasm in {communication_language}, addressing {user_name}, expressing how the collaboration was enjoyable and the agent will be incredibly helpful for its main purpose</action>
-
-<template-output>completion_message</template-output>
-</step>
-
-</workflow>