bmad-method 6.0.0-alpha.12 → 6.0.0-alpha.13

package/src/modules/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/src/modules/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/src/modules/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/src/modules/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/src/modules/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/src/modules/bmb/workflows/edit-workflow/workflow.md

@@ -0,0 +1,58 @@
+---
+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_folder}/bmb/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `{workflow_path}/steps/step-01-analyze.md` to begin the workflow.

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

@@ -0,0 +1,152 @@
+---
+name: 'step-01-validate-goal'
+description: 'Confirm workflow path and validation goals before proceeding'
+
+# Path Definitions
+workflow_path: '{project-root}/{bmad_folder}/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_folder}/bmb/docs/workflows/step-template.md'
+workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/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
+
+### 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.