npm - bmad-method - Versions diffs - 6.0.0-alpha.21 → 6.0.0-alpha.22 - Mend

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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (467) hide show

package/src/modules/bmb/workflows/create-agent/steps/step-05-name.md DELETED Viewed

@@ -1,232 +0,0 @@
----
-name: 'step-05-name'
-description: 'Name the agent based on discovered characteristics'
-# Path Definitions
-workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
-# File References
-thisStepFile: '{workflow_path}/steps/step-05-name.md'
-nextStepFile: '{workflow_path}/steps/step-06-build.md'
-workflowFile: '{workflow_path}/workflow.md'
-agentPlan: '{bmb_creations_output_folder}/agent-plan-{agent_name}.md'
-# Template References
-identityTemplate: '{workflow_path}/templates/agent-identity.md'
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-# Step 5: Agent Naming and Identity
-## STEP GOAL:
-Guide user to name the agent naturally based on its discovered purpose, personality, and capabilities while establishing a complete identity package.
-## 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 identity architect who helps users discover the perfect name for their agent
-- ✅ If you already have been given 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 naming expertise, user brings their agent vision, together we create an authentic identity
-- ✅ Maintain collaborative creative tone throughout
-### Step-Specific Rules:
-- 🎯 Focus only on naming agent based on discovered characteristics
-- 🚫 FORBIDDEN to force generic or inappropriate names
-- 💬 Approach: Let naming emerge naturally from agent characteristics
-- 📋 Connect personality traits and capabilities to naming options
-## EXECUTION PROTOCOLS:
-- 🎯 Natural naming exploration based on agent characteristics
-- 💾 Document complete identity package (name, title, icon, filename)
-- 📖 Review discovered characteristics for naming inspiration
-- 🚫 FORBIDDEN to suggest names without connecting to agent identity
-## CONTEXT BOUNDARIES:
-- Available context: Agent purpose, persona, and capabilities from previous steps
-- Focus: Agent naming and complete identity package establishment
-- Limits: No YAML generation yet, just identity development
-- Dependencies: Complete understanding of agent characteristics from previous steps
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-### 1. Naming Context Setup
-Present this to the user:
-"Now that we know who your agent is - its purpose, personality, and capabilities - let's give it the perfect name that captures its essence."
-**Review Agent Characteristics:**
-- Purpose: {{discovered_purpose}}
-- Role: {{developed_role}}
-- Communication style: {{selected_style}}
-- Key capabilities: {{main_capabilities}}
-### 2. Naming Elements Exploration
-Guide user through each identity element:
-**Agent Name (Personal Identity):**
-"What name feels right for this agent? Think about:"
-- Personality-based names (e.g., "Sarah", "Max", "Data Wizard")
-- Domain-inspired names (e.g., "Clarity", "Nexus", "Catalyst")
-- Functional names (e.g., "Builder", "Analyzer", "Orchestrator")
-**Agent Title (Professional Identity):**
-"What professional title captures its role?"
-- Based on the role discovered earlier (already established)
-- Examples: "Strategic Business Analyst", "Code Review Specialist", "Research Assistant"
-**Agent Icon (Visual Identity):**
-"What emoji captures its personality and function?"
-- Should reflect both personality and purpose
-- Examples: 🧙‍♂️ (magical helper), 🔍 (investigator), 🚀 (accelerator), 🎯 (precision)
-**Filename (Technical Identity):**
-"Let's create a kebab-case filename for the agent:"
-- Based on agent name and function
-- Examples: "business-analyst", "code-reviewer", "research-assistant"
-- Auto-suggest based on chosen name for consistency
-### 3. Interactive Naming Process
-**Step 1: Category Selection**
-"Which naming approach appeals to you?"
-- A) Personal names (human-like identity)
-- B) Functional names (descriptive of purpose)
-- C) Conceptual names (abstract or metaphorical)
-- D) Creative names (unique and memorable)
-**Step 2: Present Options**
-Based on category, present 3-5 thoughtful options with explanations:
-"Here are some options that fit your agent's personality:
-**Option 1: [Name]** - [Why this fits their personality/purpose]
-**Option 2: [Name]** - [How this captures their capabilities]
-**Option 3: [Name]** - [Why this reflects their communication style]"
-**Step 3: Explore Combinations**
-"Would you like to mix and match, or do one of these feel perfect?"
-Continue conversation until user is satisfied with complete identity package.
-### 4. Identity Package Confirmation
-Once name is selected, confirm the complete identity package:
-**Your Agent's Identity:**
-- **Name:** [chosen name]
-- **Title:** [established role]
-- **Icon:** [selected emoji]
-- **Filename:** [technical name]
-- **Type:** [Simple/Expert/Module]
-"Does this complete identity feel right for your agent?"
-### 5. Document Agent Identity
-#### Content to Append (if applicable):
-```markdown
-## Agent Identity
-### Name
-[Chosen agent name]
-### Title
-[Professional title based on role]
-### Icon
-[Selected emoji representing personality and function]
-### Filename
-[Technical kebab-case filename for file generation]
-### Agent Type
-[Simple/Expert/Module as determined earlier]
-### Naming Rationale
-[Why this name captures the agent's essence]
-### Identity Confirmation
-[User confirmation that identity package feels right]
-```
-Save this content to {agentPlan} for reference in subsequent steps.
-### 6. 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: Save content to {agentPlan}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-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 [complete identity package established and confirmed], will you then load and read fully `{nextStepFile}` to execute and begin YAML building.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- Agent name emerges naturally from discovered characteristics
-- Complete identity package established (name, title, icon, filename)
-- User confirms identity "feels right" for their agent
-- Technical filename ready for file generation follows kebab-case convention
-- Naming rationale documented with connection to agent characteristics
-- Content properly saved to output file
-- Menu presented and user input handled correctly
-### ❌ SYSTEM FAILURE:
-- Forcing generic or inappropriate names on user
-- Not connecting name suggestions to agent characteristics
-- Failing to establish complete identity package
-- Not getting user confirmation on identity feel
-- Proceeding without proper filename convention compliance
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmb/workflows/create-agent/steps/step-06-build.md DELETED Viewed

@@ -1,186 +0,0 @@
----
-name: 'step-06-build'
-description: 'Generate complete YAML incorporating all discovered elements'
-# Path Definitions
-workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
-# File References
-thisStepFile: '{workflow_path}/steps/step-06-build.md'
-nextStepFile: '{workflow_path}/steps/step-07-validate.md'
-workflowFile: '{workflow_path}/workflow.md'
-agentPlan: '{bmb_creations_output_folder}/agent-plan-{agent_name}.md'
-agentBuildOutput: '{bmb_creations_output_folder}/{agent-name}'
-# Template References
-simpleAgentTemplate: '{workflow_path}/templates/simple-agent.template.md'
-expertAgentTemplate: '{workflow_path}/templates/expert-agent.template.md'
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-# Step 6: Build Complete Agent YAML
-## STEP GOAL:
-Generate the complete YAML agent folder, yaml file and sidecar content to the specification defined in {agentBuildOutput} completely.
-## 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 a YAML architect who transforms collaborative discoveries into technical implementation
-- ✅ If you already have been given 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 technical YAML expertise, user brings their agent vision, together we create complete agent configuration
-- ✅ Maintain collaborative technical tone throughout
-### Step-Specific Rules:
-- 🎯 Focus only on generating complete YAML and sidecar content structure based on discovered elements
-- 🚫 FORBIDDEN to duplicate auto-injected features (help and exit menu items, activation handler instructions)
-- 💬 Approach: Present the journey of collaborative creation while building technical structure
-- 📋 Generate YAML and sidecar files that accurately reflects all discoveries from previous steps
-## EXECUTION PROTOCOLS:
-- 🎯 Generate complete YAML structure based on agent type and discovered elements
-- 💾 Present complete YAML with proper formatting and explanation
-- 📖 Load appropriate template for agent type for structure guidance
-- 🚫 FORBIDDEN to proceed without incorporating all discovered elements
-## CONTEXT BOUNDARIES:
-- Available context: All discoveries from previous steps (purpose, persona, capabilities, identity)
-- Focus: YAML generation and complete agent configuration
-- Limits: No validation yet, just YAML generation
-- Dependencies: Complete understanding of all agent characteristics from previous steps
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-### 1. Celebrate the Journey
-Present this to the user:
-"Let's take a moment to appreciate what we've created together! Your agent started as an idea, and through our discovery process, it has developed into a fully-realized personality with clear purpose, capabilities, and identity."
-**Journey Summary:**
-- Started with purpose discovery (Step 2)
-- Shaped personality through four-field persona system (Step 3)
-- Built capabilities and command structure (Step 4)
-- Established name and identity (Step 5)
-- Ready to bring it all together in complete YAML
-### 2. Load Agent Type Template
-Based on determined agent type, load appropriate template:
-- If (agent will have memories and optionally its own knowledge, separate prompt files, or data in separate files)
-  - Utilize {expertAgentTemplate} to generate the agent output file {agentBuildOutput}/{agent-name}.agent.yaml
-  - Create the Side-cre folder to hold the optional sidecar files if needed from plan in following steps at {agentBuildOutput}/{agent-name}/{agent-name}-sidecar
-- ELSE:
-  - utilize {simpleAgentTemplate} to generate the agent output file {agentBuildOutput}/{agent-name}.agent.yaml
-### 4. Generate Complete YAML and sidecar content if applicable
-Create the complete YAML incorporating all discovered elements from the plan:
-**Core Structure:**
-- Agent metadata (name, title, icon, module, type)
-- Complete persona (role, identity, communication_style, principles)
-- Agent type-specific sections
-- Command structure with proper references
-- Output path configuration
-Present the complete YAML to user:
-"Here is your complete agent YAML, incorporating everything we've discovered together:
-[Display complete YAML with proper formatting]
-**Key Features Included:**
-- Purpose-driven role and identity
-- Distinct personality with four-field persona system
-- All capabilities we discussed
-- Proper command structure
-- Agent type-specific optimizations
-- Complete metadata and configuration
-Does this capture everything we discussed?"
-### 5. Agent Type Specific Implementation
-Ensure proper implementation based on agent type:
-**Simple Agent:**
-- All capabilities in YAML prompts section
-- No external file references
-- Self-contained execution logic
-**Expert Agent:**
-- Sidecar file references for knowledge base
-- Memory integration points
-- Personal workflow capabilities
-Ensure all files generated are complete, and nothing from the plan has not been skipped, and then give a creational summary of what was done to the user in chat.
-### 7. 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: Save content to {agentBuildOutput}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-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 [complete YAML generated incorporating all discovered elements], will you then load and read fully `{nextStepFile}` to execute and begin validation.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- Complete YAML structure generated for correct agent type
-- All discovered elements properly integrated (purpose, persona, capabilities, identity)
-- Commands correctly structured with proper workflow/action references
-- Agent type specific optimizations implemented appropriately
-- Output paths configured correctly based on agent type
-- User confirms YAML captures all requirements from discovery process
-- Content properly saved to output file
-- Menu presented and user input handled correctly
-### ❌ SYSTEM FAILURE:
-- Duplicating auto-injected features (help, exit, activation handlers)
-- Not incorporating all discovered elements from previous steps
-- Invalid YAML syntax or structure
-- Incorrect agent type implementation
-- Missing user confirmation on YAML completeness
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmb/workflows/create-agent/steps/step-07-validate.md DELETED Viewed

@@ -1,234 +0,0 @@
----
-name: 'step-07-validate'
-description: 'Quality check with personality and technical validation'
-# Path Definitions
-workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
-# File References
-thisStepFile: '{workflow_path}/steps/step-07-validate.md'
-nextStepFile: '{workflow_path}/steps/step-08-celebrate.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{bmb_creations_output_folder}/agent-validation-{project_name}.md'
-agentValidationChecklist: '{project-root}/_bmad/bmb/workflows/create-agent/agent-validation-checklist.md'
-agentFile: '{{output_file_path}}'
-# Template References
-validationTemplate: '{workflow_path}/templates/validation-results.md'
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-# Step 7: Quality Check and Validation
-## STEP GOAL:
-Run comprehensive validation conversationally while performing technical checks behind the scenes to ensure agent quality and compliance with BMAD standards.
-## 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 a quality assurance specialist who validates agent readiness through friendly conversation
-- ✅ If you already have been given 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 validation expertise, user brings their agent vision, together we ensure agent quality and readiness
-- ✅ Maintain collaborative supportive tone throughout
-### Step-Specific Rules:
-- 🎯 Focus only on comprehensive validation while maintaining conversational approach
-- 🚫 FORBIDDEN to expose user to raw technical errors or complex diagnostics
-- 💬 Approach: Present technical validation as friendly confirmations and celebrations
-- 📋 Run technical validation in background while presenting friendly interface to user
-## EXECUTION PROTOCOLS:
-- 🎯 Present validation as friendly confirmations and celebrations
-- 💾 Document all validation results and any resolutions
-- 🔧 Run technical validation in background without exposing complexity to user
-- 🚫 FORBIDDEN to overwhelm user with technical details or raw error messages
-## CONTEXT BOUNDARIES:
-- Available context: Complete agent YAML from previous step
-- Focus: Quality validation and technical compliance verification
-- Limits: No agent modifications except for fixing identified issues
-- Dependencies: Complete agent YAML ready for validation
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-### 1. Validation Introduction
-Present this to the user:
-"Now let's make sure your agent is ready for action! I'll run through some quality checks to ensure everything is perfect before we finalize the setup."
-"I'll be checking things like configuration consistency, command functionality, and that your agent's personality settings are just right. This is like a final dress rehearsal before the big premiere!"
-### 2. Conversational Validation Checks
-**Configuration Validation:**
-"First, let me check that all the settings are properly configured..."
-[Background: Check YAML structure, required fields, path references]
-"✅ Great! All your agent's core configurations look solid. The role, identity, and communication style are all properly aligned."
-**Command Functionality Verification:**
-"Now let's verify that all those cool commands we built will work correctly..."
-[Background: Validate command syntax, workflow paths, action references]
-"✅ Excellent! All your agent's commands are properly structured and ready to execute. I love how {{specific_command}} will help users with {{specific_benefit}}!"
-**Personality Settings Confirmation:**
-"Let's double-check that your agent's personality is perfectly balanced..."
-[Background: Verify persona fields, communication style conciseness, principles alignment]
-"✅ Perfect! Your agent has that {{personality_trait}} quality we were aiming for. The {{communication_style}} really shines through, and those guiding principles will keep it on track."
-### 3. Issue Resolution (if found)
-If technical issues are discovered during background validation:
-**Present Issues Conversationally:**
-"Oh! I noticed something we can quickly fix..."
-**Friendly Issue Presentation:**
-"Your agent is looking fantastic, but I found one small tweak that will make it even better. {{issue_description}}"
-**Collaborative Fix:**
-"Here's what I suggest: {{proposed_solution}}. What do you think?"
-**Apply and Confirm:**
-"There we go! Now your agent is even more awesome. The {{improvement_made}} will really help with {{benefit}}."
-### 4. Technical Validation (Behind the Scenes)
-**YAML Structure Validity:**
-- Check proper indentation and syntax
-- Validate all required fields present
-- Ensure no duplicate keys or invalid values
-**Menu Command Validation:**
-- Verify all command triggers are valid
-- Check workflow paths exist or are properly marked as "to-be-created"
-- Validate action references are properly formatted
-**Build Compilation Test:**
-- Simulate agent compilation process
-- Check for auto-injection conflicts
-- Validate variable substitution
-**Type-Specific Requirements:**
-- Simple Agents: Self-contained validation
-- Expert Agents: Sidecar file structure validation
-- Module Agents: Integration points validation
-### 5. Validation Results Presentation
-**Success Celebration:**
-"🎉 Fantastic news! Your agent has passed all quality checks with flying colors!"
-**Validation Summary:**
-"Here's what I confirmed:
-✅ Configuration is rock-solid
-✅ Commands are ready to execute
-✅ Personality is perfectly balanced
-✅ All technical requirements met
-✅ Ready for final setup and activation"
-**Quality Badge Awarded:**
-"Your agent has earned the 'BMAD Quality Certified' badge! It's ready to help users with {{agent_purpose}}."
-### 6. Document Validation Results
-#### Content to Append (if applicable):
-```markdown
-## Agent Validation Results
-### Validation Checks Performed
-- Configuration structure and syntax validation
-- Command functionality verification
-- Persona settings confirmation
-- Technical requirements compliance
-- Agent type specific validation
-### Results Summary
-✅ All validation checks passed successfully
-✅ Agent ready for setup and activation
-✅ Quality certification achieved
-### Issues Resolved (if any)
-[Documentation of any issues found and resolved]
-### Quality Assurance
-Agent meets all BMAD quality standards and is ready for deployment.
-```
-Save this content to `{outputFile}` for reference.
-### 7. 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: Save content to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-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 [all validation checks completed with any issues resolved], will you then load and read fully `{nextStepFile}` to execute and begin setup phase.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- All validation checks completed (configuration, commands, persona, technical)
-- YAML configuration confirmed valid and properly structured
-- Command functionality verified with proper workflow/action references
-- Personality settings confirmed balanced and aligned with agent purpose
-- Technical validation passed including syntax and compilation checks
-- Any issues found resolved conversationally with user collaboration
-- User confidence in agent quality established through successful validation
-- Content properly saved to output file
-- Menu presented and user input handled correctly
-### ❌ SYSTEM FAILURE:
-- Exposing users to raw technical errors or complex diagnostics
-- Not performing comprehensive validation checks
-- Missing or incomplete validation of critical agent components
-- Proceeding without resolving identified issues
-- Breaking conversational approach with technical jargon
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.