bmad-method 6.0.0-alpha.2 → 6.0.0-alpha.20

package/bmad/core/workflows/brainstorming/template.md

@@ -1,102 +0,0 @@
-# Brainstorming Session Results
-
-**Session Date:** {{date}}
-**Facilitator:** {{agent_role}} {{agent_name}}
-**Participant:** {{user_name}}
-
-## Executive Summary
-
-**Topic:** {{session_topic}}
-
-**Session Goals:** {{stated_goals}}
-
-**Techniques Used:** {{techniques_list}}
-
-**Total Ideas Generated:** {{total_ideas}}
-
-### Key Themes Identified:
-
-{{key_themes}}
-
-## Technique Sessions
-
-{{technique_sessions}}
-
-## Idea Categorization
-
-### Immediate Opportunities
-
-_Ideas ready to implement now_
-
-{{immediate_opportunities}}
-
-### Future Innovations
-
-_Ideas requiring development/research_
-
-{{future_innovations}}
-
-### Moonshots
-
-_Ambitious, transformative concepts_
-
-{{moonshots}}
-
-### Insights and Learnings
-
-_Key realizations from the session_
-
-{{insights_learnings}}
-
-## Action Planning
-
-### Top 3 Priority Ideas
-
-#### #1 Priority: {{priority_1_name}}
-
-- Rationale: {{priority_1_rationale}}
-- Next steps: {{priority_1_steps}}
-- Resources needed: {{priority_1_resources}}
-- Timeline: {{priority_1_timeline}}
-
-#### #2 Priority: {{priority_2_name}}
-
-- Rationale: {{priority_2_rationale}}
-- Next steps: {{priority_2_steps}}
-- Resources needed: {{priority_2_resources}}
-- Timeline: {{priority_2_timeline}}
-
-#### #3 Priority: {{priority_3_name}}
-
-- Rationale: {{priority_3_rationale}}
-- Next steps: {{priority_3_steps}}
-- Resources needed: {{priority_3_resources}}
-- Timeline: {{priority_3_timeline}}
-
-## Reflection and Follow-up
-
-### What Worked Well
-
-{{what_worked}}
-
-### Areas for Further Exploration
-
-{{areas_exploration}}
-
-### Recommended Follow-up Techniques
-
-{{recommended_techniques}}
-
-### Questions That Emerged
-
-{{questions_emerged}}
-
-### Next Session Planning
-
-- **Suggested topics:** {{followup_topics}}
-- **Recommended timeframe:** {{timeframe}}
-- **Preparation needed:** {{preparation}}
-
----
-
-_Session facilitated using the BMAD CIS brainstorming framework_

package/bmad/core/workflows/brainstorming/workflow.yaml

@@ -1,43 +0,0 @@
-# Brainstorming Session Workflow Configuration
-name: "brainstorming"
-description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."
-author: "BMad"
-
-# Critical variables load from config_source
-config_source: "{project-root}/bmad/cis/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-date: system-generated
-
-# Optional inputs for guided brainstorming
-recommended_inputs:
-  - session_context: "Context document passed via data attribute"
-  - previous_results: "{output_folder}/brainstorming-*.md"
-
-# Context can be provided via data attribute when invoking
-# Example: data="{path}/context.md" provides domain-specific guidance
-
-# Module path and component files
-installed_path: "{project-root}/bmad/core/workflows/brainstorming"
-template: "{installed_path}/template.md"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-brain_techniques: "{installed_path}/brain-methods.csv"
-
-# Output configuration
-default_output_file: "{output_folder}/brainstorming-session-results-{{date}}.md"
-
-standalone: true
-
-web_bundle:
-  name: "brainstorming"
-  description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."
-  author: "BMad"
-  template: "bmad/core/workflows/brainstorming/template.md"
-  instructions: "bmad/core/workflows/brainstorming/instructions.md"
-  brain_techniques: "bmad/core/workflows/brainstorming/brain-methods.csv"
-  use_advanced_elicitation: true
-  web_bundle_files:
-    - "bmad/core/workflows/brainstorming/instructions.md"
-    - "bmad/core/workflows/brainstorming/brain-methods.csv"
-    - "bmad/core/workflows/brainstorming/template.md"

package/bmad/core/workflows/party-mode/instructions.md

@@ -1,188 +0,0 @@
-# Party Mode - Multi-Agent Discussion Instructions
-
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
-<critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
-
-<workflow>
-
-<step n="1" goal="Load Agent Manifest and Configurations">
-  <action>Load the agent manifest CSV from {{manifest}}</action>
-  <action>Parse CSV to extract all agent entries with their condensed information:</action>
-    - name (agent identifier)
-    - displayName (agent's persona name)
-    - title (formal position)
-    - icon (visual identifier)
-    - role (capabilities summary)
-    - identity (background/expertise)
-    - communicationStyle (how they communicate)
-    - principles (decision-making philosophy)
-    - module (source module)
-    - path (file location)
-
-<action>For each agent found in manifest:</action>
-<check>Look for config override at {{agent_overrides}}[module]-[agent-name].customize.yaml</check>
-<action if="agent override exists">Load the override configuration</action>
-<action>MERGE override data with manifest data (overrides take precedence):</action> - Override role replaces manifest role if present - Override identity replaces manifest identity if present - Override communicationStyle replaces manifest communicationStyle if present - Override principles replace manifest principles if present - Any additional persona elements from override are added
-
-<action>Build complete agent roster with merged personalities</action>
-<action>Store agent data for use in conversation orchestration</action>
-</step>
-
-<step n="2" goal="Initialize Party Mode">
-  <action>Announce party mode activation with enthusiasm</action>
-  <action>List all participating agents with their merged information:</action>
-  <format>
-    🎉 PARTY MODE ACTIVATED! 🎉
-    All agents are here for a group discussion!
-
-    Participating agents:
-    [For each agent in roster:]
-    - [Agent Name] ([Title]): [Role from merged data]
-
-    [Total count] agents ready to collaborate!
-
-    What would you like to discuss with the team?
-
-  </format>
-  <action>Wait for user to provide initial topic or question</action>
-</step>
-
-<step n="3" goal="Orchestrate Multi-Agent Discussion" repeat="until-exit">
-  <action>For each user message or topic:</action>
-
-  <substep n="3a" goal="Determine Relevant Agents">
-    <action>Analyze the user's message/question</action>
-    <action>Identify which agents would naturally respond based on:</action>
-      - Their role and capabilities (from merged data)
-      - Their stated principles
-      - Their memories/context if relevant
-      - Their collaboration patterns
-    <action>Select 2-3 most relevant agents for this response</action>
-    <note>If user addresses specific agent by name, prioritize that agent</note>
-  </substep>
-
-  <substep n="3b" goal="Generate In-Character Responses">
-    <action>For each selected agent, generate authentic response:</action>
-    <action>Use the agent's merged personality data:</action>
-      - Apply their communicationStyle exactly
-      - Reflect their principles in reasoning
-      - Draw from their identity and role for expertise
-      - Maintain their unique voice and perspective
-
-    <action>Enable natural cross-talk between agents:</action>
-      - Agents can reference each other by name
-      - Agents can build on previous points
-      - Agents can respectfully disagree or offer alternatives
-      - Agents can ask follow-up questions to each other
-
-  </substep>
-
-  <substep n="3c" goal="Handle Questions and Interactions">
-    <check if="an agent asks the user a direct question">
-      <action>Clearly highlight the question</action>
-      <action>End that round of responses</action>
-      <action>Display: "[Agent Name]: [Their question]"</action>
-      <action>Display: "[Awaiting user response...]"</action>
-      <action>WAIT for user input before continuing</action>
-    </check>
-
-    <check if="agents ask each other questions">
-      <action>Allow natural back-and-forth in the same response round</action>
-      <action>Maintain conversational flow</action>
-    </check>
-
-    <check if="discussion becomes circular or repetitive">
-      <action>The BMad Master will summarize</action>
-      <action>Redirect to new aspects or ask for user guidance</action>
-    </check>
-
-  </substep>
-
-  <substep n="3d" goal="Format and Present Responses">
-    <action>Present each agent's contribution clearly:</action>
-    <format>
-      [Agent Name]: [Their response in their voice/style]
-
-      [Another Agent]: [Their response, potentially referencing the first]
-
-      [Third Agent if selected]: [Their contribution]
-    </format>
-
-    <action>Maintain spacing between agents for readability</action>
-    <action>Preserve each agent's unique voice throughout</action>
-
-  </substep>
-
-  <substep n="3e" goal="Check for Exit Conditions">
-    <check if="user message contains any {{exit_triggers}}">
-      <action>Have agents provide brief farewells in character</action>
-      <action>Thank user for the discussion</action>
-      <goto step="4">Exit party mode</goto>
-    </check>
-
-    <check if="user seems done or conversation naturally concludes">
-      <ask>Would you like to continue the discussion or end party mode?</ask>
-      <check if="user indicates end">
-        <goto step="4">Exit party mode</goto>
-      </check>
-    </check>
-
-  </substep>
-</step>
-
-<step n="4" goal="Exit Party Mode">
-  <action>Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other</action>
-  <format>
-    [Agent 1]: [Brief farewell in their style]
-
-    [Agent 2]: [Their goodbye]
-
-    🎊 Party Mode ended. Thanks for the great discussion!
-
-  </format>
-  <action>Exit workflow</action>
-</step>
-
-</workflow>
-
-## Role-Playing Guidelines
-
-<guidelines>
-  <guideline>Keep all responses strictly in-character based on merged personality data</guideline>
-  <guideline>Use each agent's documented communication style consistently</guideline>
-  <guideline>Reference agent memories and context when relevant</guideline>
-  <guideline>Allow natural disagreements and different perspectives</guideline>
-  <guideline>Maintain professional discourse while being engaging</guideline>
-  <guideline>Let agents reference each other naturally by name or role</guideline>
-  <guideline>Include personality-driven quirks and occasional humor</guideline>
-  <guideline>Respect each agent's expertise boundaries</guideline>
-</guidelines>
-
-## Question Handling Protocol
-
-<question-protocol>
-  <direct-to-user>
-    When agent asks user a specific question (e.g., "What's your budget?"):
-    - End that round immediately after the question
-    - Clearly highlight the questioning agent and their question
-    - Wait for user response before any agent continues
-  </direct-to-user>
-
-  <rhetorical>
-    Agents can ask rhetorical or thinking-aloud questions without pausing
-  </rhetorical>
-
-  <inter-agent>
-    Agents can question each other and respond naturally within same round
-  </inter-agent>
-</question-protocol>
-
-## Moderation Notes
-
-<moderation>
-  <note>If discussion becomes circular, have bmad-master summarize and redirect</note>
-  <note>If user asks for specific agent, let that agent take primary lead</note>
-  <note>Balance fun and productivity based on conversation tone</note>
-  <note>Ensure all agents stay true to their merged personalities</note>
-  <note>Exit gracefully when user indicates completion</note>
-</moderation>

package/bmad/core/workflows/party-mode/workflow.yaml

@@ -1,23 +0,0 @@
-# Party Mode - Multi-Agent Group Discussion Workflow
-name: "party-mode"
-description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
-author: "BMad"
-
-# Critical data sources - manifest and config overrides
-agent_manifest: "{project-root}/bmad/_cfg/agent-manifest.csv"
-agent_overrides: "{project-root}/bmad/_cfg/agents/*.customize.yaml"
-date: system-generated
-
-# This is an interactive action workflow - no template output
-template: false
-instructions: "{project-root}/bmad/core/workflows/party-mode/instructions.md"
-
-# Exit conditions
-exit_triggers:
-  - "*exit"
-  - "end party mode"
-  - "stop party mode"
-
-standalone: true
-
-web_bundle: false

package/bmad/docs/claude-code-instructions.md

@@ -1,25 +0,0 @@
-# BMAD Method - Claude Code Instructions
-
-## Activating Agents
-
-BMAD agents are installed as slash commands in `.claude/commands/bmad/`.
-
-### How to Use
-
-1. **Type Slash Command**: Start with `/` to see available commands
-2. **Select Agent**: Type `/bmad-{agent-name}` (e.g., `/bmad-dev`)
-3. **Execute**: Press Enter to activate that agent persona
-
-### Examples
-
-```
-/bmad:bmm:agents:dev - Activate development agent
-/bmad:bmm:agents:architect - Activate architect agent
-/bmad:bmm:workflows:dev-story - Execute dev-story workflow
-```
-
-### Notes
-
-- Commands are autocompleted when you type `/`
-- Agent remains active for the conversation
-- Start a new conversation to switch agents

package/bmad/docs/codex-instructions.md

@@ -1,21 +0,0 @@
-# BMAD Method - Codex Instructions
-
-## Activating Agents
-
-BMAD agents, tasks and workflows are installed as custom prompts in
-`$CODEX_HOME/prompts/bmad-*.md` files. If `CODEX_HOME` is not set, it
-defaults to `$HOME/.codex/`.
-
-### Examples
-
-```
-/bmad-bmm-agents-dev - Activate development agent
-/bmad-bmm-agents-architect - Activate architect agent
-/bmad-bmm-workflows-dev-story - Execute dev-story workflow
-```
-
-### Notes
-
-Prompts are autocompleted when you type /
-Agent remains active for the conversation
-Start a new conversation to switch agents

package/bmd/README.md

@@ -1,193 +0,0 @@
-# BMD - BMAD Development Module
-
-**Version:** 1.0.0-alpha.0
-**Purpose:** Specialized agents and tools for maintaining and developing the BMAD framework itself
-
-## Overview
-
-The BMD module is fundamentally different from other BMAD modules:
-
-- **BMM (BMad Method)** - Helps users build software projects using BMAD
-- **BMB (BMad Builder)** - Helps users create agents/workflows/modules for their projects
-- **CIS (Creative Intelligence Suite)** - Provides creative tools for any domain
-- **BMD (BMAD Development)** - Helps maintainers build and maintain BMAD itself
-
-## Who Is This For?
-
-- BMAD core contributors
-- Framework maintainers
-- Advanced users who want to enhance BMAD
-- Anyone working on the BMAD-METHOD repository
-
-## Agents
-
-### The Core Trinity
-
-BMD launches with three essential maintainer agents, forming the foundation of the BMAD development team:
-
----
-
-### Scott - Chief CLI Tooling Officer 🔧
-
-**Type:** Expert Agent with sidecar resources
-
-**Domain:** Complete mastery of `tools/cli/` infrastructure
-
-**Capabilities:**
-
-- Diagnose CLI installation and runtime issues
-- Configure IDE integrations (Codex, Cursor, etc.)
-- Build and update module installers
-- Configure installation question flows
-- Enhance CLI functionality
-- Maintain CLI documentation
-- Share installer and bundler patterns
-- Track known issues and solutions
-
-**Personality:** Star Trek Chief Engineer - systematic, urgent, and capable
-
-**Usage:**
-
-```bash
-/bmad:bmd:agents:cli-chief
-```
-
----
-
-### Commander - Chief Release Officer 🚀
-
-**Type:** Expert Agent with sidecar resources
-
-**Domain:** Release management, versioning, changelogs, deployments
-
-**Capabilities:**
-
-- Prepare releases with complete checklists
-- Generate changelogs from git history
-- Manage semantic versioning
-- Create and push git release tags
-- Validate release readiness
-- Publish to NPM registry
-- Create GitHub releases
-- Coordinate hotfix releases
-- Manage rollbacks if needed
-- Track release history and patterns
-
-**Personality:** Space Mission Control - calm, precise, checklist-driven
-
-**Usage:**
-
-```bash
-/bmad:bmd:agents:release-chief
-```
-
----
-
-### Atlas - Chief Documentation Keeper 📚
-
-**Type:** Expert Agent with sidecar resources
-
-**Domain:** All documentation files, guides, examples, README accuracy
-
-**Capabilities:**
-
-- Audit documentation for accuracy
-- Validate links and cross-references
-- Verify and update code examples
-- Synchronize docs with code changes
-- Update README files across project
-- Generate API documentation
-- Check documentation style and consistency
-- Identify documentation gaps
-- Track documentation health metrics
-- Maintain CHANGELOG accuracy
-
-**Personality:** Nature Documentarian - observational, precise, finding wonder in organization
-
-**Usage:**
-
-```bash
-/bmad:bmd:agents:doc-keeper
-```
-
----
-
-### Future Agents
-
-The BMD module will continue to expand with:
-
-- **Bundler Expert** - Web bundle compilation and validation specialist
-- **Architecture Guardian** - Code pattern enforcement and structural integrity
-- **Testing Coordinator** - Test coverage, CI/CD management, quality gates
-- **Workflow Auditor** - Audits BMAD's own internal workflows
-- **Issue Triager** - GitHub issue classification and management
-- **Migration Assistant** - Version upgrade assistance and breaking change handling
-- **Code Quality Enforcer** - ESLint/Prettier enforcement and technical debt tracking
-- **Dependency Manager** - NPM package management and security scanning
-
-## Installation
-
-Since BMD is part of the BMAD-METHOD source, install it like any other module:
-
-```bash
-npm run install:bmad -- --target . --modules bmd --ides codex --non-interactive
-```
-
-Or for contributors working directly in BMAD-METHOD:
-
-```bash
-npm run install:bmad -- --target /path/to/BMAD-METHOD --modules bmd --ides codex
-```
-
-## Module Structure
-
-```
-src/modules/bmd/
-├── agents/
-│   ├── cli-chief.agent.yaml           # Scott - CLI expert
-│   ├── cli-chief-sidecar/             # Scott's workspace
-│   │   ├── memories.md
-│   │   ├── instructions.md
-│   │   └── knowledge/
-│   ├── release-chief.agent.yaml       # Commander - Release manager
-│   ├── release-chief-sidecar/         # Commander's workspace
-│   │   ├── memories.md
-│   │   ├── instructions.md
-│   │   └── knowledge/
-│   ├── doc-keeper.agent.yaml          # Atlas - Documentation keeper
-│   └── doc-keeper-sidecar/            # Atlas's workspace
-│       ├── memories.md
-│       ├── instructions.md
-│       └── knowledge/
-├── workflows/                         # Future: release prep, validation
-├── config.yaml                        # Module configuration
-└── README.md                          # This file
-```
-
-## Development Philosophy
-
-BMD agents are **maintainers**, not just helpers. They:
-
-- Build institutional knowledge over time
-- Remember past issues and solutions
-- Evolve with the framework
-- Become true partners in development
-- Focus on specific domains (CLI, bundler, releases, etc.)
-
-## Contributing
-
-When adding new BMD agents:
-
-1. Consider if it's truly for BMAD development (not user project development)
-2. Use Expert agent type for domain-specific maintainers
-3. Include comprehensive sidecar resources
-4. Document the domain boundaries clearly
-5. Build knowledge accumulation into the agent
-
-## Vision
-
-BMD agents will become the "senior engineering team" for BMAD itself - each with deep expertise in their domain, able to guide contributors, maintain quality, and evolve the framework intelligently.
-
-## License
-
-Same as BMAD-METHOD repository