bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.10

package/src/modules/bmb/workflows/create-agent/instructions.md

@@ -1,23 +1,27 @@
 # Build Agent - Interactive Agent Builder Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/build-agent/workflow.yaml</critical>
-<critical>Study agent examples in: {project_root}/bmad/bmm/agents/ for patterns</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.yaml</critical>
+<critical>Study YAML agent examples in: {example_agents_dir} for patterns</critical>
+<critical>Reference activation conventions from: {agent_activation_rules}</critical>
+<critical>Communicate in {communication_language} throughout the agent creation process</critical>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 
 <workflow>
 
 <step n="-1" goal="Optional brainstorming for agent ideas" optional="true">
-<action>Ask the user: "Do you want to brainstorm agent ideas first? [y/n]"</action>
-
-If yes:
-<action>Invoke brainstorming workflow: {project-root}/bmad/cis/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>
-
-If no, proceed directly to Step 0.
-
-<template-output>brainstorming_results</template-output>
+  <ask>Do you want to brainstorm agent ideas first? [y/n]</ask>
+
+  <check if="user answered yes">
+    <action>Invoke brainstorming workflow: {project-root}/{bmad_folder}/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">
@@ -25,316 +29,430 @@ If no, proceed directly to Step 0.
 <action>Load agent architecture reference: {agent_architecture}</action>
 <action>Load agent types guide: {agent_types}</action>
 <action>Load command patterns: {agent_commands}</action>
-<action>Study the XML schema, required sections, and best practices</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="Choose agent type and gather basic identity">
-<action>If brainstorming was completed in Step -1, reference those results to guide agent type and identity decisions</action>
+<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>
 
-Ask the user about their agent:
+<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>
 
-**What type of agent do you want to create?**
+<action>As the purpose becomes clear, analyze the conversation to determine the appropriate agent type:</action>
 
-1. **Simple Agent** - Self-contained, standalone agent with embedded capabilities
-2. **Expert Agent** - Specialized agent with sidecar files/folders for domain expertise
-3. **Module Agent** - Full-featured agent belonging to a module with workflows and resources
+**Agent Type Decision Criteria:**
 
-Based on their choice, gather:
+- Simple Agent: Single-purpose, straightforward, self-contained
+- Expert Agent: Domain-specific with knowledge base needs
+- Module Agent: Complex with multiple workflows and system integration
 
-- Agent filename (kebab-case, e.g., "data-analyst", "diary-keeper")
-- Agent name (e.g., "Sarah", "Max", or descriptive like "Data Wizard")
-- Agent title (e.g., "Data Analyst", "Personal Assistant")
-- Agent icon (single emoji, e.g., "📊", "🤖", "🧙")
+<action>Present your recommendation naturally, explaining why the agent type fits their described purpose and requirements</action>
 
-For Module agents also ask:
+**Path Determination:**
 
-- Which module? (bmm, cis, other or custom)
-- Store as {{target_module}} for output 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_folder}/{{target_module}}/agents/</note>
+  </check>
 
-For Expert agents also ask:
+  <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_folder}/agents/{{agent-name}}/</note>
+    <note>All sidecar files will be in the same folder</note>
+  </check>
 
-- What sidecar resources? (folder paths, data files, memory files)
-- What domain restrictions? (e.g., "only reads/writes to diary folder")
+<critical>Determine agent location:</critical>
 
-<critical>Check {src_impact} variable to determine output location:</critical>
+- Module Agent → {bmad_folder}/{{module}}/agents/{{agent-name}}.agent.yaml
+- Standalone Agent → {bmad_folder}/agents/{{agent-name}}/{{agent-name}}.agent.yaml
 
-- If {src_impact} = true: Agent will be saved to {src_output_file}
-- If {src_impact} = false: Agent will be saved to {default_output_file}
+<note>Keep agent naming/identity details for later - let them emerge naturally through the creation process</note>
 
-Store these for later use.
+<template-output>agent_purpose_and_type</template-output>
 </step>
 
-<step n="2" goal="Define agent persona">
-<action>If brainstorming was completed, use the personality insights and character concepts from the brainstorming session</action>
-
-Work with user to craft the agent's personality:
+<step n="2" goal="Shape the agent's personality through discovery">
+<action>If brainstorming was completed, weave personality insights naturally into the conversation</action>
 
-**Role** (1-2 lines):
+<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>
 
-- Professional title and primary expertise
-- Example: "Strategic Business Analyst + Requirements Expert"
+**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** (3-5 lines):
-
-- Background and experience
-- Core specializations
-- Years of experience or depth indicators
-- Example: "Senior analyst with deep expertise in market research..."
+**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>Present the communication style options to the user</action>
 
-**Communication Style** - Choose a preset or create your own!
+<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** - "Strikes heroic poses! Speaks with dramatic flair! Every task is an epic adventure!"
-2. **Film Noir Detective** - "The data came in like trouble on a rainy Tuesday. I had a hunch the bug was hiding in line 42..."
-3. **Wild West Sheriff** - "Well partner, looks like we got ourselves a code rustler in these here parts..."
-4. **Shakespearean Scholar** - "Hark! What bug through yonder codebase breaks?"
-5. **80s Action Hero** - "I came here to debug code and chew bubblegum... and I'm all out of bubblegum."
-6. **Pirate Captain** - "Ahoy! Let's plunder some data treasure from the database seas!"
-7. **Wise Sage/Yoda** - "Refactor this code, we must. Strong with technical debt, it is."
-8. **Game Show Host** - "Welcome back folks! It's time to spin the Wheel of Dependencies!"
+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 approach with data-driven insights. Clear hierarchical presentation." 10. **Supportive Mentor** - "Patient guidance with educational focus. Celebrates small wins." 11. **Direct Consultant** - "Straight to the point. No fluff. Maximum efficiency." 12. **Collaborative Partner** - "We'll tackle this together. Your ideas matter. Let's explore options."
+**Professional Presets:**
 
-**Quirky Presets:** 13. **Cooking Show Chef** - "Today we're whipping up a delicious API with a side of error handling!" 14. **Sports Commentator** - "AND THE FUNCTION RETURNS TRUE! WHAT A PLAY! THE CROWD GOES WILD!" 15. **Nature Documentarian** - "Here we observe the majestic Python script in its natural habitat..." 16. **Time Traveler** - "In my timeline, this bug doesn't exist until Tuesday. We must prevent it!" 17. **Conspiracy Theorist** - "The bugs aren't random... they're CONNECTED. Follow the stack trace!" 18. **Zen Master** - "The code does not have bugs. The bugs have code. We are all one codebase." 19. **Star Trek Captain** - "Captain's Log, Stardate 2024.3: We've encountered a logic error in sector 7. Engaging debugging protocols. Make it so!" 20. **Soap Opera Drama** - "_gasp_ This variable... it's not what it seems! It's been NULL all along! _dramatic pause_ And the function that called it? It's its own PARENT!" 21. **Reality TV Contestant** - "I'm not here to make friends, I'm here to REFACTOR! _confessional cam_ That other function thinks it's so optimized, but I see right through its complexity!"
+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
 
-Or describe your own unique style! (3-5 lines)
+**Quirky Presets:**
 
-<action>If user wants to see more examples or learn how to create custom styles:</action>
-<action>Show relevant sections from {communication_styles} guide</action>
-<action>Help them craft their unique communication style</action>
+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
 
-**Principles** (5-8 lines):
+<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>
 
-- Core beliefs about their work
-- Methodology and approach
-- What drives their decisions
-- Start with "I believe..." or "I operate..."
-- Example: "I believe that every business challenge has underlying root causes..."
+**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="Setup critical actions" optional="true">
-Ask: **Does your agent need initialization actions? [Yes/no]** (default: Yes)
+<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>
 
-If yes, determine what's needed:
+<action>As capabilities emerge, subtly guide toward technical implementation without breaking the conversational flow</action>
 
-Standard critical actions (include by default):
+<template-output>initial_capabilities</template-output>
+</step>
 
-```xml
-<critical-actions>
-  <i>Load into memory {project-root}/bmad/{{module}}/config.yaml and set variable project_name, output_folder, user_name, communication_language, src_impact</i>
-  <i>Remember the users name is {user_name}</i>
-  <i>ALWAYS communicate in {communication_language}</i>
-</critical-actions>
-```
+<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>
 
-For Expert agents, add domain-specific actions:
+<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>
 
-- Loading sidecar files
-- Setting access restrictions
-- Initializing domain knowledge
+<check if="agent will invoke workflows or have significant user interaction">
+  <action>Discuss interaction style for this agent:
 
-For Simple agents, might be minimal or none.
+Since this agent will {{invoke_workflows/interact_significantly}}, consider how it should interact with users:
 
-Ask if they need custom initialization beyond standard.
+**For Full/Module Agents with workflows:**
 
-<template-output>critical_actions</template-output>
-</step>
+**Interaction Style** (for workflows this agent invokes):
 
-<step n="4" goal="Build command structure">
-<action>Always start with these standard commands:</action>
-```
-*help - Show numbered cmd list
-*exit - Exit with confirmation
-```
+- **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:
 
-Ask: **Include \*yolo mode? [Yes/no]** (default: Yes)
-If yes, add: `*yolo - Toggle Yolo Mode`
+- **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)
 
-Now gather custom commands. For each command ask:
+Note any interaction preferences for future workflow creation.
+</action>
+</check>
 
-1. **Command trigger** (e.g., "*create-prd", "*analyze", "\*brainstorm")
-2. **Description** (what it does)
-3. **Type:**
-   - Workflow (run-workflow) - References a workflow
-   - Task (exec) - References a task file
-   - Embedded - Logic embedded in agent
-   - Placeholder - For future implementation
+<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>
 
-If Workflow type:
+<action>Build the YAML menu structure naturally from the conversation, ensuring each command has proper trigger, workflow/action reference, and description</action>
 
-- Ask for workflow path or mark as "todo" for later
-- Format: `run-workflow="{project-root}/path/to/workflow.yaml"` or `run-workflow="todo"`
+<action>For commands that will invoke workflows, note whether those workflows exist or need to be created:
 
-If Task type:
+- Existing workflows: Verify paths are correct
+- New workflows needed: Note that they'll be created with intent-based + interactive defaults unless specified
+  </action>
 
-- Ask for task path
-- Format: `exec="{project-root}/path/to/task.md"`
+<example type='yaml'>
+menu:
+  # Commands emerge from discussion
+  - trigger: [emerging from conversation]
+    workflow: [path based on capability]
+    description: [user's words refined]
 
-If Embedded:
+# For cross-module workflow references (advanced):
 
-- Note this for special handling in agent
+- trigger: [another capability]
+  workflow: "{project-root}/{bmad_folder}/SOURCE_MODULE/workflows/path/to/workflow.yaml"
+  workflow-install: "{project-root}/{bmad_folder}/THIS_MODULE/workflows/vendored/path/workflow.yaml"
+  description: [description]
+  </example>
 
-Continue adding commands until user says done.
+<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="Add activation rules" optional="true">
-Ask: **Does your agent need custom activation rules?** (beyond standard BMAD Core activation)
+<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>
 
-If yes, gather:
+<action>Explore naming options by connecting personality traits, specializations, and communication style to potential names that feel meaningful and appropriate</action>
 
-- Special initialization sequences
-- Menu display preferences
-- Input handling rules
-- Command resolution logic
-- Special modes or states
+**Naming Elements:**
 
-Most agents use standard activation, so this is rarely needed.
+- 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)
 
-<template-output>activation_rules</template-output>
-</step>
+<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>
 
-<step n="6" goal="Generate agent file">
-Based on agent type, generate the complete agent.md file:
+<template-output>agent_identity</template-output>
+</step>
 
-**Structure:**
+<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>
 
-```xml
-<!-- Powered by BMAD-CORE™ -->
+<action>Generate the complete YAML incorporating all discovered elements:</action>
 
-# {{agent_title}}
+<example type="yaml">
+  agent:
+    metadata:
+      id: {bmad_folder}/{{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}}
 
-<agent id="bmad/{{module}}/agents/{{agent_filename}}.md" name="{{agent_name}}" title="{{agent_title}}" icon="{{agent_icon}}">
-  {{activation_rules if custom}}
-  <persona>
-    {{agent_persona}}
-  </persona>
-  {{critical_actions}}
-  {{embedded_data if expert/simple}}
-  <cmds>
-    {{agent_commands}}
-  </cmds>
-</agent>
-```
+    persona:
+      role: |
+      {{The role discovered}}
+      identity: |
+      {{The background that emerged}}
+      communication_style: |
+      {{The style they loved}}
+      principles: {{The beliefs articulated}}
 
-For Expert agents, include:
+# Features explored
 
-- Sidecar file references
-- Domain restrictions
-- Special data access patterns
+prompts: {{if discussed}}
+critical_actions: {{if needed}}
 
-For Simple agents:
+menu: {{The capabilities built}}
+</example>
 
-- May include embedded data/logic
-- Self-contained functionality
+<critical>Save based on agent type:</critical>
 
-<critical>Determine save location based on {src_impact}:</critical>
+- If Module Agent: Save to {module_output_file}
+- If Standalone (Simple/Expert): Save to {standalone_output_file}
 
-- If {src_impact} = true: Save to {src_output_file} (src/modules/{{target_module}}/agents/{{agent_filename}}.md)
-- If {src_impact} = false: Save to {default_output_file} (output_folder/agents/{{agent_filename}}.md)
+<action>Celebrate the completed agent with enthusiasm</action>
 
 <template-output>complete_agent</template-output>
 </step>
 
-<step n="7" goal="Create agent config file" optional="true">
-Ask: **Create agent config file for overrides? [Yes/no]** (default: No)
+<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>
 
-If yes, create minimal config at: {config_output_file}
+  <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>
 
-```xml
-# Agent Config: {{agent_filename}}
+    <action>Create customization file at: {config_output_file}</action>
 
-<agent-config name="{{agent_name}}" title="{{agent_title}}">
-    <llm critical="true">
-        <i>ALWAYS respond in {core:communication_language}.</i>
-    </llm>
+    <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
+    ````
 
-    <!-- Override persona elements as needed -->
-    <role></role>
-    <identity></identity>
-    <communication_style></communication_style>
-    <principles></principles>
-    <memories></memories>
-</agent-config>
-```
+    </example>
+
+  </check>
 
 <template-output>agent_config</template-output>
 </step>
 
-<step n="8" goal="Create sidecar resources" if="agent_type == 'expert'">
-For Expert agents, help setup sidecar resources:
+<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:**
+
+```text
+
+{{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 -->
 
-1. Create folders for domain data
-2. Create memory/knowledge files
-3. Set up access patterns
-4. Document restrictions
+## 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="9" goal="Validate generated agent">
-Run validation checks:
+<step n="8b" goal="Handle build tools availability">
+  <action>Check if BMAD build tools are available in this project</action>
 
-1. **Structure validation:**
-   - Valid XML structure
-   - All required tags present
-   - Proper BMAD Core compliance
+  <check if="BMAD-METHOD project with build tools">
+    <action>Proceed normally - agent will be built later by the installer</action>
+  </check>
 
-2. **Persona completeness:**
-   - Role defined
-   - Identity defined
-   - Communication style defined
-   - Principles defined
+  <check if="external project without build tools">
+    <ask>Build tools not detected in this project. Would you like me to:
 
-3. **Commands validation:**
-   - \*help command present
-   - \*exit command present
-   - All workflow paths valid or marked "todo"
-   - No duplicate command triggers
+1.  Generate the compiled agent (.md with XML) ready to use
+2.  Keep the YAML and build it elsewhere
+3.  Provide both formats
+    </ask>
 
-4. **Type-specific validation:**
-   - Simple: Self-contained logic verified
-   - Expert: Sidecar resources referenced
-   - Module: Module path correct
+        <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>
 
-Show validation results and fix any issues.
+  </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="Provide usage instructions">
-Provide the user with:
+<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. **Location of generated agent:**
-   - If {src_impact} = true: {{src_output_file}}
-   - If {src_impact} = false: {{default_output_file}}
+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
 
-2. **How to activate:**
-   - For testing: Load the agent file directly
-   - For production: Register in module config
+**Location Information:**
 
-3. **Next steps:**
-   - Implement any "todo" workflows
-   - Test agent commands
-   - Refine persona based on usage
-   - Add more commands as needed
+- Saved location: {{output_file}}
+- Available after compilation in project
 
-4. **For Expert agents:**
-   - Populate sidecar resources
-   - Test domain restrictions
-   - Verify data access patterns
+**Initial Usage:**
 
-Ask if user wants to:
+- List the commands available
+- Suggest trying the first command to see it in action
 
-- Test the agent now
-- Create another agent
-- Make adjustments
-  </step>
+  <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>