siesa-agents 2.1.40 → 2.1.41

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

@@ -1,140 +1,140 @@
-# 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}
+# 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

@@ -1,59 +1,59 @@
----
-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.
+---
+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.