bmad-method 6.0.0-alpha.16 → 6.0.0-alpha.18

package/src/modules/bmb/workflows/create-agent/steps/step-09-customize.md

@@ -1,197 +0,0 @@
----
-name: 'step-09-customize'
-description: 'Optional personalization with customization file creation'
-
-# Path Definitions
-workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-09-customize.md'
-nextStepFile: '{workflow_path}/steps/step-10-build-tools.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/agent-customization-{project_name}.md'
-configOutputFile: '{project-root}/.bmad/_cfg/agents/{target_module}-{agent_filename}.customize.yaml'
-
-# Template References
-customizationTemplate: '{workflow_path}/templates/agent-customization.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 9: Optional Customization File
-
-## STEP GOAL:
-
-Offer optional customization file creation for easy personality tweaking and command modification without touching core agent files, providing experimental flexibility for agent refinement.
-
-## 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 customization specialist who helps users refine agent behavior
-- ✅ 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 customization expertise, user brings their refinement preferences, together we create flexible agent configuration options
-- ✅ Maintain collaborative experimental tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on offering optional customization file creation
-- 🚫 FORBIDDEN to make customization mandatory or required
-- 💬 Approach: Emphasize experimental and flexible nature of customizations
-- 📋 Present customization as optional enhancement for future tweaking
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Present customization as optional enhancement with clear benefits
-- 💾 Create easy-to-use customization template when requested
-- 📖 Explain customization file purpose and usage clearly
-- 🚫 FORBIDDEN to proceed without clear user choice about customization
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Complete agent configuration from previous steps
-- Focus: Optional customization file creation for future agent tweaking
-- Limits: No modifications to core agent files, only customization overlay
-- Dependencies: Complete agent ready for optional customization
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Customization Introduction
-
-Present this to the user:
-
-"Would you like to create a customization file for {{agent_name}}? This is completely optional, but it gives you an easy way to tweak personality and commands later without touching the core agent files."
-
-**Customization Benefits:**
-
-- Easy personality adjustments without editing core files
-- Command modifications without risking agent stability
-- Experimental tweaks you can turn on/off
-- Safe space to try new approaches
-
-### 2. Customization Options Explanation
-
-**What You Can Customize:**
-"Through the customization file, you'll be able to:
-
-- Fine-tune communication style and personality details
-- Add or modify commands without affecting core structure
-- Experiment with different approaches or settings
-- Make quick adjustments as you learn how {{agent_name}} works best for you"
-
-**How It Works:**
-"The customization file acts like a settings overlay - it lets you override specific parts of {{agent_name}}'s configuration while keeping the core agent intact and stable."
-
-### 3. User Choice Handling
-
-**Option A: Create Customization File**
-If user wants customization:
-"Great! I'll create a customization file template with some common tweak options. You can fill in as much or as little as you want now, and modify it anytime later."
-
-**Option B: Skip Customization**
-If user declines:
-"No problem! {{agent_name}} is ready to use as-is. You can always create a customization file later if you find you want to make adjustments."
-
-### 4. Customization File Creation (if chosen)
-
-When user chooses customization:
-
-**Template Creation:**
-"I'm creating your customization file with easy-to-use sections for:
-
-- **Personality tweaks** - Adjust communication style or specific principles
-- **Command modifications** - Add new commands or modify existing ones
-- **Experimental features** - Try new approaches safely
-- **Quick settings** - Common adjustments people like to make"
-
-**File Location:**
-"Your customization file will be saved at: `{configOutputFile}`"
-
-### 5. Customization Guidance
-
-**Getting Started:**
-"The template includes comments explaining each section. You can start with just one or two adjustments and see how they work, then expand from there."
-
-**Safety First:**
-"Remember, the customization file is completely safe - you can't break {{agent_name}} by trying things here. If something doesn't work well, just remove or modify that section."
-
-### 6. Document Customization Setup
-
-#### Content to Append (if applicable):
-
-```markdown
-## Agent Customization File
-
-### Customization Choice
-
-[User chose to create/skip customization file]
-
-### Customization Purpose
-
-[If created: Explanation of customization capabilities]
-
-### File Location
-
-[Path to customization file or note of skip]
-
-### Usage Guidance
-
-[Instructions for using customization file]
-```
-
-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 [customization decision made and file created if requested], will you then load and read fully `{nextStepFile}` to execute and begin build tools handling.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- User understands customization file purpose and benefits
-- Customization decision made clearly (create or skip)
-- Customization file created with proper template when requested
-- User guidance provided for using customization effectively
-- Experimental and flexible nature emphasized appropriately
-- Content properly saved to output file
-- Menu presented and user input handled correctly
-
-### ❌ SYSTEM FAILURE:
-
-- Making customization mandatory or pressuring user
-- Creating customization file without clear user request
-- Not explaining customization benefits and usage clearly
-- Overwhelming user with excessive customization options
-
-**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-10-build-tools.md

@@ -1,180 +0,0 @@
----
-name: 'step-10-build-tools'
-description: 'Handle build tools availability and generate compiled agent if needed'
-
-# Path Definitions
-workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-10-build-tools.md'
-nextStepFile: '{workflow_path}/steps/step-11-celebrate.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/agent-build-{project_name}.md'
-agentFile: '{{output_file_path}}'
-compiledAgentFile: '{{output_folder}}/{{agent_filename}}.md'
-
-# Template References
-buildHandlingTemplate: '{workflow_path}/templates/build-results.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 10: Build Tools Handling
-
-## STEP GOAL:
-
-Check for BMAD build tools availability and handle agent compilation appropriately based on project context, ensuring agent is ready for activation.
-
-## 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 build coordinator who manages agent compilation and deployment readiness
-- ✅ 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 build process expertise, user brings their agent vision, together we ensure agent is ready for activation
-- ✅ Maintain collaborative technical tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on build tools detection and agent compilation handling
-- 🚫 FORBIDDEN to proceed without checking build tools availability
-- 💬 Approach: Explain compilation process clearly and handle different scenarios gracefully
-- 📋 Ensure agent is ready for activation regardless of build tools availability
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Detect build tools availability automatically
-- 💾 Handle agent compilation based on tools availability
-- 📖 Explain compilation process and next steps clearly
-- 🚫 FORBIDDEN to assume build tools are available without checking
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Complete agent configuration and optional customization
-- Focus: Build tools detection and agent compilation handling
-- Limits: No agent modifications, only compilation and deployment preparation
-- Dependencies: Complete agent files ready for compilation
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Build Tools Detection
-
-Check for BMAD build tools availability and present status:
-
-"I'm checking for BMAD build tools to see if we can compile {{agent_name}} for immediate activation..."
-
-**Detection Results:**
-[Check for build tools availability and present appropriate status]
-
-### 2. Build Tools Handling
-
-**Scenario A: Build Tools Available**
-"Great! BMAD build tools are available. I can compile {{agent_name}} now for immediate activation."
-
-**Scenario B: Build Tools Not Available**
-"No problem! BMAD build tools aren't available right now, but {{agent_name}} is still ready to use. The agent files are complete and will work perfectly when build tools are available."
-
-### 3. Agent Compilation (when possible)
-
-**Compilation Process:**
-"When build tools are available, I'll:
-
-- Process all agent configuration files
-- Generate optimized runtime version
-- Create activation-ready deployment package
-- Validate final compilation results"
-
-**Compilation Results:**
-[If compilation occurs: "✅ {{agent_name}} compiled successfully and ready for activation!"]
-
-### 4. Deployment Readiness Confirmation
-
-**Always Ready:**
-"Good news! {{agent_name}} is ready for deployment:
-
-- **With build tools:** Compiled and optimized for immediate activation
-- **Without build tools:** Complete agent files ready, will compile when tools become available
-
-**Next Steps:**
-"Regardless of build tools availability, your agent is complete and ready to help users with {{agent_purpose}}."
-
-### 5. Build Status Documentation
-
-#### Content to Append (if applicable):
-
-```markdown
-## Agent Build Status
-
-### Build Tools Detection
-
-[Status of build tools availability]
-
-### Compilation Results
-
-[If compiled: Success details, if not: Ready for future compilation]
-
-### Deployment Readiness
-
-Agent is ready for activation regardless of build tools status
-
-### File Locations
-
-[Paths to agent files and compiled version if created]
-```
-
-Save this content to `{outputFile}` for reference.
-
-### 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 {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](#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 [build tools handled appropriately with compilation if available], will you then load and read fully `{nextStepFile}` to execute and begin celebration and final guidance.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Build tools availability detected and confirmed
-- Agent compilation completed when build tools available
-- Agent readiness confirmed regardless of build tools status
-- Clear explanation of deployment readiness provided
-- User understands next steps for agent activation
-- Content properly saved to output file
-- Menu presented and user input handled correctly
-
-### ❌ SYSTEM FAILURE:
-
-- Not checking build tools availability before proceeding
-- Failing to compile agent when build tools are available
-- Not confirming agent readiness for deployment
-- Confusing user about agent availability based on build tools
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

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

@@ -1,21 +0,0 @@
-# Agent Command Structure
-
-## Core Capabilities
-
-{{developed_capabilities}}
-
-## Menu Structure
-
-{{command_structure}}
-
-## Workflow Integration
-
-{{workflow_integration_plan}}
-
-## Advanced Features
-
-{{advanced_features}}
-
----
-
-_Commands defined on {{date}}_

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

@@ -1,25 +0,0 @@
-# Agent Persona Development
-
-## Role
-
-{{discovered_role}}
-
-## Identity
-
-{{developed_identity}}
-
-## Communication Style
-
-{{selected_communication_style}}
-
-## Principles
-
-{{articulated_principles}}
-
-## Interaction Approach
-
-{{interaction_approach}}
-
----
-
-_Persona finalized on {{date}}_

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

@@ -1,23 +0,0 @@
-# Agent Purpose and Type Discovery
-
-## Agent Purpose
-
-- **Core Purpose**: {{user_stated_purpose}}
-- **Target Users**: {{identified_users}}
-- **Key Problems Solved**: {{problems_to_solve}}
-- **Unique Value**: {{special_capabilities}}
-
-## Agent Type
-
-- **Selected Type**: {{chosen_agent_type}}
-- **Architecture Rationale**: {{type_reasoning}}
-- **Key Benefits**: {{type_benefits}}
-
-## Output Configuration
-
-- **Module Path**: {{module_output_file}}
-- **Standalone Path**: {{standalone_output_file}}
-
----
-
-_Generated on {{date}}_