npm - bmad-method - Versions diffs - 6.0.0-alpha.22 → 6.0.0-alpha.23 - Mend

bmad-method 6.0.0-alpha.22 → 6.0.0-alpha.23

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

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-05-intent-spectrum-validation.md DELETED Viewed

@@ -1,265 +0,0 @@
----
-name: 'step-05-intent-spectrum-validation'
-description: 'Dedicated analysis and validation of intent vs prescriptive spectrum positioning'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/workflow-compliance-check'
-# File References
-thisStepFile: '{workflow_path}/steps/step-05-intent-spectrum-validation.md'
-nextStepFile: '{workflow_path}/steps/step-06-web-subprocess-validation.md'
-workflowFile: '{workflow_path}/workflow.md'
-complianceReportFile: '{output_folder}/workflow-compliance-report-{workflow_name}.md'
-targetWorkflowPath: '{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'
-intentSpectrum: '{project-root}/_bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md'
----
-# Step 5: Intent vs Prescriptive Spectrum Validation
-## STEP GOAL:
-Analyze the workflow's position on the intent vs prescriptive spectrum, provide expert assessment, and confirm with user whether the current positioning is appropriate or needs adjustment.
-## 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 design philosophy 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 intent vs prescriptive design principles
-- ✅ User brings their workflow and needs guidance on spectrum positioning
-### Step-Specific Rules:
-- 🎯 Focus only on spectrum analysis and user confirmation
-- 🚫 FORBIDDEN to make spectrum decisions without user input
-- 💬 Approach: Educational, analytical, and collaborative
-- 📋 Ensure user understands spectrum implications before confirming
-## EXECUTION PROTOCOLS:
-- 🎯 Analyze workflow's current spectrum position based on all previous findings
-- 💾 Provide expert assessment with specific examples and reasoning
-- 📖 Educate user on spectrum implications for their workflow type
-- 🚫 FORBIDDEN to proceed without user confirmation of spectrum position
-## CONTEXT BOUNDARIES:
-- Available context: Complete analysis from workflow, step, and file validation phases
-- Focus: Intent vs prescriptive spectrum analysis and user confirmation
-- Limits: Spectrum analysis only, holistic workflow analysis comes next
-- Dependencies: Successful completion of file size and formatting validation
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-### 1. Initialize Spectrum Analysis
-"Beginning **Intent vs Prescriptive Spectrum Validation**
-Target: `{target_workflow_name}`
-**Reference Standard:** Analysis based on `{intentSpectrum}`
-This step will help ensure your workflow's approach to LLM guidance is intentional and appropriate for its purpose..."
-### 2. Spectrum Position Analysis
-**A. Current Position Assessment:**
-Based on analysis of workflow.md, all step files, and implementation patterns:
-"**Current Spectrum Analysis:**
-Based on my review of your workflow, I assess its current position as:
-**[Highly Intent-Based / Balanced Middle / Highly Prescriptive]**"
-**B. Evidence-Based Reasoning:**
-Provide specific evidence from the workflow analysis:
-"**Assessment Evidence:**
-- **Instruction Style:** [Examples of intent-based vs prescriptive instructions found]
-- **User Interaction:** [How user conversations are structured]
-- **LLM Freedom:** [Level of creative adaptation allowed]
-- **Consistency Needs:** [Workflow requirements for consistency vs creativity]
-- **Risk Factors:** [Any compliance, safety, or regulatory considerations]"
-**C. Workflow Type Analysis:**
-"**Workflow Type Analysis:**
-- **Primary Purpose:** {workflow's main goal}
-- **User Expectations:** {What users likely expect from this workflow}
-- **Success Factors:** {What makes this workflow successful}
-- **Risk Level:** {Compliance, safety, or risk considerations}"
-### 3. Recommended Spectrum Position
-**A. Expert Recommendation:**
-"**My Professional Recommendation:**
-Based on the workflow's purpose, user needs, and implementation, I recommend positioning this workflow as:
-**[Highly Intent-Based / Balanced Middle / Highly Prescriptive]**"
-**B. Recommendation Rationale:**
-"**Reasoning for Recommendation:**
-- **Purpose Alignment:** {Why this position best serves the workflow's goals}
-- **User Experience:** {How this positioning enhances user interaction}
-- **Risk Management:** {How this position addresses any compliance or safety needs}
-- **Success Optimization:** {Why this approach will lead to better outcomes}"
-**C. Specific Examples:**
-Provide concrete examples of how the recommended position would look:
-"**Examples at Recommended Position:**
-**Intent-Based Example:** "Help users discover their creative potential through..."
-**Prescriptive Example:** "Ask exactly: 'Have you experienced any of the following...'"
-**Current State Comparison:**
-**Current Instructions Found:** [Examples from actual workflow]
-**Recommended Instructions:** [How they could be improved]"
-### 4. Spectrum Education and Implications
-**A. Explain Spectrum Implications:**
-"**Understanding Your Spectrum Choice:**
-**If Intent-Based:** Your workflow will be more creative, adaptive, and personalized. Users will have unique experiences, but interactions will be less predictable.
-**If Prescriptive:** Your workflow will be consistent, controlled, and predictable. Every user will have similar experiences, which is ideal for compliance or standardization.
-**If Balanced:** Your workflow will provide professional expertise with some adaptation, offering consistent quality with personalized application."
-**B. Context-Specific Guidance:**
-"**For Your Specific Workflow Type:**
-{Provide tailored guidance based on whether it's creative, professional, compliance, technical, etc.}"
-### 5. User Confirmation and Decision
-**A. Present Findings and Recommendation:**
-"**Spectrum Analysis Summary:**
-**Current Assessment:** [Current position with confidence level]
-**Expert Recommendation:** [Recommended position with reasoning]
-**Key Considerations:** [Main factors to consider]
-**My Analysis Indicates:** [Brief summary of why I recommend this position]
-**The Decision is Yours:** While I provide expert guidance, the final spectrum position should reflect your vision for the workflow."
-**B. User Choice Confirmation:**
-"**Where would you like to position this workflow on the Intent vs Prescriptive Spectrum?**
-**Options:**
-1. **Keep Current Position** - [Current position] - Stay with current approach
-2. **Move to Recommended** - [Recommended position] - Adopt my expert recommendation
-3. **Move Toward Intent-Based** - Increase creative freedom and adaptation
-4. **Move Toward Prescriptive** - Increase consistency and control
-5. **Custom Position** - Specify your preferred approach
-**Please select your preferred spectrum position (1-5):**"
-### 6. Document Spectrum Decision
-**A. Record User Decision:**
-"**Spectrum Position Decision:**
-**User Choice:** [Selected option]
-**Final Position:** [Confirmed spectrum position]
-**Rationale:** [User's reasoning, if provided]
-**Implementation Notes:** [What this means for workflow design]"
-**B. Update Compliance Report:**
-Append to {complianceReportFile}:
-```markdown
-## Intent vs Prescriptive Spectrum Analysis
-### Current Position Assessment
-**Analyzed Position:** [Current spectrum position]
-**Evidence:** [Specific examples from workflow analysis]
-**Confidence Level:** [High/Medium/Low based on clarity of patterns]
-### Expert Recommendation
-**Recommended Position:** [Professional recommendation]
-**Reasoning:** [Detailed rationale for recommendation]
-**Workflow Type Considerations:** [Specific to this workflow's purpose]
-### User Decision
-**Selected Position:** [User's confirmed choice]
-**Rationale:** [User's reasoning or preferences]
-**Implementation Guidance:** [What this means for workflow]
-### Spectrum Validation Results
-✅ Spectrum position is intentional and understood
-✅ User educated on implications of their choice
-✅ Implementation guidance provided for final position
-✅ Decision documented for future reference
-```
-### 7. Continuation Confirmation
-"**Spectrum Validation Complete:**
-- **Final Position:** [Confirmed spectrum position]
-- **User Understanding:** Confirmed implications and benefits
-- **Implementation Ready:** Guidance provided for maintaining position
-**Ready for Phase 6:** Web Subprocess Validation analysis
-- Flow validation and completion paths
-- Goal alignment and optimization assessment
-- Meta-workflow failure analysis and improvement recommendations
-**Select an Option:** [C] Continue to Web Subprocess Validation [X] Exit"
-## Menu Handling Logic:
-- IF C: Save spectrum decision to report, update frontmatter, then load, read entire file, then execute {nextStepFile}
-- IF X: Save current spectrum 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 [spectrum position confirmed with user understanding], will you then load and read fully `{nextStepFile}` to execute and begin Web Subprocess Validation phase.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- Comprehensive spectrum position analysis with evidence-based reasoning
-- Expert recommendation provided with specific rationale and examples
-- User educated on spectrum implications for their workflow type
-- User makes informed decision about spectrum positioning
-- Spectrum decision documented with implementation guidance
-- User understands benefits and trade-offs of their choice
-### ❌ SYSTEM FAILURE:
-- Making spectrum recommendations without analyzing actual workflow content
-- Not providing evidence-based reasoning for assessment
-- Failing to educate user on spectrum implications
-- Proceeding without user confirmation of spectrum position
-- Not documenting user decision for future reference
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-06-web-subprocess-validation.md DELETED Viewed

@@ -1,361 +0,0 @@
----
-name: 'step-06-web-subprocess-validation'
-description: 'Analyze web search utilization and subprocess optimization opportunities across workflow steps'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/workflow-compliance-check'
-# File References
-thisStepFile: '{workflow_path}/steps/step-06-web-subprocess-validation.md'
-nextStepFile: '{workflow_path}/steps/step-07-holistic-analysis.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'
-intentSpectrum: '{project-root}/_bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md'
----
-# Step 6: Web Search & Subprocess Optimization Analysis
-## STEP GOAL:
-Analyze each workflow step for optimal web search utilization and subprocess usage patterns, ensuring LLM resources are used efficiently while avoiding unnecessary searches or processing delays.
-## 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 performance optimization specialist and resource efficiency analyst
-- ✅ 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 LLM optimization, web search strategy, and subprocess utilization
-- ✅ User brings their workflow and needs efficiency recommendations
-### Step-Specific Rules:
-- 🎯 Focus only on web search necessity and subprocess optimization opportunities
-- 🚫 FORBIDDEN to recommend web searches when LLM knowledge is sufficient
-- 💬 Approach: Analytical and optimization-focused with clear efficiency rationale
-- 📋 Use subprocesses when analyzing multiple steps to improve efficiency
-## EXECUTION PROTOCOLS:
-- 🎯 Analyze each step for web search appropriateness vs. LLM knowledge sufficiency
-- 💾 Identify subprocess optimization opportunities for parallel processing
-- 📖 Use subprocesses/subagents when analyzing multiple steps for efficiency
-- 🚫 FORBIDDEN to overlook inefficiencies or recommend unnecessary searches
-## CONTEXT BOUNDARIES:
-- Available context: All workflow step files and subprocess availability
-- Focus: Web search optimization and subprocess utilization analysis
-- Limits: Resource optimization analysis only, holistic workflow analysis comes next
-- Dependencies: Completed Intent Spectrum validation from previous phase
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-### 1. Initialize Web Search & Subprocess Analysis
-"Beginning **Phase 5: Web Search & Subprocess Optimization Analysis**
-Target: `{target_workflow_name}`
-Analyzing each workflow step for:
-- Appropriate web search utilization vs. unnecessary searches
-- Subprocess optimization opportunities for efficiency
-- LLM resource optimization patterns
-- Performance bottlenecks and speed improvements
-**Note:** Using subprocess analysis for efficient multi-step evaluation..."
-### 2. Web Search Necessity Analysis
-**A. Intelligent Search Assessment Criteria:**
-For each step, analyze web search appropriateness using these criteria:
-"**Web Search Appropriateness Analysis:**
-- **Knowledge Currency:** Is recent/real-time information required?
-- **Specific Data Needs:** Are there specific facts/data not in LLM training?
-- **Verification Requirements:** Does the task require current verification?
-- **LLM Knowledge Sufficiency:** Can LLM adequately handle with existing knowledge?
-- **Search Cost vs. Benefit:** Is search time worth the information gain?"
-**B. Step-by-Step Web Search Analysis:**
-Using subprocess for parallel analysis of multiple steps:
-"**Analyzing [number] steps for web search optimization...**"
-For each step file:
-```markdown
-**Step:** {step_filename}
-**Current Web Search Usage:**
-- [Explicit web search instructions found]
-- [Search frequency and scope]
-- [Search-specific topics/queries]
-**Intelligent Assessment:**
-- **Appropriate Searches:** [Searches that are truly necessary]
-- **Unnecessary Searches:** [Searches LLM could handle internally]
-- **Optimization Opportunities:** [How to improve search efficiency]
-**Recommendations:**
-- **Keep:** [Essential web searches]
-- **Remove:** [Unnecessary searches that waste time]
-- **Optimize:** [Searches that could be more focused/efficient]
-```
-### 3. Subprocess & Parallel Processing Analysis
-**A. Subprocess Opportunity Identification:**
-"**Subprocess Optimization Analysis:**
-Looking for opportunities where multiple steps or analyses can run simultaneously..."
-**Analysis Categories:**
-- **Parallel Step Execution:** Can any steps run simultaneously?
-- **Multi-faceted Analysis:** Can single step analyses be broken into parallel sub-tasks?
-- **Batch Processing:** Can similar operations be grouped for efficiency?
-- **Background Processing:** Can any analyses run while user interacts?
-**B. Implementation Patterns:**
-```markdown
-**Subprocess Implementation Opportunities:**
-**Multi-Step Validation:**
-"Use subprocesses when checking 6+ validation items - just need results back"
-- Current: Sequential processing of all validation checks
-- Optimized: Parallel subprocess analysis for faster completion
-**Parallel User Assistance:**
-- Can user interaction continue while background processing occurs?
-- Can multiple analyses run simultaneously during user wait times?
-**Batch Operations:**
-- Can similar file operations be grouped?
-- Can multiple data sources be processed in parallel?
-```
-### 4. LLM Resource Optimization Analysis
-**A. Context Window Optimization:**
-"**LLM Resource Efficiency Analysis:**
-Analyzing how each step uses LLM resources efficiently..."
-**Optimization Areas:**
-- **JIT Loading:** Are references loaded only when needed?
-- **Context Management:** Is context used efficiently vs. wasted?
-- **Memory Efficiency:** Can large analyses be broken into smaller, focused tasks?
-- **Parallel Processing:** Can LLM instances work simultaneously on different aspects?
-**B. Speed vs. Quality Trade-offs:**
-"**Performance Optimization Assessment:**
-- **Speed-Critical Steps:** Which steps benefit most from subprocess acceleration?
-- **Quality-Critical Steps:** Which steps need focused LLM attention?
-- **Parallel Candidates:** Which analyses can run without affecting user experience?
-- **Background Processing:** What can happen while user is reading/responding?"
-### 5. Step-by-Step Optimization Recommendations
-**A. Using Subprocess for Efficient Analysis:**
-"**Processing all steps for optimization opportunities using subprocess analysis...**"
-**For each workflow step, analyze:**
-**1. Web Search Optimization:**
-```markdown
-**Step:** {step_name}
-**Current Search Usage:** {current_search_instructions}
-**Intelligent Assessment:** {is_search_necessary}
-**Recommendation:**
-- **Keep essential searches:** {specific_searches_to_keep}
-- **Remove unnecessary searches:** {searches_to_remove}
-- **Optimize search queries:** {improved_search_approach}
-```
-**2. Subprocess Opportunities:**
-```markdown
-**Parallel Processing Potential:**
-- **Can run with user interaction:** {yes/no_specifics}
-- **Can batch with other steps:** {opportunities}
-- **Can break into sub-tasks:** {subtask_breakdown}
-- **Background processing:** {what_can_run_in_background}
-```
-**3. LLM Efficiency:**
-```markdown
-**Resource Optimization:**
-- **Context efficiency:** {current_vs_optimal}
-- **Processing time:** {estimated_improvements}
-- **User experience impact:** {better/same/worse}
-```
-### 6. Aggregate Optimization Analysis
-**A. Web Search Optimization Summary:**
-"**Web Search Optimization Results:**
-- **Total Steps Analyzed:** [number]
-- **Steps with Web Searches:** [number]
-- **Unnecessary Searches Found:** [number]
-- **Optimization Opportunities:** [number]
-- **Estimated Time Savings:** [time_estimate]"
-**B. Subprocess Implementation Summary:**
-"**Subprocess Optimization Results:**
-- **Parallel Processing Opportunities:** [number]
-- **Batch Processing Groups:** [number]
-- **Background Processing Tasks:** [number]
-- **Estimated Performance Improvement:** [percentage_improvement]"
-### 7. User-Facing Optimization Report
-**A. Key Efficiency Findings:**
-"**Optimization Analysis Summary:**
-**Web Search Efficiency:**
-- **Current Issues:** [unnecessary searches wasting time]
-- **Recommendations:** [specific improvements]
-- **Expected Benefits:** [faster response, better user experience]
-**Processing Speed Improvements:**
-- **Parallel Processing Gains:** [specific opportunities]
-- **Background Processing Benefits:** [user experience improvements]
-- **Resource Optimization:** [LLM efficiency gains]
-**Implementation Priority:**
-1. **High Impact, Low Effort:** [Quick wins]
-2. **High Impact, High Effort:** [Major improvements]
-3. **Low Impact, Low Effort:** [Fine-tuning]
-4. **Future Considerations:** [Advanced optimizations]"
-### 8. Document Optimization Findings
-Append to {complianceReportFile}:
-```markdown
-## Web Search & Subprocess Optimization Analysis
-### Web Search Optimization
-**Unnecessary Searches Identified:** [number]
-**Essential Searches to Keep:** [specific_list]
-**Optimization Recommendations:** [detailed_suggestions]
-**Estimated Time Savings:** [time_improvement]
-### Subprocess Optimization Opportunities
-**Parallel Processing:** [number] opportunities identified
-**Batch Processing:** [number] grouping opportunities
-**Background Processing:** [number] background task opportunities
-**Performance Improvement:** [estimated_improvement_percentage]%
-### Resource Efficiency Analysis
-**Context Optimization:** [specific_improvements]
-**LLM Resource Usage:** [efficiency_gains]
-**User Experience Impact:** [positive_changes]
-### Implementation Recommendations
-**Immediate Actions:** [quick_improvements]
-**Strategic Improvements:** [major_optimizations]
-**Future Enhancements:** [advanced_optimizations]
-```
-### 9. Continuation Confirmation
-"**Web Search & Subprocess Analysis Complete:**
-- **Web Search Optimization:** [summary of improvements]
-- **Subprocess Opportunities:** [number of optimization areas]
-- **Performance Impact:** [expected efficiency gains]
-- **User Experience Benefits:** [specific improvements]
-**Ready for Phase 7:** Holistic workflow analysis
-- Flow validation and completion paths
-- Goal alignment with optimized resources
-- Meta-workflow failure analysis
-- Strategic recommendations with efficiency considerations
-**Select an Option:** [C] Continue to Holistic Analysis [X] Exit"
-## Menu Handling Logic:
-- IF C: Save optimization 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 [web search and subprocess analysis complete with optimization recommendations documented], will you then load and read fully `{nextStepFile}` to execute and begin holistic analysis phase.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- Intelligent assessment of web search necessity vs. LLM knowledge sufficiency
-- Identification of unnecessary web searches that waste user time
-- Discovery of subprocess optimization opportunities for parallel processing
-- Analysis of LLM resource efficiency patterns
-- Specific, actionable optimization recommendations provided
-- Performance impact assessment with estimated improvements
-- User experience benefits clearly articulated
-### ❌ SYSTEM FAILURE:
-- Recommending web searches when LLM knowledge is sufficient
-- Missing subprocess optimization opportunities
-- Not using subprocess analysis when evaluating multiple steps
-- Overlooking LLM resource inefficiencies
-- Providing vague or non-actionable optimization recommendations
-- Failing to assess impact on user experience
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.