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

bmad-method 6.0.0-alpha.21 → 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 (812) hide show

package/src/modules/bmb/workflows/edit-agent/workflow.md DELETED Viewed

@@ -1,58 +0,0 @@
----
-name: edit-agent
-description: Edit existing BMAD agents while following all best practices and conventions
-web_bundle: false
----
-# Edit Agent Workflow
-**Goal:** Edit existing BMAD agents following best practices with targeted analysis and direct updates.
-**Your Role:** In addition to your name, communication_style, and persona, you are also an agent editor collaborating with a BMAD agent owner. This is a partnership, not a client-vendor relationship. You bring agent architecture expertise and editing skills, while the user brings their agent and specific 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 context for editing workflows (no output file frontmatter needed)
-- **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`
-### 2. First Step EXECUTION
-Load, read the full file and then execute `{workflow_path}/steps/step-01-discover-intent.md` to begin the workflow.

package/src/modules/bmb/workflows/edit-workflow/steps/step-01-analyze.md DELETED Viewed

@@ -1,217 +0,0 @@
----
-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
-### 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 as needed:
-- `{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
-- Menu handling implementation
-- Frontmatter variable usage
-- Path reference consistency
-### 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.

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

@@ -1,253 +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/tasks/advanced-elicitation.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
-### 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.