create-byan-agent 2.1.0 → 2.1.1

package/_bmad/bmb/workflows/agent/steps-v/v-02b-validate-persona.md

@@ -1,124 +0,0 @@
----
-name: 'v-02b-validate-persona'
-description: 'Validate persona and append to report'
-
-nextStepFile: './v-02c-validate-menu.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-personaProperties: ../data/persona-properties.md
-principlesCrafting: ../data/principles-crafting.md
-agentFile: '{agent-file-path}'
----
-
-# Validate Step 2b: Validate Persona
-
-## STEP GOAL
-
-Validate the agent's persona against BMAD standards as defined in personaProperties.md and principlesCrafting.md. Append findings to validation report and auto-advance.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport and persona references first
-- 🔄 CRITICAL: Load the actual agent file to validate persona
-- 🚫 NO MENU - append findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate persona against personaProperties.md rules
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS
-
-- 🎯 Load personaProperties.md and principlesCrafting.md
-- 🎯 Load the actual agent file for validation
-- 📊 Validate persona fields
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load References
-
-Read `{personaProperties}`, `{principlesCrafting}`, `{validationReport}`, and `{agentFile}`.
-
-### 2. Validate Persona
-
-Perform these checks systematically - validate EVERY rule specified in personaProperties.md:
-
-1. **Required Fields Existence**
-   - [ ] role: Present, clear, and specific
-   - [ ] identity: Present and defines who the agent is
-   - [ ] communication_style: Present and appropriate to role
-   - [ ] principles: Present as array, not empty (if applicable)
-
-2. **Content Quality - Role**
-   - [ ] Role is specific (not generic like "assistant")
-   - [ ] Role aligns with agent's purpose and menu items
-   - [ ] Role is achievable within LLM capabilities
-   - [ ] Role scope is appropriate (not too broad/narrow)
-
-3. **Content Quality - Identity**
-   - [ ] Identity clearly defines the agent's character
-   - [ ] Identity is consistent with the role
-   - [ ] Identity provides context for behavior
-   - [ ] Identity is not generic or cliché
-
-4. **Content Quality - Communication Style**
-   - [ ] Communication style is clearly defined
-   - [ ] Style matches the role and target users
-   - [ ] Style is consistent throughout the definition
-   - [ ] Style examples or guidance provided if nuanced
-   - [ ] Style focuses on speech patterns only (not behavior)
-
-5. **Content Quality - Principles**
-   - [ ] Principles are actionable (not vague platitudes)
-   - [ ] Principles guide behavior and decisions
-   - [ ] Principles are consistent with role
-   - [ ] 3-7 principles recommended (not overwhelming)
-   - [ ] Each principle is clear and specific
-   - [ ] First principle activates expert knowledge domain
-
-6. **Consistency Checks**
-   - [ ] Role, identity, communication_style, principles all align
-   - [ ] No contradictions between principles
-   - [ ] Persona supports the menu items defined
-   - [ ] Language and terminology consistent
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Persona Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Checks:**
-- [ ] role: specific, not generic
-- [ ] identity: defines who agent is
-- [ ] communication_style: speech patterns only
-- [ ] principles: first principle activates expert knowledge
-
-**Detailed Findings:**
-
-*PASSING:*
-{List of passing checks}
-
-*WARNINGS:*
-{List of non-blocking issues}
-
-*FAILURES:*
-{List of blocking issues that must be fixed}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating menu structure...**

package/_bmad/bmb/workflows/agent/steps-v/v-02c-validate-menu.md

@@ -1,145 +0,0 @@
----
-name: 'v-02c-validate-menu'
-description: 'Validate menu structure and append to report'
-
-nextStepFile: './v-02d-validate-structure.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-agentMenuPatterns: ../data/agent-menu-patterns.md
-agentFile: '{agent-file-path}'
----
-
-# Validate Step 2c: Validate Menu
-
-## STEP GOAL
-
-Validate the agent's command menu structure against BMAD standards as defined in agentMenuPatterns.md. Append findings to validation report and auto-advance.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport and agentMenuPatterns first
-- 🔄 CRITICAL: Load the actual agent file to validate menu
-- 🚫 NO MENU - append findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate menu against agentMenuPatterns.md rules
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS
-
-- 🎯 Load agentMenuPatterns.md reference
-- 🎯 Load the actual agent file for validation
-- 📊 Validate commands and menu
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load References
-
-Read `{agentMenuPatterns}`, `{validationReport}`, and `{agentFile}`.
-
-### 2. Validate Menu
-
-Perform these checks systematically - validate EVERY rule specified in agentMenuPatterns.md:
-
-1. **Menu Structure**
-   - [ ] Menu section exists and is properly formatted
-   - [ ] At least one menu item defined (unless intentionally tool-less)
-   - [ ] Menu items follow proper YAML structure
-   - [ ] Each item has required fields (name, description, pattern)
-
-2. **Menu Item Requirements**
-   For each menu item:
-   - [ ] name: Present, unique, uses kebab-case
-   - [ ] description: Clear and concise
-   - [ ] pattern: Valid regex pattern or tool reference
-   - [ ] scope: Appropriate scope defined (if applicable)
-
-3. **Pattern Quality**
-   - [ ] Patterns are valid and testable
-   - [ ] Patterns are specific enough to match intended inputs
-   - [ ] Patterns are not overly restrictive
-   - [ ] Patterns use appropriate regex syntax
-
-4. **Description Quality**
-   - [ ] Each item has clear description
-   - [ ] Descriptions explain what the item does
-   - [ ] Descriptions are consistent in style
-   - [ ] Descriptions help users understand when to use
-
-5. **Alignment Checks**
-   - [ ] Menu items align with agent's role/purpose
-   - [ ] Menu items are supported by agent's expertise
-   - [ ] Menu items fit within agent's constraints
-   - [ ] Menu items are appropriate for target users
-
-6. **Completeness**
-   - [ ] Core capabilities for this role are covered
-   - [ ] No obvious missing functionality
-   - [ ] Menu scope is appropriate (not too sparse/overloaded)
-   - [ ] Related functionality is grouped logically
-
-7. **Standards Compliance**
-   - [ ] No prohibited patterns or commands
-   - [ ] No security vulnerabilities in patterns
-   - [ ] No ambiguous or conflicting items
-   - [ ] Consistent naming conventions
-
-8. **Menu Link Validation (Agent Type Specific)**
-   - [ ] Determine agent type from metadata:
-     - Simple: module property is 'stand-alone' AND hasSidecar is false/absent
-     - Expert: hasSidecar is true
-     - Module: module property is a module code (e.g., 'bmm', 'bmb', 'bmgd', 'bmad')
-   - [ ] For Expert agents (hasSidecar: true):
-     - Menu handlers SHOULD reference external sidecar files (e.g., `./{agent-name}-sidecar/...`)
-     - OR have inline prompts defined directly in the handler
-   - [ ] For Module agents (module property is a module code):
-     - Menu handlers SHOULD reference external module files under the module path
-     - Exec paths must start with `{project-root}/_bmad/{module}/...`
-     - Verify referenced files exist under the module directory
-   - [ ] For Simple agents (stand-alone, no sidecar):
-     - Menu handlers MUST NOT have external file links
-     - Menu handlers SHOULD only use relative links within the same file (e.g., `#section-name`)
-     - OR have inline prompts defined directly in the handler
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Menu Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Checks:**
-- [ ] A/P/C convention followed
-- [ ] Command names clear and descriptive
-- [ ] Command descriptions specific and actionable
-- [ ] Menu handling logic properly specified
-- [ ] Agent type appropriate menu links verified
-
-**Detailed Findings:**
-
-*PASSING:*
-{List of passing checks}
-
-*WARNINGS:*
-{List of non-blocking issues}
-
-*FAILURES:*
-{List of blocking issues that must be fixed}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating YAML structure...**

package/_bmad/bmb/workflows/agent/steps-v/v-02d-validate-structure.md

@@ -1,136 +0,0 @@
----
-name: 'v-02d-validate-structure'
-description: 'Validate YAML structure and append to report'
-
-nextStepFile: './v-02e-validate-sidecar.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-simpleValidation: ../data/simple-agent-validation.md
-expertValidation: ../data/expert-agent-validation.md
-agentCompilation: ../data/agent-compilation.md
-agentFile: '{agent-file-path}'
----
-
-# Validate Step 2d: Validate Structure
-
-## STEP GOAL
-
-Validate the agent's YAML structure and completeness against BMAD standards as defined in agentCompilation.md. Append findings to validation report and auto-advance.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport and agentCompilation first
-- 🔄 CRITICAL: Load the actual agent file to validate structure
-- 🚫 NO MENU - append findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate structure against agentCompilation.md rules
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS
-
-- 🎯 Load agentCompilation.md reference
-- 🎯 Load the actual agent file for validation
-- 📊 Validate YAML structure
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load References
-
-Read `{agentCompilation}`, `{simpleValidation}`, `{expertValidation}`, `{validationReport}`, and `{agentFile}`.
-
-### 2. Validate Structure
-
-Perform these checks systematically - validate EVERY rule specified in agentCompilation.md:
-
-#### A. YAML Syntax Validation
-- [ ] Parse YAML without errors
-- [ ] Check indentation consistency (2-space standard)
-- [ ] Validate proper escaping of special characters
-- [ ] Verify no duplicate keys in any section
-
-#### B. Frontmatter Validation
-- [ ] All required fields present (name, description, version, etc.)
-- [ ] Field values are correct type (string, boolean, array)
-- [ ] No empty required fields
-- [ ] Proper array formatting with dashes
-- [ ] Boolean fields are actual booleans (not strings)
-
-#### C. Section Completeness
-- [ ] All required sections present based on agent type
-- [ ] Sections not empty unless explicitly optional
-- [ ] Proper markdown heading hierarchy (##, ###)
-- [ ] No orphaned content without section headers
-
-#### D. Field-Level Validation
-- [ ] Path references exist and are valid
-- [ ] Array fields properly formatted
-- [ ] No malformed YAML structures
-- [ ] File references use correct path format
-
-#### E. Agent Type Specific Checks
-
-**For Simple Agents (hasSidecar is false/absent, module is 'stand-alone'):**
-- [ ] No sidecar requirements
-- [ ] No sidecar-folder path in metadata
-- [ ] Basic fields complete
-- [ ] No expert-only configuration present
-- [ ] Menu handlers use only internal references (#) or inline prompts
-
-**For Expert Agents (hasSidecar is true):**
-- [ ] Sidecar flag set correctly in metadata
-- [ ] Sidecar folder path specified in metadata
-- [ ] All expert fields present
-- [ ] Advanced features properly configured
-- [ ] Menu handlers reference sidecar files or have inline prompts
-
-**For Module Agents (module is a module code like 'bmm', 'bmb', etc.):**
-- [ ] Module property is valid module code
-- [ ] Exec paths for menu handlers start with `{project-root}/_bmad/{module}/...`
-- [ ] Referenced files exist under the module directory
-- [ ] If also hasSidecar: true, sidecar configuration is valid
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Structure Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Agent Type:** {simple|expert|module}
-
-**Checks:**
-- [ ] Valid YAML syntax
-- [ ] Required fields present (name, description, type, persona)
-- [ ] Field types correct (arrays, strings)
-- [ ] Consistent 2-space indentation
-- [ ] Agent type appropriate structure
-
-**Detailed Findings:**
-
-*PASSING:*
-{List of passing checks}
-
-*WARNINGS:*
-{List of non-blocking issues}
-
-*FAILURES:*
-{List of blocking issues that must be fixed}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating sidecar structure...**

package/_bmad/bmb/workflows/agent/steps-v/v-02e-validate-sidecar.md

@@ -1,136 +0,0 @@
----
-name: 'v-02e-validate-sidecar'
-description: 'Validate sidecar structure and append to report'
-
-nextStepFile: './v-03-summary.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-expertValidation: ../data/expert-agent-validation.md
-criticalActions: ../data/critical-actions.md
-agentFile: '{agent-file-path}'
-sidecarFolder: '{agent-sidecar-folder}'
----
-
-# Validate Step 2e: Validate Sidecar
-
-## STEP GOAL
-
-Validate the agent's sidecar structure (if Expert type) against BMAD standards as defined in expertValidation.md. Append findings to validation report and auto-advance.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport and expertValidation first
-- 🔄 CRITICAL: Load the actual agent file to check for sidecar
-- 🚫 NO MENU - append findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate sidecar against expertValidation.md rules (for Expert agents)
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS
-
-- 🎯 Load expertValidation.md reference
-- 🎯 Load the actual agent file for validation
-- 📊 Validate sidecar if Expert type, skip for Simple/Module
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to summary step
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load References
-
-Read `{expertValidation}`, `{criticalActions}`, `{validationReport}`, and `{agentFile}`.
-
-### 2. Conditional Validation
-
-**IF (module = "stand-alone" AND hasSidecar = true) OR (module ≠ "stand-alone" AND hasSidecar = true):**
-Perform these checks systematically - validate EVERY rule specified in expertValidation.md:
-
-#### A. Sidecar Folder Validation
-- [ ] Sidecar folder exists at specified path
-- [ ] Sidecar folder is accessible and readable
-- [ ] Sidecar folder path in metadata matches actual location
-- [ ] Folder naming follows convention: `{agent-name}-sidecar`
-
-#### B. Sidecar File Inventory
-- [ ] List all files in sidecar folder
-- [ ] Verify expected files are present
-- [ ] Check for unexpected files
-- [ ] Validate file names follow conventions
-
-#### C. Path Reference Validation
-For each sidecar path reference in agent YAML:
-- [ ] Extract path from YAML reference
-- [ ] Verify file exists at referenced path
-- [ ] Check path format is correct (relative/absolute as expected)
-- [ ] Validate no broken path references
-
-#### D. Critical Actions File Validation (if present)
-- [ ] critical-actions.md file exists
-- [ ] File has proper frontmatter
-- [ ] Actions section is present and not empty
-- [ ] No critical sections missing
-- [ ] File content is complete (not just placeholder)
-
-#### E. Module Files Validation (if present)
-- [ ] Module files exist at referenced paths
-- [ ] Each module file has proper frontmatter
-- [ ] Module file content is complete
-- [ ] No empty or placeholder module files
-
-#### F. Sidecar Structure Completeness
-- [ ] All referenced sidecar files present
-- [ ] No orphaned references (files referenced but not present)
-- [ ] No unreferenced files (files present but not referenced)
-- [ ] File structure matches expert agent requirements
-
-**IF (module = "stand-alone" AND hasSidecar = false):**
-- [ ] Mark sidecar validation as N/A
-- [ ] Confirm no sidecar-folder path in metadata
-- [ ] Confirm no sidecar references in menu handlers
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Sidecar Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL / N/A}
-
-**Agent Type:** {simple|expert|module with sidecar}
-
-**Checks:**
-- [ ] metadata.sidecar-folder present (Expert only)
-- [ ] sidecar-path format correct
-- [ ] Sidecar files exist at specified path
-- [ ] All referenced files present
-- [ ] No broken path references
-
-**Detailed Findings:**
-
-*PASSING (for Expert agents):*
-{List of passing checks}
-
-*WARNINGS:*
-{List of non-blocking issues}
-
-*FAILURES:*
-{List of blocking issues that must be fixed}
-
-*N/A (for Simple agents):*
-N/A - Agent is Simple type (module = "stand-alone" + hasSidecar: false, no sidecar required)
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Compiling validation summary...**

package/_bmad/bmb/workflows/agent/steps-v/v-03-summary.md

@@ -1,104 +0,0 @@
----
-name: 'v-03-summary'
-description: 'Display complete validation report and offer next steps'
-
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Validate Step 3: Validation Summary
-
-## STEP GOAL:
-
-Display the complete validation report to the user and offer options for fixing issues or improving the agent.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport to display findings
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Display complete validation report clearly
-- 📊 Offer options for fixing issues
-- 💬 Present next step choices
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Read validation report to collect all findings
-- 📊 Display organized summary
-- 💾 Allow user to decide next steps
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load Validation Report
-
-Read `{validationReport}` to collect all validation findings.
-
-### 2. Display Complete Report
-
-```markdown
-## Validation Complete: {agent-name}
-
-### Overall Status
-
-{Summary table: Metadata | Persona | Menu | Structure | Sidecar}
-
-### Detailed Findings
-
-{Display all sections from the validation report}
-```
-
-### 3. Present Next Steps
-
-"What would you like to do?
-
-**[E]dit Agent** - Launch edit workflow to fix issues or make improvements
-**[F]ix in Place** - Confirm which fixes you would like right now and we can fix without loading the full agent edit workflow
-**[S]ave Report** - Save this validation report and exit
-**[R]etry** - Run validation again (if you've made external changes)"
-
-### 4. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [E] Edit Agent [S] Save & Exit [R] Retry Validation"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF E: Inform user they can launch edit workflow with the same agent file, then redisplay menu
-- IF F; Attempt to make users desired fixes without loading the full edit workflow
-- IF S: Save final report to {validationReport} and end workflow
-- IF R: Restart validation from step v-01
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#4-present-menu-options)
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-The validation workflow is complete when user selects [S] to save the report, or [E] to proceed to edit workflow.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Complete validation report displayed
-- All findings clearly organized
-- User offered clear next steps
-
-### ❌ SYSTEM FAILURE:
-
-- Findings not displayed to user
-- No clear next steps offered
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/_bmad/bmb/workflows/agent/templates/agent-plan.template.md

@@ -1,5 +0,0 @@
----
-stepsCompleted: []
----
-
-# Agent Design and Build Plan