@delorenj/pjangler 1.1.3

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-10-tools.md

@@ -0,0 +1,90 @@
+---
+name: 'step-10-tools'
+description: 'MCP tools, integrations, external services the module might need'
+
+nextStepFile: './step-11-scenarios.md'
+advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
+---
+
+# Step 10: Tools
+
+## STEP GOAL:
+
+Identify MCP tools, integrations, and external services the module might need.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+- ✅ You are the **Module Architect** — integrations thinker
+- ✅ Keep it practical — only what's needed
+- 💬 Ask "what external capabilities would help?"
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. MCP Tools
+
+"**Does your module need any MCP (Model Context Protocol) tools?**"
+
+Explain: MCP tools connect agents to external capabilities.
+
+Common MCP tools:
+- Database connectors
+- Git integration
+- Web automation (Playwright)
+- API tools
+- Knowledge bases
+
+**"What would help your module work better?"**
+
+### 2. External Services
+
+"**Any external services or APIs?**"
+
+- Web APIs?
+- Cloud services?
+- Data sources?
+- Third-party tools?
+
+### 3. Module Integrations
+
+"**Does this integrate with other BMAD modules?****
+
+- Uses workflows from other modules?
+- Shares agents or extends them?
+- Depends on another module's capabilities?
+
+### 4. Capture the List
+
+Document:
+- **MCP Tools:** {list or "none"}
+- **External Services:** {list or "none"}
+- **Module Integrations:** {list or "none"}
+
+Note: These are placeholders for later — the create workflow can implement them.
+
+### 5. MENU OPTIONS
+
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+- IF A: Execute `{advancedElicitationTask}`
+- IF P: Execute `{partyModeWorkflow}`
+- IF C: Load `{nextStepFile}`
+- IF Any other: Help, then redisplay
+
+---
+
+## Success Metrics
+
+✅ MCP tools identified (or "none" decided)
+✅ External services documented (or "none")
+✅ Module integrations noted (or "none")

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-11-scenarios.md

@@ -0,0 +1,83 @@
+---
+name: 'step-11-scenarios'
+description: 'User journey — tell stories of how people will use this module'
+
+nextStepFile: './step-12-creative.md'
+advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
+---
+
+# Step 11: Scenarios
+
+## STEP GOAL:
+
+Tell stories of how users will actually use this module — bring the vision to life.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+- ✅ You are the **Module Architect** — storyteller
+- ✅ Paint a picture of actual usage
+- 💬 Narrative mode — "imagine this..."
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Set the Scene
+
+"**Let me tell you a story about how someone will use your module.**"
+
+"Close your eyes and imagine..."
+
+### 2. Tell Usage Stories
+
+Walk through 2-3 scenarios:
+
+**Scenario 1: First Use**
+- User's situation: {context}
+- They load the module: {what happens}
+- They run an agent: {which agent, what workflow}
+- They get a result: {outcome}
+- They feel: {emotion}
+
+**Scenario 2: Advanced Use**
+- Power user context
+- Complex workflow
+- Multiple agents collaborating
+- Impressive result
+
+**Scenario 3: "Aha!" Moment**
+- When the module really shines
+- Surprising capability
+- Delightful experience
+
+### 3. Validate the Stories
+
+"**Do these stories feel right? Can you see your module being used this way?**"
+
+Adjust based on feedback.
+
+### 4. MENU OPTIONS
+
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+- IF A: Execute `{advancedElicitationTask}`
+- IF P: Execute `{partyModeWorkflow}`
+- IF C: Load `{nextStepFile}`
+- IF Any other: Help, then redisplay
+
+---
+
+## Success Metrics
+
+✅ 2-3 usage scenarios told
+✅ User can visualize their module in action
+✅ Stories feel authentic and exciting

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-12-creative.md

@@ -0,0 +1,94 @@
+---
+name: 'step-12-creative'
+description: 'Creative features — easter eggs, lore, delightful touches'
+
+nextStepFile: './step-13-review.md'
+advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
+---
+
+# Step 12: Creative Features
+
+## STEP GOAL:
+
+Add the magic — easter eggs, lore, delightful touches that make the module memorable.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+- ✅ You are the **Module Architect** — creative magician
+- ✅ This is where personality comes alive
+- 💬 "What would make someone smile?"
+
+### Step-Specific Rules:
+- 🎯 This is optional creativity — not all modules need this
+- 🎯 Party mode is perfect here
+- ✨ Have fun with it!
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Set the Creative Tone
+
+"**Now for the fun part — what makes your module delightful?** ✨
+
+"Great modules work. Amazing modules have personality. What's yours?"
+
+### 2. Explore Creative Elements
+
+**Personality & Theming:**
+- Do the agents have running jokes or catchphrases?
+- Is there a consistent tone or vibe?
+- Any thematic elements? (space, medieval, corporate, etc.)
+
+**Easter Eggs:**
+- Hidden commands or responses?
+- Fun interactions when users try certain things?
+- Surprises that delight?
+
+**Module Lore:**
+- Backstory for the agents?
+- A consistent "universe" the module lives in?
+- Narrative elements?
+
+### 3. Party Mode Ideation
+
+"**Want to brainstorm creative ideas together?**"
+
+- IF yes: Execute `{partyModeWorkflow}` with creative focus
+- Generate wild ideas
+- Keep the gems, discard the rest
+
+### 4. Capture the Creative Elements
+
+Document:
+- **Personality theme:** {theme or "none"}
+- **Easter eggs:** {ideas or "none"}
+- **Module lore:** {concepts or "none"}
+
+Note: These are optional — a module can be great without them.
+
+### 5. MENU OPTIONS
+
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+- IF A: Execute `{advancedElicitationTask}`
+- IF P: Execute `{partyModeWorkflow}` — perfect for creative brainstorming!
+- IF C: Load `{nextStepFile}`
+- IF Any other: Help, then redisplay
+
+---
+
+## Success Metrics
+
+✅ Creative elements explored (even if "none")
+✅ Personality themes considered
+✅ User excited about the possibilities

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-13-review.md

@@ -0,0 +1,104 @@
+---
+name: 'step-13-review'
+description: 'Read through the brief together, "Does this excite you?"'
+
+nextStepFile: './step-14-finalize.md'
+briefTemplateFile: '../../templates/brief-template.md'
+---
+
+# Step 13: Review
+
+## STEP GOAL:
+
+Read through the brief together and confirm the vision is complete and exciting.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+- ✅ You are the **Module Architect** — review facilitator
+- ✅ Read back what we've discovered
+- ✅ Ensure nothing important is missing
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Gather All Decisions
+
+Collect everything from steps 1-12:
+
+- Module type: {Standalone/Extension/Global}
+- Module code: {code}
+- Module name: {name}
+- Vision: {vision summary}
+- Users: {who it's for}
+- Value proposition: {what makes it special}
+- Agents: {agent team}
+- Workflows: {workflow list}
+- Tools: {MCP, integrations}
+- Creative features: {personality, easter eggs}
+
+### 2. Read It Back
+
+"**Let me read back what we've designed together.**"
+
+Present the brief in an inspiring way:
+
+"**Your Module: {name} ({code})**"
+
+"**Vision:** {vision}"
+
+"**For:** {users}"
+
+"**What makes it special:** {value proposition}"
+
+"**Agent Team:** {agents}"
+
+"**Key Workflows:** {workflows}"
+
+"**Creative Touch:** {creative elements}"
+
+### 3. The Excitement Check
+
+"**Does this excite you?****
+
+- Is this the module you envisioned?
+- Anything missing?
+- Anything you want to change?"
+
+**Make updates if needed.**
+
+### 4. Final Confirmation
+
+"**Are you happy with this brief? Ready to finalize?**"
+
+### 5. MENU OPTIONS
+
+**Select an Option:** [B] Back to refine [C] Continue to Finalize
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input
+- ONLY proceed to next step when user selects 'C' and confirms
+
+#### Menu Handling Logic:
+
+- IF B: Go back to specific step to refine (ask which one)
+- IF C: Load `{nextStepFile}`
+- IF Any other: Ask for clarification, then redisplay menu
+
+---
+
+## Success Metrics
+
+✅ Brief reviewed completely
+✅ User confirms excitement
+✅ No major gaps identified
+✅ Ready to finalize

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-14-finalize.md

@@ -0,0 +1,117 @@
+---
+name: 'step-14-finalize'
+description: 'Final polish, output the brief document'
+
+briefTemplateFile: '../../templates/brief-template.md'
+bmbCreationsOutputFolder: '{bmb_creations_output_folder}'
+---
+
+# Step 14: Finalize
+
+## STEP GOAL:
+
+Create the final module brief document and save it to the bmb-creations output folder.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+- ✅ You are the **Module Architect** — completing the brief
+- ✅ Assemble everything into a beautiful document
+- ✅ Celebrate the completion!
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Load Template
+
+Load `{briefTemplateFile}` to use as the base.
+
+### 2. Assemble the Brief
+
+Fill in all sections with what we've gathered:
+
+**Frontmatter:**
+- date: {today's date}
+- user_name: {from config}
+- module_code: {from step 5}
+- module_type: {from step 3}
+- status: "Ready for Development"
+
+**Executive Summary:**
+- module_vision: {from step 4}
+- module_category: {derived from vision}
+- target_users: {from step 6}
+- complexity_level: {assess from agent/workflow count}
+
+**Module Identity:**
+- module_code, module_name: {from step 5}
+- module_identity: {vision summary}
+- personality_theme: {from step 5 or step 12}
+
+**Module Type:**
+- module_type: {from step 3}
+- module_type_explanation: {explain the choice}
+
+**Unique Value Proposition:**
+- unique_value_proposition: {from step 7}
+- value_proposition_details: {elaborate}
+
+**User Scenarios:**
+- target_users: {from step 6}
+- primary_use_case: {from step 11}
+- user_journey: {from step 11}
+
+**Agent Architecture:**
+- agent_count_strategy: {single or multi, why}
+- agent_roster_table: {from step 8}
+- agent_interaction_model: {how they work together}
+- agent_communication_style: {from step 8}
+
+**Workflow Ecosystem:**
+- core_workflows: {from step 9}
+- feature_workflows: {from step 9}
+- utility_workflows: {from step 9}
+
+**Tools & Integrations:**
+- mcp_tools: {from step 10}
+- external_services: {from step 10}
+- module_integrations: {from step 10}
+
+**Creative Features:**
+- creative_personality: {from step 12}
+- easter_eggs: {from step 12}
+- module_lore: {from step 12}
+
+### 3. Write the Brief File
+
+Save to: `{bmbCreationsOutputFolder}/modules/module-brief-{module_code}.md`
+
+### 4. Celebrate and Next Steps
+
+"**🎉 Your module brief is complete!**"
+
+"**Saved to:** {file path}"
+
+"**Next steps:**"
+1. **Review the brief** — Make sure it captures your vision
+2. **Run the module workflow (Create mode)** — This will build the module structure
+3. **Create agents** — Use the agent-builder workflow for each agent
+4. **Create workflows** — Use the workflow-builder workflow for each workflow
+5. **Test and iterate** — Install and refine
+
+"**You've created something amazing. Let's build it!**"
+
+---
+
+## Success Metrics
+
+✅ Brief document created and saved
+✅ All sections filled with gathered information
+✅ File path provided to user
+✅ Next steps clearly explained

package/templates/commonproject/_bmad/bmb/workflows/module/steps-c/step-01-load-brief.md

@@ -0,0 +1,178 @@
+---
+name: 'step-01-load-brief'
+description: 'Load brief or user write-up, validate completeness'
+
+nextStepFile: './step-02-structure.md'
+continueFile: './step-01b-continue.md'
+agentSpecTemplate: '../../templates/agent-spec-template.md'
+workflowSpecTemplate: '../../templates/workflow-spec-template.md'
+moduleStandardsFile: '../../data/module-standards.md'
+moduleYamlConventionsFile: '../../data/module-yaml-conventions.md'
+advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
+---
+
+# Step 1: Load Brief (Create Mode)
+
+## STEP GOAL:
+
+Load the module brief (or get a detailed user write-up) and validate it has the information needed to build the module.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the **Module Builder** — structured, competent, ready to build
+- ✅ Validate input before proceeding
+- ✅ Ensure we have what we need to succeed
+
+### Step-Specific Rules:
+
+- 🎯 This is a continuable workflow — check for existing work
+- 🚫 FORBIDDEN to proceed without complete brief or write-up
+- 💾 Track progress for continuation
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 📖 Create/update output file to track progress
+- 🚫 FORBIDDEN to load next step until brief is validated
+
+## CONTEXT BOUNDARIES:
+
+- Input: Module brief from Brief mode OR user-provided write-up
+- Output: Module structure ready for implementation
+- This mode requires complete information to proceed
+
+---
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly.
+
+### 1. Check for Existing Work
+
+Look for existing module build state:
+- Check for `module-build-{module_code}.md` in output folder
+- If exists AND has `stepsCompleted` → load `{continueFile}`
+- If not exists → continue to step 1.2
+
+### 2. Get the Brief or Write-Up
+
+"**Welcome to Create mode! I'll build your module structure from your brief.**"
+
+**"Where is your module brief?"**
+
+Options:
+- **A)** Brief from Brief mode → `{bmb_creations_output_folder}/modules/module-brief-{code}.md`
+- **B)** User-provided write-up → Ask for path
+- **C)** Detailed description → User describes the module now
+
+**IF A or B:** Load and read the brief/write-up
+
+**IF C:** Gather the needed information through conversation:
+- Module name and code
+- Module type (Standalone/Extension/Global)
+- Agent roster (roles, names)
+- Workflow list
+- Key features and tools
+
+### 3. Validate Brief Completeness
+
+Load `{moduleStandardsFile}` and check that the brief contains:
+
+**Required Information:**
+- [ ] Module code and name
+- [ ] Module type (Standalone/Extension/Global)
+- [ ] Module vision/purpose
+- [ ] Agent roster (at least minimum)
+- [ ] Workflow list (at least core workflows)
+- [ ] Any special tools or integrations
+
+**IF Extension Module:**
+- [ ] Base module code (for matching)
+
+**IF anything missing:**
+
+"**Your brief is missing some key information. Let me help you complete it.**"
+
+Use `{advancedElicitationTask}` if needed to gather missing details.
+
+### 4. Confirm and Create Tracking
+
+Once validated:
+
+"**I have everything I need to build your module!**"
+
+"**Module:** {name} ({code})"
+"**Type:** {Standalone/Extension/Global}"
+
+Create or update the build tracking file:
+
+```yaml
+---
+moduleCode: {code}
+moduleName: {name}
+moduleType: {type}
+briefFile: {brief path or "user-provided"}
+stepsCompleted: ['step-01-load-brief']
+created: {date}
+status: IN_PROGRESS
+---
+```
+
+### 5. Preview the Build Process
+
+"**Here's what I'll build for you:**"
+
+1. Directory structure (based on module type)
+2. module.yaml with install configuration
+3. _module-installer/ folder (if needed)
+4. Agent placeholder/spec files
+5. Workflow placeholder/spec files
+6. README.md and TODO.md
+
+"**Ready to start building?**"
+
+### 6. Present MENU OPTIONS
+
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input
+- ONLY proceed to next step when user selects 'C'
+
+#### Menu Handling Logic:
+
+- IF A: Execute `{advancedElicitationTask}` for any refinements
+- IF P: Execute `{partyModeWorkflow}` for creative pre-build discussion
+- IF C: Update tracking file, then load `{nextStepFile}`
+- IF Any other: Help user, then redisplay menu
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Brief or write-up loaded
+- All required information validated
+- Tracking file created
+- User confirms ready to build
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding with incomplete brief
+- Missing key information (code, type, agents, workflows)
+- Not validating extension base module
+
+**Master Rule:** Garbage in, garbage out. Ensure we have complete information before building.