npm - siesa-agents - Versions diffs - 2.1.78 → 2.1.80 - Mend

siesa-agents 2.1.78 → 2.1.80

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

package/bmad/bmb/workflows/edit-workflow/steps/step-02-discover.md DELETED Viewed

@@ -1,254 +0,0 @@
----
-name: 'step-02-discover'
-description: 'Discover improvement goals collaboratively'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/edit-workflow'
-# File References
-thisStepFile: '{workflow_path}/steps/step-02-discover.md'
-nextStepFile: '{workflow_path}/steps/step-03-improve.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/workflow-edit-{target_workflow_name}.md'
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
-# Template References
-goalsTemplate: '{workflow_path}/templates/improvement-goals.md'
----
-# Step 2: Discover Improvement Goals
-## STEP GOAL:
-To collaboratively discover what the user wants to improve and why, before diving into any edits.
-## 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 workflow editor and improvement specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You guide discovery with thoughtful questions
-- ✅ User brings their context, feedback, and goals
-### Step-Specific Rules:
-- 🎯 Focus ONLY on understanding improvement goals
-- 🚫 FORBIDDEN to suggest specific solutions yet
-- 💬 Ask open-ended questions to understand needs
-- 🚪 ORGANIZE improvements by priority and impact
-## EXECUTION PROTOCOLS:
-- 🎯 Guide collaborative discovery conversation
-- 💾 Document goals in {outputFile}
-- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
-- 🚫 FORBIDDEN to load next step until user selects 'C' and goals are documented
-## CONTEXT BOUNDARIES:
-- Analysis from step 1 is available and informs discovery
-- Focus areas identified in step 1 guide deeper exploration
-- Focus on WHAT to improve and WHY
-- Don't discuss HOW to improve yet
-- This is about detailed needs assessment, not solution design
-## DISCOVERY PROCESS:
-### 1. Understand Motivation
-Engage in collaborative discovery with open-ended questions:
-"What prompted you to want to edit this workflow?"
-Listen for:
-- User feedback they've received
-- Issues they've encountered
-- New requirements that emerged
-- Changes in user needs or context
-### 2. Explore User Experience
-Ask about how users interact with the workflow:
-"What feedback have you gotten from users running this workflow?"
-Probe for:
-- Confusing steps or unclear instructions
-- Points where users get stuck
-- Repetitive or tedious parts
-- Missing guidance or context
-- Friction in the user journey
-### 3. Assess Current Performance
-Discuss effectiveness:
-"Is the workflow achieving its intended outcome?"
-Explore:
-- Are users successful with this workflow?
-- What are the success/failure rates?
-- Where do most users drop off?
-- Are there quality issues with outputs?
-### 4. Identify Growth Opportunities
-Ask about future needs:
-"Are there new capabilities you want to add?"
-Consider:
-- New features or steps
-- Integration with other workflows
-- Expanded use cases
-- Enhanced flexibility
-### 5. Evaluate Instruction Style
-Discuss communication approach:
-"How is the instruction style working for your users?"
-Explore:
-- Is it too rigid or too loose?
-- Should certain steps be more adaptive?
-- Do some steps need more specificity?
-- Does the style match the workflow's purpose?
-### 6. Dive Deeper into Focus Areas
-Based on the focus areas identified in step 1, explore more deeply:
-#### For User Experience Issues
-"Let's explore the user experience issues you mentioned:
-- Which specific steps feel clunky or confusing?
-- At what points do users get stuck?
-- What kind of guidance would help them most?"
-#### For Functional Problems
-"Tell me more about the functional issues:
-- When do errors occur?
-- What specific functionality isn't working?
-- Are these consistent issues or intermittent?"
-#### For New Features
-"Let's detail the new features you want:
-- What should these features accomplish?
-- How should users interact with them?
-- Are there examples of similar workflows to reference?"
-#### For Compliance Issues
-"Let's understand the compliance concerns:
-- Which best practices need addressing?
-- Are there specific standards to meet?
-- What validation would be most valuable?"
-### 7. Organize Improvement Opportunities
-Based on their responses and your analysis, organize improvements:
-**CRITICAL Issues** (blocking successful runs):
-- Broken references or missing files
-- Unclear or confusing instructions
-- Missing essential functionality
-**IMPORTANT Improvements** (enhancing user experience):
-- Streamlining step flow
-- Better guidance and context
-- Improved error handling
-**NICE-TO-HAVE Enhancements** (for polish):
-- Additional validation
-- Better documentation
-- Performance optimizations
-### 8. Prioritize Collaboratively
-Work with the user to prioritize:
-"Looking at all these opportunities, which ones matter most to you right now?"
-Help them consider:
-- Impact on users
-- Effort to implement
-- Dependencies between improvements
-- Timeline constraints
-## CONTENT TO APPEND TO DOCUMENT:
-After discovery, append to {outputFile}:
-Load and append the content from {goalsTemplate}
-### 8. Present MENU OPTIONS
-Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu
-- User can chat or ask questions - always respond and then end with display again of the menu options
-- Use menu handling logic section below
-#### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Save goals to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-menu-options)
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN C is selected and goals are saved to document and frontmatter is updated, will you then load, read entire file, then execute {nextStepFile} to execute and begin collaborative improvement step.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- User improvement goals clearly understood
-- Issues and opportunities identified
-- Priorities established collaboratively
-- Goals documented in {outputFile}
-- User ready to proceed with improvements
-### ❌ SYSTEM FAILURE:
-- Skipping discovery dialogue
-- Making assumptions about user needs
-- Not documenting discovered goals
-- Rushing to solutions without understanding
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/bmad/bmb/workflows/edit-workflow/steps/step-03-improve.md DELETED Viewed

@@ -1,218 +0,0 @@
----
-name: 'step-03-improve'
-description: 'Facilitate collaborative improvements to the workflow'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/edit-workflow'
-# File References
-thisStepFile: '{workflow_path}/steps/step-03-improve.md'
-nextStepFile: '{workflow_path}/steps/step-04-validate.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/workflow-edit-{target_workflow_name}.md'
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
-# Template References
-improvementLogTemplate: '{workflow_path}/templates/improvement-log.md'
----
-# Step 3: Collaborative Improvement
-## STEP GOAL:
-To facilitate collaborative improvements to the workflow, working iteratively on each identified issue.
-## 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 workflow editor and improvement specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You guide improvements with explanations and options
-- ✅ User makes decisions and approves changes
-### Step-Specific Rules:
-- 🎯 Work on ONE improvement at a time
-- 🚫 FORBIDDEN to make changes without user approval
-- 💬 Explain the rationale for each proposed change
-- 🚪 ITERATE: improve, review, refine
-## EXECUTION PROTOCOLS:
-- 🎯 Facilitate improvements collaboratively and iteratively
-- 💾 Document all changes in improvement log
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
-- 🚫 FORBIDDEN to load next step until user selects 'C' and improvements are complete
-## CONTEXT BOUNDARIES:
-- Analysis and goals from previous steps guide improvements
-- Load workflow creation documentation as needed
-- Focus on improvements prioritized in step 2
-- This is about collaborative implementation, not solo editing
-## IMPROVEMENT PROCESS:
-### 1. Load Reference Materials
-Load documentation as needed for specific improvements:
-- `{project-root}/_bmad/bmb/docs/workflows/templates/step-template.md`
-- `{project-root}/_bmad/bmb/docs/workflows/templates/workflow-template.md`
-- `{project-root}/_bmad/bmb/docs/workflows/architecture.md`
-### 2. Address Each Improvement Iteratively
-For each prioritized improvement:
-#### A. Explain Current State
-Show the relevant section:
-"Here's how this step currently works:
-[Display current content]
-This can cause {{problem}} because {{reason}}."
-#### B. Propose Improvement
-Suggest specific changes:
-"Based on best practices, we could:
-{{proposedSolution}}
-This would help users by {{benefit}}."
-#### C. Collaborate on Approach
-Ask for input:
-"Does this approach address your need?"
-"Would you like to modify this suggestion?"
-"What concerns do you have about this change?"
-#### D. Get Explicit Approval
-"Should I apply this change?"
-#### E. Apply and Show Result
-Make the change and display:
-"Here's the updated version:
-[Display new content]
-Does this look right to you?"
-### 3. Common Improvement Patterns
-#### Step Flow Improvements
-- Merge redundant steps
-- Split complex steps
-- Reorder for better flow
-- Add missing transitions
-#### Instruction Style Refinement
-Load step-template.md for reference:
-- Convert prescriptive to intent-based for discovery steps
-- Add structure to vague instructions
-- Balance guidance with autonomy
-#### Variable Consistency Fixes
-- Identify all variable references
-- Ensure consistent naming (snake_case)
-- Verify variables are defined in workflow.md
-- Update all occurrences
-#### Menu System Updates
-- Standardize menu patterns
-- Ensure proper A/P/C options
-- Fix menu handling logic
-- Add Advanced Elicitation where useful
-#### Frontmatter Compliance
-- Add required fields to workflow.md
-- Ensure proper path variables
-- Include web_bundle configuration if needed
-- Remove unused fields
-#### Template Updates
-- Align template variables with step outputs
-- Improve variable naming
-- Add missing template sections
-- Test variable substitution
-### 4. Track All Changes
-For each improvement made, document:
-- What was changed
-- Why it was changed
-- Files modified
-- User approval
-## CONTENT TO APPEND TO DOCUMENT:
-After each improvement iteration, append to {outputFile}:
-Load and append content from {improvementLogTemplate}
-### 5. Present MENU OPTIONS
-Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu
-- User can chat or ask questions - always respond and then end with display again of the menu options
-- Use menu handling logic section below
-#### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Save improvement log to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN C is selected and all prioritized improvements are complete and documented, will you then load, read entire file, then execute {nextStepFile} to execute and begin validation step.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- All prioritized improvements addressed
-- User approved each change
-- Changes documented clearly
-- Workflow follows best practices
-- Improvement log updated
-### ❌ SYSTEM FAILURE:
-- Making changes without user approval
-- Not documenting changes
-- Skipping prioritized improvements
-- Breaking workflow functionality
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/bmad/bmb/workflows/edit-workflow/steps/step-04-validate.md DELETED Viewed

@@ -1,194 +0,0 @@
----
-name: 'step-04-validate'
-description: 'Validate improvements and prepare for completion'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmb/workflows/edit-workflow'
-# File References
-thisStepFile: '{workflow_path}/steps/step-04-validate.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/workflow-edit-{target_workflow_name}.md'
-nextStepFile: '{workflow_path}/steps/step-05-compliance-check.md'
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
-# Template References
-validationTemplate: '{workflow_path}/templates/validation-results.md'
-completionTemplate: '{workflow_path}/templates/completion-summary.md'
----
-# Step 4: Validation and Completion
-## STEP GOAL:
-To validate all improvements and prepare a completion summary of the workflow editing process.
-## MANDATORY EXECUTION RULES (READ FIRST):
-### Universal Rules:
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Always 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 improvement specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You ensure quality and completeness
-- ✅ User confirms final state
-### Step-Specific Rules:
-- 🎯 Focus ONLY on validation and completion
-- 🚫 FORBIDDEN to make additional edits at this stage
-- 💬 Explain validation results clearly
-- 🚪 PREPARE final summary and next steps
-## EXECUTION PROTOCOLS:
-- 🎯 Validate all changes systematically
-- 💾 Document validation results
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
-- 🚫 FORBIDDEN to load next step until user selects 'C' and validation is complete
-## CONTEXT BOUNDARIES:
-- All improvements from step 3 should be implemented
-- Focus on validation, not additional changes
-- Reference best practices for validation criteria
-- This completes the editing process
-## VALIDATION PROCESS:
-### 1. Comprehensive Validation Checks
-Validate the improved workflow systematically:
-#### File Structure Validation
-- [ ] All required files present
-- [ ] Directory structure correct
-- [ ] File names follow conventions
-- [ ] Path references resolve correctly
-#### Configuration Validation
-- [ ] workflow.md frontmatter complete
-- [ ] All variables properly formatted
-- [ ] Path variables use correct syntax
-- [ ] No hardcoded paths exist
-#### Step File Compliance
-- [ ] Each step follows template structure
-- [ ] Mandatory rules included
-- [ ] Menu handling implemented properly
-- [ ] Step numbering sequential
-- [ ] Step files reasonably sized (5-10KB)
-#### Cross-File Consistency
-- [ ] Variable names match across files
-- [ ] No orphaned references
-- [ ] Dependencies correctly defined
-- [ ] Template variables match outputs
-#### Best Practices Adherence
-- [ ] Collaborative dialogue implemented
-- [ ] Error handling included
-- [ ] Naming conventions followed
-- [ ] Instructions clear and specific
-### 2. Present Validation Results
-Load validationTemplate and document findings:
-- If issues found: Explain clearly and propose fixes
-- If all passes: Confirm success warmly
-### 3. Create Completion Summary
-Load completionTemplate and prepare:
-- Story of transformation
-- Key improvements made
-- Impact on users
-- Next steps for testing
-### 4. Guide Next Steps
-Based on changes made, suggest:
-- Testing the edited workflow
-- Running it with sample data
-- Getting user feedback
-- Additional refinements if needed
-### 5. Document Final State
-Update {outputFile} with:
-- Validation results
-- Completion summary
-- Change log summary
-- Recommendations
-## CONTENT TO APPEND TO DOCUMENT:
-After validation, append to {outputFile}:
-Load and append content from {validationTemplate}
-Then load and append content from {completionTemplate}
-## FINAL MENU OPTIONS
-Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
-### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu
-- User can chat or ask questions - always respond and then end with display again of the menu options
-- Use menu handling logic section below
-#### 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}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#final-menu-options)
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN C is selected and content is saved to {outputFile} with frontmatter updated, will you then load, read entire file, then execute {nextStepFile} to execute and begin compliance validation step.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- All improvements validated successfully
-- No critical issues remain
-- Completion summary provided
-- Next steps clearly outlined
-- User satisfied with results
-### ❌ SYSTEM FAILURE:
-- Skipping validation steps
-- Not documenting final state
-- Ending without user confirmation
-- Leaving issues unresolved
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.