@delorenj/pjangler 1.2.25 → 1.3.0

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-03-module-type.md

@@ -1,148 +0,0 @@
----
-name: 'step-03-module-type'
-description: 'EARLY decision: Standalone, Extension, or Global module?'
-
-nextStepFile: './step-04-vision.md'
-moduleStandardsFile: '../data/module-standards.md'
-advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
----
-
-# Step 3: Module Type
-
-## STEP GOAL:
-
-Make the EARLY key decision: Is this a Standalone, Extension, or Global module? This decision affects everything that follows.
-
-## 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 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** — you understand module types and their implications
-- ✅ Help the user make an informed decision
-- ✅ This is a commitment — get it right
-
-### Step-Specific Rules:
-
-- 🎯 This decision MUST happen early
-- 🚫 FORBIDDEN to proceed without clarity on module type
-- 💬 Explain the trade-offs clearly
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load `{moduleStandardsFile}` to reference module types
-- 🎯 Follow the MANDATORY SEQUENCE exactly
-- 📖 Load next step when user selects 'C'
-
----
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly.
-
-### 1. Explain Module Types
-
-Load `{moduleStandardsFile}` and present the three types:
-
-"**Before we go further, we need to decide: What type of module is this?** This decision affects where files go, how installation works, and how the module integrates with BMAD."
-
-**Standalone Module:**
-- A new, independent module
-- Own module code and identity
-- Installed alongside other modules
-- Example: CIS — a creative innovation suite
-
-**Extension Module:**
-- Extends an existing BMAD module
-- Shares the base module's code (e.g., `code: bmm`)
-- Adds or overrides agents/workflows
-- Example: A security extension for BMM
-
-**Global Module:**
-- Affects the entire BMAD framework
-- Core functionality impacting all modules
-- Rare — use sparingly
-- Example: Universal logging/telemetry
-
-### 2. Determine Type Together
-
-**"Based on your idea, what type makes sense?"**
-
-Help them think through:
-- **"Is this a brand new domain?"** → Likely Standalone
-- **"Does this build on an existing module?"** → Likely Extension
-- **"Does this affect all modules?"** → Possibly Global (be cautious)
-
-**If considering Extension:**
-- "Which existing module does it extend?"
-- "Are you adding new agents/workflows, or modifying existing ones?"
-- "This means your `code:` will match the base module"
-
-**If considering Global:**
-- "Are you sure? Global modules are rare."
-- "Could this be a standalone module instead?"
-
-### 3. Confirm and Store
-
-Once decided:
-
-"**Module Type: {Standalone/Extension/Global}**"
-
-**IF Extension:**
-"Base module to extend: {base-module-code}"
-"Folder name will be unique: {e.g., bmm-security}"
-
-**Store this decision.** It affects:
-- Where files are created
-- What `code:` goes in module.yaml
-- Installation behavior
-
-### 4. Preview Implications
-
-Briefly explain what this means:
-- "As a {type}, your module will {implications}"
-- "When we build, files will go to {location}"
-
-### 5. Present MENU OPTIONS
-
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input
-- User can change their mind before proceeding
-- ONLY proceed to next step when user selects 'C' and confirms the type
-
-#### Menu Handling Logic:
-
-- IF A: Execute `{advancedElicitationTask}` for deeper exploration of the decision
-- IF P: Execute `{partyModeWorkflow}` for brainstorming the approach
-- IF C: Confirm the decision, then load `{nextStepFile}`
-- IF Any other: Help user, then redisplay menu
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Module type clearly decided
-- User understands the implications
-- Extension modules know their base module
-- Decision is stored for later steps
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding without clear module type
-- User doesn't understand the implications
-- Extension module without clear base
-
-**Master Rule:** This is a gateway decision. Get clarity before moving forward.

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-04-vision.md

@@ -1,82 +0,0 @@
----
-name: 'step-04-vision'
-description: 'Deep dive into the vision — what would make this module extraordinary?'
-
-nextStepFile: './step-05-identity.md'
-advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
----
-
-# Step 4: Vision
-
-## STEP GOAL:
-
-Deep dive into the vision — explore what would make this module extraordinary, not just functional.
-
-## 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** — visioning, dreaming big
-- ✅ Push beyond "good enough" to "extraordinary"
-- 💬 Ask "what would make this amazing?"
-
-### Step-Specific Rules:
-- 🎯 This is about the vision, not the details
-- 🚫 FORBIDDEN to jump to implementation
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Set the Visioning Tone
-
-"**Let's dream big. What would make this module extraordinary?**"
-
-"Good modules solve problems. Great modules inspire people. Let's make yours great."
-
-### 2. Explore the Vision
-
-Ask visioning questions:
-
-**"If this module succeeds wildly, what does that look like?"**
-- How are people using it?
-- What are they able to do that they couldn't before?
-- What's the feeling when they use it?
-
-**"What would make someone say 'I love this module'?"**
-- Delightful features?
-- Surprising capabilities?
-- The way it makes them feel?
-
-**"What's the 'secret sauce' — the thing that makes this special?"**
-
-### 3. Capture the Vision
-
-Summarize:
-- "Your vision: {summary}"
-- "What makes it special: {unique aspect}"
-- "The dream outcome: {dream}"
-
-### 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
-
-✅ Vision feels inspiring and clear
-✅ "Extraordinary" elements identified
-✅ User excited about the possibility

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-05-identity.md

@@ -1,96 +0,0 @@
----
-name: 'step-05-identity'
-description: 'Module code, name, and personality/theme'
-
-nextStepFile: './step-06-users.md'
-advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
----
-
-# Step 5: Identity
-
-## STEP GOAL:
-
-Define the module's identity — code, name, and personality/theme.
-
-## 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** — naming, branding, theming
-- ✅ This is where personality comes in
-- 💬 Have fun with this!
-
-### Step-Specific Rules:
-- 🎯 Module code follows conventions (kebab-case, 2-20 chars)
-- 🚫 FORBIDDEN to use reserved codes or existing module codes (for standalone)
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Module Code
-
-"**Let's give your module a code.**"
-
-Explain:
-- kebab-case (e.g., `bmm`, `cis`, `healthcare-ai`)
-- Short, memorable, descriptive
-- 2-20 characters
-
-**IF Extension:** Code matches base module (already decided)
-
-**IF Standalone:** Propose options based on the module name/domain
-
-### 2. Module Name
-
-"**What's the display name?**"
-
-This is the human-facing name in module.yaml:
-- "BMM: BMad Method Agile-AI Driven-Development"
-- "CIS: Creative Innovation Suite"
-- "Your Module: Your Description"
-
-### 3. Personality Theme
-
-"**Does your module have a personality or theme?**"
-
-Some modules have fun themes:
-- BMM — Agile team (personas like John, Winston)
-- CIS — Creative innovators
-- BMGD — Game dev team
-
-**Questions:**
-- Should the agents have a consistent theme?
-- Any personality vibes? (Corporate team, fantasy party, reality show cast?)
-- Or keep it professional/focused?
-
-### 4. Store Identity
-
-Capture:
-- Module code: `{code}`
-- Module name: `{name}`
-- Personality theme: `{theme or "none/professional"}`
-
-### 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
-
-✅ Module code decided and validated
-✅ Module name defined
-✅ Personality theme decided (even if "none")

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-06-users.md

@@ -1,85 +0,0 @@
----
-name: 'step-06-users'
-description: 'Who + How — personas AND user journey combined'
-
-nextStepFile: './step-07-value.md'
-advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
----
-
-# Step 6: Users
-
-## STEP GOAL:
-
-Define who the module is for AND how they'll use it — personas and user journey combined.
-
-## 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** — user-centric, empathetic
-- ✅ Help the user walk in their users' shoes
-- 💬 Tell the story of how this will be used
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Define the Users
-
-"**Let's get specific about who this is for.**"
-
-**Primary Users:**
-- Who will use this module most often?
-- What's their role? (developer, designer, analyst, etc.)
-- What's their skill level? (beginner, intermediate, expert)
-
-**Secondary Users:**
-- Who else might use it?
-- How is their experience different?
-
-### 2. Build User Personas
-
-Create 1-2 brief personas:
-
-**Persona 1:**
-- Name/role: {e.g., "Sarah, Software Engineer"}
-- Goals: {what they want to accomplish}
-- Pain points: {what frustrates them now}
-- What success looks like
-
-### 3. Tell the User Journey Story
-
-"**Let's walk through how someone would use this module.**"
-
-Tell a story:
-1. User has a problem → {their situation}
-2. They load the module → {what they expect}
-3. They run an agent/workflow → {what happens}
-4. They get a result → {the outcome}
-5. This helps them → {the achievement}
-
-"**Can you see this flow? Does it match what you envision?**"
-
-### 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
-
-✅ User personas defined
-✅ User journey story told
-✅ User can visualize how their module will be used

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-07-value.md

@@ -1,75 +0,0 @@
----
-name: 'step-07-value'
-description: 'Unique Value Proposition — what makes this module special?'
-
-nextStepFile: './step-08-agents.md'
-advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
----
-
-# Step 7: Value
-
-## STEP GOAL:
-
-Define the Unique Value Proposition — what makes this module special and why users would choose it.
-
-## 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** — focused on differentiation
-- ✅ Help identify what makes this unique
-- 💬 Ask "why this and not something else?"
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Explore Differentiation
-
-"**What makes your module special? Why would someone choose it?**"
-
-Ask:
-- **What can users do with your module that they can't do otherwise?**
-- **What's the 'aha!' moment — when they realize this is exactly what they need?**
-- **What problem does this solve better than anything else?**
-
-### 2. Identify the Unique Value Proposition
-
-Help craft a clear statement:
-
-**"For {target users}, {module name} provides {key benefit} unlike {alternatives} because {unique differentiator}."**
-
-Example:
-"For software teams, BMM provides AI-driven agile delivery unlike manual processes because it orchestrates specialized agents for every phase of development."
-
-### 3. Competitive Context
-
-**"What else exists in this space? How is yours different?"**
-
-- Similar modules?
-- Manual approaches?
-- Why is yours better?
-
-### 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
-
-✅ Unique value proposition articulated
-✅ Differentiation from alternatives clear
-✅ User can explain why someone would choose this module

package/templates/commonproject/_bmad/bmb/workflows/module/steps-b/step-08-agents.md

@@ -1,96 +0,0 @@
----
-name: 'step-08-agents'
-description: 'Agent architecture — party mode simulation of interactions'
-
-nextStepFile: './step-09-workflows.md'
-agentArchitectureFile: '../data/agent-architecture.md'
-advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
----
-
-# Step 8: Agents
-
-## STEP GOAL:
-
-Design the agent architecture — who's on your team? Simulate how agents might interact.
-
-## 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** — team designer
-- ✅ Focus on high-level planning (role, workflows, name, style)
-- ✅ Don't worry about YAML format — agent-builder handles that
-
-### Step-Specific Rules:
-- 🎯 Load `{agentArchitectureFile}` for guidance
-- 🎯 Party mode is great here — simulate agent interactions
-- 🚫 FORBIDDEN to design full agent specs (that's agent-builder's job)
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Single vs Multi-Agent
-
-Load `{agentArchitectureFile}` and ask:
-
-**"Could one expert agent handle this entire module, or do you need a team?"**
-
-Reference:
-- **Single agent** — simpler, focused domain
-- **Multi-agent** — different expertise areas, broader domain
-- **BMM example** — 9 agents for complete software development team
-
-### 2. Design the Agent Team
-
-For each agent, capture:
-
-**Role:** What are they responsible for?
-**Workflows:** Which workflows will they trigger?
-**Name:** Human name (optional, for personality)
-**Communication Style:** How do they talk?
-**Memory:** Do they need to remember things over time? (hasSidecar)
-
-Keep it high-level — don't design full agent specs!
-
-### 3. Party Mode Simulation
-
-**"Want to simulate how your agents might interact?"**
-
-- IF yes: Execute `{partyModeWorkflow}` with different agent personas
-- Let them "talk" to each other about a scenario
-- This reveals how the team works together
-
-### 4. Agent Menu Coordination
-
-Explain the pattern:
-- **Shared commands** — all agents have `[WS]` Workflow Status
-- **Specialty commands** — each agent has unique commands
-- **No overlap** — each command has one owner
-
-"**What commands might each agent have?**"
-
-### 5. MENU OPTIONS
-
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
-
-- IF A: Execute `{advancedElicitationTask}`
-- IF P: Execute `{partyModeWorkflow}` — great for agent interaction simulation
-- IF C: Load `{nextStepFile}`
-- IF Any other: Help, then redisplay
-
----
-
-## Success Metrics
-
-✅ Single vs multi-agent decided
-✅ Agent roles defined
-✅ Agent-workflow mappings clear
-✅ Agent interactions explored (via party mode if used)

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

@@ -1,82 +0,0 @@
----
-name: 'step-09-workflows'
-description: 'Workflow ecosystem — brainstorm what workflows could exist'
-
-nextStepFile: './step-10-tools.md'
-advancedElicitationTask: '../../../../core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '../../../../core/workflows/party-mode/workflow.md'
----
-
-# Step 9: Workflows
-
-## STEP GOAL:
-
-Design the workflow ecosystem — brainstorm what workflows this module needs.
-
-## 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** — workflow designer
-- ✅ Focus on what workflows exist, not their details
-- 💬 Brainstorm mode — generate lots of ideas
-
-### Step-Specific Rules:
-- 🎯 Categorize workflows: Core, Feature, Utility
-- 🚫 FORBIDDEN to design full workflow specs (that's create-workflow's job)
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Brainstorm Workflows
-
-"**What workflows should your module have?**"
-
-Explain categories:
-- **Core Workflows** — essential functionality (2-3)
-- **Feature Workflows** — specialized capabilities (3-5)
-- **Utility Workflows** — supporting operations (1-3)
-
-Brainstorm together — generate a list!
-
-### 2. For Each Workflow
-
-Capture briefly:
-
-**Workflow name:** {e.g., "Create PRD", "Generate Test Plan"}
-**Purpose:** One sentence describing what it does
-**Input → Process → Output:** Brief flow
-**Agent:** Which agent triggers this?
-
-### 3. Workflow Connections
-
-"**How do workflows connect?**"
-
-- Does workflow A feed into workflow B?
-- Are there dependencies?
-- What's the typical sequence?
-
-### 4. MENU OPTIONS
-
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
-
-- IF A: Execute `{advancedElicitationTask}` — great for workflow brainstorming
-- IF P: Execute `{partyModeWorkflow}` — different perspectives on workflows
-- IF C: Load `{nextStepFile}`
-- IF Any other: Help, then redisplay
-
----
-
-## Success Metrics
-
-✅ Workflow list generated (core, feature, utility)
-✅ Each workflow has a clear purpose
-✅ Agent-workflow mappings defined
-✅ Workflow connections understood