siesa-agents 2.1.35 → 2.1.37

package/_bmad/bmb/workflows/create-workflow/steps/step-09-complete.md

@@ -0,0 +1,188 @@
+---
+name: 'step-09-complete'
+description: 'Final completion and wrap-up of workflow creation process'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/workflows/create-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-09-complete.md'
+workflowFile: '{workflow_path}/workflow.md'
+# Output files for workflow creation process
+targetWorkflowPath: '{bmb_creations_output_folder}/workflows/{new_workflow_name}'
+workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md'
+completionFile: '{targetWorkflowPath}/completion-summary-{new_workflow_name}.md'
+---
+
+# Step 9: Workflow Creation Complete
+
+## STEP GOAL:
+
+To complete the workflow creation process with a final summary, confirmation, and next steps for using the new workflow.
+
+## 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 architect and systems designer
+- ✅ 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 bring expertise in workflow deployment and usage guidance
+- ✅ User brings their specific workflow needs
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on completion and next steps
+- 🚫 FORBIDDEN to modify the generated workflow
+- 💬 Provide clear guidance on how to use the workflow
+- 🚫 This is the final step - no next step to load
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Present completion summary
+- 💾 Create final completion documentation
+- 📖 Update plan frontmatter with completion status
+- 🚫 This is the final step
+
+## CONTEXT BOUNDARIES:
+
+- All previous steps are complete
+- Workflow has been generated and reviewed
+- Focus ONLY on completion and next steps
+- This step concludes the create-workflow process
+
+## COMPLETION PROCESS:
+
+### 1. Initialize Completion
+
+"**Workflow Creation Complete!**
+
+Congratulations! We've successfully created your new workflow. Let's finalize everything and ensure you have everything you need to start using it."
+
+### 2. Final Summary
+
+Present a complete summary of what was created:
+
+**Workflow Created:** {new_workflow_name}
+**Location:** {targetWorkflowPath}
+**Files Generated:** [list from build step]
+
+### 3. Create Completion Summary
+
+Create {completionFile} with:
+
+```markdown
+---
+workflowName: { new_workflow_name }
+creationDate: [current date]
+module: [module from plan]
+status: COMPLETE
+stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9]
+---
+
+# Workflow Creation Summary
+
+## Workflow Information
+
+- **Name:** {new_workflow_name}
+- **Module:** [module]
+- **Created:** [date]
+- **Location:** {targetWorkflowPath}
+
+## Generated Files
+
+[List all files created]
+
+## Quick Start Guide
+
+[How to run the new workflow]
+
+## Next Steps
+
+[Post-creation recommendations]
+```
+
+### 4. Usage Guidance
+
+Provide clear instructions on how to use the new workflow:
+
+**How to Use Your New Workflow:**
+
+1. **Running the Workflow:**
+   - [Instructions based on workflow type]
+   - [Initial setup if needed]
+
+2. **Common Use Cases:**
+   - [Typical scenarios for using the workflow]
+   - [Expected inputs and outputs]
+
+3. **Tips for Success:**
+   - [Best practices for this specific workflow]
+   - [Common pitfalls to avoid]
+
+### 5. Post-Creation Recommendations
+
+"**Next Steps:**
+
+1. **Test the Workflow:** Run it with sample data to ensure it works as expected
+2. **Customize if Needed:** You can modify the workflow based on your specific needs
+3. **Share with Team:** If others will use this workflow, provide them with the location and instructions
+4. **Monitor Usage:** Keep track of how well the workflow meets your needs"
+
+### 6. Final Confirmation
+
+"**Is there anything else you need help with regarding your new workflow?**
+
+- I can help you test it
+- We can make adjustments if needed
+- I can help you create documentation for users
+- Or any other support you need"
+
+### 7. Update Final Status
+
+Update {workflowPlanFile} frontmatter:
+
+- Set status to COMPLETE
+- Set completion date
+- Add stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9]
+
+## MENU OPTIONS
+
+Display: **Workflow Creation Complete!** [T] Test Workflow [M] Make Adjustments [D] Get Help
+
+### Menu Handling Logic:
+
+- IF T: Offer to run the newly created workflow with sample data
+- IF M: Offer to make specific adjustments to the workflow
+- IF D: Provide additional help and resources
+- IF Any other: Respond to user needs
+
+## CRITICAL STEP COMPLETION NOTE
+
+This is the final step. When the user is satisfied, the workflow creation process is complete.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Workflow fully created and reviewed
+- Completion summary generated
+- User understands how to use the workflow
+- All documentation is in place
+
+### ❌ SYSTEM FAILURE:
+
+- Not providing clear usage instructions
+- Not creating completion summary
+- Leaving user without next steps
+
+**Master Rule:** Ensure the user has everything needed to successfully use their new workflow.

package/_bmad/bmb/workflows/create-workflow/workflow.md

@@ -0,0 +1,59 @@
+---
+name: create-workflow
+description: Create structured standalone workflows using markdown-based step architecture
+web_bundle: true
+---
+
+# Create Workflow
+
+**Goal:** Create structured, repeatable standalone workflows through collaborative conversation and step-by-step guidance.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a workflow architect and systems designer collaborating with a workflow creator. This is a partnership, not a client-vendor relationship. You bring expertise in workflow design patterns, step architecture, and collaborative facilitation, while the user brings their domain knowledge and specific workflow requirements. 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+---
+
+## 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`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.

package/_bmad/bmb/workflows/edit-workflow/steps/step-01-analyze.md

@@ -0,0 +1,217 @@
+---
+name: 'step-01-analyze'
+description: 'Load and deeply understand the target workflow'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmb/workflows/edit-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-analyze.md'
+nextStepFile: '{workflow_path}/steps/step-02-discover.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/workflow-edit-{target_workflow_name}.md'
+
+# Template References
+analysisTemplate: '{workflow_path}/templates/workflow-analysis.md'
+---
+
+# Step 1: Workflow Analysis
+
+## STEP GOAL:
+
+To load and deeply understand the target workflow, including its structure, purpose, and potential improvement areas.
+
+## 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 bring workflow analysis expertise and best practices knowledge
+- ✅ User brings their workflow context and improvement needs
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on analysis and understanding, not editing yet
+- 🚫 FORBIDDEN to suggest specific changes in this step
+- 💬 Ask questions to understand the workflow path
+- 🚪 DETECT if this is a new format (standalone) or old format workflow
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Analyze workflow thoroughly and systematically
+- 💾 Document analysis findings in {outputFile}
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until user selects 'C' and analysis is complete
+
+## CONTEXT BOUNDARIES:
+
+- User provides the workflow path to analyze
+- Load all workflow documentation for reference
+- Focus on understanding current state, not improvements yet
+- This is about discovery and analysis
+
+## WORKFLOW ANALYSIS PROCESS:
+
+### 1. Get Workflow Information
+
+Ask the user:
+"I need two pieces of information to help you edit your workflow effectively:
+
+1. **What is the path to the workflow you want to edit?**
+   - Path to workflow.md file (new format)
+   - Path to workflow.yaml file (legacy format)
+   - Path to the workflow directory
+   - Module and workflow name (e.g., 'bmb/workflows/create-workflow')
+
+2. **What do you want to edit or improve in this workflow?**
+   - Briefly describe what you want to achieve
+   - Are there specific issues you've encountered?
+   - Any user feedback you've received?
+   - New features you want to add?
+
+This will help me focus my analysis on what matters most to you."
+
+### 2. Load Workflow Files
+
+Load the target workflow completely:
+
+- workflow.md (or workflow.yaml for old format)
+- steps/ directory with all step files
+- templates/ directory (if exists)
+- data/ directory (if exists)
+- Any additional referenced files
+
+### 3. Determine Workflow Format
+
+Detect if this is:
+
+- **New standalone format**: workflow.md with steps/ subdirectory
+- **Legacy XML format**: workflow.yaml with instructions.md
+- **Mixed format**: Partial migration
+
+### 4. Focused Analysis
+
+Analyze the workflow with attention to the user's stated goals:
+
+#### Initial Goal-Focused Analysis
+
+Based on what the user wants to edit:
+
+- If **user experience issues**: Focus on step clarity, menu patterns, instruction style
+- If **functional problems**: Focus on broken references, missing files, logic errors
+- If **new features**: Focus on integration points, extensibility, structure
+- If **compliance issues**: Focus on best practices, standards, validation
+
+#### Structure Analysis
+
+- Identify workflow type (document, action, interactive, autonomous, meta)
+- Count and examine all steps
+- Map out step flow and dependencies
+- Check for proper frontmatter in all files
+
+#### Content Analysis
+
+- Understand purpose and user journey
+- Evaluate instruction style (intent-based vs prescriptive)
+- Review menu patterns and user interaction points
+- Check variable consistency across files
+
+#### Compliance Analysis
+
+Load reference documentation to understand what ideal workflow files sound be when doing the review:
+
+- `{project-root}/_bmad/bmb/docs/workflows/architecture.md`
+- `{project-root}/_bmad/bmb/docs/workflows/templates/step-template.md`
+- `{project-root}/_bmad/bmb/docs/workflows/templates/workflow-template.md`
+
+Check against best practices:
+
+- Step file size and structure (each step file 80-250 lines)
+- Menu handling implementation (every menu item has a handler, and continue will only proceed after writes to output if applicable have completed)
+- Frontmatter variable usage - no unused variables in the specific step front matter, and all files referenced in the file are done through a variable in the front matter
+
+### 5. Present Analysis Findings
+
+Share your analysis with the user in a conversational way:
+
+- What this workflow accomplishes (purpose and value)
+- How it's structured (type, steps, interaction pattern)
+- Format type (new standalone vs legacy)
+- Initial findings related to their stated goals
+- Potential issues or opportunities in their focus area
+
+### 6. Confirm Understanding and Refine Focus
+
+Ask:
+"Based on your goal to {{userGoal}}, I've noticed {{initialFindings}}.
+Does this align with what you were expecting? Are there other areas you'd like me to focus on in my analysis?"
+
+This allows the user to:
+
+- Confirm you're on the right track
+- Add or modify focus areas
+- Clarify any misunderstandings before proceeding
+
+### 7. Final Confirmation
+
+Ask: "Does this analysis cover what you need to move forward with editing?"
+
+## CONTENT TO APPEND TO DOCUMENT:
+
+After analysis, append to {outputFile}:
+
+Load and append the content from {analysisTemplate}
+
+### 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 analysis 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](#7-present-menu-options)
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and analysis is saved to document and frontmatter is updated, will you then load, read entire file, then execute {nextStepFile} to execute and begin improvement discovery step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Target workflow loaded completely
+- Analysis performed systematically
+- Findings documented clearly
+- User confirms understanding
+- Analysis saved to {outputFile}
+
+### ❌ SYSTEM FAILURE:
+
+- Skipping analysis steps
+- Not loading all workflow files
+- Making suggestions without understanding
+- Not saving analysis findings
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.