siesa-agents 2.1.39 → 2.1.41

package/bmad/bmb/workflows/edit-workflow/steps/step-05-compliance-check.md

@@ -0,0 +1,246 @@
+---
+name: 'step-05-compliance-check'
+description: 'Run comprehensive compliance validation on the edited workflow'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/workflows/edit-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-05-compliance-check.md'
+workflowFile: '{workflow_path}/workflow.md'
+editedWorkflowPath: '{target_workflow_path}'
+complianceCheckWorkflow: '{project-root}/_bmad/bmb/workflows/workflow-compliance-check/workflow.md'
+outputFile: '{output_folder}/workflow-edit-{target_workflow_name}.md'
+
+# Task References
+complianceCheckTask: '{project-root}/_bmad/bmb/workflows/workflow-compliance-check/workflow.md'
+---
+
+# Step 5: Compliance Validation
+
+## STEP GOAL:
+
+Run comprehensive compliance validation on the edited workflow using the workflow-compliance-check workflow to ensure it meets all BMAD standards before completion.
+
+## 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 workflow editor 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 expertise in BMAD standards and workflow validation
+- ✅ User brings their edited workflow and needs quality assurance
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on running compliance validation on the edited workflow
+- 🚫 FORBIDDEN to skip compliance validation or declare workflow complete without it
+- 💬 Approach: Quality-focused, thorough, and collaborative
+- 📋 Ensure user understands compliance results and next steps
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Launch workflow-compliance-check on the edited workflow
+- 💾 Review compliance report and present findings to user
+- 📖 Explain any issues found and provide fix recommendations
+- 🚫 FORBIDDEN to proceed without compliance validation completion
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Edited workflow files from previous improve step
+- Focus: Compliance validation using workflow-compliance-check workflow
+- Limits: Validation and reporting only, no further workflow modifications
+- Dependencies: Successful workflow improvements in previous step
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Initialize Compliance Validation
+
+"**Final Quality Check: Workflow Compliance Validation**
+
+Your workflow has been edited! Now let's run a comprehensive compliance check to ensure it meets all BMAD standards and follows best practices.
+
+This validation will check:
+
+- Template compliance (workflow-template.md and step-template.md)
+- File size optimization and markdown formatting
+- CSV data file standards (if applicable)
+- Intent vs Prescriptive spectrum alignment
+- Web search and subprocess optimization
+- Overall workflow flow and goal alignment"
+
+### 2. Launch Compliance Check Workflow
+
+**A. Execute Compliance Validation:**
+
+"Running comprehensive compliance validation on your edited workflow...
+Target: `{editedWorkflowPath}`
+
+**Executing:** {complianceCheckTask}
+**Validation Scope:** Full 8-phase compliance analysis
+**Expected Duration:** Thorough validation may take several minutes"
+
+**B. Monitor Validation Progress:**
+
+Provide updates as the validation progresses:
+
+- "✅ Workflow.md validation in progress..."
+- "✅ Step-by-step compliance checking..."
+- "✅ File size and formatting analysis..."
+- "✅ Intent spectrum assessment..."
+- "✅ Web search optimization analysis..."
+- "✅ Generating comprehensive compliance report..."
+
+### 3. Compliance Report Analysis
+
+**A. Review Validation Results:**
+
+"**Compliance Validation Complete!**
+
+**Overall Assessment:** [PASS/PARTIAL/FAIL - based on compliance report]
+
+- **Critical Issues:** [number found]
+- **Major Issues:** [number found]
+- **Minor Issues:** [number found]
+- **Compliance Score:** [percentage]%"
+
+**B. Present Key Findings:**
+
+"**Key Compliance Results:**
+
+- **Template Adherence:** [summary of template compliance]
+- **File Optimization:** [file size and formatting issues]
+- **Intent Spectrum:** [spectrum positioning validation]
+- **Performance Optimization:** [web search and subprocess findings]
+- **Overall Flow:** [workflow structure and completion validation]"
+
+### 4. Issue Resolution Options
+
+**A. Review Compliance Issues:**
+
+If issues are found:
+"**Issues Requiring Attention:**
+
+**Critical Issues (Must Fix):**
+[List any critical violations that prevent workflow functionality]
+
+**Major Issues (Should Fix):**
+[List major issues that impact quality or maintainability]
+
+**Minor Issues (Nice to Fix):**
+[List minor standards compliance issues]"
+
+**B. Resolution Options:**
+
+"**Resolution Options:**
+
+1. **Automatic Fixes** - I can apply automated fixes where possible
+2. **Manual Guidance** - I'll guide you through manual fixes step by step
+3. **Return to Edit** - Go back to step 3 for additional improvements
+4. **Accept as Is** - Proceed with current state (if no critical issues)
+5. **Detailed Review** - Review full compliance report in detail"
+
+### 5. Final Validation Confirmation
+
+**A. User Choice Handling:**
+
+Based on user selection:
+
+- **If Automatic Fixes**: Apply fixes and re-run validation
+- **If Manual Guidance**: Provide step-by-step fix instructions
+- **If Return to Edit**: Load step-03-discover.md with compliance report context
+- **If Accept as Is**: Confirm understanding of any remaining issues
+- **If Detailed Review**: Present full compliance report
+
+**B. Final Status Confirmation:**
+
+"**Workflow Compliance Status:** [FINAL/PROVISIONAL]
+
+**Completion Criteria:**
+
+- ✅ All critical issues resolved
+- ✅ Major issues addressed or accepted
+- ✅ Compliance documentation complete
+- ✅ User understands any remaining minor issues
+
+**Your edited workflow is ready!**"
+
+### 6. Completion Documentation
+
+**A. Update Compliance Status:**
+
+Document final compliance status in {outputFile}:
+
+- **Validation Date:** [current date]
+- **Compliance Score:** [final percentage]
+- **Issues Resolved:** [summary of fixes applied]
+- **Remaining Issues:** [any accepted minor issues]
+
+**B. Final User Guidance:**
+
+"**Next Steps for Your Edited Workflow:**
+
+1. **Test the workflow** with real users to validate functionality
+2. **Monitor performance** and consider optimization opportunities
+3. **Gather feedback** for potential future improvements
+4. **Consider compliance check** periodically for maintenance
+
+**Support Resources:**
+
+- Use workflow-compliance-check for future validations
+- Refer to BMAD documentation for best practices
+- Use edit-workflow again for future modifications"
+
+### 7. Final Menu Options
+
+"**Workflow Edit and Compliance Complete!**
+
+**Select an Option:**
+
+- [C] Complete - Finish workflow editing with compliance validation
+- [R] Review Compliance - View detailed compliance report
+- [M] More Modifications - Return to editing for additional changes
+- [T] Test Workflow - Try a test run (if workflow supports testing)"
+
+## Menu Handling Logic:
+
+- IF C: End workflow editing successfully with compliance validation summary
+- IF R: Present detailed compliance report findings
+- IF M: Return to step-03-discover.md for additional improvements
+- IF T: If workflow supports testing, suggest test execution method
+- IF Any other comments or queries: respond and redisplay completion options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN compliance validation is complete and user confirms final workflow status, will the workflow editing process be considered successfully finished.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Comprehensive compliance validation executed on edited workflow
+- All compliance issues identified and documented with severity rankings
+- User provided with clear understanding of validation results
+- Appropriate resolution options offered and implemented
+- Final edited workflow meets BMAD standards and is ready for production
+- User satisfaction with workflow quality and compliance
+
+### ❌ SYSTEM FAILURE:
+
+- Skipping compliance validation before workflow completion
+- Not addressing critical compliance issues found during validation
+- Failing to provide clear guidance on issue resolution
+- Declaring workflow complete without ensuring standards compliance
+- Not documenting final compliance status for future reference
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/bmad/bmb/workflows/edit-workflow/templates/completion-summary.md

@@ -0,0 +1,75 @@
+## Workflow Edit Complete!
+
+### Transformation Summary
+
+#### Starting Point
+
+- **Workflow**: {{workflowName}}
+- **Initial State**: {{initialState}}
+- **Primary Issues**: {{primaryIssues}}
+
+#### Improvements Made
+
+{{#improvements}}
+
+- **{{area}}**: {{description}}
+  - **Impact**: {{impact}}
+    {{/improvements}}
+
+#### Key Changes
+
+1. {{change1}}
+2. {{change2}}
+3. {{change3}}
+
+### Impact Assessment
+
+#### User Experience Improvements
+
+- **Before**: {{beforeUX}}
+- **After**: {{afterUX}}
+- **Benefit**: {{uxBenefit}}
+
+#### Technical Improvements
+
+- **Compliance**: {{complianceImprovement}}
+- **Maintainability**: {{maintainabilityImprovement}}
+- **Performance**: {{performanceImpact}}
+
+### Files Modified
+
+{{#modifiedFiles}}
+
+- **{{type}}**: {{path}}
+  {{/modifiedFiles}}
+
+### Next Steps
+
+#### Immediate Actions
+
+1. {{immediateAction1}}
+2. {{immediateAction2}}
+
+#### Testing Recommendations
+
+- {{testingRecommendation1}}
+- {{testingRecommendation2}}
+
+#### Future Considerations
+
+- {{futureConsideration1}}
+- {{futureConsideration2}}
+
+### Support Information
+
+- **Edited by**: {{userName}}
+- **Date**: {{completionDate}}
+- **Documentation**: {{outputFile}}
+
+### Thank You!
+
+Thank you for collaboratively improving this workflow. Your workflow now follows best practices and should provide a better experience for your users.
+
+---
+
+_Edit workflow completed successfully on {{completionDate}}_

package/bmad/bmb/workflows/edit-workflow/templates/improvement-goals.md

@@ -0,0 +1,68 @@
+## Improvement Goals
+
+### Motivation
+
+- **Trigger**: {{editTrigger}}
+- **User Feedback**: {{userFeedback}}
+- **Success Issues**: {{successIssues}}
+
+### User Experience Issues
+
+{{#uxIssues}}
+
+- {{.}}
+  {{/uxIssues}}
+
+### Performance Gaps
+
+{{#performanceGaps}}
+
+- {{.}}
+  {{/performanceGaps}}
+
+### Growth Opportunities
+
+{{#growthOpportunities}}
+
+- {{.}}
+  {{/growthOpportunities}}
+
+### Instruction Style Considerations
+
+- **Current Style**: {{currentStyle}}
+- **Desired Changes**: {{styleChanges}}
+- **Style Fit Assessment**: {{styleFit}}
+
+### Prioritized Improvements
+
+#### Critical (Must Fix)
+
+{{#criticalItems}}
+
+1. {{.}}
+   {{/criticalItems}}
+
+#### Important (Should Fix)
+
+{{#importantItems}}
+
+1. {{.}}
+   {{/importantItems}}
+
+#### Nice-to-Have (Could Fix)
+
+{{#niceItems}}
+
+1. {{.}}
+   {{/niceItems}}
+
+### Focus Areas for Next Step
+
+{{#focusAreas}}
+
+- {{.}}
+  {{/focusAreas}}
+
+---
+
+_Goals identified on {{date}}_

package/bmad/bmb/workflows/edit-workflow/templates/improvement-log.md

@@ -0,0 +1,40 @@
+## Improvement Log
+
+### Change Summary
+
+- **Date**: {{date}}
+- **Improvement Area**: {{improvementArea}}
+- **User Goal**: {{userGoal}}
+
+### Changes Made
+
+#### Change #{{changeNumber}}
+
+**Issue**: {{issueDescription}}
+**Solution**: {{solutionDescription}}
+**Rationale**: {{changeRationale}}
+
+**Files Modified**:
+{{#modifiedFiles}}
+
+- {{.}}
+  {{/modifiedFiles}}
+
+**Before**:
+
+```markdown
+{{beforeContent}}
+```
+
+**After**:
+
+```markdown
+{{afterContent}}
+```
+
+**User Approval**: {{userApproval}}
+**Impact**: {{expectedImpact}}
+
+---
+
+{{/improvementLog}}

package/bmad/bmb/workflows/edit-workflow/templates/validation-results.md

@@ -0,0 +1,51 @@
+## Validation Results
+
+### Overall Status
+
+**Result**: {{validationResult}}
+**Date**: {{date}}
+**Validator**: {{validator}}
+
+### Validation Categories
+
+#### File Structure
+
+- **Status**: {{fileStructureStatus}}
+- **Details**: {{fileStructureDetails}}
+
+#### Configuration
+
+- **Status**: {{configurationStatus}}
+- **Details**: {{configurationDetails}}
+
+#### Step Compliance
+
+- **Status**: {{stepComplianceStatus}}
+- **Details**: {{stepComplianceDetails}}
+
+#### Cross-File Consistency
+
+- **Status**: {{consistencyStatus}}
+- **Details**: {{consistencyDetails}}
+
+#### Best Practices
+
+- **Status**: {{bestPracticesStatus}}
+- **Details**: {{bestPracticesDetails}}
+
+### Issues Found
+
+{{#validationIssues}}
+
+- **{{severity}}**: {{description}}
+  - **Impact**: {{impact}}
+  - **Recommendation**: {{recommendation}}
+    {{/validationIssues}}
+
+### Validation Summary
+
+{{validationSummary}}
+
+---
+
+_Validation completed on {{date}}_

package/bmad/bmb/workflows/edit-workflow/templates/workflow-analysis.md

@@ -0,0 +1,56 @@
+## Workflow Analysis
+
+### Target Workflow
+
+- **Path**: {{workflowPath}}
+- **Name**: {{workflowName}}
+- **Module**: {{workflowModule}}
+- **Format**: {{workflowFormat}} (Standalone/Legacy)
+
+### Structure Analysis
+
+- **Type**: {{workflowType}}
+- **Total Steps**: {{stepCount}}
+- **Step Flow**: {{stepFlowPattern}}
+- **Files**: {{fileStructure}}
+
+### Content Characteristics
+
+- **Purpose**: {{workflowPurpose}}
+- **Instruction Style**: {{instructionStyle}}
+- **User Interaction**: {{interactionPattern}}
+- **Complexity**: {{complexityLevel}}
+
+### Initial Assessment
+
+#### Strengths
+
+{{#strengths}}
+
+- {{.}}
+  {{/strengths}}
+
+#### Potential Issues
+
+{{#issues}}
+
+- {{.}}
+  {{/issues}}
+
+#### Format-Specific Notes
+
+{{#formatNotes}}
+
+- {{.}}
+  {{/formatNotes}}
+
+### Best Practices Compliance
+
+- **Step File Structure**: {{stepCompliance}}
+- **Frontmatter Usage**: {{frontmatterCompliance}}
+- **Menu Implementation**: {{menuCompliance}}
+- **Variable Consistency**: {{variableCompliance}}
+
+---
+
+_Analysis completed on {{date}}_

package/bmad/bmb/workflows/edit-workflow/workflow.md

@@ -0,0 +1,59 @@
+---
+name: edit-workflow
+description: Intelligent workflow editor that helps modify existing workflows while following best practices
+web_bundle: true
+---
+
+# Edit Workflow
+
+**Goal:** Collaboratively edit and improve existing workflows, ensuring they follow best practices and meet user needs effectively.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a workflow editor and improvement specialist collaborating with a workflow owner. This is a partnership, not a client-vendor relationship. You bring expertise in workflow design patterns, best practices, and collaborative facilitation, while the user brings their workflow context, user feedback, and improvement goals. 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 output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents 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`, `bmb_creations_output_folder`
+- ✅ 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-analyze.md` to begin the workflow.