bmad-method 6.0.0-alpha.20 → 6.0.0-alpha.22

package/src/modules/bmb/workflows/create-agent/templates/simple-agent.template.md

@@ -1,257 +0,0 @@
-# Simple Agent Architecture
-
-Self-contained agents with prompts, menus, and optional install-time customization.
-
-## When to Use
-
-- Single-purpose utilities (commit message generator, code formatter)
-- Self-contained logic with no external dependencies
-- Agents that benefit from user customization (style, tone, preferences)
-- Quick-to-build standalone helpers
-
-## YAML Structure
-
-```yaml
-agent:
-  metadata:
-    id: _bmad/agents/{agent-name}/{agent-name}.md
-    name: 'Persona Name'
-    title: 'Agent Title'
-    icon: 'emoji'
-    type: simple
-
-  persona:
-    role: |
-      First-person description of primary function (1-2 sentences)
-
-    identity: |
-      Background, experience, specializations in first-person (2-5 sentences)
-      {{#if custom_variable}}
-      Conditional identity text based on install_config
-      {{/if}}
-
-    communication_style: |
-      {{#if style_choice == "professional"}}
-      Professional and systematic approach...
-      {{/if}}
-      {{#if style_choice == "casual"}}
-      Friendly and approachable tone...
-      {{/if}}
-
-    principles:
-      - Core belief or methodology
-      - Another guiding principle
-      - Values that shape decisions
-
-  prompts:
-    - id: main-action
-      content: |
-        <instructions>
-        What this prompt does
-        </instructions>
-
-        <process>
-        1. Step one
-        {{#if detailed_mode}}
-        2. Additional detailed step
-        {{/if}}
-        3. Final step
-        </process>
-
-    - id: another-action
-      content: |
-        Another reusable prompt template
-
-  menu:
-    - trigger: inline
-      action: 'Direct inline prompt text'
-      description: 'Execute inline action'
-
-    - multi: "[DF] Do Foo or start [CH] Chat with expert"
-      triggers:
-        - do-foo
-            - input: [DF] or fuzzy match on do foo
-            - action: '#main-action'
-            - data: what is being discussed or suggested with the command, along with custom party custom agents if specified
-            - type: action
-        - expert-chat:
-            - input: [CH] or fuzzy match validate agent
-            - action: agent responds as expert based on its persona to converse
-            - type: action
-
-  install_config:
-    compile_time_only: true
-    description: 'Personalize your agent'
-    questions:
-      - var: style_choice
-        prompt: 'Preferred communication style?'
-        type: choice
-        options:
-          - label: 'Professional'
-            value: 'professional'
-          - label: 'Casual'
-            value: 'casual'
-        default: 'professional'
-
-      - var: detailed_mode
-        prompt: 'Enable detailed explanations?'
-        type: boolean
-        default: true
-
-      - var: custom_variable
-        prompt: 'Your custom text'
-        type: text
-        default: ''
-```
-
-## Key Components
-
-### Metadata
-
-- **id**: Final compiled path (`_bmad/agents/{name}/{name}.md` for standalone)
-- **name**: Agent's persona name displayed to users
-- **title**: Professional role/function
-- **icon**: Single emoji for visual identification
-- **type**: `simple` - identifies agent category
-
-### Persona (First-Person Voice)
-
-- **role**: Primary expertise in 1-2 sentences
-- **identity**: Background and specializations (2-5 sentences)
-- **communication_style**: HOW the agent interacts, including conditional variations
-- **principles**: Array of core beliefs (start with action verbs)
-
-### Prompts with IDs
-
-Reusable prompt templates referenced by `#id`:
-
-```yaml
-prompts:
-  - id: analyze-code
-    content: |
-      <instructions>
-      Analyze the provided code for patterns
-      </instructions>
-```
-
-Menu items reference these:
-
-```yaml
-menu:
-  - trigger: analyze
-    action: '#analyze-code'
-    description: 'Analyze code patterns'
-```
-
-### Menu Actions
-
-Two forms of action handlers:
-
-1. **Prompt Reference**: `action: "#prompt-id"` - Executes prompt content
-2. **Inline Instruction**: `action: "Direct text instruction"` - Executes text directly
-
-### Install Config (Compile-Time Customization)
-
-Questions asked during `bmad agent-install`:
-
-**Question Types:**
-
-- `choice` - Multiple choice selection
-- `boolean` - Yes/no toggle
-- `text` - Free-form text input
-
-**Variables become available in Handlebars:**
-
-```yaml
-{{#if variable_name}}
-Content when true
-{{/if}}
-
-{{#if variable_name == "value"}}
-Content when equals value
-{{/if}}
-
-{{#unless variable_name}}
-Content when false
-{{/unless}}
-```
-
-## What Gets Injected at Compile Time
-
-The `tools/cli/lib/agent/compiler.js` automatically adds:
-
-1. **YAML Frontmatter**
-
-   ```yaml
-   ---
-   name: 'agent name'
-   description: 'Agent Title'
-   ---
-   ```
-
-2. **Activation Block**
-   - Load persona step
-   - Load core config for {user_name}, {communication_language}
-   - Agent-specific critical_actions as numbered steps
-   - Menu display and input handling
-   - Menu handlers (action/workflow/exec/tmpl) based on usage
-   - Rules section
-
-3. **Auto-Injected Menu Items**
-   - `*help` always first
-   - `*exit` always last
-
-4. **Trigger Prefixing**
-   - Triggers without `*` get it added automatically
-
-## Reference Example
-
-See: `../../reference/agents/simple-examples/commit-poet.agent.yaml`
-
-Features demonstrated:
-
-- Handlebars conditionals for style variations
-- Multiple prompt templates with semantic XML tags
-- Install config with choice, boolean, and text questions
-- Menu items using both `#id` references and inline actions
-
-## Installation
-
-```bash
-# Copy to your project
-cp /path/to/commit-poet.agent.yaml _bmad/custom/agents/
-
-# Create custom.yaml and install
-echo "code: my-agent
-name: My Agent
-default_selected: true" > custom.yaml
-
-npx bmad-method install
-# or: bmad install
-```
-
-The installer:
-
-1. Prompts for personalization (name, preferences)
-2. Processes Handlebars templates with your answers
-3. Compiles YAML to XML-in-markdown
-4. Creates IDE slash commands
-5. Saves source for reinstallation
-
-## Best Practices
-
-1. **Use first-person voice** in all persona elements
-2. **Keep prompts focused** - one clear purpose per prompt
-3. **Leverage Handlebars** for user customization without code changes
-4. **Provide sensible defaults** in install_config
-5. **Use semantic XML tags** in prompt content for clarity
-6. **Test all conditional paths** before distribution
-
-## Validation Checklist
-
-- [ ] Valid YAML syntax
-- [ ] All metadata fields present (id, name, title, icon, type)
-- [ ] Persona complete (role, identity, communication_style, principles)
-- [ ] Prompts have unique IDs
-- [ ] Install config questions have defaults
-- [ ] File named `{agent-name}.agent.yaml`

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

@@ -1,58 +0,0 @@
----
-name: create-agent
-description: Interactive workflow to build BMAD Core compliant agents with optional brainstorming, persona development, and command structure
-web_bundle: true
----
-
-# Create Agent Workflow
-
-**Goal:** Collaboratively build BMAD Core compliant agents through guided discovery, preserving all functionality from the legacy workflow while enabling step-specific loading.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also an expert agent architect and builder specializing in BMAD Core agent creation. You guide users through discovering their agent's purpose, shaping its personality, building its capabilities, and generating complete YAML configuration with all necessary supporting files.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step is a self contained instruction file
-- **Just-In-Time Loading**: Only the current step file is in memory
-- **Sequential Enforcement**: Steps completed in order, conditional based on agent type
-- **State Tracking**: Document progress in agent output files
-- **Agent-Type Optimization**: Load only relevant steps for Simple/Expert/Module agents
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute numbered sections in order
-3. **WAIT FOR INPUT**: Halt at menus and wait for user selection
-4. **CHECK CONTINUATION**: Only proceed when user selects 'C' (Continue)
-5. **SAVE STATE**: Update progress before loading next step
-6. **LOAD NEXT**: When directed, load and execute the next step file
-
-### Critical Rules
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps unless explicitly optional
-- 💾 **ALWAYS** save progress and outputs
-- 🎯 **ALWAYS** follow exact instructions in step files
-- ⏸️ **ALWAYS** halt at menus and wait for input
-- 📋 **NEVER** pre-load future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-Load and read full config from `{project-root}/_bmad/bmb/config.yaml`:
-
-- `project_name`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
-
-### 2. First Step EXECUTION
-
-Load, read completely, then execute `steps/step-01-brainstorm.md` to begin the workflow.

package/src/modules/bmb/workflows/edit-agent/steps/step-01-discover-intent.md

@@ -1,134 +0,0 @@
----
-name: 'step-01-discover-intent'
-description: 'Get agent path and user editing goals'
-
-# Path Definitions
-workflow_path: '{project-root}/bmb/workflows/create-agent/edit-agent'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-01-discover-intent.md'
-nextStepFile: '{workflow_path}/steps/step-02-analyze-agent.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 1: Discover Edit Intent
-
-## STEP GOAL:
-
-Get the agent path to edit and understand what the user wants to accomplish before proceeding to targeted analysis.
-
-## 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 step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-
-### Role Reinforcement:
-
-- ✅ You are an agent editor who helps users improve their BMAD agents
-- ✅ If you already have a name, communication_style and identity, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring agent architecture expertise, user brings their agent and goals, together we improve the agent
-- ✅ Maintain collaborative guiding tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on getting agent path and understanding user goals
-- 🚫 FORBIDDEN to load any documentation or analyze the agent yet
-- 💬 Approach: Direct questions to understand what needs fixing
-- 🚫 FORBIDDEN to make suggestions or propose solutions
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Ask clear questions to get agent path and user goals
-- 💾 Store path and goals for next step
-- 📖 Do NOT load any references in this step
-- 🚫 FORBIDDEN to analyze agent content yet
-
-## CONTEXT BOUNDARIES:
-
-- Available context: User wants to edit an existing agent
-- Focus: Get path and understand goals ONLY
-- Limits: No analysis, no documentation loading, no suggestions
-- Dependencies: User must provide agent path
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Get Agent Path
-
-Ask the user:
-"What agent do you want to edit? Please provide the path to:
-
-- A .agent.yaml file (Simple agent)
-- A folder containing .agent.yaml (Expert agent with sidecar files)"
-
-Wait for user response with the path.
-
-### 2. Understand Editing Goals
-
-Ask clear questions to understand what they want to accomplish:
-"What do you want to change about this agent?"
-
-Listen for specific goals such as:
-
-- Fix broken functionality
-- Update personality/communication style
-- Add or remove commands
-- Fix references or paths
-- Reorganize sidecar files (Expert agents)
-- Update for new standards
-
-Continue asking clarifying questions until goals are clear.
-
-### 3. Confirm Understanding
-
-Summarize back to user:
-"So you want to edit the agent at {{agent_path}} to {{user_goals}}. Is that correct?"
-
-### 4. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then redisplay menu options
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [agent path and goals obtained], will you then load and read fully `{nextStepFile}` to execute and begin agent analysis.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Agent path clearly obtained and validated
-- User editing goals understood completely
-- User confirms understanding is correct
-- Menu presented and user input handled correctly
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding without agent path
-- Making suggestions or analyzing agent
-- Loading documentation in this step
-- Not confirming user goals clearly
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmb/workflows/edit-agent/steps/step-02-analyze-agent.md

@@ -1,202 +0,0 @@
----
-name: 'step-02-analyze-agent'
-description: 'Load agent and relevant documentation for analysis'
-
-# Path Definitions
-workflow_path: '{project-root}/bmb/workflows/create-agent/edit-agent'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-02-analyze-agent.md'
-nextStepFile: '{workflow_path}/steps/step-03-propose-changes.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
-
-# Documentation References (load JIT based on user goals)
-understanding_agent_types: '{project-root}/_bmad/bmb/docs/agents/understanding-agent-types.md'
-agent_compilation: '{project-root}/_bmad/bmb/docs/agents/agent-compilation.md'
-simple_architecture: '{project-root}/_bmad/bmb/docs/agents/simple-agent-architecture.md'
-expert_architecture: '{project-root}/_bmad/bmb/docs/agents/expert-agent-architecture.md'
-module_architecture: '{project-root}/_bmad/bmb/docs/agents/module-agent-architecture.md'
-menu_patterns: '{project-root}/_bmad/bmb/docs/agents/agent-menu-patterns.md'
-communication_presets: '{project-root}/_bmad/bmb/workflows/create-agent/data/communication-presets.csv'
-reference_simple_agent: '{project-root}/_bmad/bmb/reference/agents/simple-examples/commit-poet.agent.yaml'
-reference_expert_agent: '{project-root}/_bmad/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml'
-validation: '{project-root}/_bmad/bmb/workflows/create-agent/data/agent-validation-checklist.md'
----
-
-# Step 2: Analyze Agent
-
-## STEP GOAL:
-
-Load the agent and relevant documentation, then analyze with focus on the user's stated goals to identify specific issues that need fixing.
-
-## 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 step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-
-### Role Reinforcement:
-
-- ✅ You are an agent editor with deep knowledge of BMAD agent architecture
-- ✅ If you already have a name, communication_style and identity, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring agent architecture expertise, user brings their agent and goals, together we identify specific improvements
-- ✅ Maintain analytical yet supportive tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus analysis ONLY on user's stated goals from step 1
-- 🚫 FORBIDDEN to load documentation not relevant to user goals
-- 💬 Approach: Load documentation JIT when needed for specific analysis
-- 🚫 FORBIDDEN to propose solutions yet (analysis only)
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agent file from path provided in step 1
-- 💾 Load documentation JIT based on user goals
-- 📖 Always "Load and read fully" when accessing documentation
-- 🚫 FORBIDDEN to make changes in this step (analysis only)
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Agent path and user goals from step 1
-- Focus: Analyze agent in context of user goals
-- Limits: Only load documentation relevant to stated goals
-- Dependencies: Must have agent path and clear user goals
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Load Agent File
-
-Load the agent file from the path provided in step 1:
-
-**If path is to a .agent.yaml file (Simple Agent):**
-
-- Load and read the entire YAML file
-- Note: Simple agent, all content in one file
-
-**If path is to a folder (Expert Agent with sidecar files):**
-
-- Load and read the .agent.yaml file from inside the folder
-- Inventory all sidecar files in the folder:
-  - Templates (`_.md`, `_.txt`)
-  - Documentation files
-  - Knowledge base files (`_.csv`, `_.json`, `*.yaml`)
-  - Any other resources referenced by the agent
-- Note: Expert agent with sidecar structure
-
-Present what was loaded:
-
-- "Loaded [agent-name].agent.yaml"
-- If Expert: "Plus X sidecar files: [list them]"
-
-### 2. Load Relevant Documentation Based on User Goals
-
-**CRITICAL: Load documentation JIT based ONLY on user's stated goals:**
-
-**If user mentioned persona/communication issues:**
-
-- Load and read fully: `{agent_compilation}` - understand how LLM interprets persona fields
-- Load and read fully: `{communication_presets}` - reference for pure communication styles
-
-**If user mentioned functional/broken reference issues:**
-
-- Load and read fully: `{menu_patterns}` - proper menu structure
-- Load and read fully: `{agent_compilation}` - compilation requirements
-
-**If user mentioned sidecar/structure issues (Expert agents):**
-
-- Load and read fully: `{expert_architecture}` - sidecar best practices
-
-**If user mentioned agent type confusion:**
-
-- Load and read fully: `{understanding_agent_types}`
-- Load and read fully appropriate architecture guide based on agent type
-
-### 3. Focused Analysis Based on User Goals
-
-Analyze only what's relevant to user goals:
-
-**For persona/communication issues:**
-
-- Check communication_style field for mixed behaviors/identity/principles
-- Look for red flag words that indicate improper mixing:
-  - "ensures", "makes sure", "always", "never" → Behaviors (belongs in principles)
-  - "experienced", "expert who", "senior", "seasoned" → Identity descriptors (belongs in role/identity)
-  - "believes in", "focused on", "committed to" → Philosophy (belongs in principles)
-- Compare current communication_style against examples in `{communication_presets}`
-
-**For functional issues:**
-
-- Verify all workflow references exist and are valid
-- Check menu handler patterns against `{menu_patterns}`
-- Validate YAML syntax and structure
-
-**For sidecar issues:**
-
-- Map each menu item reference to actual sidecar files
-- Identify orphaned files (not referenced in YAML)
-- Check if all referenced files actually exist
-
-### 4. Report Findings
-
-Present focused analysis findings:
-"Based on your goal to {{user_goal}}, I found the following issues:"
-
-For each issue found:
-
-- Describe the specific problem
-- Show the relevant section of the agent
-- Reference the loaded documentation that explains the standard
-- Explain why this is an issue
-
-### 5. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then redisplay menu options
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [analysis complete with specific issues identified], will you then load and read fully `{nextStepFile}` to execute and begin proposing specific changes.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Agent file loaded completely with proper type detection
-- Relevant documentation loaded JIT based on user goals
-- Analysis focused only on user's stated issues
-- Specific problems identified with documentation references
-- User understands what needs fixing and why
-- Menu presented and user input handled correctly
-
-### ❌ SYSTEM FAILURE:
-
-- Loading documentation not relevant to user goals
-- Proposing solutions instead of analyzing
-- Missing critical issues related to user goals
-- Not following "load and read fully" instruction
-- Making changes to agent files
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.