siesa-agents 2.1.78 → 2.1.80

package/bmad/bmb/workflows-legacy/edit-module/checklist.md

@@ -1,163 +0,0 @@
-# Edit Module - Validation Checklist
-
-Use this checklist to validate module edits meet BMAD Core standards.
-
-## Module Structure Validation
-
-- [ ] Module has clear abbreviation code (bmm, bmb, cis, etc.)
-- [ ] agents/ directory exists
-- [ ] workflows/ directory exists
-- [ ] config.yaml exists in module root
-- [ ] README.md exists in module root
-- [ ] Directory structure follows BMAD conventions
-
-## Configuration Validation
-
-### Required Fields
-
-- [ ] module_name is descriptive and clear
-- [ ] module_code is 3-letter code matching directory name
-- [ ] user_name field present
-- [ ] communication_language field present
-- [ ] output_folder field present
-
-### Optional Fields (if used)
-
-- [ ] bmb_creations_output_folder documented
-- [ ] Module-specific fields documented in README
-
-### File Quality
-
-- [ ] config.yaml is valid YAML syntax
-- [ ] No duplicate keys
-- [ ] Values are appropriate types (strings, paths, etc.)
-- [ ] Comments explain non-obvious fields
-
-## Agent Validation
-
-### Agent Files
-
-- [ ] All agents in agents/ directory
-- [ ] Agent files follow naming: {agent-name}.agent.yaml or .md
-- [ ] Agent filenames use kebab-case
-- [ ] No orphaned or temporary agent files
-
-### Agent Content
-
-- [ ] Each agent has clear role and purpose
-- [ ] Agents reference workflows correctly
-- [ ] Agent workflow paths are valid
-- [ ] Agents load module config correctly (if needed)
-- [ ] Agent menu items reference existing workflows
-
-### Agent Integration
-
-- [ ] All agents listed in module README
-- [ ] Agent relationships documented (if applicable)
-- [ ] Cross-agent workflows properly linked
-
-## Workflow Validation
-
-### Workflow Structure
-
-- [ ] All workflows in workflows/ directory
-- [ ] Each workflow directory has workflow.yaml
-- [ ] Each workflow directory has instructions.md
-- [ ] Workflow directories use kebab-case naming
-- [ ] No orphaned or incomplete workflow directories
-
-### Workflow Content
-
-- [ ] workflow.yaml is valid YAML
-- [ ] workflow.yaml has name field
-- [ ] workflow.yaml has description field
-- [ ] workflow.yaml has author field
-- [ ] instructions.md has proper <workflow> structure
-- [ ] Workflow steps are numbered and logical
-
-### Workflow Integration
-
-- [ ] All workflows listed in module README
-- [ ] Workflow paths in agents are correct
-- [ ] Cross-module workflow references are valid
-- [ ] Sub-workflow references exist
-
-## Documentation Validation
-
-### Module README
-
-- [ ] Module README describes purpose clearly
-- [ ] README lists all agents with descriptions
-- [ ] README lists all workflows with descriptions
-- [ ] README includes installation instructions (if applicable)
-- [ ] README explains module's role in BMAD ecosystem
-
-### Workflow READMEs
-
-- [ ] Each workflow has its own README.md
-- [ ] Workflow READMEs explain purpose
-- [ ] Workflow READMEs list inputs/outputs
-- [ ] Workflow READMEs include usage examples
-
-### Other Documentation
-
-- [ ] Usage guides present (if needed)
-- [ ] Architecture docs present (if complex module)
-- [ ] Examples provided (if applicable)
-
-## Cross-References Validation
-
-- [ ] Agent workflow references point to existing workflows
-- [ ] Workflow sub-workflow references are valid
-- [ ] Cross-module references use correct paths
-- [ ] Config file paths use {project-root} correctly
-- [ ] No hardcoded absolute paths
-
-## Installer Validation (Source Modules Only)
-
-- [ ] Installer script exists in tools/cli/installers/
-- [ ] Installer script name: install-{module-code}.js
-- [ ] Module metadata in installer is correct
-- [ ] Web bundle configuration valid (if applicable)
-- [ ] Installation paths are correct
-- [ ] Dependencies documented in installer
-
-## Web Bundle Validation (If Applicable)
-
-- [ ] Web bundles configured in workflow.yaml files
-- [ ] All referenced files included in web_bundle_files
-- [ ] Paths are _bmad/-relative (not project-root)
-- [ ] No config_source references in web bundles
-- [ ] Invoked workflows included in dependencies
-
-## Quality Checks
-
-- [ ] No placeholder text remains ({MODULE_NAME}, {CODE}, etc.)
-- [ ] No broken file references
-- [ ] No duplicate content across files
-- [ ] Consistent naming conventions throughout
-- [ ] Module purpose is clear from README alone
-
-## Integration Checks
-
-- [ ] Module doesn't conflict with other modules
-- [ ] Shared resources properly documented
-- [ ] Dependencies on other modules explicit
-- [ ] Module can be installed independently (if designed that way)
-
-## User Experience
-
-- [ ] Module purpose is immediately clear
-- [ ] Agents have intuitive names
-- [ ] Workflows have descriptive names
-- [ ] Menu items are logically organized
-- [ ] Error messages are helpful
-- [ ] Success messages confirm actions
-
-## Final Checks
-
-- [ ] All files have been saved
-- [ ] File permissions are correct
-- [ ] Git status shows expected changes
-- [ ] Module is ready for testing
-- [ ] Documentation accurately reflects changes

package/bmad/bmb/workflows-legacy/edit-module/instructions.md

@@ -1,340 +0,0 @@
-# Edit Module - Module Editor Instructions
-
-<critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/_bmad/bmb/workflows/edit-module/workflow.yaml</critical>
-<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
-<critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
-<critical>Communicate all responses in {communication_language}</critical>
-
-<workflow>
-
-<step n="1" goal="Load and deeply understand the target module">
-<ask>What is the path to the module source you want to edit?</ask>
-
-<action>Load the module directory structure completely:
-
-- Scan all directories and files
-- Load config.yaml
-- Load README.md
-- List all agents in agents/ directory
-- List all workflows in workflows/ directory
-- Identify any custom structure or patterns
-  </action>
-
-<action>Load ALL module documentation to inform understanding:
-
-- Module structure guide: {module_structure_guide}
-- Study reference modules: BMM, BMB, CIS
-- Understand BMAD module patterns and conventions
-  </action>
-
-<action>Analyze the module deeply:
-
-- Identify module purpose and role in BMAD ecosystem
-- Understand agent organization and relationships
-- Map workflow organization and dependencies
-- Evaluate config structure and completeness
-- Check documentation quality and currency
-- Assess installer configuration (if source module)
-- Identify cross-module integrations
-- Evaluate against best practices from loaded guides
-  </action>
-
-<action>Reflect understanding back to {user_name}:
-
-Present a warm, conversational summary adapted to the module's complexity:
-
-- What this module provides (its purpose and value in BMAD)
-- How it's organized (agents, workflows, structure)
-- What you notice (strengths, potential improvements, issues)
-- How it fits in the larger BMAD ecosystem
-- Your initial assessment based on best practices
-
-Be conversational and insightful. Help {user_name} see their module through your eyes.
-</action>
-
-<ask>Does this match your understanding of what this module should provide?</ask>
-<template-output>module_understanding</template-output>
-</step>
-
-<step n="2" goal="Discover improvement goals collaboratively">
-<critical>Understand WHAT the user wants to improve and WHY before diving into edits</critical>
-
-<action>Engage in collaborative discovery:
-
-Ask open-ended questions to understand their goals:
-
-- What prompted you to want to edit this module?
-- What feedback have you gotten from users of this module?
-- Are there specific agents or workflows that need attention?
-- Is the module fulfilling its intended purpose?
-- Are there new capabilities you want to add?
-- How well does it integrate with other modules?
-- Is the documentation helping users understand and use the module?
-
-Listen for clues about:
-
-- Structural issues (poor organization, hard to navigate)
-- Agent/workflow issues (outdated, broken, missing functionality)
-- Configuration issues (missing fields, incorrect setup)
-- Documentation issues (outdated, incomplete, unclear)
-- Integration issues (doesn't work well with other modules)
-- Installer issues (installation problems, missing files)
-- User experience issues (confusing, hard to use)
-  </action>
-
-<action>Based on their responses and your analysis from step 1, identify improvement opportunities:
-
-Organize by priority and user goals:
-
-- CRITICAL issues blocking module functionality
-- IMPORTANT improvements enhancing user experience
-- NICE-TO-HAVE enhancements for polish
-
-Present these conversationally, explaining WHY each matters and HOW it would help.
-</action>
-
-<action>Collaborate on priorities:
-
-Don't just list options - discuss them:
-
-- "I noticed {{issue}} - this could make it hard for users to {{problem}}. Want to address this?"
-- "The module could be more {{improvement}} which would help when {{use_case}}. Worth exploring?"
-- "Based on what you said about {{user_goal}}, we might want to {{suggestion}}. Thoughts?"
-
-Let the conversation flow naturally. Build a shared vision of what "better" looks like.
-</action>
-
-<template-output>improvement_goals</template-output>
-</step>
-
-<step n="3" goal="Facilitate improvements collaboratively" repeat="until-user-satisfied">
-<critical>Work iteratively - improve, review, refine. Never dump all changes at once.</critical>
-<critical>For agent and workflow edits, invoke specialized workflows rather than doing inline</critical>
-
-<action>For each improvement area, facilitate collaboratively:
-
-1. **Explain the current state and why it matters**
-   - Show relevant sections of the module
-   - Explain how it works now and implications
-   - Connect to user's goals from step 2
-
-2. **Propose improvements with rationale**
-   - Suggest specific changes that align with best practices
-   - Explain WHY each change helps
-   - Provide examples from reference modules: {bmm_module_dir}, {bmb_module_dir}, {cis_module_dir}
-   - Reference agents from: {existing_agents_dir}
-   - Reference workflows from: {existing_workflows_dir}
-   - Reference the structure guide's patterns naturally
-
-3. **Collaborate on the approach**
-   - Ask if the proposed change addresses their need
-   - Invite modifications or alternative approaches
-   - Explain tradeoffs when relevant
-   - Adapt based on their feedback
-
-4. **Apply changes appropriately**
-   - For agent edits: Invoke edit-agent workflow
-   - For workflow edits: Invoke edit-workflow workflow
-   - For module-level changes: Make directly and iteratively
-   - Show updates and confirm satisfaction
-     </action>
-
-<action>Common improvement patterns to facilitate:
-
-**If improving module organization:**
-
-- Discuss how the current structure serves (or doesn't serve) users
-- Propose reorganization that aligns with mental models
-- Consider feature-based vs type-based organization
-- Plan the reorganization steps
-- Update all references after moving files
-
-**If updating module configuration:**
-
-- Review current config.yaml fields
-- Check for missing standard fields (user_name, communication_language, output_folder)
-- Add module-specific fields as needed
-- Remove unused or outdated fields
-- Ensure config is properly documented
-
-**If managing agents:**
-
-- Ask which agent needs attention and why
-- For editing existing agent: <invoke-workflow path="{agent_editor}">
-- For adding new agent: Guide creation and integration
-- For removing agent: Confirm, remove, update references
-- Ensure all agent references in workflows remain valid
-
-**If managing workflows:**
-
-- Ask which workflow needs attention and why
-- For editing existing workflow: <invoke-workflow path="{workflow_editor}">
-- For adding new workflow: Guide creation and integration
-- For removing workflow: Confirm, remove, update agent references
-- Ensure all workflow files are properly organized
-
-**If improving documentation:**
-
-- Review current README and identify gaps
-- Discuss what users need to know
-- Update module overview and purpose
-- List agents and workflows with clear descriptions
-- Add usage examples if helpful
-- Ensure installation/setup instructions are clear
-
-**If setting up cross-module integration:**
-
-- Identify which workflows from other modules are needed
-- Show how to reference workflows properly: {project-root}/_bmad/{{module}}/workflows/{{workflow}}/workflow.yaml
-- Document the integration in README
-- Ensure dependencies are clear
-- Consider adding example usage
-
-**If updating installer (source modules only):**
-
-- Review installer script for correctness
-- Check web bundle configurations
-- Verify all files are included
-- Test installation paths
-- Update module metadata
-  </action>
-
-<action>When invoking specialized workflows:
-
-Explain why you're handing off:
-
-- "This agent needs detailed attention. Let me invoke the edit-agent workflow to give it proper focus."
-- "The workflow editor can handle this more thoroughly. I'll pass control there."
-
-After the specialized workflow completes, return and continue:
-
-- "Great! That agent/workflow is updated. Want to work on anything else in the module?"
-  </action>
-
-<action>Throughout improvements, educate when helpful:
-
-Share insights from the guides naturally:
-
-- "The module structure guide recommends {{pattern}} for this scenario"
-- "Looking at how BMM organized this, we could use {{approach}}"
-- "The BMAD convention is to {{pattern}} which helps with {{benefit}}"
-
-Connect improvements to broader BMAD principles without being preachy.
-</action>
-
-<ask>After each significant change:
-
-- "Does this organization feel more intuitive?"
-- "Want to refine this further, or move to the next improvement?"
-- "How does this change affect users of the module?"
-  </ask>
-
-<template-output>improvement_implementation</template-output>
-</step>
-
-<step n="4" goal="Validate improvements holistically">
-<action>Run comprehensive validation conversationally:
-
-Don't just check boxes - explain what you're validating and why it matters:
-
-- "Let me verify the module structure is solid..."
-- "Checking that all agent workflow references are valid..."
-- "Making sure config.yaml has all necessary fields..."
-- "Validating documentation is complete and accurate..."
-- "Ensuring cross-module references work correctly..."
-  </action>
-
-<action>Load validation checklist: {installed_path}/checklist.md</action>
-<action>Check all items from checklist systematically</action>
-
-<check if="validation_issues_found">
-  <action>Present issues conversationally:
-
-Explain what's wrong and implications:
-
-- "I found {{issue}} which could cause {{problem}} for users"
-- "The {{component}} needs {{fix}} because {{reason}}"
-
-Propose fixes immediately:
-
-- "I can fix this by {{solution}}. Should I?"
-- "We have a couple options here: {{option1}} or {{option2}}. Thoughts?"
-  </action>
-
-<action>Fix approved issues and re-validate</action>
-</check>
-
-<check if="validation_passes">
-  <action>Confirm success warmly:
-
-"Excellent! Everything validates cleanly:
-
-- Module structure is well-organized
-- All agent and workflow references are valid
-- Configuration is complete
-- Documentation is thorough and current
-- Cross-module integrations work properly
-- Installer is correct (if applicable)
-
-Your module is in great shape."
-</action>
-</check>
-
-<template-output>validation_results</template-output>
-</step>
-
-<step n="5" goal="Review improvements and guide next steps">
-<action>Create a conversational summary of what improved:
-
-Tell the story of the transformation:
-
-- "We started with {{initial_state}}"
-- "You wanted to {{user_goals}}"
-- "We made these key improvements: {{changes_list}}"
-- "Now your module {{improved_capabilities}}"
-
-Highlight the impact:
-
-- "This means users will experience {{benefit}}"
-- "The module is now more {{quality}}"
-- "It follows best practices for {{patterns}}"
-  </action>
-
-<action>Guide next steps based on changes made:
-
-If structure changed significantly:
-
-- "Since we reorganized the structure, you should update any external references to this module"
-
-If agents or workflows were updated:
-
-- "The updated agents/workflows should be tested with real user interactions"
-
-If cross-module integration was added:
-
-- "Test the integration with {{other_module}} to ensure it works smoothly"
-
-If installer was updated:
-
-- "Test the installation process to verify all files are included correctly"
-
-If this is part of larger BMAD work:
-
-- "Consider if patterns from this module could benefit other modules"
-
-Be a helpful guide to what comes next, not just a task completer.
-</action>
-
-<ask>Would you like to:
-
-- Test the edited module by invoking one of its agents
-- Edit a specific agent or workflow in more detail
-- Make additional refinements to the module
-- Work on a different module
-  </ask>
-
-<template-output>completion_summary</template-output>
-</step>
-
-</workflow>

package/bmad/bmb/workflows-legacy/edit-module/workflow.yaml

@@ -1,33 +0,0 @@
-# Edit Module - Module Editor Configuration
-name: "edit-module"
-description: "Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices"
-author: "BMad"
-
-# Critical variables load from config_source
-config_source: "{project-root}/_bmad/bmb/config.yaml"
-communication_language: "{config_source}:communication_language"
-user_name: "{config_source}:user_name"
-
-# Required Data Files - Critical for understanding module conventions
-module_structure_guide: "{project-root}/_bmad/bmb/workflows/create-module/module-structure.md"
-
-# Related workflow editors
-agent_editor: "{project-root}/_bmad/bmb/workflows/edit-agent/workflow.yaml"
-workflow_editor: "{project-root}/_bmad/bmb/workflows/edit-workflow/workflow.yaml"
-
-# Reference examples - for learning patterns
-bmm_module_dir: "{project-root}/_bmad/bmm/"
-bmb_module_dir: "{project-root}/_bmad/bmb/"
-cis_module_dir: "{project-root}/_bmad/cis/"
-existing_agents_dir: "{project-root}/_bmad/*/agents/"
-existing_workflows_dir: "{project-root}/_bmad/*/workflows/"
-
-# Module path and component files
-installed_path: "{project-root}/_bmad/bmb/workflows/edit-module"
-template: false # This is an action workflow - no template needed
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-standalone: true
-
-# Web bundle configuration