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

package/src/modules/bmb/workflows/create-workflow/steps/step-01-init.md

@@ -0,0 +1,168 @@
+---
+name: 'step-01-init'
+description: 'Initialize workflow creation session by detecting continuation state and setting up project'
+
+# Path Definitions
+workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-init.md'
+nextStepFile: '{workflow_path}/steps/step-02-gather.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'
+
+# Template References
+projectInfoTemplate: '{workflow_path}/templates/project-info.md'
+workflowPlanTemplate: '{workflow_path}/templates/workflow-plan.md'
+---
+
+# Step 1: Workflow Creation Initialization
+
+## STEP GOAL:
+
+To initialize the workflow creation process by detecting continuation state, understanding project context, and preparing for collaborative 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
+- 🔄 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 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 workflow design expertise, user brings their specific requirements
+- ✅ Together we will create a structured, repeatable workflow
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on initialization and project understanding
+- 🚫 FORBIDDEN to start designing workflow steps in this step
+- 💬 Ask questions conversationally to understand context
+- 🚪 DETECT existing workflow state and handle continuation properly
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show analysis before taking any action
+- 💾 Initialize document and update frontmatter
+- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until initialization is complete
+
+## CONTEXT BOUNDARIES:
+
+- Variables from workflow.md are available in memory
+- Previous context = what's in output document + frontmatter
+- Don't assume knowledge from other steps
+- Input discovery happens in this step
+
+## INITIALIZATION SEQUENCE:
+
+### 1. Check for Existing Workflow Creation
+
+First, check if there's already a workflow folder with the proposed name:
+
+- Look for folder at `{custom_workflow_location}/{new_workflow_name}/`
+- If exists, check if it contains a workflow.md file
+- If not exists, this is a fresh workflow creation session
+
+### 2. Handle Continuation (If Workflow Exists)
+
+If the workflow folder exists and has been worked on:
+
+- **STOP here** and continue with step 4 (Welcome Back)
+- Do not proceed with fresh initialization
+- Let step 4 handle the continuation logic
+
+### 3. Handle Completed Workflow
+
+If the workflow folder exists AND is complete:
+
+- Ask user: "I found an existing workflow '{new_workflow_name}' from [date]. Would you like to:
+  1. Create a new workflow with a different name
+  2. Review or modify the existing workflow"
+- If option 1: Get a new workflow name
+- If option 2: Load step 5 (Review)
+
+### 4. Fresh Workflow Setup (If No Workflow)
+
+#### A. Project Discovery
+
+Welcome the user and understand their needs:
+"Welcome! I'm excited to help you create a new workflow. Let's start by understanding what you want to build."
+
+Ask conversationally:
+
+- What type of workflow are you looking to create?
+- What problem will this workflow solve?
+- Who will use this workflow?
+- What module will it belong to (bmb, bmm, cis, custom, stand-alone)?
+- What would you like to name this workflow folder? (kebab-case, e.g., "user-story-generator")
+
+#### B. Create Workflow Plan Document
+
+Create the workflow plan document at `{workflowPlanFile}` using the workflow plan template `{workflowPlanTemplate}`.
+Initialize frontmatter with:
+
+```yaml
+---
+workflowName: ''
+targetModule: ''
+workflowType: ''
+flowPattern: ''
+date: [current date]
+user_name: { user_name }
+stepsCompleted: [1]
+lastStep: 'init'
+---
+```
+
+This plan will capture all requirements and design details before building the actual workflow.
+
+### 5. Welcome Message
+
+"Great! I'm ready to help you create a structured workflow using our step-based architecture. We'll work together to design a workflow that's collaborative, maintainable, and follows best practices."
+
+### 6. Present MENU OPTIONS
+
+Display: **Proceeding to requirements gathering...**
+
+#### EXECUTION RULES:
+
+- This is an initialization step with no user choices
+- Proceed directly to next step after setup
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- After setup completion, immediately load, read entire file, then execute `{workflow_path}/step-02-gather.md` to begin requirements gathering
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Workflow name confirmed and validated
+- Target folder location determined
+- User welcomed and project context understood
+- Ready to proceed to step 2
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding with step 2 without workflow name
+- Not checking for existing workflow folders
+- Not determining target location properly
+- Skipping welcome message
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmb/workflows/create-workflow/steps/step-02-gather.md

@@ -0,0 +1,233 @@
+---
+name: 'step-02-gather'
+description: 'Gather comprehensive requirements for the workflow being created'
+
+# Path Definitions
+workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-02-gather.md'
+nextStepFile: '{workflow_path}/steps/step-03-tools-overview.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'
+
+# Template References
+requirementsTemplate: '{workflow_path}/templates/requirements-section.md'
+---
+
+# Step 2: Requirements Gathering
+
+## STEP GOAL:
+
+To gather comprehensive requirements through collaborative conversation that will inform the design of a structured workflow tailored to the user's needs and use case.
+
+## 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 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 workflow design expertise and best practices
+- ✅ User brings their domain knowledge and specific requirements
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on collecting requirements and understanding needs
+- 🚫 FORBIDDEN to propose workflow solutions or step designs in this step
+- 💬 Ask questions conversationally, not like a form
+- 🚫 DO NOT skip any requirement area - each affects workflow design
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Engage in natural conversation to gather requirements
+- 💾 Store all requirements information for workflow design
+- 📖 Proceed to next step with 'C' selection
+- 🚫 FORBIDDEN to load next step until user selects 'C'
+
+## CONTEXT BOUNDARIES:
+
+- Workflow name and target location from initialization
+- Focus ONLY on collecting requirements and understanding needs
+- Don't provide workflow designs in this step
+- This is about understanding, not designing
+
+## REQUIREMENTS GATHERING PROCESS:
+
+### 1. Workflow Purpose and Scope
+
+Explore through conversation:
+
+- What specific problem will this workflow solve?
+- Who is the primary user of this workflow?
+- What is the main outcome or deliverable?
+
+### 2. Workflow Type Classification
+
+Help determine the workflow type:
+
+- **Document Workflow**: Generates documents (PRDs, specs, plans)
+- **Action Workflow**: Performs actions (refactoring, tools orchestration)
+- **Interactive Workflow**: Guided sessions (brainstorming, coaching, training, practice)
+- **Autonomous Workflow**: Runs without human input (batch processing, multi-step tasks)
+- **Meta-Workflow**: Coordinates other workflows
+
+### 3. Workflow Flow and Step Structure
+
+Let's load some examples to help you decide the workflow pattern:
+
+Load and reference the Meal Prep & Nutrition Plan workflow as an example:
+
+```
+Read: {project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/workflow.md
+```
+
+This shows a linear workflow structure. Now let's explore your desired pattern:
+
+- Should this be a linear workflow (step 1 → step 2 → step 3 → finish)?
+- Or should it have loops/repeats (e.g., keep generating items until user says done)?
+- Are there branching points based on user choices?
+- Should some steps be optional?
+- How many logical phases does this workflow need? (e.g., Gather → Design → Validate → Generate)
+
+**Based on our reference examples:**
+
+- **Linear**: Like Meal Prep Plan (Init → Profile → Assessment → Strategy → Shopping → Prep)
+  - See: `{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/`
+- **Looping**: User Story Generator (Generate → Review → Refine → Generate more... until done)
+- **Branching**: Architecture Decision (Analyze → Choose pattern → Implement based on choice)
+- **Iterative**: Document Review (Load → Analyze → Suggest changes → Implement → Repeat until approved)
+
+### 4. User Interaction Style
+
+Understand the desired interaction level:
+
+- How much user input is needed during execution?
+- Should it be highly collaborative or mostly autonomous?
+- Are there specific decision points where user must choose?
+- Should the workflow adapt to user responses?
+
+### 5. Instruction Style (Intent-Based vs Prescriptive)
+
+Determine how the AI should execute in this workflow:
+
+**Intent-Based (Recommended for most workflows)**:
+
+- Steps describe goals and principles, letting the AI adapt conversation naturally
+- More flexible, conversational, responsive to user context
+- Example: "Guide user to define their requirements through open-ended discussion"
+
+**Prescriptive**:
+
+- Steps provide exact instructions and specific text to use
+- More controlled, predictable, consistent across runs
+- Example: "Ask: 'What is your primary goal? Choose from: A) Growth B) Efficiency C) Quality'"
+
+Which style does this workflow need, or should it be a mix of both?
+
+### 6. Input Requirements
+
+Identify what the workflow needs:
+
+- What documents or data does the workflow need to start?
+- Are there prerequisites or dependencies?
+- Will users need to provide specific information?
+- Are there optional inputs that enhance the workflow?
+
+### 7. Output Specifications
+
+Define what the workflow produces:
+
+- What is the primary output (document, action, decision)?
+- Are there intermediate outputs or checkpoints?
+- Should outputs be saved automatically?
+- What format should outputs be in?
+
+### 8. Target Location and Module Configuration
+
+Determine where the workflow will be created:
+
+- For bmb module: Workflows go to `{custom_workflow_location}` (defaults to `{bmad_folder}/custom/src/workflows`)
+- For other modules: Check their install-config.yaml for custom workflow locations
+- Confirm the exact folder path where the workflow will be created
+- Ensure the folder name doesn't conflict with existing workflows
+
+### 9. Technical Constraints
+
+Discuss technical requirements:
+
+- Any specific tools or dependencies needed?
+- Does it need to integrate with other systems?
+- Any performance considerations?
+- Should it be standalone or callable by other workflows?
+
+### 10. Success Criteria
+
+Define what makes the workflow successful:
+
+- How will you know the workflow achieved its goal?
+- What are the quality criteria for outputs?
+- Are there measurable outcomes?
+- What would make a user satisfied with the result?
+
+## STORE REQUIREMENTS:
+
+After collecting all requirements, append them to {workflowPlanFile} using {requirementsTemplate}:
+
+This information will be used in the design phase to create the workflow structure.
+
+### 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: Append requirements to {workflowPlanFile}, update frontmatter, 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 requirements are stored, will you then load, read entire file, then execute {nextStepFile} to execute and begin workflow structure design step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Requirements collected through conversation (not interrogation)
+- All workflow aspects documented
+- Requirements stored using template
+- Menu presented and user input handled correctly
+
+### ❌ SYSTEM FAILURE:
+
+- Generating workflow designs without requirements
+- Skipping requirement areas
+- Proceeding to next step without 'C' selection
+- Not storing requirements properly
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmb/workflows/create-workflow/steps/step-03-tools-overview.md

@@ -0,0 +1,127 @@
+---
+name: 'step-03-tools-overview'
+description: 'Present available tools from CSV and gather initial user requirements'
+
+# Path Definitions
+workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-tools-overview.md'
+nextStepFile: '{workflow_path}/steps/step-04-core-tools.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 3: Tools Overview
+
+## STEP GOAL:
+
+Load and present available tools from the CSV, then gather the user's general tool requirements for their 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 integration specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring expertise in BMAD tools and workflow optimization
+- ✅ User brings their workflow requirements
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load CSV and present tools dynamically
+- 💾 Gather user's general tool requirements
+- 📖 Document requirements in workflow plan
+- 🚫 FORBIDDEN to proceed without user input
+
+## SEQUENCE OF INSTRUCTIONS:
+
+### 1. Initialize Tools Discussion
+
+"Beginning **Tools Integration and Configuration**
+
+Based on your workflow requirements, I'll help identify the best tools and integrations. Let me first load the available tools from our reference."
+
+### 2. Load and Present Available Tools
+
+Load `{commonToolsCsv}` and present tools organized by type:
+
+"**Available BMAD Tools and Integrations:**
+
+**Always Available (Recommended for Most Workflows):**
+
+- [List tools from CSV where propose='always', organized by type]
+
+**Example Tools (Available When Needed):**
+
+- [List tools from CSV where propose='example', organized by type]
+
+\*\*Tools requiring installation will be noted."
+
+### 3. Gather Initial Requirements
+
+"**Your Tool Requirements:**
+
+Based on your workflow type and goals, what tools do you anticipate needing?
+
+1. **Core BMAD Tools:** Do you want collaborative idea generation, critical evaluation, or brainstorming capabilities?
+2. **LLM Features:** Will you need web access, file management, sub-agents, or parallel processing?
+3. **Memory:** Does your workflow need persistent state across sessions?
+4. **External Tools:** Will you need MCP integrations like documentation access, browser automation, or database connections?
+
+**Initial Tool Preferences:** [gather user's general requirements]"
+
+### 4. Document Requirements
+
+Append to {workflowPlanFile}:
+
+```markdown
+## Tool Requirements Summary
+
+**Initial Tool Preferences:**
+
+- Core BMAD Tools: [user selections]
+- LLM Features: [user selections]
+- Memory Requirements: [user selections]
+- External Tools: [user selections]
+  **Installation Willingness:** [user comfort level with installing tools]
+```
+
+### 5. Menu Options
+
+Display: **Select an Option:** [C] Continue to Core Tools [M] Modify Requirements
+
+#### Menu Handling Logic:
+
+- IF C: Append tools overview to {workflowPlanFile}, update frontmatter, then load {nextStepFile}
+- IF M: Refine requirements discussion
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and requirements are documented will you load {nextStepFile} to configure core tools.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- CSV loaded and tools presented clearly
+- User's initial tool requirements gathered
+- Requirements documented in workflow plan
+- User ready to proceed to detailed configuration
+
+### ❌ SYSTEM FAILURE:
+
+- Not loading tools from CSV
+- Duplicating CSV content in step file
+- Proceeding without user requirements input

package/src/modules/bmb/workflows/create-workflow/steps/step-04-core-tools.md

@@ -0,0 +1,145 @@
+---
+name: 'step-04-core-tools'
+description: 'Configure always-available core tools and their integration points'
+
+# Path Definitions
+workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-04-core-tools.md'
+nextStepFile: '{workflow_path}/steps/step-05-memory-requirements.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 4: Core Tools Configuration
+
+## STEP GOAL:
+
+Configure always-available core tools (party-mode, advanced-elicitation, brainstorming, and LLM features) with specific integration points in the 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 integration specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring expertise in BMAD tools and integration patterns
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load core tools from CSV and configure integration points
+- 💾 Confirm user choices for each core tool
+- 📖 Document configuration in workflow plan
+- 🚫 FORBIDDEN to proceed without user confirmation
+
+## SEQUENCE OF INSTRUCTIONS:
+
+### 1. Initialize Core Tools Configuration
+
+"Configuring **Core BMAD Tools and Features**
+
+These core tools significantly enhance workflow quality. Let's configure each one for optimal integration into your workflow."
+
+### 2. Present Core Tools from CSV
+
+Load `{commonToolsCsv}` and filter for `propose='always'`:
+
+"**Core Tools (Always Available):**
+
+**Workflows & Tasks:**
+
+- **Party-Mode:** [description from CSV]
+- **Advanced Elicitation:** [description from CSV]
+- **Brainstorming:** [description from CSV]
+
+**LLM Tool Features:**
+
+- **Web-Browsing:** [description from CSV]
+- **File I/O:** [description from CSV]
+- **Sub-Agents:** [description from CSV]
+- **Sub-Processes:** [description from CSV]
+
+**Tool-Memory:**
+
+- **Sidecar File:** [description from CSV]"
+
+### 3. Configure Integration Points
+
+For each tool, ask about integration:
+
+"**Core Tools Integration:**
+
+**Workflows & Tasks:**
+
+1. **Party-Mode** - Where should collaborative AI sessions be offered? [decision points, creative phases]
+2. **Advanced Elicitation** - Where should critical evaluation checkpoints be placed? [after content creation, quality gates]
+3. **Brainstorming** - Where should creative ideation be integrated? [idea generation phases, innovation points]
+
+**LLM Features:** 4. **Web-Browsing** - When is current information needed? [real-time data, current events] 5. **File I/O** - What document operations are required? [file creation, data management] 6. **Sub-Agents** - Where would specialized delegation help? [complex tasks, parallel processing] 7. **Sub-Processes** - Where would parallel processing improve performance? [long operations, resource optimization]
+
+**Tool-Memory:** 8. **Sidecar File** - Does your workflow need persistent state? [session continuity, agent initialization]"
+
+### 4. Document Core Tools Configuration
+
+Append to {workflowPlanFile}:
+
+```markdown
+## Core Tools Configuration
+
+### Workflows & Tasks
+
+**Party-Mode:** [included/excluded] - Integration points: [specific phases]
+**Advanced Elicitation:** [included/excluded] - Integration points: [specific phases]
+**Brainstorming:** [included/excluded] - Integration points: [specific phases]
+
+### LLM Tool Features
+
+**Web-Browsing:** [included/excluded] - Integration points: [specific phases]
+**File I/O:** [included/excluded] - Integration points: [specific phases]
+**Sub-Agents:** [included/excluded] - Integration points: [specific phases]
+**Sub-Processes:** [included/excluded] - Integration points: [specific phases]
+
+### Tool-Memory
+
+**Sidecar File:** [included/excluded] - Use case: [history tracking, agent initialization]
+```
+
+### 5. Menu Options
+
+Display: **Select an Option:** [C] Continue to Memory Configuration [M] Modify Core Tools
+
+#### Menu Handling Logic:
+
+- IF C: Append core tools configuration to {workflowPlanFile}, update frontmatter, then load {nextStepFile}
+- IF M: Return to tool configuration
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and core tools are documented will you load {nextStepFile} to configure memory requirements.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Core tools presented using CSV descriptions
+- Integration points configured for each selected tool
+- Configuration documented in workflow plan
+- User understands how tools enhance workflow
+
+### ❌ SYSTEM FAILURE:
+
+- Duplicating CSV content instead of referencing it
+- Not confirming integration points with user
+- Proceeding without user confirmation of configuration