npm - bmad-method - Versions diffs - 6.0.0-alpha.13 → 6.0.0-alpha.14 - Mend

bmad-method 6.0.0-alpha.13 → 6.0.0-alpha.14

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

package/src/modules/bmb/workflows/create-workflow/steps/step-06-external-tools.md DELETED Viewed

@@ -1,154 +0,0 @@
----
-name: 'step-06-external-tools'
-description: 'Configure MCP integrations and installation requirements'
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
-# File References
-thisStepFile: '{workflow_path}/steps/step-06-external-tools.md'
-nextStepFile: '{workflow_path}/steps/step-07-installation-guidance.md'
-workflowFile: '{workflow_path}/workflow.md'
-workflowPlanFile: '{output_folder}/workflow-plan-{new_workflow_name}.md'
-# Documentation References
-commonToolsCsv: '{project-root}/{bmad_folder}/bmb/docs/workflows/common-workflow-tools.csv'
----
-# Step 6: External Tools Configuration
-## STEP GOAL:
-Identify and configure MCP integrations and external tools that the workflow requires.
-## 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 integration specialist
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring expertise in MCP integrations and external tools
-## EXECUTION PROTOCOLS:
-- 🎯 Load external tools from CSV
-- 💾 Identify specific MCP needs for workflow
-- 📖 Document which tools require installation
-- 🚫 FORBIDDEN to proceed without confirming tool selections
-## SEQUENCE OF INSTRUCTIONS:
-### 1. Initialize External Tools Assessment
-"Configuring **External Tools and MCP Integrations**
-These tools extend workflow capabilities but typically require installation. Let's identify what your workflow actually needs."
-### 2. Present External Tools from CSV
-Load `{commonToolsCsv}` and filter for `propose='example'` and `type='mcp'`:
-"**Available External Tools:**
-**MCP Integrations (Require Installation):**
-- [List MCP tools from CSV with URLs and descriptions]
-**Example Workflows/Tasks:**
-- [List example workflows/tasks from CSV with descriptions]
-**Installation Note:** Tools marked with `requires_install=yes` will need setup steps."
-### 3. Identify Specific Tool Needs
-"**External Tool Requirements:**
-Based on your workflow goals, which external tools do you need?
-**Common MCP Needs:**
-- **Documentation Access:** Context-7 for current API docs
-- **Browser Automation:** Playwright for web interactions
-- **Git Operations:** Direct version control integration
-- **Database Access:** Multiple database connectivity
-- **Custom Tools:** Any domain-specific MCPs you need
-**Your Requirements:**
-1. What external data or APIs will your workflow access?
-2. Does your workflow need web browser automation?
-3. Will it interact with version control systems?
-4. Are database connections required?
-5. Any custom MCPs you plan to use?"
-### 4. Document External Tools Selection
-Append to {workflowPlanFile}:
-```markdown
-## External Tools Configuration
-### MCP Integrations
-**Selected Tools:** [list from CSV]
-**Purpose:** [how each MCP enhances workflow]
-**Integration Points:** [where external tools are essential]
-**Installation Required:** [yes/no, which tools]
-### Example Workflows/Tasks
-**Selected:** [list chosen workflows/tasks]
-**Purpose:** [how they enhance workflow capabilities]
-**Integration:** [where they fit in workflow flow]
-```
-### 5. Installation Assessment
-"**Installation Requirements Assessment:**
-**Tools Requiring Installation:** [list from CSV where requires_install=yes]
-**Installation Guidance Options:**
-1. Include detailed setup steps in workflow
-2. Provide user installation checklist
-3. Assume tools are pre-installed
-**Your Preference:** [ask user how to handle installation]"
-### 6. Menu Options
-Display: **Select an Option:** [C] Continue to Installation Guidance [M] Modify External Tools
-#### Menu Handling Logic:
-- IF C: Append external tools configuration to {workflowPlanFile}, update frontmatter, then load {nextStepFile}
-- IF M: Refine external tool requirements
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN C is selected and external tools are documented will you load {nextStepFile} to configure installation guidance.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- External tools presented from CSV with installation requirements
-- User's specific tool needs identified and documented
-- Installation requirements clearly marked
-- User understands which tools need setup
-### ❌ SYSTEM FAILURE:
-- Not filtering CSV for relevant tool types
-- Missing installation requirement information
-- Proceeding without confirming tool selections

package/src/modules/bmb/workflows/create-workflow/steps/step-07-installation-guidance.md DELETED Viewed

@@ -1,159 +0,0 @@
----
-name: 'step-07-installation-guidance'
-description: 'Configure installation guidance for tools that require setup'
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
-# File References
-thisStepFile: '{workflow_path}/steps/step-07-installation-guidance.md'
-nextStepFile: '{workflow_path}/steps/step-08-tools-summary.md'
-workflowFile: '{workflow_path}/workflow.md'
-workflowPlanFile: '{output_folder}/workflow-plan-{new_workflow_name}.md'
-# Documentation References
-commonToolsCsv: '{project-root}/{bmad_folder}/bmb/docs/workflows/common-workflow-tools.csv'
----
-# Step 7: Installation Guidance Configuration
-## STEP GOAL:
-Configure installation guidance for any selected tools that require setup, ensuring users can successfully prepare their environment.
-## 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 integration specialist
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring expertise in tool installation and setup procedures
-## EXECUTION PROTOCOLS:
-- 🎯 Identify tools requiring installation from CSV
-- 💾 Configure installation approach based on user preference
-- 📖 Generate or skip installation guidance as appropriate
-- 🚫 FORBIDDEN to proceed without confirming installation approach
-## SEQUENCE OF INSTRUCTIONS:
-### 1. Initialize Installation Guidance
-"Configuring **Installation Guidance**
-Let's ensure users can successfully set up any tools your workflow requires. This prevents runtime errors and improves user experience."
-### 2. Identify Installation Requirements
-Load `{commonToolsCsv}` and filter for selected tools with `requires_install=yes`:
-"**Installation Requirements:**
-**Tools Requiring Installation:**
-- [List selected tools from CSV where requires_install=yes]
-- [Include URLs from CSV for each tool]
-**No Installation Required:**
-- [List selected tools from CSV where requires_install=no]
-- All BMAD core tools, LLM features, and sidecar file memory"
-### 3. Installation Approach Options
-"**Installation Guidance Options:**
-Based on your selected tools, how should the workflow handle installation?
-1. **Include Installation Steps** - Add detailed setup instructions in early workflow step
-2. **User Instructions Only** - Provide guidance but don't embed in workflow
-3. **Assume Pre-Installed** - Skip installation guidance (advanced users)
-**Installation Prerequisites (if included):**
-- Node.js 18+ (for Node.js-based MCPs)
-- Python 3.8+ (for Python-based MCPs)
-- Git for cloning repositories
-- MCP-compatible AI client (Claude Desktop or similar)"
-### 4. Configure Installation Guidance
-If user chooses installation guidance:
-"**Installation Step Configuration:**
-For each tool requiring installation, the workflow will include:
-- Clone/download instructions using URL from CSV
-- Dependency installation commands
-- Configuration file setup
-- Server startup procedures
-- Claude Desktop configuration steps
-**Installation Checklist (if included):**
-- [ ] Download and install Claude Desktop
-- [ ] Clone MCP repositories
-- [ ] Install required dependencies
-- [ ] Configure MCP servers
-- [ ] Add to Claude configuration
-- [ ] Test connectivity
-- [ ] Verify functionality"
-### 5. Document Installation Configuration
-Append to {workflowPlanFile}:
-```markdown
-## Installation Guidance Configuration
-### Installation Approach
-**Selected Approach:** [detailed steps/user instructions/assume pre-installed]
-**Tools Requiring Installation:** [list with URLs]
-**Installation Step Placement:** [early in workflow, after setup]
-### Installation Content
-**Prerequisites:** [system requirements]
-**Setup Steps:** [commands and procedures]
-**Verification:** [testing procedures]
-**User Support:** [troubleshooting guidance]
-```
-### 6. Menu Options
-Display: **Select an Option:** [C] Continue to Tools Summary [M] Modify Installation Approach
-#### Menu Handling Logic:
-- IF C: Append installation configuration to {workflowPlanFile}, update frontmatter, then load {nextStepFile}
-- IF M: Refine installation approach
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN C is selected and installation guidance is documented will you load {nextStepFile} to complete tools configuration.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- Installation requirements clearly identified from CSV
-- Installation approach configured based on user preference
-- Documentation prepared for setup procedures
-- User understands how tools will be installed
-### ❌ SYSTEM FAILURE:
-- Missing installation requirement assessment
-- Not using URLs from CSV for installation guidance
-- Proceeding without confirming installation approach

package/src/modules/bmb/workflows/create-workflow/steps/step-08-tools-summary.md DELETED Viewed

@@ -1,167 +0,0 @@
----
-name: 'step-08-tools-summary'
-description: 'Summarize tools configuration and proceed to workflow design'
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
-# File References
-thisStepFile: '{workflow_path}/steps/step-08-tools-summary.md'
-nextStepFile: '{workflow_path}/steps/step-09-design.md'
-workflowFile: '{workflow_path}/workflow.md'
-workflowPlanFile: '{output_folder}/workflow-plan-{new_workflow_name}.md'
-# Documentation References
-commonToolsCsv: '{project-root}/{bmad_folder}/bmb/docs/workflows/common-workflow-tools.csv'
----
-# Step 8: Tools Configuration Summary
-## STEP GOAL:
-Summarize the complete tools configuration and confirm readiness to proceed to workflow design.
-## 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 integration specialist
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring expertise in tools integration and workflow optimization
-## EXECUTION PROTOCOLS:
-- 🎯 Compile complete tools configuration summary
-- 💾 Present final configuration for user confirmation
-- 📖 Update workflow plan with comprehensive summary
-- 🚫 FORBIDDEN to proceed to design without user confirmation
-## SEQUENCE OF INSTRUCTIONS:
-### 1. Initialize Tools Summary
-"**Tools Configuration Summary**
-Let's review your complete tools configuration before proceeding to workflow design. This ensures all integrations are properly planned."
-### 2. Present Complete Configuration
-Load all previous configurations from {workflowPlanFile} and CSV:
-"**Complete Tools Configuration:**
-**Core BMAD Tools:**
-- [List selected core tools with integration points]
-- [Load descriptions from CSV for confirmation]
-**LLM Tool Features:**
-- [List selected LLM features with integration points]
-- [Load descriptions from CSV for confirmation]
-**Tool-Memory:**
-- [Selected memory types with implementation details]
-- [Load descriptions from CSV for confirmation]
-**External Tools:**
-- [List selected MCP integrations with URLs]
-- [Load descriptions from CSV for confirmation]
-- [Mark which require installation]
-**Installation Guidance:**
-- [Approach selected and tools included]
-- [Setup steps configured as needed]
-**Integration Strategy:**
-- [How tools enhance rather than disrupt workflow]
-- [Checkpoint approaches and user choice points]
-- [Performance optimization opportunities]"
-### 3. Final Configuration Confirmation
-"**Final Configuration Review:**
-**Your workflow will include:**
-- **Total Tools:** [count of selected tools]
-- **Core Tools:** [number selected]
-- **External Tools:** [number selected]
-- **Installation Required:** [yes/no, which tools]
-**Key Integration Points:**
-- [Major phases where tools enhance workflow]
-- [User experience considerations]
-- [Performance optimizations]
-**Ready to proceed with this configuration?**"
-### 4. Update Workflow Plan with Final Summary
-Append to {workflowPlanFile}:
-```markdown
-## Final Tools Configuration Summary
-### Tools Inventory
-**Core BMAD Tools:** [count and list]
-**LLM Features:** [count and list]
-**Memory Implementation:** [type and use case]
-**External Tools:** [count and list with URLs]
-**Installation Required:** [tools and setup complexity]
-### Integration Strategy
-**User Experience:** [how tools enhance workflow]
-**Checkpoint Approach:** [when tools are offered]
-**Performance Optimization:** [efficiency improvements]
-**Installation Strategy:** [how users prepare environment]
-### Ready for Design
-All tools configured and ready for workflow design phase.
-```
-### 5. Menu Options
-Display: **Select an Option:** [C] Continue to Workflow Design [M] Modify Configuration
-#### Menu Handling Logic:
-- IF C: Save final summary, update frontmatter stepsCompleted: [3, 4, 5, 6, 7, 8], then load {nextStepFile}
-- IF M: Return to specific configuration step
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN C is selected and summary is saved will you load {nextStepFile} to begin workflow design phase.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- Complete tools configuration summarized clearly
-- All descriptions loaded from CSV (not duplicated)
-- User confirms configuration before proceeding
-- Frontmatter updated with completed steps
-- Ready to proceed to workflow design
-### ❌ SYSTEM FAILURE:
-- Not presenting complete configuration summary
-- Duplicating CSV content instead of referencing it
-- Proceeding to design without user confirmation
-- Not updating workflow plan with final summary

package/src/modules/bmb/workflows/create-workflow/steps/step-10-plan-review.md DELETED Viewed

@@ -1,215 +0,0 @@
----
-name: 'step-10-plan-review'
-description: 'Review the complete workflow plan before generating files'
-# Path Definitions
-workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
-# File References
-thisStepFile: '{workflow_path}/steps/step-10-plan-review.md'
-nextStepFile: '{workflow_path}/steps/step-11-build.md'
-workflowFile: '{workflow_path}/workflow.md'
-# Output files for workflow creation process
-workflowPlanFile: '{output_folder}/workflow-plan-{new_workflow_name}.md'
-targetWorkflowPath: '{custom_workflow_location}/{new_workflow_name}'
-# Task References
-advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
----
-# Step 4: Workflow Plan Review
-## STEP GOAL:
-To present the complete workflow plan for user review and approval before generating the actual workflow files.
-## 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
-### 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 present the plan clearly and answer questions
-- ✅ User provides approval or requests changes
-### Step-Specific Rules:
-- 🎯 Focus ONLY on reviewing the plan, not building yet
-- 🚫 FORBIDDEN to generate any workflow files in this step
-- 💬 Present the complete plan clearly and answer all questions
-- 🚪 GET explicit approval before proceeding to build
-## EXECUTION PROTOCOLS:
-- 🎯 Present the complete workflow plan for review
-- 💾 Update plan frontmatter with review status
-- 📖 Only proceed to build step with explicit user approval
-- 🚫 FORBIDDEN to skip review or proceed without consent
-## CONTEXT BOUNDARIES:
-- Requirements and design from previous steps are in the plan
-- Focus ONLY on review and approval
-- Don't modify the design significantly here
-- This is the final checkpoint before file generation
-## REVIEW REFERENCE MATERIALS:
-When reviewing, you may load for comparison:
-- Example workflow: `{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/workflow.md`
-- Step examples from same workflow's steps folder
-- Architecture guide: `{project-root}/{bmad_folder}/bmb/docs/workflows/architecture.md`
-## PLAN REVIEW PROCESS:
-### 1. Present the Complete Plan
-Read the entire {workflowPlanFile} and present it to the user:
-- Executive Summary
-- Requirements Analysis
-- Detailed Design
-- Implementation Plan
-- Target Location and file structure
-### 2. Analyze Plan for Gaps and Issues
-Perform systematic analysis of the loaded plan:
-**Logical Flow Check:**
-- Do requirements align with proposed solution?
-- Are tools appropriate for the workflow type?
-- Is step sequence logical and complete?
-- Are there missing transitions between steps?
-**Completeness Review:**
-- All requirements captured and addressed?
-- Design covers all user scenarios?
-- Implementation plan includes all necessary files?
-- Are there unclear or ambiguous specifications?
-**Architecture Validation:**
-- Follows BMAD step-file architecture?
-- Proper use of template patterns?
-- Menu flow is logical and complete?
-- Variable naming is consistent?
-**Issue Identification:**
-If gaps or issues found:
-- Clearly identify each issue
-- Propose specific solutions
-- Ask for user input on resolution approach
-### 3. Present Menu for Plan Approval
-Display: **Plan Review Complete - Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Build
-### 4. Address Questions and Concerns
-Ask for specific feedback:
-- Does this plan fully address your requirements?
-- Are there any missing aspects?
-- Would you like any changes to the design?
-- Are you satisfied with the proposed structure?
-### 5. Confirm or Revise
-Based on feedback:
-- If approved: Proceed to build step
-- If changes needed: Go back to design step with specific feedback
-- If major revisions: Consider going back to requirements step
-## REVIEW CHECKPOINTS:
-### Requirements Coverage
-- [ ] All user requirements addressed
-- [ ] Success criteria defined
-- [ ] Technical constraints considered
-- [ ] User interaction level appropriate
-### Design Quality
-- [ ] Step flow is logical
-- [ ] Instruction style chosen appropriately
-- [ ] Menu systems designed properly
-- [ ] Error handling included
-### Implementation Feasibility
-- [ ] File structure is clear
-- [ ] Target location confirmed
-- [ ] Templates identified correctly
-- [ ] Dependencies documented
-## PLAN APPROVAL:
-### Explicit Confirmation Required
-Before proceeding to build, get explicit confirmation:
-"Based on this plan, I will generate:
-- [List of files]
-  in [target location]"
-Ready to proceed when you are! Select your option below to build or modify the plan.
-### 6. Present MENU OPTIONS
-Display: **Review Complete - Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Build
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to build step with explicit 'C' selection AND approval
-- 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: AND user has approved the plan, update plan frontmatter, then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN C is selected AND user has explicitly approved the plan, will you then update the plan frontmatter and load, read entire file, then execute {nextStepFile} to execute and begin workflow file generation step.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- Complete plan presented clearly
-- All user questions answered
-- Feedback collected and documented
-- Explicit approval received (or revisions planned)
-- Plan ready for implementation
-### ❌ SYSTEM FAILURE:
-- Skipping the review presentation
-- Proceeding without explicit approval
-- Not answering user questions
-- Rushing through the review process
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.