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

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

@@ -0,0 +1,155 @@
+---
+nextStepFile: '{installed_path}/steps/step-02-concept.md'
+continueFile: '{installed_path}/steps/step-01b-continue.md'
+modulePlanTemplate: '{installed_path}/templates/module-plan.template.md'
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+customModuleLocation: '{bmb_creations_output_folder}'
+modulePlanFile: '{bmb_creations_output_folder}/{module_name}/module-plan-{module_name}.md'
+---
+
+# Step 1: Workflow Initialization
+
+## STEP GOAL:
+
+To initialize the create-module workflow by getting the module name from the user, checking for existing work, handling continuation if needed, and creating the initial module plan document.
+
+## 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 Module Architect and BMAD Systems Specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring expertise in BMAD architecture and module creation, user brings their module requirements
+- ✅ Maintain collaborative, guiding tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on initialization, getting module name, and setting up tracking
+- 🚫 FORBIDDEN to look ahead to future steps
+- 💬 Handle initialization professionally
+- 🚪 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 setup 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
+- Module brief discovery happens in this step
+
+## SEQUENCE OF INSTRUCTIONS:
+
+### 1. Welcome and Get Module Name
+
+Greet the user warmly by their {user_name}, welcoming them to the BMAD Module Creator. Through conversation, collaboratively work with them to:
+
+- Understand what kind of module they want to create
+- Help them choose a good name in kebab-case (provide examples if needed)
+- Validate the name will work for module creation
+
+### 2. Check for Existing Work
+
+Once you have the module name:
+
+- Check if a folder already exists at {customModuleLocation}/{module_name}
+- If it exists, look for a module plan document inside
+- Read any existing work carefully to understand what was already done
+
+### 3. Handle Continuation (If Work Exists)
+
+If you find an existing module plan:
+
+- Review what's been completed based on the stepsCompleted array
+- Present a clear summary of the current status
+- Ask if they want to continue where they left off, update existing work, or start fresh
+- If continuing, load step-01b-continue.md
+
+### 4. Look for Supporting Documents
+
+Check for any existing documents that could help:
+
+- Module briefs in the module folder or output folder
+- Brainstorming results in the output folder
+- Any other relevant documentation
+
+### 5. Guide User's Next Decision
+
+If no supporting documents are found:
+
+- Explain their three options clearly and helpfully
+- Option 1: Proceed with creating the module based on their ideas
+- Option 2: Exit and create a module brief first (explain the module-brief workflow)
+- Option 3: Exit and do brainstorming first (explain the brainstorming workflow)
+- Support whatever choice they make
+
+### 6. Create Module Foundation
+
+If proceeding:
+
+- Create the module folder if needed
+- Create the initial module-plan-{module_name}.md document using the module plan template from {modulePlanTemplate}
+- Initialize proper frontmatter with current date, user name, and add "step-01-init" to stepsCompleted array
+- Add any discovered documents to inputDocuments field
+- Include a brief section about the legacy reference
+
+### 7. Prepare for Next Step
+
+- Confirm everything is set up properly
+- Let the user know what you've accomplished
+- Transition smoothly to the next phase of defining the module concept
+
+### 8. Present MENU OPTIONS
+
+Display: **Proceeding to define your module concept...**
+
+#### EXECUTION RULES:
+
+- This is an initialization step with no user choices (after inputs handled)
+- Proceed directly to next step after setup
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+- After setup completion, add step-01-init to the end of the stepsCompleted array in module plan frontmatter, then load, read entire file, then execute `{nextStepFile}` to define the module concept
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Module name obtained and validated through collaborative dialogue
+- Module plan document created from template with frontmatter initialized
+- "step-01-init" added to stepsCompleted array
+- Module plan document created at correct location
+- User feels welcomed and informed
+- Ready to proceed to step 2
+- OR existing workflow properly routed to step-01b-continue.md
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding with step 2 without module plan creation
+- Not checking for existing documents properly
+- Creating module without user input on name
+- Skipping folder creation
+- Not routing to step-01b-continue.md when appropriate
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN initialization setup is complete and module plan document is created (OR continuation is properly routed), will you then immediately load, read entire file, then execute `{nextStepFile}` to begin defining the module concept.

package/src/modules/bmb/workflows/create-module/steps/step-01b-continue.md

@@ -0,0 +1,169 @@
+---
+modulePlanFile: '{bmb_creations_output_folder}/{module_name}/module-plan-{module_name}.md'
+---
+
+# Step 1b: Continue Module Creation
+
+## 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 Module Architect and BMAD Systems Specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring expertise in BMAD architecture and module creation, user brings their module requirements
+- ✅ Maintain collaborative, guiding tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on handling continuation and resuming workflow
+- 🚫 FORBIDDEN to modify existing work without user consent
+- 💬 Present status clearly and get user direction
+- 📋 Track completion status accurately
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load and analyze existing module plan
+- 💾 Update frontmatter with continuation status
+- 📖 Route to appropriate next step based on progress
+- 🚫 FORBIDDEN to skip steps just because they exist
+
+## CONTEXT BOUNDARIES:
+
+- Module plan document exists with previous work
+- Focus on understanding what's been done and what remains
+- Don't assume completion without verification
+- User direction guides next actions
+
+## STEP GOAL:
+
+To resume module creation by presenting current status, understanding what's been accomplished, and determining the next step in the process.
+
+## CONTINUATION HANDLING SEQUENCE:
+
+### 1. Load and Analyze Existing Module Plan
+
+Load module plan from: {modulePlanFile}
+Read entire document including frontmatter
+Extract current status from frontmatter fields:
+
+- stepsCompleted array
+- lastStep (the final item in the stepsCompleted array)
+- module_name
+- module_code
+- date
+- inputDocuments
+
+### 2. Present Current Status
+
+"Welcome back! I found your in-progress module creation for **{module_name}**.
+
+**Current Status:**
+
+- **Module Code:** {module_code}
+- **Started:** {date}
+- **Last Step:** {lastStep}
+- **Steps Completed:** {stepsCompleted count}/{total steps}
+- **Location:** {bmb_creations_output_folder}/{module_name}
+
+Progress Summary:"
+
+Based on stepsCompleted, show:
+
+- [✅] Step 1: Init - Complete
+- [ ] Step 2: Concept - {status}
+- [ ] Step 3: Components - {status}
+- [ ] Step 4: Structure - {status}
+- [ ] Step 5: Configuration - {status}
+- [ ] Step 6: Agents - {status}
+- [ ] Step 7: Workflows - {status}
+- [ ] Step 8: Installer - {status}
+- [ ] Step 9: Documentation - {status}
+- [ ] Step 10: Roadmap - {status}
+- [ ] Step 11: Validation - {status}
+
+### 3. Review What's Been Done
+
+Read content sections of module plan
+Summarize what's been accomplished:
+
+"**Completed Work:**
+
+- Module identity defined
+- Component planning complete
+- [Other completed items based on content]"
+
+### 4. Determine Next Step
+
+Based on stepsCompleted array:
+Find highest completed step number
+Next step = highest completed + 1
+
+"**Ready to Continue:**
+Your next step would be: **Step {nextStep} - [step name]**
+
+What would you like to do?
+
+1. **Continue** from where you left off
+2. **Review** what's been done so far
+3. **Modify** previous work
+4. **Start over** with a new plan"
+
+### 5. Handle User Choice
+
+User your best judgement in how to handle the users choice
+
+### 6. Update Continuation Status
+
+Update modulePlanFile frontmatter:
+
+- Set lastStep: 'continued'
+- Add note about continuation date
+- Keep stepsCompleted unchanged
+
+## ✅ SUCCESS METRICS:
+
+- User understands current progress
+- Next step identified correctly
+- User choice handled appropriately
+- Module plan updated with continuation status
+- Workflow resumed at correct location
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Not accurately reading previous status
+- Skipping steps just because they exist
+- Not offering review option
+- Losing previous work
+- Not updating continuation tracking
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Existing work properly loaded and analyzed
+- User clearly understands current status
+- Continuation options presented clearly
+- Next step determined correctly
+- Module plan updated with continuation information
+
+### ❌ SYSTEM FAILURE:
+
+- Not reading existing plan completely
+- Misrepresenting progress status
+- Losing track of what's been done
+- Not offering appropriate continuation options
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN user selects 'C' (Continue) and appropriate updates are saved to modulePlanFile, will you then load, read entire file, then execute the determined next step file to resume the module creation workflow.

package/src/modules/bmb/workflows/create-module/steps/step-02-concept.md

@@ -0,0 +1,217 @@
+---
+installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
+nextStepFile: '{installed_path}/steps/step-03-components.md'
+modulePlanFile: '{bmb_creations_output_folder}/{module_name}/module-plan-{module_name}.md'
+moduleStructureGuide: '{project-root}/bmb/workflows/create-agent-legacy/create-module/module-structure.md'
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 2: Define Module Concept and Scope
+
+## 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 Module Architect and Business Analyst
+- ✅ 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 module design and BMAD patterns, user brings their domain knowledge
+- ✅ Maintain collaborative, educational tone
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on defining the module concept and scope
+- 🚫 FORBIDDEN to start designing components in this step
+- 💬 Ask questions conversationally to understand vision
+- 🚫 FORBIDDEN to proceed without clear module identity
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load and study module structure guide for context
+- 💾 Document all module identity details in plan
+- 📖 Add "step-02-concept" to stepsCompleted array` before loading next step
+- 🚫 FORBIDDEN to load next step until user selects 'C'
+
+## CONTEXT BOUNDARIES:
+
+- Module name and location from step 1
+- Input documents (brief/brainstorming) if any
+- Focus ONLY on concept and scope definition
+- Don't assume module details beyond what user provides
+
+## STEP GOAL:
+
+To articulate the module's vision, define its identity, and establish clear boundaries for what it will and won't do.
+
+## MODULE CONCEPT DEFINITION PROCESS:
+
+### 1. Load Context and Briefs
+
+"Let's define your module's concept and identity. This will guide all the decisions we make about agents, workflows, and features."
+
+Load module-plan.md and check inputDocuments field
+
+Read the module brief completely
+"I see you have a module brief. Let me review that to understand your vision..."
+Use brief content to inform concept development questions
+
+Load and study the module structure guide for context
+
+### 2. Guide Concept Development
+
+Ask conversationally:
+
+"**Understanding Your Vision:**
+
+1. **What problem will this module solve?** - What pain point or need are you addressing?
+
+2. **Who is the primary user?** - Who will benefit most from this module?
+
+3. **What's the main outcome?** - What will users be able to do after using your module?
+
+4. **Why is this important?** - What makes this module valuable or unique?"
+
+### 3. Module Identity Development
+
+Based on their responses, collaboratively develop:
+
+**Module Name:**
+
+- Start with their module code: {module_name}
+- Suggest a display name in Title Case
+- Get user confirmation or refinement
+
+**Module Purpose:**
+
+- Distill their problem statement into 1-2 clear sentences
+- Focus on value and outcomes
+- Get user validation
+
+**Target Audience:**
+
+- Identify primary user persona
+- Consider skill level (beginner/intermediate/advanced)
+- Note any secondary audiences
+
+**Module Scope:**
+
+- What's IN scope (core features)
+- What's OUT of scope (explicitly state what it won't do)
+- Success criteria (how will we know it works?)
+
+### 4. Module Theme and Category
+
+"**Module Classification:**
+
+Based on your description, this seems to fit in the [Domain-Specific/Creative/Technical/Business/Personal] category.
+
+Does this sound right? Or would you categorize it differently?
+
+**Example Categories:**
+
+- **Domain-Specific**: Legal, Medical, Finance, Education
+- **Creative**: RPG/Gaming, Story Writing, Music Production
+- **Technical**: DevOps, Testing, Architecture, Security
+- **Business**: Project Management, Marketing, Sales
+- **Personal**: Journaling, Learning, Productivity"
+
+### 5. Module Type Estimation
+
+"Based on what you've described, I'm thinking this might be a:
+
+- **Simple Module** (1-2 agents, 2-3 workflows) - Focused, single-purpose
+- **Standard Module** (3-5 agents, 5-10 workflows) - Comprehensive solution
+- **Complex Module** (5+ agents, 10+ workflows) - Full platform/framework
+
+Which feels right for your vision? We'll confirm this after planning components."
+
+### 6. Document Module Concept
+
+Update module-plan.md with concept section:
+
+```markdown
+## Module Concept
+
+**Module Name:** {module_display_name}
+**Module Code:** {module_name}
+**Category:** [category]
+**Type:** [estimated type]
+
+**Purpose Statement:**
+[1-2 sentence clear purpose]
+
+**Target Audience:**
+
+- Primary: [description]
+- Secondary: [if any]
+
+**Scope Definition:**
+
+**In Scope:**
+
+- [core feature 1]
+- [core feature 2]
+- [core feature 3]
+
+**Out of Scope:**
+
+- [explicitly excluded item 1]
+- [explicitly excluded item 2]
+
+**Success Criteria:**
+
+- [measurable outcome 1]
+- [measurable outcome 2]
+- [user satisfaction indicator]
+```
+
+### 7. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask} to explore alternative concept approaches
+- IF P: Execute {partyModeWorkflow} to get creative input on module identity
+- IF C: Save concept to module-plan.md, add step-02-concept to the end of the stepsCompleted array in frontmatter, then load nextStepFile
+- IF Any other comments or queries: help user respond then redisplay menu
+
+#### 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 then end with display again of the menu options
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Module purpose clearly articulated
+- Module identity established (name, audience, scope)
+- Category and type determined
+- Concept documented in module plan
+- User feels the concept matches their vision
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding without clear module purpose
+- Not defining scope boundaries
+- Skipping user validation of concept
+- Not documenting concept details
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and module concept is saved to module-plan.md with stepsCompleted updated to [1, 2], will you then load, read entire file, then execute `{nextStepFile}` to begin component planning.