npm - siesa-agents - Versions diffs - 2.1.78 → 2.1.80 - Mend

siesa-agents 2.1.78 → 2.1.80

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 (968) hide show

package/bmad/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md DELETED Viewed

@@ -1,302 +0,0 @@
----
-name: 'step-08-generate-report'
-description: 'Generate comprehensive compliance report with fix recommendations'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/workflow-compliance-check'
-# File References
-thisStepFile: '{workflow_path}/steps/step-08-generate-report.md'
-workflowFile: '{workflow_path}/workflow.md'
-complianceReportFile: '{output_folder}/workflow-compliance-report-{workflow_name}.md'
-targetWorkflowFile: '{target_workflow_path}'
-# Template References
-complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
-# Documentation References
-stepTemplate: '{project-root}/_bmad/bmb/docs/workflows/templates/step-template.md'
-workflowTemplate: '{project-root}/_bmad/bmb/docs/workflows/templates/workflow-template.md'
----
-# Step 8: Comprehensive Compliance Report Generation
-## STEP GOAL:
-Generate comprehensive compliance report compiling all validation findings, provide severity-ranked fix recommendations, and offer concrete next steps for achieving full compliance.
-## MANDATORY EXECUTION RULES (READ FIRST):
-### Universal Rules:
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-### Role Reinforcement:
-- ✅ You are a compliance validator and quality assurance specialist
-- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring report generation and strategic recommendation expertise
-- ✅ User brings their validated workflow and needs actionable improvement plan
-### Step-Specific Rules:
-- 🎯 Focus only on compiling comprehensive compliance report
-- 🚫 FORBIDDEN to generate report without including all findings from previous phases
-- 💬 Approach: Systematic compilation with clear, actionable recommendations
-- 📋 Ensure report is complete, accurate, and immediately useful
-## EXECUTION PROTOCOLS:
-- 🎯 Compile all findings from previous validation phases
-- 💾 Generate structured compliance report with clear sections
-- 📖 Provide severity-ranked recommendations with specific fixes
-- 🚫 FORBIDDEN to overlook any validation findings or recommendations
-## CONTEXT BOUNDARIES:
-- Available context: Complete validation findings from all previous phases
-- Focus: Comprehensive report generation and strategic recommendations
-- Limits: Report generation only, no additional validation
-- Dependencies: Successful completion of all previous validation phases
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-### 1. Initialize Report Generation
-"**Phase 5: Comprehensive Compliance Report Generation**
-Target: `{target_workflow_name}`
-Compiling all validation findings into structured compliance report with actionable recommendations..."
-### 2. Generate Compliance Report Structure
-Create comprehensive report at {complianceReportFile}:
-```markdown
-# Workflow Compliance Report
-**Workflow:** {target_workflow_name}
-**Date:** {current_date}
-**Standards:** BMAD workflow-template.md and step-template.md
----
-## Executive Summary
-**Overall Compliance Status:** [PASS/FAIL/PARTIAL]
-**Critical Issues:** [number] - Must be fixed immediately
-**Major Issues:** [number] - Significantly impacts quality/maintainability
-**Minor Issues:** [number] - Standards compliance improvements
-**Compliance Score:** [percentage]% based on template adherence
----
-## Phase 1: Workflow.md Validation Results
-### Critical Violations
-[Critical issues with template references and specific fixes]
-### Major Violations
-[Major issues with template references and specific fixes]
-### Minor Violations
-[Minor issues with template references and specific fixes]
----
-## Phase 2: Step-by-Step Validation Results
-### Summary by Step
-[Each step file with its violation summary]
-### Most Common Violations
-1. [Most frequent violation type with count]
-2. [Second most frequent with count]
-3. [Third most frequent with count]
-### Workflow Type Assessment
-**Workflow Type:** [editing/creation/validation/etc.]
-**Template Appropriateness:** [appropriate/needs improvement]
-**Recommendations:** [specific suggestions]
----
-## Phase 3: Holistic Analysis Results
-### Flow Validation
-[Flow analysis findings with specific issues]
-### Goal Alignment
-**Alignment Score:** [percentage]%
-**Stated vs. Actual:** [comparison with gaps]
-### Optimization Opportunities
-[Priority improvements with expected benefits]
----
-## Meta-Workflow Failure Analysis
-### Issues That Should Have Been Prevented
-**By create-workflow:**
-- [Specific issues that should have been caught during creation]
-- [Suggested improvements to create-workflow]
-**By edit-workflow (if applicable):**
-- [Specific issues introduced during editing]
-- [Suggested improvements to edit-workflow]
-### Recommended Meta-Workflow Improvements
-[Specific actionable improvements for meta-workflows]
----
-## Severity-Ranked Fix Recommendations
-### IMMEDIATE - Critical (Must Fix for Functionality)
-1. **[Issue Title]** - [File: filename.md]
-   - **Problem:** [Clear description]
-   - **Template Reference:** [Specific section]
-   - **Fix:** [Exact action needed]
-   - **Impact:** [Why this is critical]
-### HIGH PRIORITY - Major (Significantly Impacts Quality)
-1. **[Issue Title]** - [File: filename.md]
-   - **Problem:** [Clear description]
-   - **Template Reference:** [Specific section]
-   - **Fix:** [Exact action needed]
-   - **Impact:** [Quality/maintainability impact]
-### MEDIUM PRIORITY - Minor (Standards Compliance)
-1. **[Issue Title]** - [File: filename.md]
-   - **Problem:** [Clear description]
-   - **Template Reference:** [Specific section]
-   - **Fix:** [Exact action needed]
-   - **Impact:** [Standards compliance]
----
-## Automated Fix Options
-### Fixes That Can Be Applied Automatically
-[List of violations that can be automatically corrected]
-### Fixes Requiring Manual Review
-[List of violations requiring human judgment]
----
-## Next Steps Recommendation
-**Recommended Approach:**
-1. Fix all Critical issues immediately (workflow may not function)
-2. Address Major issues for reliability and maintainability
-3. Implement Minor issues for full standards compliance
-4. Update meta-workflows to prevent future violations
-**Estimated Effort:**
-- Critical fixes: [time estimate]
-- Major fixes: [time estimate]
-- Minor fixes: [time estimate]
-```
-### 3. Final Report Summary
-"**Compliance Report Generated:** `{complianceReportFile}`
-**Report Contents:**
-- ✅ Complete violation analysis from all validation phases
-- ✅ Severity-ranked recommendations with specific fixes
-- ✅ Meta-workflow failure analysis with improvement suggestions
-- ✅ Automated vs manual fix categorization
-- ✅ Strategic next steps and effort estimates
-**Key Findings:**
-- **Overall Compliance Score:** [percentage]%
-- **Critical Issues:** [number] requiring immediate attention
-- **Major Issues:** [number] impacting quality
-- **Minor Issues:** [number] for standards compliance
-**Meta-Workflow Improvements Identified:** [number] specific suggestions
-### 4. Offer Next Steps
-"**Phase 6 Complete:** Comprehensive compliance analysis finished
-All 8 validation phases completed with full report generation
-**Compliance Analysis Complete. What would you like to do next?**"
-**Available Options:**
-- **[A] Apply Automated Fixes** - I can automatically correct applicable violations
-- **[B] Launch edit-agent** - Edit the workflow with this compliance report as guidance
-- **[C] Manual Review** - Use the report for manual fixes at your pace
-- **[D] Update Meta-Workflows** - Strengthen create/edit workflows with identified improvements
-**Recommendation:** Start with Critical issues, then proceed through High and Medium priority items systematically."
-### 5. Report Completion Options
-Display: "**Select an Option:** [A] Apply Automated Fixes [B] Launch Edit-Agent [C] Manual Review [D] Update Meta-Workflows [X] Exit"
-## Menu Handling Logic:
-- IF A: Begin applying automated fixes from the report
-- IF B: Launch edit-agent workflow with this compliance report as context
-- IF C: End workflow with guidance for manual review using the report
-- IF D: Provide specific recommendations for meta-workflow improvements
-- IF X: Save report and end workflow gracefully
-## CRITICAL STEP COMPLETION NOTE
-The workflow is complete when the comprehensive compliance report has been generated and the user has selected their preferred next step. The report contains all findings, recommendations, and strategic guidance needed to achieve full BMAD compliance.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- Comprehensive compliance report generated with all validation findings
-- Severity-ranked fix recommendations provided with specific actions
-- Meta-workflow failure analysis completed with improvement suggestions
-- Clear next steps offered based on user preferences
-- Report saved and accessible for future reference
-- User has actionable plan for achieving full compliance
-### ❌ SYSTEM FAILURE:
-- Generating incomplete report without all validation findings
-- Missing severity rankings or specific fix recommendations
-- Not providing clear next steps or options
-- Failing to include meta-workflow improvement suggestions
-- Creating report that is not immediately actionable
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/bmad/bmb/workflows/workflow-compliance-check/templates/compliance-report.md DELETED Viewed

@@ -1,140 +0,0 @@
-# Workflow Compliance Report Template
-**Workflow:** {workflow_name}
-**Date:** {validation_date}
-**Standards:** BMAD workflow-template.md and step-template.md
-**Report Type:** Comprehensive Compliance Validation
----
-## Executive Summary
-**Overall Compliance Status:** {compliance_status}
-**Critical Issues:** {critical_count} - Must be fixed immediately
-**Major Issues:** {major_count} - Significantly impacts quality/maintainability
-**Minor Issues:** {minor_count} - Standards compliance improvements
-**Compliance Score:** {compliance_score}% based on template adherence
-**Workflow Type Assessment:** {workflow_type} - {type_appropriateness}
----
-## Phase 1: Workflow.md Validation Results
-### Template Adherence Analysis
-**Reference Standard:** {workflow_template_path}
-### Critical Violations
-{critical_violations}
-### Major Violations
-{major_violations}
-### Minor Violations
-{minor_violations}
----
-## Phase 2: Step-by-Step Validation Results
-### Summary by Step
-{step_validation_summary}
-### Most Common Violations
-1. {most_common_violation_1}
-2. {most_common_violation_2}
-3. {most_common_violation_3}
-### Workflow Type Appropriateness
-**Analysis:** {workflow_type_analysis}
-**Recommendations:** {type_recommendations}
----
-## Phase 3: Holistic Analysis Results
-### Flow Validation
-{flow_validation_results}
-### Goal Alignment
-**Stated Goal:** {stated_goal}
-**Actual Implementation:** {actual_implementation}
-**Alignment Score:** {alignment_score}%
-**Gap Analysis:** {gap_analysis}
-### Optimization Opportunities
-{optimization_opportunities}
----
-## Meta-Workflow Failure Analysis
-### Issues That Should Have Been Prevented
-**By create-workflow:**
-{create_workflow_failures}
-**By edit-workflow:**
-{edit_workflow_failures}
-### Recommended Meta-Workflow Improvements
-{meta_workflow_improvements}
----
-## Severity-Ranked Fix Recommendations
-### IMMEDIATE - Critical (Must Fix for Functionality)
-{critical_recommendations}
-### HIGH PRIORITY - Major (Significantly Impacts Quality)
-{major_recommendations}
-### MEDIUM PRIORITY - Minor (Standards Compliance)
-{minor_recommendations}
----
-## Automated Fix Options
-### Fixes That Can Be Applied Automatically
-{automated_fixes}
-### Fixes Requiring Manual Review
-{manual_fixes}
----
-## Next Steps Recommendation
-**Recommended Approach:**
-{recommended_approach}
-**Estimated Effort:**
-- Critical fixes: {critical_effort}
-- Major fixes: {major_effort}
-- Minor fixes: {minor_effort}
----
-**Report Generated:** {timestamp}
-**Validation Engine:** BMAD Workflow Compliance Checker
-**Next Review Date:** {next_review_date}

package/bmad/bmb/workflows/workflow-compliance-check/workflow.md DELETED Viewed

@@ -1,59 +0,0 @@
----
-name: workflow-compliance-check
-description: Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting
-web_bundle: false
----
-# Workflow Compliance Check
-**Goal:** Systematically validate workflows against BMAD standards through adversarial analysis, generating detailed compliance reports with severity-ranked violations and improvement recommendations.
-**Your Role:** In addition to your name, communication_style, and persona, you are also a compliance validator and quality assurance specialist collaborating with a workflow owner. This is a partnership, not a client-vendor relationship. You bring expertise in BMAD standards, workflow architecture, and systematic validation, while the user brings their workflow and specific compliance concerns. Work together as equals.
----
-## WORKFLOW ARCHITECTURE
-This uses **step-file architecture** for disciplined execution:
-### Core Principles
-- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
-- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in context for compliance checking (no output file frontmatter needed)
-- **Append-Only Building**: Build compliance reports by appending content as directed to the output file
-### Step Processing Rules
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-### Critical Rules (NO EXCEPTIONS)
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
----
-## INITIALIZATION SEQUENCE
-### 1. Configuration Loading
-Load and read full config from {project-root}/_bmad/bmb/config.yaml and resolve:
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-### 2. First Step EXECUTION
-Load, read the full file and then execute `{workflow_path}/steps/step-01-validate-goal.md` to begin the workflow. If the path to a workflow was provided, set `user_provided_path` to that path.

package/bmad/bmb/workflows-legacy/edit-module/README.md DELETED Viewed

@@ -1,171 +0,0 @@
-# Edit Module Workflow
-Interactive workflow for editing existing BMAD modules, including structure, agents, workflows, configuration, and documentation.
-## Purpose
-This workflow helps you improve and maintain BMAD modules by:
-- Analyzing module structure against best practices
-- Managing agents and workflows within the module
-- Updating configuration and documentation
-- Ensuring cross-module integration works correctly
-- Maintaining installer configuration (for source modules)
-## When to Use
-Use this workflow when you need to:
-- Add new agents or workflows to a module
-- Update module configuration
-- Improve module documentation
-- Reorganize module structure
-- Set up cross-module workflow sharing
-- Fix issues in module organization
-- Update installer configuration
-## What You'll Need
-- Path to the module directory you want to edit
-- Understanding of what changes you want to make
-- Access to module documentation (loaded automatically)
-## Workflow Steps
-1. **Load and analyze target module** - Provide path to module directory
-2. **Analyze against best practices** - Automatic audit of module structure
-3. **Select editing focus** - Choose what aspect to edit
-4. **Load relevant documentation and tools** - Auto-loads guides and workflows
-5. **Perform edits** - Review and approve changes iteratively
-6. **Validate all changes** - Comprehensive validation checklist
-7. **Generate change summary** - Summary of improvements made
-## Editing Options
-The workflow provides 12 focused editing options:
-1. **Fix critical issues** - Address missing files, broken references
-2. **Update module config** - Edit config.yaml fields
-3. **Manage agents** - Add, edit, or remove agents
-4. **Manage workflows** - Add, edit, or remove workflows
-5. **Update documentation** - Improve README files and guides
-6. **Reorganize structure** - Fix directory organization
-7. **Add new agent** - Create and integrate new agent
-8. **Add new workflow** - Create and integrate new workflow
-9. **Update installer** - Modify installer configuration (source only)
-10. **Cross-module integration** - Set up workflow sharing with other modules
-11. **Remove deprecated items** - Delete unused agents, workflows, or files
-12. **Full module review** - Comprehensive analysis and improvements
-## Integration with Other Workflows
-This workflow integrates with:
-- **edit-agent** - For editing individual agents
-- **edit-workflow** - For editing individual workflows
-- **create-agent** - For adding new agents
-- **create-workflow** - For adding new workflows
-When you select options to manage agents or workflows, the appropriate specialized workflow is invoked automatically.
-## Module Structure
-A proper BMAD module has:
-```
-module-code/
-├── agents/              # Agent definitions
-│   └── *.agent.yaml
-├── workflows/           # Workflow definitions
-│   └── workflow-name/
-│       ├── workflow.yaml
-│       ├── instructions.md
-│       ├── checklist.md
-│       └── README.md
-├── config.yaml          # Module configuration
-└── README.md           # Module documentation
-```
-## Standard Module Config
-Every module config.yaml should have:
-```yaml
-module_name: 'Full Module Name'
-module_code: 'xyz'
-user_name: 'User Name'
-communication_language: 'english'
-output_folder: 'path/to/output'
-```
-Optional fields may be added for module-specific needs.
-## Cross-Module Integration
-Modules can share workflows:
-```yaml
-# In agent menu item:
-workflow: '{project-root}/_bmad/other-module/workflows/shared-workflow/workflow.yaml'
-```
-Common patterns:
-- BMM uses CIS brainstorming workflows
-- All modules can use core workflows
-- Modules can invoke each other's workflows
-## Output
-The workflow modifies module files in place, including:
-- config.yaml
-- Agent files
-- Workflow files
-- README and documentation files
-- Directory structure (if reorganizing)
-Changes are reviewed and approved by you before being applied.
-## Best Practices
-- **Start with analysis** - Let the workflow audit your module first
-- **Use specialized workflows** - Let edit-agent and edit-workflow handle detailed edits
-- **Update documentation** - Keep README files current with changes
-- **Validate thoroughly** - Use the validation step to catch structural issues
-- **Test after editing** - Invoke agents and workflows to verify they work
-## Tips
-- For adding agents/workflows, use options 7-8 to create and integrate in one step
-- For quick config changes, use option 2 (update module config)
-- Cross-module integration (option 10) helps set up workflow sharing
-- Full module review (option 12) is great for inherited or legacy modules
-- The workflow handles path updates when you reorganize structure
-## Example Usage
-```
-User: I want to add a new workflow to BMM for API design
-Workflow: Analyzes BMM → You choose option 8 (add new workflow)
-          → Invokes create-workflow → Creates workflow
-          → Integrates it into module → Updates README → Done
-```
-## Activation
-Invoke via BMad Builder agent:
-```
-/bmad:bmb:agents:bmad-builder
-Then select: *edit-module
-```
-Or directly via workflow.xml with this workflow config.
-## Related Resources
-- **Module Structure Guide** - Comprehensive module architecture documentation
-- **BMM Module** - Example of full-featured module
-- **BMB Module** - Example of builder/tooling module
-- **CIS Module** - Example of workflow library module