bmad-method 6.0.0-alpha.2 → 6.0.0-alpha.20

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

@@ -0,0 +1,187 @@
+---
+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
+
+### 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/src/modules/bmb/workflows/create-workflow/workflow.md

@@ -0,0 +1,58 @@
+---
+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
+
+---
+
+## 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/src/modules/bmb/workflows/edit-agent/steps/step-01-discover-intent.md

@@ -0,0 +1,134 @@
+---
+name: 'step-01-discover-intent'
+description: 'Get agent path and user editing goals'
+
+# Path Definitions
+workflow_path: '{project-root}/bmb/workflows/create-agent/edit-agent'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-discover-intent.md'
+nextStepFile: '{workflow_path}/steps/step-02-analyze-agent.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 1: Discover Edit Intent
+
+## STEP GOAL:
+
+Get the agent path to edit and understand what the user wants to accomplish before proceeding to targeted 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 an agent editor who helps users improve their BMAD agents
+- ✅ If you already have a name, communication_style and identity, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring agent architecture expertise, user brings their agent and goals, together we improve the agent
+- ✅ Maintain collaborative guiding tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on getting agent path and understanding user goals
+- 🚫 FORBIDDEN to load any documentation or analyze the agent yet
+- 💬 Approach: Direct questions to understand what needs fixing
+- 🚫 FORBIDDEN to make suggestions or propose solutions
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Ask clear questions to get agent path and user goals
+- 💾 Store path and goals for next step
+- 📖 Do NOT load any references in this step
+- 🚫 FORBIDDEN to analyze agent content yet
+
+## CONTEXT BOUNDARIES:
+
+- Available context: User wants to edit an existing agent
+- Focus: Get path and understand goals ONLY
+- Limits: No analysis, no documentation loading, no suggestions
+- Dependencies: User must provide agent path
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Get Agent Path
+
+Ask the user:
+"What agent do you want to edit? Please provide the path to:
+
+- A .agent.yaml file (Simple agent)
+- A folder containing .agent.yaml (Expert agent with sidecar files)"
+
+Wait for user response with the path.
+
+### 2. Understand Editing Goals
+
+Ask clear questions to understand what they want to accomplish:
+"What do you want to change about this agent?"
+
+Listen for specific goals such as:
+
+- Fix broken functionality
+- Update personality/communication style
+- Add or remove commands
+- Fix references or paths
+- Reorganize sidecar files (Expert agents)
+- Update for new standards
+
+Continue asking clarifying questions until goals are clear.
+
+### 3. Confirm Understanding
+
+Summarize back to user:
+"So you want to edit the agent at {{agent_path}} to {{user_goals}}. Is that correct?"
+
+### 4. Present MENU OPTIONS
+
+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: Load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then redisplay menu options
+
+#### 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
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [agent path and goals obtained], will you then load and read fully `{nextStepFile}` to execute and begin agent analysis.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Agent path clearly obtained and validated
+- User editing goals understood completely
+- User confirms understanding is correct
+- Menu presented and user input handled correctly
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding without agent path
+- Making suggestions or analyzing agent
+- Loading documentation in this step
+- Not confirming user goals clearly
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmb/workflows/edit-agent/steps/step-02-analyze-agent.md

@@ -0,0 +1,202 @@
+---
+name: 'step-02-analyze-agent'
+description: 'Load agent and relevant documentation for analysis'
+
+# Path Definitions
+workflow_path: '{project-root}/bmb/workflows/create-agent/edit-agent'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-02-analyze-agent.md'
+nextStepFile: '{workflow_path}/steps/step-03-propose-changes.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+
+# Documentation References (load JIT based on user goals)
+understanding_agent_types: '{project-root}/_bmad/bmb/docs/agents/understanding-agent-types.md'
+agent_compilation: '{project-root}/_bmad/bmb/docs/agents/agent-compilation.md'
+simple_architecture: '{project-root}/_bmad/bmb/docs/agents/simple-agent-architecture.md'
+expert_architecture: '{project-root}/_bmad/bmb/docs/agents/expert-agent-architecture.md'
+module_architecture: '{project-root}/_bmad/bmb/docs/agents/module-agent-architecture.md'
+menu_patterns: '{project-root}/_bmad/bmb/docs/agents/agent-menu-patterns.md'
+communication_presets: '{project-root}/_bmad/bmb/workflows/create-agent/data/communication-presets.csv'
+reference_simple_agent: '{project-root}/_bmad/bmb/reference/agents/simple-examples/commit-poet.agent.yaml'
+reference_expert_agent: '{project-root}/_bmad/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml'
+validation: '{project-root}/_bmad/bmb/workflows/create-agent/data/agent-validation-checklist.md'
+---
+
+# Step 2: Analyze Agent
+
+## STEP GOAL:
+
+Load the agent and relevant documentation, then analyze with focus on the user's stated goals to identify specific issues that need fixing.
+
+## 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 an agent editor with deep knowledge of BMAD agent architecture
+- ✅ If you already have a name, communication_style and identity, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring agent architecture expertise, user brings their agent and goals, together we identify specific improvements
+- ✅ Maintain analytical yet supportive tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus analysis ONLY on user's stated goals from step 1
+- 🚫 FORBIDDEN to load documentation not relevant to user goals
+- 💬 Approach: Load documentation JIT when needed for specific analysis
+- 🚫 FORBIDDEN to propose solutions yet (analysis only)
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load agent file from path provided in step 1
+- 💾 Load documentation JIT based on user goals
+- 📖 Always "Load and read fully" when accessing documentation
+- 🚫 FORBIDDEN to make changes in this step (analysis only)
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Agent path and user goals from step 1
+- Focus: Analyze agent in context of user goals
+- Limits: Only load documentation relevant to stated goals
+- Dependencies: Must have agent path and clear user goals
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Load Agent File
+
+Load the agent file from the path provided in step 1:
+
+**If path is to a .agent.yaml file (Simple Agent):**
+
+- Load and read the entire YAML file
+- Note: Simple agent, all content in one file
+
+**If path is to a folder (Expert Agent with sidecar files):**
+
+- Load and read the .agent.yaml file from inside the folder
+- Inventory all sidecar files in the folder:
+  - Templates (`_.md`, `_.txt`)
+  - Documentation files
+  - Knowledge base files (`_.csv`, `_.json`, `*.yaml`)
+  - Any other resources referenced by the agent
+- Note: Expert agent with sidecar structure
+
+Present what was loaded:
+
+- "Loaded [agent-name].agent.yaml"
+- If Expert: "Plus X sidecar files: [list them]"
+
+### 2. Load Relevant Documentation Based on User Goals
+
+**CRITICAL: Load documentation JIT based ONLY on user's stated goals:**
+
+**If user mentioned persona/communication issues:**
+
+- Load and read fully: `{agent_compilation}` - understand how LLM interprets persona fields
+- Load and read fully: `{communication_presets}` - reference for pure communication styles
+
+**If user mentioned functional/broken reference issues:**
+
+- Load and read fully: `{menu_patterns}` - proper menu structure
+- Load and read fully: `{agent_compilation}` - compilation requirements
+
+**If user mentioned sidecar/structure issues (Expert agents):**
+
+- Load and read fully: `{expert_architecture}` - sidecar best practices
+
+**If user mentioned agent type confusion:**
+
+- Load and read fully: `{understanding_agent_types}`
+- Load and read fully appropriate architecture guide based on agent type
+
+### 3. Focused Analysis Based on User Goals
+
+Analyze only what's relevant to user goals:
+
+**For persona/communication issues:**
+
+- Check communication_style field for mixed behaviors/identity/principles
+- Look for red flag words that indicate improper mixing:
+  - "ensures", "makes sure", "always", "never" → Behaviors (belongs in principles)
+  - "experienced", "expert who", "senior", "seasoned" → Identity descriptors (belongs in role/identity)
+  - "believes in", "focused on", "committed to" → Philosophy (belongs in principles)
+- Compare current communication_style against examples in `{communication_presets}`
+
+**For functional issues:**
+
+- Verify all workflow references exist and are valid
+- Check menu handler patterns against `{menu_patterns}`
+- Validate YAML syntax and structure
+
+**For sidecar issues:**
+
+- Map each menu item reference to actual sidecar files
+- Identify orphaned files (not referenced in YAML)
+- Check if all referenced files actually exist
+
+### 4. Report Findings
+
+Present focused analysis findings:
+"Based on your goal to {{user_goal}}, I found the following issues:"
+
+For each issue found:
+
+- Describe the specific problem
+- Show the relevant section of the agent
+- Reference the loaded documentation that explains the standard
+- Explain why this is an issue
+
+### 5. Present MENU OPTIONS
+
+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: Load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then redisplay menu options
+
+#### 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
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [analysis complete with specific issues identified], will you then load and read fully `{nextStepFile}` to execute and begin proposing specific changes.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Agent file loaded completely with proper type detection
+- Relevant documentation loaded JIT based on user goals
+- Analysis focused only on user's stated issues
+- Specific problems identified with documentation references
+- User understands what needs fixing and why
+- Menu presented and user input handled correctly
+
+### ❌ SYSTEM FAILURE:
+
+- Loading documentation not relevant to user goals
+- Proposing solutions instead of analyzing
+- Missing critical issues related to user goals
+- Not following "load and read fully" instruction
+- Making changes to agent files
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.