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

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

@@ -0,0 +1,83 @@
+---
+name: 'step-01b-continue'
+description: 'Handle workflow continuation for Create mode'
+
+workflowFile: '../workflow.md'
+buildTrackingFile: '{bmb_creations_output_folder}/modules/module-build-{module_code}.md'
+---
+
+# Step 1b: Continue (Create Mode)
+
+## STEP GOAL:
+
+Resume a paused Create mode session by loading the build tracking state and routing to the correct step.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the **Module Builder** — picking up where we left off
+- ✅ Warm welcome back
+- ✅ Seamless resume
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Welcome Back
+
+"**Welcome back to the Module Builder!** 👋"
+
+### 2. Load Build Tracking
+
+Load `{buildTrackingFile}` and read:
+- `stepsCompleted` array
+- `moduleCode`
+- `moduleName`
+- `moduleType`
+- `status`
+
+### 3. Report Progress
+
+"**Here's where we are:**"
+
+**Module:** {moduleName} ({moduleCode})
+**Type:** {moduleType}
+**Status:** {status}
+
+**Completed steps:**
+- {list completed steps}
+
+### 4. Determine Next Step
+
+Find the last completed step and route to the next one:
+
+| Last Completed | Next Step |
+|---------------|-----------|
+| step-01-load-brief | step-02-structure |
+| step-02-structure | step-03-config |
+| step-03-config | step-04-installer |
+| step-04-installer | step-05-agents |
+| step-05-agents | step-06-workflows |
+| step-06-workflows | step-07-docs |
+| step-07-docs | step-08-complete |
+
+### 5. Route to Next Step
+
+"**Continuing to: {next step name}**"
+
+Load the appropriate step file and execute.
+
+---
+
+## Success Metrics
+
+✅ User welcomed back
+✅ Build state loaded
+✅ Correct next step identified
+✅ Seamless resume

package/src/modules/bmb/workflows/module/steps-c/step-02-structure.md

@@ -0,0 +1,109 @@
+---
+name: 'step-02-structure'
+description: 'Create directory structure based on module type'
+
+nextStepFile: './step-03-config.md'
+moduleStandardsFile: '../../data/module-standards.md'
+buildTrackingFile: '{bmb_creations_output_folder}/modules/module-build-{module_code}.md'
+---
+
+# Step 2: Directory Structure
+
+## STEP GOAL:
+
+Create the module directory structure based on the module type (Standalone/Extension/Global).
+
+## 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** — creating the foundation
+- ✅ Structure follows standards
+- ✅ Confirm before creating
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Determine Target Location
+
+Load `{moduleStandardsFile}` and determine location:
+
+**IF Standalone:**
+- Target: `src/modules/{module_code}/`
+
+**IF Extension:**
+- Target: `src/modules/{base_module_code}/extensions/{extension_folder_name}/`
+- Get base_module_code from brief
+- extension_folder_name: unique name (e.g., `{base_module}-{feature}`)
+
+**IF Global:**
+- Target: `src/modules/{module_code}/`
+- Will add `global: true` to module.yaml
+
+### 2. Present Structure Plan
+
+"**I'll create this directory structure:**"
+
+```
+{target_location}/
+├── module.yaml
+├── README.md
+├── agents/
+│   └── {agent files}
+├── workflows/
+│   └── {workflow folders}
+└── _module-installer/
+    ├── installer.js
+    └── platform-specifics/
+```
+
+"**Location:** {target_location}"
+"**Module type:** {Standalone/Extension/Global}"
+
+### 3. Confirm and Create
+
+"**Shall I create the directory structure?**"
+
+**IF confirmed:**
+
+Create folders:
+- `{target_location}/agents/`
+- `{target_location}/workflows/`
+- `{target_location}/_module-installer/`
+- `{target_location}/_module-installer/platform-specifics/`
+
+### 4. Update Build Tracking
+
+Update `{buildTrackingFile}`:
+- Add 'step-02-structure' to stepsCompleted
+- Set targetLocation
+- Update status
+
+### 5. Report Success
+
+"**✓ Directory structure created at:** {target_location}"
+
+### 6. MENU OPTIONS
+
+**Select an Option:** [C] Continue
+
+- IF C: Update tracking, load `{nextStepFile}`
+- IF Any other: Help, then redisplay menu
+
+---
+
+## Success Metrics
+
+✅ Directory structure created
+✅ Location based on module type
+✅ Folders: agents/, workflows/, _module-installer/
+✅ Build tracking updated

package/src/modules/bmb/workflows/module/steps-c/step-03-config.md

@@ -0,0 +1,118 @@
+---
+name: 'step-03-config'
+description: 'Generate module.yaml with install questions'
+
+nextStepFile: './step-04-installer.md'
+moduleYamlConventionsFile: '../../data/module-yaml-conventions.md'
+buildTrackingFile: '{bmb_creations_output_folder}/modules/module-build-{module_code}.md'
+targetLocation: '{build_tracking_targetLocation}'
+---
+
+# Step 3: Module Configuration
+
+## STEP GOAL:
+
+Generate module.yaml with install configuration and custom variables.
+
+## 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** — configuration expert
+- ✅ Follow module.yaml conventions
+- ✅ Ask about custom variables
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Load Conventions
+
+Load `{moduleYamlConventionsFile}` for reference.
+
+### 2. Generate Base module.yaml
+
+Create `{targetLocation}/module.yaml` with:
+
+**Required fields:**
+```yaml
+code: {module_code}
+name: "{module_display_name}"
+header: "{brief_header}"
+subheader: "{additional_context}"
+default_selected: false
+```
+
+**Note for Extension modules:** `code:` matches base module
+
+### 3. Add Custom Variables
+
+"**Does your module need any custom configuration variables?**"
+
+Reference the brief for:
+- User input needed during installation
+- Paths or settings users should configure
+- Feature flags or options
+
+**For each variable, create:**
+```yaml
+variable_name:
+  prompt: "{question to ask}"
+  default: "{default_value}"
+  result: "{template}"
+```
+
+**Common patterns:**
+- Text input (names, titles)
+- Boolean (enable features)
+- Single-select (experience levels)
+- Multi-select (platforms)
+- Paths (artifact folders)
+
+**IF no custom variables needed:**
+
+Keep it simple — just use core config variables.
+
+### 4. Write module.yaml
+
+Write the complete module.yaml to `{targetLocation}/module.yaml`
+
+### 5. Update Build Tracking
+
+Update `{buildTrackingFile}`:
+- Add 'step-03-config' to stepsCompleted
+- Note: module.yaml created
+
+### 6. Report and Confirm
+
+"**✓ module.yaml created with:**"
+
+- Code: {code}
+- {count} custom variables
+
+"**Review the file and confirm it looks correct.**"
+
+### 7. MENU OPTIONS
+
+**Select an Option:** [C] Continue
+
+- IF C: Update tracking, load `{nextStepFile}`
+- IF Any other: Help, then redisplay menu
+
+---
+
+## Success Metrics
+
+✅ module.yaml created
+✅ Required fields populated
+✅ Custom variables added (if any)
+✅ Extension modules use correct code
+✅ Build tracking updated

package/src/modules/bmb/workflows/module/steps-c/step-04-installer.md

@@ -0,0 +1,160 @@
+---
+name: 'step-04-installer'
+description: 'Setup _module-installer folder and installer.js'
+
+nextStepFile: './step-05-agents.md'
+moduleInstallerStandardsFile: '../../data/module-installer-standards.md'
+buildTrackingFile: '{bmb_creations_output_folder}/modules/module-build-{module_code}.md'
+targetLocation: '{build_tracking_targetLocation}'
+---
+
+# Step 4: Module Installer
+
+## STEP GOAL:
+
+Setup the _module-installer folder and create installer.js if needed.
+
+## 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** — installer expert
+- ✅ Not all modules need installers
+- ✅ Follow installer patterns
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Assess Need for Installer
+
+Load `{moduleInstallerStandardsFile}` and ask:
+
+"**Does your module need an installer?**"
+
+Installers are needed when:
+- Creating directories from config variables
+- Copying template/assets
+- IDE-specific configuration
+- Platform-specific setup
+
+**If NO installer needed:**
+
+Skip to step 5. Folder structure already exists.
+
+**If YES:** Continue to step 4.2
+
+### 2. Determine Installer Requirements
+
+"**What should the installer do?**"
+
+- Create directories? (which variables)
+- Copy assets? (from where)
+- IDE configuration? (which IDEs)
+- Platform-specific setup?
+
+### 3. Create installer.js
+
+Create `{targetLocation}/_module-installer/installer.js`:
+
+```javascript
+const fs = require('fs-extra');
+const path = require('node:path');
+const chalk = require('chalk');
+const platformCodes = require(path.join(__dirname, '../../../../tools/cli/lib/platform-codes'));
+
+/**
+ * {module_name} Module Installer
+ */
+async function install(options) {
+  const { projectRoot, config, installedIDEs, logger } = options;
+
+  try {
+    logger.log(chalk.blue('Installing {module_name}...'));
+
+    // Create directories
+    if (config['{variable_name}']) {
+      const dirConfig = config['{variable_name}'].replace('{project-root}/', '');
+      const dirPath = path.join(projectRoot, dirConfig);
+      if (!(await fs.pathExists(dirPath))) {
+        logger.log(chalk.yellow(`Creating directory: ${dirConfig}`));
+        await fs.ensureDir(dirPath);
+      }
+    }
+
+    // IDE-specific configuration
+    if (installedIDEs && installedIDEs.length > 0) {
+      for (const ide of installedIDEs) {
+        await configureForIDE(ide, projectRoot, config, logger);
+      }
+    }
+
+    logger.log(chalk.green('✓ {module_name} installation complete'));
+    return true;
+  } catch (error) {
+    logger.error(chalk.red(`Error installing module: ${error.message}`));
+    return false;
+  }
+}
+
+async function configureForIDE(ide, projectRoot, config, logger) {
+  if (!platformCodes.isValidPlatform(ide)) {
+    logger.warn(chalk.yellow(`Unknown platform: '${ide}'. Skipping.`));
+    return;
+  }
+
+  const platformSpecificPath = path.join(__dirname, 'platform-specifics', `${ide}.js`);
+
+  try {
+    if (await fs.pathExists(platformSpecificPath)) {
+      const platformHandler = require(platformSpecificPath);
+      if (typeof platformHandler.install === 'function') {
+        await platformHandler.install({ projectRoot, config, logger });
+      }
+    }
+  } catch (error) {
+    logger.warn(chalk.yellow(`Warning: Could not configure ${ide}: ${error.message}`));
+  }
+}
+
+module.exports = { install };
+```
+
+Customize based on module requirements.
+
+### 4. Platform-Specific Handlers (Optional)
+
+If IDE-specific setup needed, ask which IDEs and create:
+- `{targetLocation}/_module-installer/platform-specifics/claude-code.js`
+- `{targetLocation}/_module-installer/platform-specifics/windsurf.js`
+- etc.
+
+### 5. Update Build Tracking
+
+Update `{buildTrackingFile}`:
+- Add 'step-04-installer' to stepsCompleted
+- Note: installer created or skipped
+
+### 6. MENU OPTIONS
+
+**Select an Option:** [C] Continue
+
+- IF C: Update tracking, load `{nextStepFile}`
+- IF Any other: Help, then redisplay menu
+
+---
+
+## Success Metrics
+
+✅ Assessed installer need
+✅ installer.js created (if needed)
+✅ Platform handlers created (if needed)
+✅ Build tracking updated

package/src/modules/bmb/workflows/module/steps-c/step-05-agents.md

@@ -0,0 +1,167 @@
+---
+name: 'step-05-agents'
+description: 'Create agent placeholder/spec files'
+
+nextStepFile: './step-06-workflows.md'
+agentSpecTemplate: '../../templates/agent-spec-template.md'
+agentArchitectureFile: '../../data/agent-architecture.md'
+buildTrackingFile: '{bmb_creations_output_folder}/modules/module-build-{module_code}.md'
+targetLocation: '{build_tracking_targetLocation}'
+---
+
+# Step 5: Agent Specs
+
+## STEP GOAL:
+
+Create agent placeholder/spec files based on the brief.
+
+## 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** — creating agent specs
+- ✅ These are specs, not full agents (agent-builder does that)
+- ✅ Keep it high-level
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Load Agent Architecture
+
+Load `{agentArchitectureFile}` for guidance.
+
+### 2. Get Agent Roster from Brief
+
+Extract from the brief:
+- Agent names
+- Roles
+- Workflows they're responsible for
+- Communication style
+- Memory needs (hasSidecar)
+
+### 3. For Each Agent, Create Spec
+
+Load `{agentSpecTemplate}` and create:
+
+`{targetLocation}/agents/{agent_name}.spec.md`
+
+With content:
+```markdown
+# Agent Specification: {agent_name}
+
+**Module:** {module_code}
+**Status:** Placeholder — To be created via create-agent workflow
+**Created:** {date}
+
+---
+
+## Agent Metadata
+
+```yaml
+agent:
+  metadata:
+    id: "_bmad/{module_code}/agents/{agent_file_name}.md"
+    name: {agent_human_name}
+    title: {agent_title}
+    icon: {agent_icon}
+    module: {module_code}
+    hasSidecar: {false/true}
+```
+
+---
+
+## Agent Persona
+
+### Role
+
+{agent_role}
+
+### Identity
+
+{agent_identity}
+
+### Communication Style
+
+{agent_communication_style}
+
+### Principles
+
+{agent_principles}
+
+---
+
+## Agent Menu
+
+### Planned Commands
+
+| Trigger | Command | Description | Workflow |
+|---------|---------|-------------|----------|
+{agent_menu_table}
+
+---
+
+## Agent Integration
+
+### Shared Context
+
+- References: `{shared_context_files}`
+- Collaboration with: {collaborating_agents}
+
+### Workflow References
+
+{workflow_references}
+
+---
+
+## Implementation Notes
+
+**Use the create-agent workflow to build this agent.**
+
+---
+
+_Spec created on {date} via BMAD Module workflow_
+```
+
+### 4. Create All Agent Specs
+
+Iterate through each agent from the brief and create their spec file.
+
+### 5. Update Build Tracking
+
+Update `{buildTrackingFile}`:
+- Add 'step-05-agents' to stepsCompleted
+- List all agent specs created
+
+### 6. Report Success
+
+"**✓ Agent specs created:**"
+
+- {count} agent spec files
+- {list agent names}
+
+"**These are specs/blueprints. Use the create-agent workflow to build each agent.**"
+
+### 7. MENU OPTIONS
+
+**Select an Option:** [C] Continue
+
+- IF C: Update tracking, load `{nextStepFile}`
+- IF Any other: Help, then redisplay menu
+
+---
+
+## Success Metrics
+
+✅ Agent spec files created for all agents
+✅ Each spec has role, workflows, menu triggers
+✅ hasSidecar documented (memory decision)
+✅ Build tracking updated