bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.1

package/readme.md

@@ -1,216 +0,0 @@
-# BMad CORE v6 Alpha
-
-[![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
-[![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
-
-**The Universal Human-AI Collaboration Platform**
-
-IMPORTANT NOTE: ALPHA is potentially an unstable release that could drastically change in many ways. While we hope that is not the case, know that it could - your using and testing it during this time though is much appreciated. Please help us out by filing issues or reaching out in Discord to discuss.
-
-IMPORTANT NOTE 2: ALPHA is not complete - there are still many small and big features, polish, doc improvements, and more agents and workflows coming ahead of the beta release!
-
-IMPORTANT NOTE 3: ALPHA Web Bundles and Agents are not fully working yet - so you will need to use a good quality IDE to test many of the features, especially with the BMad Method module. BUT - the new agent builder and stand alone agent feature can work great with weaker models - this will still evolve over the coming weeks.
-
-BMad-CORE (Collaboration Optimized Reflection Engine) is a framework that brings out the best in you through AI agents designed to enhance human thinking rather than replace it. Unlike traditional AI tools that do the work for you, BMad-CORE's specialized agents guide you through the facilitation of optimized collaborative reflective workflows to unlock your full potential across any domain. It is this magic that powers the BMad Method, which is just one of the many modules that exist or are coming soon.
-
-**[Subscribe to BMadCode on YouTube](https://www.youtube.com/@BMadCode?sub_confirmation=1)** and **[Join our amazing, active Discord Community](https://discord.gg/gk8jAdXWmj)**
-
-⭐ **If you find this project helpful or useful, please give it a star in the upper right-hand corner!** It helps others discover BMad-CORE and you will be notified of updates!
-
-## What Makes BMad-Core Different
-
-**Traditional AI**: Does the thinking for you, providing average, bland answers and solutions
-**BMad-CORE**: Brings out the best thinking in you and the AI through guided collaboration, elicitation, and facilitation
-
-### Core Philosophy: Human Amplification, Not Replacement
-
-BMad-Core's AI agents act as expert coaches, mentors, and collaborators who:
-
-- Ask the right questions to stimulate your thinking
-- Provide structured frameworks for complex problems
-- Guide you through reflective processes to discover insights
-- Help you develop mastery in your chosen domains
-- Amplify your natural abilities rather than substituting for them
-
-## The Collaboration Optimized Reflection Engine
-
-At the heart of BMad-Core lies the **C.O.R.E.** system:
-
-- **Collaboration**: Human-AI partnership where both contribute unique strengths
-- **Optimized**: The collaborative process has been refined for maximum effectiveness
-- **Reflection**: Guided thinking that helps you discover better solutions and insights
-- **Engine**: The powerful framework that orchestrates specialized agents and workflows
-
-## Universal Domain Coverage Through Modules
-
-BMad-CORE works in ANY domain through specialized modules (previously called expansion packs)!
-
-### Available Modules with Alpha Release
-
-- **BMad Core (core)**: Included and used to power every current and future module; includes a master orchestrator for the local environment and one for the web bundles used with ChatGPT or Gemini Gems, for example.
-- **BMad Method (bmm)**: Agile AI-driven software development - the classic that started it all and is still the best - but with v6, massively improved thanks to a rebuild from the ground up built on the new powerful BMad-CORE engine. The BMad Method has also been expanded to use a new "Scale Adaptive Workflow Engine"™.
-- **BMad BoMB (bmb)**: The BMad Builder is your Custom Agent, Workflow, and Module authoring tool - it's now easier than ever to customize existing modules or create whatever you can imagine as a standalone module.
-- **Creative Intelligence Suite (cis)**: Unlock innovation, problem-solving, and creative thinking! Brainstorming that was part of the BMad Method in the past is now part of this standalone module along with other workflows. The power of BMad modules still allows modules to borrow from each other - so the CIS, while standalone, also powers the brainstorming abilities for certain agents within the BMad Method!
-
-## Alpha Installation and Testing
-
-**Prerequisites**: [Node.js](https://nodejs.org) v20+ required
-
-Clone this repo ALPHA BRANCH to a folder. From the root of the folder, run `npm run install:bmad` and follow the installer questions.
-
-The Core Module will always be installed. The default initial module selection will be BMM for all the core BMad Method functionality and flow from brainstorming through software development.
-
-Note on installation: All installs now go to a single folder called `bmad` instead of multiple folders. When you install a module, you may still see folders other than the one you selected in the destination/bmad folder. This is intentional and not a bug - it will copy over to those other folders only the minimum that is needed because it is shared across the modules. For example, for now during Alpha to test this feature - BMM relies on the brainstorming feature of the CIS and some items from CORE - so this is why even if you only select BMM, you will still see bmad/core and bmad/cis along with bmad/bmm.
-
-## What's New in V6-ALPHA
-
-Stability, customizability, installation Q&A, massive prompt improvements.
-
-Everything has been rewritten from the ground up with best practices and advances learned over previous versions, standardizing on prompt format techniques. There is a lot more core usage of XML or XML-type tags within markdown, with many conventions and standards that drastically increase adherence of the agents.
-
-Customizability is a key theme of this new version. All agents are now customizable by modifying a file under the installation bmad/\_cfg/agents. Every agent installed will generate an agent file that you can customize. The nice thing about this is when agents change or update in future versions, your customizations in these sidecar files will never be lost! You can change the name, their personas, how they talk, what they call you, and most exciting - what language they communicate in!
-
-The BMad installer is 100% new from the ground up. First, along the way you will add your name (what the agents will call you and what you will author documents as), what language you want the agents to talk to you in, and every module you select will have its own set of questions to customize the experience. Also, when you install, a consolidated agent party is created so now when you use party-mode in the IDE, it is super efficient for the agent running the party to simulate all installed agents. Post alpha release, this will manifest itself in many interesting ways in time for beta - but for now, have fun with party mode and epic sprint retrospectives!
-
-Speaking of installation - everything will now install to a single core bmad folder. No more separate root folders for every module! Instead, all will be contained within bmad/.
-
-All IDE selections now support the option to add in special install functionality per module. As an example with the alpha release, if you select the BMad Method and Claude Code, you will have an option to install pre-created Claude sub-agents. Not only do they get installed, but certain workflows will have injected into their instructions key indicators to the agent when to activate the sub-agents, removing some non-determinism. The sub-agent experience is still undergoing some work, so install them if you choose, and remove them if they become a pain.
-
-Also, when you read about the BoMB below, it will link to more information about various features in this new evolution of the BMad Code - one of the exciting ones is the new agent types - there are 3 now! The most exciting, with more info coming soon, are the new standalone tiny agents that you can easily generate and deploy free from any module - specialized for your own exact needs.
-
-### BMad Method
-
-The BMad Method is significantly transforming and yet more powerful than ever. **Scale Adaptive** is a new term that means when you start the workflow to create a PRD or a GDD (or a simple tech-spec in the case of simple tasks), you will first answer some questions about the scope of the project, new vs. existing codebase and its state, and other questions. This will trigger a leveling of the effort from 0-4, and based on this scale adaptation, it will guide the workflow in different directions.
-
-Right now, this is still a bit alpha feeling and disjointed, but before beta it will be tied together through all four workflow phases with a potential single orchestration if you choose - or you can still jump right in, especially for simple tasks that just need a simple tech-spec and then right off to development.
-
-To test and experience this now, here is the new main flow for BMM v6 alpha:
-
-(Docs will be all linked in soon with new user guide and workflow diagrams coming this week)
-
-NOTE: Game Development expansion packs are all being rolled into the official BNad Method module - along with any more game engine platforms being added. Additionally game development planning for the GDD is not only scale adpative, but also adapts to the type of game you are making - so you can plan all that is needed for your dream game!
-
-#### **PHASE 1 - Analysis**
-
-**Analyst:**
-
-- `brainstorm-project`
-- `research` (market research, deep research, deep research prompt generation)
-- `product-brief`
-
-**Game Designer (Optional):**
-
-- `brainstorm-game`
-- `game-brief`
-- `research`
-
----
-
-#### **PHASE 2 - Planning**
-
-**PM:**
-
-- `plan-project`
-
-**Game Designer:**
-
-- `plan-game` (calls the same plan-project workflow, but input docs or your answers should drive it towards GDD)
-
----
-
-#### **PHASE 3 - Solutioning**
-
-**Architect or Game Architect:**
-
-Just like the scale-adjusted planning, architecture is the same. No more document sharding though!! Now in the IDE you create an architecture that adapts to the type of project you are working on - based on the inputs from your PRD, it will adapt the sections it includes to your project type. No longer is the architecture biased just towards full stack or back-end APIs. There are many more options now, from embedded hardware to mobile to many other options - with many more coming with beta.
-
-- `solution-architecture`
-
-> **Note:** Testing, DevOps, or security concerns beyond the basics are generally not included in the architecture. If it is more complicated, especially for complex massive undertakings, you will be suggested to pull in specific agents to help with those areas. _(Not released with alpha.0, coming soon)_
-
-Once the full architecture is complete, you can still use the PO to run the checklist to validate the epics and stories are still correct - although the architect should also be keeping them updated as needed (needs some tuning during alpha). Once done, then it's time to create the tech spec for your first epic.
-
-- `tech-spec`
-
-The tech spec pulls all technical information from all planning thus far, along with any further research needed from the web to produce an **Epic Tech Spec** - each epic will have one. This is going to make the SM even more capable of finding the info it needs for each story when we get to phase 4!!
-
----
-
-#### **PHASE 4 - Implementation**
-
-And now here we are at phase 4 - where we, just like in BMad Method of yore, use the SM and the Dev Agent. No more QA agent here though; the dev now has a dev task and also a senior dev agent review task.
-
-**Scrum Master (SM) Tasks:**
-
-Before the dev starts, the SM will:
-
-1. `create-story`
-2. `story-context` _(NEW!)_
-
-**Story-context** is a game-changing new feature beyond what we had with create-story in the past. Create-story still pulls in all the info it needs from the tech-spec and elsewhere as needed (including previously completed stories), but the generation of the new story-context takes it up a whole new level.
-
-This real-time prep means no more generic devLoadAlways list of story files. During the alpha phase, we will be tuning what goes into this context, but this is going to supercharge and specialize your dev to the story at hand!
-
----
-
-> **🎉 There are many other exciting changes throughout for you to discover during the alpha BMad Method module!**
-
-## CIS
-
-The CIS has 5 agents to try out, each with their own workflow! This is a new module that will drastically change over time.
-
-- [CIS Readme](./src/modules/cis/readme.md)
-
-### BoMB: BMad Builder
-
-#### Agent Docs
-
-- [Agent Architecture](src/modules/bmb/workflows/create-agent/agent-architecture)
-- [Agent command patterns](src/modules/bmb/workflows/create-agent/agent-command-patterns.md)
-- [Agent Types](src/modules/bmb/workflows/create-agent/agent-types.md)
-- [Communication Styles](src/modules/bmb/workflows/create-agent/communication-styles.md)
-
-#### Modules
-
-Modules are what we used to call Expansion Packs. A new repository to contribute modules is coming very soon with the beta release where you can start contributing modules - we just want to make sure the final format and conventions are stable. A module will generally be made up of agents and workflows. Tasks are still also possible, but generally should be avoided in favor of more flexible workflows. Workflows can have sub-workflows and soon will support a standardized multi-workflow orchestration pattern that the BMad master will be able to guide users through.
-
-- [Module Structure](src/modules/bmb/workflows/create-module/module-structure.md)
-
-#### Workflows
-
-What used to be tasks and create-doc templates are now all workflows! Simpler, yet more powerful and support many ways of achieving many different outcomes! A lot more documentation will be coming. This document is used by the agent builder to generate workflows or convert to workflows, but there is a lot more than what we have documented here in this alpha doc.
-
-- [Workflow Creation Guide](src/modules/bmb/workflows/create-workflow/workflow-creation-guide)
-
-### Installer Changes
-
-- [IDE Injections](docs/installers-bundlers/ide-injections)
-- [Installers Modules Platforms References](docs/installers-bundlers/installers-modules-platforms-reference)
-- [Web Bundler Usage](docs/installers-bundlers/web-bundler-usage)
-- [Claude Code Sub Module BMM Installer](src/modules/bmm/sub-modules/claude-code/readme.md)
-
-## Support & Community
-
-- 💬 [Discord Community](https://discord.gg/gk8jAdXWmj) - Get help, share ideas, collaborate
-- 🐛 [Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues) - Bug reports and feature requests
-- 💬 [Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions) - Community conversations
-
-## Contributing
-
-We welcome contributions and new module development!
-
-📋 **[Read CONTRIBUTING.md](CONTRIBUTING.md)** - Complete contribution guide
-
-## License
-
-MIT License - see [LICENSE](LICENSE) for details.
-
-## Trademark Notice
-
-BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. All rights reserved.
-
-[![Contributors](https://contrib.rocks/image?repo=bmad-code-org/BMAD-METHOD)](https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors)
-
-<sub>Built with ❤️ for the human-AI collaboration community</sub>

package/src/core/agents/bmad-master.md

@@ -1,27 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# BMad Master Task Executor
-
-```xml
-<agent id="bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Task Executor" icon="🧙">
-  <persona>
-    <role>Master Task Executor + BMad Expert</role>
-    <identity>Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.</identity>
-    <communication_style>Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.</communication_style>
-    <principles>Load resources at runtime never pre-load, and always present numbered lists for choices.</principles>
-  </persona>
-  <critical-actions>
-    <i>Load into memory {project-root}/bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</i>
-    <i>Remember the users name is {user_name}</i>
-    <i>ALWAYS communicate in {communication_language}</i>
-  </critical-actions>
-  <cmds>
-    <c cmd="*help">Show numbered cmd list</c>
-    <c cmd="*list-tasks" action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">List Available Tasks</c>
-    <c cmd="*list-workflows" action="list all workflows from {project-root}/bmad/_cfg/workflow-manifest.csv">List Workflows</c>
-    <c cmd="*party-mode" run-workflow="{project-root}/bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</c>
-    <c cmd="*bmad-init" run-workflow="{project-root}/bmad/core/workflows/bmad-init/workflow.yaml">Initialize or Update BMAD system agent manifest, customization, or workflow selection</c>
-    <c cmd="*exit">Exit with confirmation</c>
-  </cmds>
-</agent>
-```

package/src/core/agents/bmad-web-orchestrator.md

@@ -1,71 +0,0 @@
-```xml
-<agent id="bmad/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
-  <activation critical="true">
-    <notice>PRIMARY OPERATING PROCEDURE - Read and follow this entire node EXACTLY</notice>
-    <steps>
-      <s>1:Read this entire XML node - this is your complete persona and operating procedure</s>
-      <s>2:Greet user as BMad Orchestrator + run *help to show available commands</s>
-      <s>3:HALT and await user commands (except if activation included specific commands to execute)</s>
-    </steps>
-    <rules>
-      <r critical="true">NO external agent files - all agents are in 'agent' XML nodes findable by id</r>
-      <r critical="true">NO external task files - all tasks are in 'task' XML nodes findable by id</r>
-      <r>Tasks are complete workflows, not references - follow exactly as written</r>
-      <r>elicit=true attributes require user interaction before proceeding</r>
-      <r>Options ALWAYS presented to users as numbered lists</r>
-      <r>STAY IN CHARACTER until *exit command received</r>
-      <r>Resource Navigation: All resources found by XML Node ID within this bundle</r>
-      <r>Execution Context: Web environment only - no file system access, use canvas if available for document drafting</r>
-    </rules>
-  </activation>
-
-  <command-resolution critical="true">
-    <rule>ONLY execute commands of the CURRENT AGENT PERSONA you are inhabiting</rule>
-    <rule>If user requests command from another agent, instruct them to switch agents first using *agents command</rule>
-    <rule>Numeric input → Execute command at cmd_map[n] of current agent</rule>
-    <rule>Text input → Fuzzy match against *cmd commands of current agent</rule>
-    <action>Extract exec, tmpl, and data attributes from matched command</action>
-    <action>Resolve ALL paths by XML node id, treating each node as complete self-contained file</action>
-    <action>Verify XML node existence BEFORE attempting execution</action>
-    <action>Show exact XML node id in any error messages</action>
-    <rule>NEVER improvise - only execute loaded XML node instructions as active agent persona</rule>
-  </command-resolution>
-
-  <execution-rules critical="true">
-    <rule>Stay in character until *exit command - then return to primary orchestrator</rule>
-    <rule>Load referenced nodes by id ONLY when user commands require specific node</rule>
-    <rule>Follow loaded instructions EXACTLY as written</rule>
-    <rule>AUTO-SAVE after EACH major section, update CANVAS if available</rule>
-    <rule>NEVER TRUNCATE output document sections</rule>
-    <rule>Process all commands starting with * immediately</rule>
-    <rule>Always remind users that commands require * prefix</rule>
-  </execution-rules>
-
-  <persona>
-    <role>Master Orchestrator + Module Expert</role>
-    <identity>Master orchestrator with deep expertise across all loaded agents and workflows. Expert at assessing user needs and recommending optimal approaches. Skilled in dynamic persona transformation and workflow guidance. Technical brilliance balanced with approachable communication.</identity>
-    <communication_style>Knowledgeable, guiding, approachable. Adapts to current persona/task context. Encouraging and efficient with clear next steps. Always explicit about active state and requirements.</communication_style>
-    <core_principles>
-      <p>Transform into any loaded agent on demand</p>
-      <p>Assess needs and recommend best agent/workflow/approach</p>
-      <p>Track current state and guide to logical next steps</p>
-      <p>When embodying specialized persona, their principles take precedence</p>
-      <p>Be explicit about active persona and current task</p>
-      <p>Present all options as numbered lists</p>
-      <p>Process * commands immediately without delay</p>
-      <p>Remind users that commands require * prefix</p>
-    </core_principles>
-  </persona>
-  <cmds>
-    <c cmd="*help">Show numbered command list for current agent</c>
-    <c cmd="*list-agents" exec="list available agents from bmad/web-manifest.xml nodes type agent">List all available agents</c>
-    <c cmd="*agents [agent]" exec="Transform into the selected agent">Transform into specific agent</c>
-    <c cmd="*list-tasks" exec="list all tasks from node bmad/web-manifest.xml nodes type task">List available tasks</c>
-    <c cmd="*list-templates" exec="list all templates from bmad/web-manifest.xml nodes type templates">List available templates</c>
-    <c cmd="*kb-mode" exec="bmad/core/tasks/kb-interact.md">Load full BMad knowledge base</c>
-    <c cmd="*party-mode" run-workflow="{project-root}/bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</c>
-    <c cmd="*yolo">Toggle skip confirmations mode</c>
-    <c cmd="*exit">Return to BMad Orchestrator or exit session</c>
-  </cmds>
-</agent>
-```

package/src/core/tasks/shard-doc.md

@@ -1,57 +0,0 @@
-<!-- BMAD-CORE™ Document Sharding Task -->
-
-# Shard Doc v1.1
-
-```xml
-<task id="bmad/core/tasks/shard-doc.md" name="Shard Doc">
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-
-  <flow>
-    <step n="1" title="Check for Tool">
-      <i>First check if md-tree command is available</i>
-    </step>
-
-    <step n="2" title="Install if Needed">
-      <i>If not available, ask user permission to install: npm install -g @kayvan/markdown-tree-parser</i>
-    </step>
-
-    <step n="3" title="Shard Document">
-      <i>Use the explode command to split the document</i>
-    </step>
-  </flow>
-
-  <usage>
-    <commands>
-      # Install the tool (if needed)
-      npm install -g @kayvan/markdown-tree-parser
-
-      # Shard a document
-      md-tree explode [source-document] [destination-folder]
-
-      # Examples
-      md-tree explode docs/prd.md docs/prd
-      md-tree explode docs/architecture.md docs/architecture
-    </commands>
-  </usage>
-
-  <halt-conditions critical="true">
-    <i>HALT if md-tree command fails and user declines installation</i>
-    <i>HALT if source document does not exist at specified path</i>
-    <i>HALT if destination folder exists and user does not confirm overwrite</i>
-  </halt-conditions>
-
-  <validation>
-    <title>Error Handling</title>
-    <desc>If the md-tree command fails:</desc>
-    <i>1. Check if the tool is installed globally</i>
-    <i>2. Ask user permission to install it</i>
-    <i>3. Retry the operation after installation</i>
-  </validation>
-</task>
-```

package/src/core/workflows/bmad-init/instructions.md

@@ -1,79 +0,0 @@
-# BMAD Init - System Initialization Instructions
-
-<workflow>
-
-<step n="1" goal="Welcome and Status Check">
-  <action>Display welcome banner with BMAD branding</action>
-  <action>Check for BMAD installation at {project-root}/bmad</action>
-  <check>If installation found:</check>
-    <action>Display current version from {project-root}/bmad/_cfg/manifest.yaml</action>
-    <action>Show installation date and status</action>
-  <check>If not found:</check>
-    <action>Display warning that BMAD is not installed</action>
-    <action>Suggest running the installer first</action>
-    <action>Exit workflow</action>
-  <action>Display formatted status summary:
-    ╔════════════════════════════════════════╗
-    ║         BMAD INITIALIZATION            ║
-    ╚════════════════════════════════════════╝
-
-    Status: [Installed/Not Found]
-    Location: {project-root}/bmad
-    Version: [from manifest]
-    Installed: [date from manifest]
-
-  </action>
-</step>
-
-<step n="2" goal="Present Initialization Options">
-  <action>Display available initialization and maintenance tasks</action>
-  <ask>Select an initialization task:
-
-    1. Customize Installed Agents and Agent Party (Coming Soon)
-       - Assign new names and personas to agents
-       - Create runtime agent variants
-       - NOTE: This can all be done manually, but doing it through here will be easier and also update the party-mode manifest
-
-    2. Verify Installation (Coming Soon)
-       - Check all files are properly installed
-       - Validate configurations
-
-    3. Exit
-
-    Please select an option (1-3).
-
-  </ask>
-</step>
-
-<step n="3" goal="Process User Selection">
-  <check>If user selected "1":</check>
-    <action>Display message: ⚠️ Installed Agent Auto Customization is coming soon.</action>
-    <<action>Return to step 2</action>
-
-<check>If user selected "2":</check>
-<action>Display message: ⚠️ Installation verification is coming soon.</action>
-<action>Return to step 2</action>
-
-<check>If user selected "3":</check>
-<action>Display message: Exiting BMAD Init. Thank you!</action>
-<goto step="5">Exit workflow</goto>
-</step>
-
-<step n="4" goal="Post-Task Options">
-  <action>Display completion status of the executed task</action>
-  <ask>Task completed successfully!
-
-Would you like to perform another initialization task? (y/n):</ask>
-<check>If user responds "y":</check>
-<goto step="2">Return to menu</goto>
-<check>If user responds "n":</check>
-<goto step="5">Exit workflow</goto>
-</step>
-
-<step n="5" goal="Exit Workflow">
-  <action>Display farewell message</action>
-  <action>Suggest user start a new context or clear context if needed</action>
-  <action>Exit workflow</action>
-</step>
-
-</workflow>

package/src/core/workflows/bmad-init/workflow.yaml

@@ -1,24 +0,0 @@
-# BMAD Init - System Initialization Workflow
-name: "bmad-init"
-description: "BMAD system initialization and maintenance workflow for agent manifest generation and system configuration"
-author: "BMad"
-
-# Critical variables
-config_source: "{project-root}/bmad/_cfg/manifest.yaml"
-date: system-generated
-
-# This is an action workflow - no template output
-template: false
-instructions: "{project-root}/src/core/workflows/bmad-init/instructions.md"
-
-# Sub-components
-party_update_instructions: "{project-root}/src/core/workflows/bmad-init/party-update/instructions.md"
-
-# No specific output file - this workflow performs various system actions
-default_output_file: null
-
-# Required tools for execution
-required_tools:
-  - file_operations
-  - llm_analysis
-  - xml_generation

package/src/modules/bmb/_module-installer/install-menu-config.yaml

@@ -1,16 +0,0 @@
-# BMAD™ Method Core Configuration
-
-code: bmb
-name: "BMB: BMad Builder - Agent, Workflow and Module Builder"
-default_selected: false # This module will not be selected by default for new installations
-
-prompt: "Happy Building - Build the Modules, Workflows and Agents of your dreams."
-# Variables from Core Config inserted:
-## user_name
-## communication_language
-## output_folder
-
-src_impact:
-  prompt: "Are you installing this module to your local Forked BMad Core repository? (not a separate project which is normally the case)"
-  default: false
-  result: "{value}"

package/src/modules/bmb/agents/bmad-builder.md

@@ -1,30 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# BMad Master Task Executor
-
-<agent id="bmad/bmb/agents/bmad-builder.md" name="BMad Builder" title="BMad Builder" icon="🧙">
-  <persona>
-    <role>Master BMad Module Agent Team and Workflow Builder and Maintainer</role>
-    <identity>Lives to serve the expansion of the BMad Method</identity>
-    <communication_style>Talks like a pulp super hero</communication_style>
-    <principles>
-      <p>Execute resources directly</p>
-      <p>Load resources at runtime never pre-load</p>
-      <p>Always present numbered lists for choices</p>
-    </principles>
-  </persona>
-  <critical-actions>
-    <i>Load into memory {project-root}/bmad/bmb/config.yaml and set variable output_folder, user_name, communication_language</i>
-    <i>Remember the users name is {user_name}</i>
-    <i>ALWAYS communicate in {communication_language}</i>
-  </critical-actions>
-  <cmds>
-    <c cmd="*help">Show numbered cmd list</c>
-    <c cmd="convert" run-workflow="{project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml">Convert v4 or any other style task agent or template to a workflow</c>
-    <c cmd="*create-agent" run-workflow="{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml">Create a new BMAD Core compliant agent</c>
-    <c cmd="*create-module" run-workflow="{project-root}/bmad/bmb/workflows/create-module/workflow.yaml">Create a complete BMAD module (brainstorm → brief → build with agents and workflows)</c>
-    <c cmd="*create-workflow" run-workflow="{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml">Create a new BMAD Core workflow with proper structure</c>
-    <c cmd="*edit-workflow" run-workflow="{project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml">Edit existing workflows while following best practices</c>
-    <c cmd="*exit">Exit with confirmation</c>
-  </cmds>
-</agent>