create-byan-agent 2.1.0 → 2.1.1

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

@@ -1,160 +0,0 @@
----
-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/_bmad/bmb/workflows/module/steps-c/step-05-agents.md

@@ -1,167 +0,0 @@
----
-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

package/_bmad/bmb/workflows/module/steps-c/step-06-workflows.md

@@ -1,183 +0,0 @@
----
-name: 'step-06-workflows'
-description: 'Create workflow placeholder/spec files'
-
-nextStepFile: './step-07-docs.md'
-workflowSpecTemplate: '../../templates/workflow-spec-template.md'
-buildTrackingFile: '{bmad_creations_output_folder}/modules/module-build-{module_code}.md'
-targetLocation: '{build_tracking_targetLocation}'
----
-
-# Step 6: Workflow Specs
-
-## STEP GOAL:
-
-Create workflow 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 workflow specs
-- ✅ These are specs, not full workflows (workflow-builder does that)
-- ✅ Keep it high-level
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Get Workflow List from Brief
-
-Extract from the brief:
-- Core workflows
-- Feature workflows
-- Utility workflows
-
-For each workflow:
-- Name
-- Purpose/goal
-- Primary agent
-- Input/output requirements
-
-### 2. For Each Workflow, Create Spec
-
-Load `{workflowSpecTemplate}` and create:
-
-`{targetLocation}/workflows/{workflow_name}/{workflow_name}.spec.md`
-
-With content:
-```markdown
-# Workflow Specification: {workflow_name}
-
-**Module:** {module_code}
-**Status:** Placeholder — To be created via create-workflow workflow
-**Created:** {date}
-
----
-
-## Workflow Overview
-
-**Goal:** {workflow_goal}
-
-**Description:** {workflow_description}
-
-**Workflow Type:** {workflow_type}
-
----
-
-## Workflow Structure
-
-### Entry Point
-
-```yaml
----
-name: {workflow_name}
-description: {workflow_description}
-web_bundle: true
-installed_path: '{project-root}/_bmad/{module_code}/workflows/{workflow_folder_name}'
----
-```
-
-### Mode
-
-- [ ] Create-only (steps-c/)
-- [ ] Tri-modal (steps-c/, steps-e/, steps-v/)
-
----
-
-## Planned Steps
-
-| Step | Name | Goal |
-|------|------|------|
-{workflow_steps_table}
-
----
-
-## Workflow Inputs
-
-### Required Inputs
-
-{required_inputs}
-
-### Optional Inputs
-
-{optional_inputs}
-
----
-
-## Workflow Outputs
-
-### Output Format
-
-- [ ] Document-producing
-- [ ] Non-document
-
-### Output Files
-
-{output_files}
-
----
-
-## Agent Integration
-
-### Primary Agent
-
-{primary_agent}
-
-### Other Agents
-
-{other_agents}
-
----
-
-## Implementation Notes
-
-**Use the create-workflow workflow to build this workflow.**
-
----
-
-_Spec created on {date} via BMAD Module workflow_
-```
-
-### 3. Create All Workflow Specs
-
-Iterate through each workflow from the brief and create their spec file.
-
-### 4. Update Build Tracking
-
-Update `{buildTrackingFile}`:
-- Add 'step-06-workflows' to stepsCompleted
-- List all workflow specs created
-
-### 5. Report Success
-
-"**✓ Workflow specs created:**"
-
-- {count} workflow spec files
-- {list workflow names}
-
-"**These are specs/blueprints. Use the create-workflow workflow to build each workflow.**"
-
-### 6. MENU OPTIONS
-
-**Select an Option:** [C] Continue
-
-- IF C: Update tracking, load `{nextStepFile}`
-- IF Any other: Help, then redisplay menu
-
----
-
-## Success Metrics
-
-✅ Workflow spec files created for all workflows
-✅ Each spec has goal, steps, inputs/outputs
-✅ Agent associations documented
-✅ Build tracking updated