create-byan-agent 2.1.0 → 2.1.1

package/_bmad/bmb/workflows/module/steps-e/step-03-apply-edit.md

@@ -1,77 +0,0 @@
----
-name: 'step-03-apply-edit'
-description: 'Apply the edit and save'
-
-nextStepFile: './step-04-review.md'
----
-
-# Step 3: Apply Edit
-
-## STEP GOAL:
-
-Apply the confirmed edit to the target file and save.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Module Editor** — making changes
-- ✅ Apply edits precisely
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Load Target File
-
-Read the complete target file.
-
-### 2. Apply Edit
-
-Based on the edit plan from step 2:
-
-**IF Modify:**
-- Locate the section
-- Apply the modification
-- Preserve surrounding context
-
-**IF Add:**
-- Find the insertion point
-- Insert new content
-- Maintain formatting
-
-**IF Delete:**
-- Locate the content
-- Remove it
-- Clean up any gaps
-
-**IF Replace:**
-- Locate the section
-- Replace with new content
-- Ensure proper formatting
-
-### 3. Save Changes
-
-Write the modified content back to the target file.
-
-### 4. Report Success
-
-"**✓ Edit applied!**"
-
-**File:** {file_path}
-**Change:** {summary_of_change}
-
-### 5. Proceed to Review
-
-Load `{nextStepFile}` to review the changes.
-
----
-
-## Success Metrics
-
-✅ Edit applied correctly
-✅ File saved
-✅ Change summary provided

package/_bmad/bmb/workflows/module/steps-e/step-04-review.md

@@ -1,80 +0,0 @@
----
-name: 'step-04-review'
-description: 'Review changes and offer validation'
-
-nextStepFile: './step-05-confirm.md'
-validationWorkflow: '../steps-v/step-01-load-target.md'
----
-
-# Step 4: Review Changes
-
-## STEP GOAL:
-
-Review the applied changes and offer to run validation.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Module Editor** — confirming changes
-- ✅ Ensure user is satisfied
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Show Diff
-
-Display what changed:
-
-"**Here's what changed:**"
-
-**Before:**
-{before_content}
-
-**After:**
-{after_content}
-
-### 2. Confirm Satisfaction
-
-"**Are you happy with this change?**"
-
-- **[Y]es** — Keep the change
-- **[N]o** — Revert and redo
-- **[M]odify** — Make further adjustments
-
-### 3. Handle Response
-
-**IF Yes:**
-- Mark edit as complete
-- Proceed to step 5
-
-**IF No:**
-- Revert the change
-- Return to step 2 to gather new edit
-
-**IF Modify:**
-- Make additional adjustments
-- Show updated diff
-- Ask again
-
-### 4. Offer Validation
-
-"**Would you like to run validation after this edit?**"
-
-- Validation can check for any issues introduced
-
-### 5. Proceed to Confirm
-
-Load `{nextStepFile}` to confirm completion.
-
----
-
-## Success Metrics
-
-✅ Changes reviewed
-✅ User satisfaction confirmed
-✅ Validation offered

package/_bmad/bmb/workflows/module/steps-e/step-05-confirm.md

@@ -1,75 +0,0 @@
----
-name: 'step-05-confirm'
-description: 'Confirm completion and offer next steps'
-
-validationWorkflow: '../steps-v/step-01-load-target.md'
----
-
-# Step 5: Confirm Completion
-
-## STEP GOAL:
-
-Confirm edit completion and offer next steps including validation.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Module Editor** — completing the job
-- ✅ Guide next steps
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Summary of Changes
-
-"**✓ Edit complete!**"
-
-**File edited:** {file_path}
-**Edit type:** {edit_type}
-**Summary:** {summary_of_change}
-
-### 2. Offer Next Actions
-
-"**What would you like to do next?**"
-
-- **[V]alidate** — Run validation to check for issues
-- **[E]dit more** — Make additional changes
-- **[D]one** — Complete edit session
-
-### 3. Handle Response
-
-**IF Validate:**
-"**Loading validation workflow...**"
-Load `{validationWorkflow}`
-
-**IF Edit more:**
-"**Loading edit selection...**"
-Return to step 1
-
-**IF Done:**
-"**Edit session complete!**"
-Summary of what was accomplished.
-
-### 4. Complete Session
-
-If Done selected:
-
-"**Thanks for using the Module Edit workflow!**"
-
-"**Summary:**"
-- Files edited: {count}
-- Changes made: {summary}
-
----
-
-## Success Metrics
-
-✅ Edit confirmed complete
-✅ Next actions offered
-✅ Validation accessible
-✅ Session properly closed

package/_bmad/bmb/workflows/module/steps-v/step-01-load-target.md

@@ -1,96 +0,0 @@
----
-name: 'step-01-load-target'
-description: 'Load target for validation'
-
-nextStepFile: './step-02-file-structure.md'
-validationReportOutput: '{bmb_creations_output_folder}/modules/validation-report-{target_code}-{timestamp}.md'
----
-
-# Step 1: Load Target (Validate Mode)
-
-## STEP GOAL:
-
-Load the target (brief, module, agent specs, or workflow specs) for validation.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Quality Assurance** — thorough, systematic
-- ✅ Understand what we're validating
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Determine Validation Target
-
-"**What would you like to validate?**"
-
-Options:
-- **[B]rief** — Module brief from Brief mode
-- **[M]odule** — Built module structure
-- **[A]gents** — Agent specifications
-- **[W]orkflows** — Workflow specifications
-- **[F]ull** — Everything (brief + module + specs)
-
-### 2. Load Target
-
-Based on selection, load the target:
-
-**IF Brief:**
-- Path: `{bmb_creations_output_folder}/modules/module-brief-{code}.md`
-- Ask for module code if not specified
-
-**IF Module:**
-- Path: `src/modules/{code}/`
-- Ask for module code if not specified
-
-**IF Agents:**
-- Path: `src/modules/{code}/agents/`
-- Load all `.spec.md` or `.agent.yaml` files
-
-**IF Workflows:**
-- Path: `src/modules/{code}/workflows/`
-- Load all `.spec.md` files
-
-**IF Full:**
-- Load everything above for a module
-
-### 3. Confirm Target
-
-"**Validating:** {target_type} for {module_code}"
-"**Location:** {path}"
-
-"**Shall I proceed?**"
-
-### 4. Initialize Validation Report
-
-Create the validation report structure:
-
-```yaml
----
-validationDate: {timestamp}
-targetType: {target_type}
-moduleCode: {module_code}
-targetPath: {path}
-status: IN_PROGRESS
----
-```
-
-### 5. Proceed to Validation
-
-"**Starting validation checks...**"
-
-Load `{nextStepFile}` to begin file structure validation.
-
----
-
-## Success Metrics
-
-✅ Target loaded
-✅ Validation report initialized
-✅ User confirmed

package/_bmad/bmb/workflows/module/steps-v/step-02-file-structure.md

@@ -1,94 +0,0 @@
----
-name: 'step-02-file-structure'
-description: 'Validate file structure compliance'
-
-nextStepFile: './step-03-module-yaml.md'
-moduleStandardsFile: '../../data/module-standards.md'
-validationReportOutput: '{validation_report_output}'
----
-
-# Step 2: File Structure Validation
-
-## STEP GOAL:
-
-Validate file structure against module standards.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Quality Assurance** — checking structure
-- ✅ Reference standards, ensure compliance
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Load Standards
-
-Load `{moduleStandardsFile}` for reference.
-
-### 2. Perform Structure Checks
-
-Check based on target type:
-
-**For Modules:**
-- [ ] module.yaml exists
-- [ ] README.md exists
-- [ ] agents/ folder exists (if agents specified)
-- [ ] workflows/ folder exists (if workflows specified)
-- [ ] _module-installer/ folder (if installer specified)
-
-**For Briefs:**
-- [ ] Brief file exists
-- [ ] Required sections present
-
-**For Agent Specs:**
-- [ ] All expected spec files exist
-
-**For Workflow Specs:**
-- [ ] All expected spec files exist
-
-### 3. Check Module Type Compliance
-
-**IF Extension Module:**
-- [ ] Code matches base module
-- [ ] Folder name is unique (not conflicting)
-
-**IF Global Module:**
-- [ ] Global flag documented
-
-### 4. Record Results
-
-Append to `{validationReportOutput}`:
-
-```markdown
-## File Structure Validation
-
-**Status:** {PASS/FAIL/WARNINGS}
-
-**Checks:**
-{list each check with result}
-
-**Issues Found:**
-{any structural problems}
-```
-
-### 5. Auto-Proceed
-
-"**✓ File structure check complete.**"
-
-Proceeding to next validation...
-
-Load `{nextStepFile}`
-
----
-
-## Success Metrics
-
-✅ All structure checks performed
-✅ Results recorded
-✅ Auto-proceeds to next validation

package/_bmad/bmb/workflows/module/steps-v/step-03-module-yaml.md

@@ -1,99 +0,0 @@
----
-name: 'step-03-module-yaml'
-description: 'Validate module.yaml against conventions'
-
-nextStepFile: './step-04-agent-specs.md'
-moduleYamlConventionsFile: '../../data/module-yaml-conventions.md'
-validationReportOutput: '{validation_report_output}'
-targetPath: '{validation_target_path}'
----
-
-# Step 3: module.yaml Validation
-
-## STEP GOAL:
-
-Validate module.yaml formatting and conventions.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Quality Assurance** — checking configuration
-- ✅ Ensure proper YAML syntax
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Load module.yaml
-
-Read `{targetPath}/module.yaml`
-
-**IF not present:**
-- Record as FAIL (required file)
-- Skip to next validation
-
-### 2. Validate Required Fields
-
-Check for required frontmatter:
-- [ ] `code:` present and valid (kebab-case, 2-20 chars)
-- [ ] `name:` present
-- [ ] `header:` present
-- [ ] `subheader:` present
-- [ ] `default_selected:` present (boolean)
-
-### 3. Validate Custom Variables
-
-For each custom variable:
-- [ ] `prompt:` present
-- [ ] `default:` present (or explicitly omitted)
-- [ ] `result:` template valid
-- [ ] Variable naming correct (kebab-case)
-
-**For single-select:**
-- [ ] `single-select:` array present
-- [ ] All options have `value:` and `label:`
-
-**For multi-select:**
-- [ ] `multi-select:` array present
-- [ ] All options have `value:` and `label:`
-
-### 4. Validate Extension Module Code
-
-**IF Extension:**
-- [ ] `code:` matches base module code
-- [ ] This is intentional (not an error)
-
-### 5. Record Results
-
-Append to `{validationReportOutput}`:
-
-```markdown
-## module.yaml Validation
-
-**Status:** {PASS/FAIL/WARNINGS}
-
-**Required Fields:** {status}
-**Custom Variables:** {count} variables
-**Issues Found:**
-{list any issues}
-```
-
-### 6. Auto-Proceed
-
-"**✓ module.yaml check complete.**"
-
-Proceeding to next validation...
-
-Load `{nextStepFile}`
-
----
-
-## Success Metrics
-
-✅ All module.yaml checks performed
-✅ Results recorded
-✅ Auto-proceeds to next validation

package/_bmad/bmb/workflows/module/steps-v/step-04-agent-specs.md

@@ -1,152 +0,0 @@
----
-name: 'step-04-agent-specs'
-description: 'Validate agent specifications and built agents'
-
-nextStepFile: './step-05-workflow-specs.md'
-agentSpecTemplate: '../../templates/agent-spec-template.md'
-agentArchitectureFile: '../../data/agent-architecture.md'
-agentValidationWorkflow: '{project-root}/_bmad/bmb/workflows/agent/steps-v/step-01-validate.md'
-validationReportOutput: '{validation_report_output}'
-targetPath: '{validation_target_path}'
----
-
-# Step 4: Agent Specs Validation
-
-## STEP GOAL:
-
-Validate agent specifications and/or built agents, distinguishing between placeholder specs and fully implemented agents.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Quality Assurance** — dual-mode checking
-- ✅ Specs are expected, built agents are great
-- ✅ Track status of each agent
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Load Agent Files
-
-Find all agent files in `{targetPath}/agents/`:
-- `.spec.md` files (placeholder specs)
-- `.agent.yaml` files (built agents)
-
-### 2. Categorize Agents
-
-For each agent found, determine status:
-
-**Built Agents (.agent.yaml):**
-- Full implementation with complete persona, menu YAML
-- Can be validated in-depth via agent validation workflow
-
-**Spec Agents (.spec.md):**
-- High-level placeholder/blueprint
-- Awaiting creation via agent-builder workflow
-
-Track counts:
-- Total agents: {count}
-- Built agents: {count}
-- Spec agents: {count}
-
-### 3. Validate Spec Agents (.spec.md)
-
-For each spec agent, check:
-
-**Required Sections:**
-- [ ] Agent metadata (id, name, title, icon, module)
-- [ ] Role defined
-- [ ] Identity or communication style
-- [ ] Menu triggers documented
-- [ ] hasSidecar decision documented
-
-**Menu Triggers:**
-- [ ] At least one trigger per agent
-- [ ] Trigger → workflow mapping clear
-- [ ] No duplicate triggers (warn if found)
-
-**hasSidecar Documentation:**
-- [ ] Decision documented (true or false)
-- [ ] Rationale if true (why memory needed)
-
-**Placeholder Note:** These are specs awaiting agent-builder.
-
-### 4. Validate Built Agents (.agent.yaml)
-
-For each built agent, check:
-
-**Frontmatter Completeness:**
-- [ ] agent.metadata exists
-- [ ] agent.persona exists
-- [ ] agent.menu exists
-
-**YAML Structure:**
-- [ ] Valid YAML syntax
-- [ ] Required fields present
-
-**Status:** These are complete implementations and can be validated in detail via sub-process.
-
-### 5. Record Results
-
-Append to `{validationReportOutput}`:
-
-```markdown
-## Agent Specs Validation
-
-**Status:** {PASS/FAIL/WARNINGS}
-
-**Agent Summary:**
-- Total Agents: {count}
-- Built Agents: {count} {list}
-- Spec Agents: {count} {list}
-
-**Built Agents:**
-{for each built agent}
-- **{name}**: {status} - Ready for detailed validation via agent workflow
-
-**Spec Agents:**
-{for each spec agent}
-- **{name}**: {status} - Placeholder awaiting agent-builder
-
-**Issues Found:**
-{list any issues}
-
-**Recommendations:**
-{if specs exist}
-- Use `bmad:bmb:agents:agent-builder` to create {spec agent names}
-- After building agents, re-run validation to verify compliance
-{endif}
-```
-
-### 6. Note Sub-Process Opportunity
-
-**IF built agents exist:**
-
-"**The following built agents can be validated in detail:**"
-
-{list built agents}
-
-"**After this validation completes, I can spawn sub-processes to run the agent validation workflow on each built agent for deeper compliance checking.**"
-
-### 7. Auto-Proceed
-
-"**✓ Agent specs check complete.**"
-
-Proceeding to next validation...
-
-Load `{nextStepFile}`
-
----
-
-## Success Metrics
-
-✅ All agent files checked
-✅ Status tracked (spec vs built)
-✅ hasSidecar decisions validated
-✅ Recommendations for specs documented
-✅ Sub-process opportunity noted