create-byan-agent 2.1.0 → 2.1.1

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

@@ -1,117 +0,0 @@
----
-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/_bmad/bmb/workflows/module/steps-c/step-01-load-brief.md

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

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

@@ -1,83 +0,0 @@
----
-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/_bmad/bmb/workflows/module/steps-c/step-02-structure.md

@@ -1,109 +0,0 @@
----
-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/_bmad/bmb/workflows/module/steps-c/step-03-config.md

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