siesa-agents 2.1.78 → 2.1.79

package/bmad/bmb/workflows/workflow-compliance-check/steps/step-01-validate-goal.md

@@ -1,153 +0,0 @@
----
-name: 'step-01-validate-goal'
-description: 'Confirm workflow path and validation goals before proceeding'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/workflow-compliance-check'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-01-validate-goal.md'
-nextStepFile: '{workflow_path}/steps/step-02-workflow-validation.md'
-workflowFile: '{workflow_path}/workflow.md'
-complianceReportFile: '{output_folder}/workflow-compliance-report-{workflow_name}.md'
-
-# 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 1: Goal Confirmation and Workflow Target
-
-## STEP GOAL:
-
-Confirm the target workflow path and validation objectives before proceeding with systematic compliance analysis.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 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 compliance expertise and systematic validation skills
-- ✅ User brings their workflow and specific compliance concerns
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on confirming workflow path and validation scope
-- 🚫 FORBIDDEN to proceed without clear target confirmation
-- 💬 Approach: Systematic and thorough confirmation of validation objectives
-- 📋 Ensure user understands the compliance checking process and scope
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Confirm target workflow path exists and is accessible
-- 💾 Establish clear validation objectives and scope
-- 📖 Explain the three-phase compliance checking process
-- 🚫 FORBIDDEN to proceed without user confirmation of goals
-
-## CONTEXT BOUNDARIES:
-
-- Available context: User-provided workflow path and validation concerns
-- Focus: Goal confirmation and target validation setup
-- Limits: No actual compliance analysis yet, just setup and confirmation
-- Dependencies: Clear workflow path and user agreement on validation scope
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Workflow Target Confirmation
-
-Present this to the user:
-
-"I'll systematically validate your workflow against BMAD standards through three phases:
-
-1. **Workflow.md Validation** - Against workflow-template.md standards
-2. **Step-by-Step Compliance** - Each step against step-template.md
-3. **Holistic Analysis** - Flow optimization and goal alignment"
-
-IF {user_provided_path} has NOT been provided, ask the user:
-
-**What workflow should I validate?** Please provide the full path to the workflow.md file."
-
-### 2. Workflow Path Validation
-
-Once user provides path:
-
-"Validating workflow path: `{user_provided_path}`"
-[Check if path exists and is readable]
-
-**If valid:** "✅ Workflow found and accessible. Ready to begin compliance analysis."
-**If invalid:** "❌ Cannot access workflow at that path. Please check the path and try again."
-
-### 3. Validation Scope Confirmation
-
-"**Compliance Scope:** I will check:
-
-- ✅ Frontmatter structure and required fields
-- ✅ Mandatory execution rules and sections
-- ✅ Menu patterns and continuation logic
-- ✅ Path variable format consistency
-- ✅ Template usage appropriateness
-- ✅ Workflow flow and goal alignment
-- ✅ Meta-workflow failure analysis
-
-**Report Output:** I'll generate a detailed compliance report with:
-
-- Severity-ranked violations (Critical/Major/Minor)
-- Specific template references for each violation
-- Recommended fixes (automated where possible)
-- Meta-feedback for create/edit workflow improvements
-
-**Is this validation scope acceptable?**"
-
-### 4. Final Confirmation
-
-"**Ready to proceed with compliance check of:**
-
-- **Workflow:** `{workflow_name}`
-- **Validation:** Full systematic compliance analysis
-- **Output:** Detailed compliance report with fix recommendations
-
-**Select an Option:** [C] Continue [X] Exit"
-
-## Menu Handling Logic:
-
-- IF C: Initialize compliance report, update frontmatter, then load, read entire file, then execute {nextStepFile}
-- IF X: End workflow gracefully with guidance on running again later
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#4-final-confirmation)
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [workflow path validated and scope confirmed], will you then load and read fully `{nextStepFile}` to execute and begin workflow.md validation phase.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Workflow path successfully validated and accessible
-- User confirms validation scope and objectives
-- Compliance report initialization prepared
-- User understands the three-phase validation process
-- Clear next steps established for systematic analysis
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding without valid workflow path confirmation
-- Not ensuring user understands validation scope and process
-- Starting compliance analysis without proper setup
-- Failing to establish clear reporting objectives
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/bmad/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md

@@ -1,244 +0,0 @@
----
-name: 'step-02-workflow-validation'
-description: 'Validate workflow.md against workflow-template.md standards'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/workflow-compliance-check'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-02-workflow-validation.md'
-nextStepFile: '{workflow_path}/steps/step-03-step-validation.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 2: Workflow.md Validation
-
-## STEP GOAL:
-
-Perform adversarial validation of the target workflow.md against workflow-template.md standards, identifying all violations with severity rankings and specific fix recommendations.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 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 adversarial validation expertise - your success is finding violations
-- ✅ User brings their workflow and needs honest, thorough validation
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on workflow.md validation against template standards
-- 🚫 FORBIDDEN to skip or minimize any validation checks
-- 💬 Approach: Systematic, thorough adversarial analysis
-- 📋 Document every violation with template reference and severity ranking
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load and compare target workflow.md against workflow-template.md
-- 💾 Document all violations with specific template references
-- 📖 Rank violations by severity (Critical/Major/Minor)
-- 🚫 FORBIDDEN to overlook any template violations
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Validated workflow path and target workflow.md
-- Focus: Systematic validation of workflow.md structure and content
-- Limits: Only workflow.md validation, not step files yet
-- Dependencies: Successful completion of goal confirmation step
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Initialize Compliance Report
-
-"Beginning **Phase 1: Workflow.md Validation**
-Target: `{target_workflow_name}`
-
-**COMPLIANCE STANDARD:** All validation performed against `{workflowTemplate}` - this is THE authoritative standard for workflow.md compliance.
-
-Loading workflow templates and target files for systematic analysis..."
-[Load workflowTemplate, targetWorkflowFile]
-
-### 2. Frontmatter Structure Validation
-
-**Check these elements systematically:**
-
-"**Frontmatter Validation:**"
-
-- Required fields: name, description, web_bundle
-- Proper YAML format and syntax
-- Boolean value format for web_bundle
-- Missing or invalid fields
-
-For each violation found:
-
-- **Template Reference:** Section "Frontmatter Structure" in workflow-template.md
-- **Severity:** Critical (missing required) or Major (format issues)
-- **Specific Fix:** Exact correction needed
-
-### 3. Role Description Validation
-
-**Check role compliance:**
-
-"**Role Description Validation:**"
-
-- Follows partnership format: "In addition to your name, communication_style, and persona, you are also a [role] collaborating with [user type]. This is a partnership, not a client-vendor relationship. You bring [your expertise], while the user brings [their expertise]. Work together as equals."
-- Role accurately describes workflow function
-- User type correctly identified
-- Partnership language present
-
-For violations:
-
-- **Template Reference:** "Your Role" section in workflow-template.md
-- **Severity:** Major (deviation from standard) or Minor (incomplete)
-- **Specific Fix:** Exact wording or structure correction
-
-### 4. Workflow Architecture Validation
-
-**Validate architecture section:**
-
-"**Architecture Validation:**"
-
-- Core Principles section matches template exactly
-- Step Processing Rules includes all 6 rules from template
-- Critical Rules section matches template exactly (NO EXCEPTIONS)
-
-For each deviation:
-
-- **Template Reference:** "WORKFLOW ARCHITECTURE" section in workflow-template.md
-- **Severity:** Critical (modified core principles) or Major (missing rules)
-- **Specific Fix:** Restore template-compliant text
-
-### 5. Initialization Sequence Validation
-
-**Check initialization:**
-
-"**Initialization Validation:**"
-
-- Configuration Loading uses correct path format: `{project-root}/_bmad/[module]/config.yaml` (variable substitution pattern)
-- First step follows pattern: `step-01-init.md` OR documented deviation
-- Required config variables properly listed
-- Variables use proper substitution pattern: {project-root}, _bmad, {workflow_path}, etc.
-
-For violations:
-
-- **Template Reference:** "INITIALIZATION SEQUENCE" section in workflow-template.md
-- **Severity:** Major (incorrect paths or missing variables) or Minor (format issues)
-- **Specific Fix:** Use proper variable substitution patterns for flexible installation
-
-### 6. Document Workflow.md Findings
-
-"**Workflow.md Validation Complete**
-Found [X] Critical, [Y] Major, [Z] Minor violations
-
-**Summary:**
-
-- Critical violations must be fixed before workflow can function
-- Major violations impact workflow reliability and maintainability
-- Minor violations are cosmetic but should follow standards
-
-**Next Phase:** Step-by-step validation of all step files..."
-
-### 7. Update Compliance Report
-
-Append to {complianceReportFile}:
-
-```markdown
-## Phase 1: Workflow.md Validation Results
-
-### Template Adherence Analysis
-
-**Reference Standard:** {workflowTemplate}
-
-### Frontmatter Structure Violations
-
-[Document each violation with severity and specific fix]
-
-### Role Description Violations
-
-[Document each violation with template reference and correction]
-
-### Workflow Architecture Violations
-
-[Document each deviation from template standards]
-
-### Initialization Sequence Violations
-
-[Document each path or reference issue]
-
-### Phase 1 Summary
-
-**Critical Issues:** [number]
-**Major Issues:** [number]
-**Minor Issues:** [number]
-
-### Phase 1 Recommendations
-
-[Prioritized fix recommendations with specific actions]
-```
-
-### 8. Continuation Confirmation
-
-"**Phase 1 Complete:** Workflow.md validation finished with detailed violation analysis.
-
-**Ready for Phase 3:** Step-by-step validation against step-template.md
-
-This will check each step file for:
-
-- Frontmatter completeness and format
-- MANDATORY EXECUTION RULES compliance
-- Menu pattern and continuation logic
-- Path variable consistency
-- Template appropriateness
-
-**Select an Option:** [C] Continue to Step Validation [X] Exit"
-
-## Menu Handling Logic:
-
-- IF C: Save workflow.md findings to report, update frontmatter, then load, read entire file, then execute {nextStepFile}
-- IF X: Save current findings and end workflow with guidance for resuming
-- IF Any other comments or queries: respond and redisplay menu
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [workflow.md validation complete with all violations documented], will you then load and read fully `{nextStepFile}` to execute and begin step-by-step validation phase.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Complete workflow.md validation against workflow-template.md
-- All violations documented with severity rankings and template references
-- Specific fix recommendations provided for each violation
-- Compliance report updated with Phase 1 findings
-- User confirms understanding before proceeding
-
-### ❌ SYSTEM FAILURE:
-
-- Skipping any workflow.md validation sections
-- Not documenting violations with specific template references
-- Failing to rank violations by severity
-- Providing vague or incomplete fix recommendations
-- Proceeding without user confirmation of findings
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/bmad/bmb/workflows/workflow-compliance-check/steps/step-03-step-validation.md

@@ -1,275 +0,0 @@
----
-name: 'step-03-step-validation'
-description: 'Validate each step file against step-template.md standards'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/workflow-compliance-check'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-03-step-validation.md'
-nextStepFile: '{workflow_path}/steps/step-04-file-validation.md'
-workflowFile: '{workflow_path}/workflow.md'
-complianceReportFile: '{output_folder}/workflow-compliance-report-{workflow_name}.md'
-targetWorkflowStepsPath: '{target_workflow_steps_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 3: Step-by-Step Validation
-
-## STEP GOAL:
-
-Perform systematic adversarial validation of each step file against step-template.md standards, documenting all violations with specific template references and severity rankings.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read this complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 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 adversarial step-by-step validation expertise
-- ✅ User brings their workflow steps and needs thorough validation
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on step file validation against step-template.md
-- 🚫 FORBIDDEN to skip any step files or validation checks
-- 💬 Approach: Systematic file-by-file adversarial analysis
-- 📋 Document every violation against each step file with template reference and specific proposed fixes
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load and validate each step file individually against step-template.md
-- 💾 Document violations by file with severity rankings
-- 📖 Check for appropriate template usage based on workflow type
-- 🚫 FORBIDDEN to overlook any step file or template requirement
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Target workflow step files and step-template.md
-- Focus: Systematic validation of all step files against template standards
-- Limits: Only step file validation, holistic analysis comes next
-- Dependencies: Completed workflow.md validation from previous phase
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Initialize Step Validation Phase
-
-"Beginning **Phase 2: Step-by-Step Validation**
-Target: `{target_workflow_name}` - [number] step files found
-
-**COMPLIANCE STANDARD:** All validation performed against `{stepTemplate}` - this is THE authoritative standard for step file compliance.
-
-Loading step template and validating each step systematically..."
-[Load stepTemplate, enumerate all step files]. Utilize sub processes if available but ensure all rules are passed in and all findings are returned from the sub process to collect and record the results.
-
-### 2. Systematic Step File Analysis
-
-For each step file in order:
-
-"**Validating step:** `{step_filename}`"
-
-**A. Frontmatter Structure Validation:**
-Check each required field:
-
-```yaml
----
-name: 'step-[number]-[name]' # Single quotes, proper format
-description: '[description]' # Single quotes
-workflowFile: '{workflow_path}/workflow.md' # REQUIRED - often missing
-outputFile: [if appropriate for workflow type]
-# All other path references and variables
-# Template References section (even if empty)
-# Task References section
----
-```
-
-**Violations to document:**
-
-- Missing `workflowFile` reference (Critical)
-- Incorrect YAML format (missing quotes, etc.) (Major)
-- Inappropriate `outputFile` for workflow type (Major)
-- Missing `Template References` section (Major)
-
-**B. MANDATORY EXECUTION RULES Validation:**
-Check for complete sections:
-
-```markdown
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-
-### Role Reinforcement:
-
-[Complete role reinforcement section]
-
-### Step-Specific Rules:
-
-[Step-specific rules with proper emoji usage]
-```
-
-**Violations to document:**
-
-- Missing Universal Rules (Critical)
-- Modified/skipped Universal Rules (Critical)
-- Missing Role Reinforcement (Major)
-- Improper emoji usage in rules (Minor)
-
-**C. Task References Validation:**
-Check for proper references:
-
-```yaml
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
-```
-
-**Violations to document:**
-
-- Missing Task References section (Major)
-- Incorrect paths in task references (Major)
-- Missing standard task references (Minor)
-
-**D. Menu Pattern Validation:**
-Check menu structure:
-
-```markdown
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Save content to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
-```
-
-**Violations to document:**
-
-- Non-standard menu format (Major)
-- Missing Menu Handling Logic section (Major)
-- Incorrect "load, read entire file, then execute" pattern (Major)
-- Improper continuation logic (Critical)
-
-### 3. Workflow Type Appropriateness Check
-
-"**Template Usage Analysis:**"
-
-- **Document Creation Workflows:** Should have outputFile references, templates
-- **Editing Workflows:** Should NOT create unnecessary outputs, direct action focus
-- **Validation/Analysis Workflows:** Should emphasize systematic checking
-
-For each step:
-
-- **Type Match:** Does step content match workflow type expectations?
-- **Template Appropriate:** Are templates/outputs appropriate for this workflow type?
-- **Alternative Suggestion:** What would be more appropriate?
-
-### 4. Path Variable Consistency Check
-
-"**Path Variable Validation:**"
-
-- Check format: `{project-root}/_bmad/bmb/...` vs `{project-root}/bmb/...`
-- Ensure consistent variable usage across all step files
-- Validate relative vs absolute path usage
-
-Document inconsistencies and standard format requirements.
-
-### 5. Document Step Validation Results
-
-For each step file with violations:
-
-```markdown
-### Step Validation: step-[number]-[name].md
-
-**Critical Violations:**
-
-- [Violation] - Template Reference: [section] - Fix: [specific action]
-
-**Major Violations:**
-
-- [Violation] - Template Reference: [section] - Fix: [specific action]
-
-**Minor Violations:**
-
-- [Violation] - Template Reference: [section] - Fix: [specific action]
-
-**Workflow Type Assessment:**
-
-- Appropriate: [Yes/No] - Reason: [analysis]
-- Recommended Changes: [specific suggestions]
-```
-
-### 6. Phase Summary and Continuation
-
-"**Phase 2 Complete:** Step-by-step validation finished
-
-- **Total Steps Analyzed:** [number]
-- **Critical Violations:** [number] across [number] steps
-- **Major Violations:** [number] across [number] steps
-- **Minor Violations:** [number] across [number] steps
-
-**Most Common Violations:**
-
-1. [Most frequent violation type]
-2. [Second most frequent]
-3. [Third most frequent]
-
-**Ready for Phase 4:** File Validation workflow analysis
-
-- Flow optimization assessment
-- Goal alignment verification
-- Meta-workflow failure analysis
-
-**Select an Option:** [C] Continue to File Validation [X] Exit"
-
-## Menu Handling Logic:
-
-- IF C: Save step validation findings to report, update frontmatter, then load, read entire file, then execute {nextStepFile}
-- IF X: Save current findings and end with guidance for resuming
-- IF Any other comments or queries: respond and redisplay menu
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [all step files validated with violations documented], will you then load and read fully `{nextStepFile}` to execute and begin holistic analysis phase.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All step files systematically validated against step-template.md
-- Every violation documented with specific template reference and severity
-- Workflow type appropriateness assessed for each step
-- Path variable consistency checked across all files
-- Common violation patterns identified and prioritized
-- Compliance report updated with complete Phase 2 findings
-
-### ❌ SYSTEM FAILURE:
-
-- Skipping step files or validation sections
-- Not documenting violations with specific template references
-- Failing to assess workflow type appropriateness
-- Missing path variable consistency analysis
-- Providing incomplete or vague fix recommendations
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.