ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

improve some file naming towards consistency

Browse Source
This commit is contained in:
Brian Madison
2025-05-25 23:24:28 -05:00
parent d7442ed043
commit 349a9ca3f2
11 changed files with 84 additions and 81 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -4,7 +4,7 @@ Demo of the BMad Agent entire workflow output from the web agent can be found in
## Web Quickstart Project Setup (Recommended) ## Web Quickstart Project Setup (Recommended)
Orchestrator Uber BMad Agent that does it all - already pre-compiled in the `./web-build-sample` folder. The contents of agent-prompt.txt should be copy and pasted into the Gemini Gem, or ChatPGT customGPT 'Instructions' field. The remaining files in this folder just need to be attached. Give it a name and save it, and you now have the BMad Agent available to help you brainstorm, research plan and execute on your vision. Orchestrator Uber BMad Agent that does it all - already pre-compiled in the `./web-build-sample` folder. You can rebuild if you have node installed from the root of the project with the command `node ./build-web-agent.js`. The contents of agent-prompt.txt in the sample or build output folder should be copied and pasted into the Gemini Gem, or ChatPGT customGPT 'Instructions' field. The remaining files in this folder just need to be attached. Give it a name and save it, and you now have the BMad Agent available to help you brainstorm, research plan and execute on your vision.
![image info](./docs/images/gem-setup.png) ![image info](./docs/images/gem-setup.png)
@@ -18,7 +18,7 @@ Here are the more [Setup and Usage Instructions](./docs/instruction.md) for IDE,
Starting with the latest version of the BMad Agents for the BMad Method is very easy - all you need to do is copy `bmad-agent` folder to your project. The dedicated dev and sm that existing in previous versions are still available and are in the `bmad-agent/personas` folder with the .ide.md extension. Copy and paste the contents into your specific IDE's method of configuring a custom agent mode. The dev and sm both are configured for architecture and prd artifacts to be in (project-root)/docs and stories will be generated and developed in/from your (project-root)/docs/stories. Starting with the latest version of the BMad Agents for the BMad Method is very easy - all you need to do is copy `bmad-agent` folder to your project. The dedicated dev and sm that existing in previous versions are still available and are in the `bmad-agent/personas` folder with the .ide.md extension. Copy and paste the contents into your specific IDE's method of configuring a custom agent mode. The dev and sm both are configured for architecture and prd artifacts to be in (project-root)/docs and stories will be generated and developed in/from your (project-root)/docs/stories.
For all other agent use (including the dev and sm) you can set up the [ide orchestrator](./bmad-agent/ide-bmad-orchestrator.md) - you can ask the orchestrator bmad to become any agent you have [configured](./bmad-agent/ide-bmad-orchestrator-cfg.md). For all other agent use (including the dev and sm) you can set up the [ide orchestrator](bmad-agent/bmad-agent.ide.md) - you can ask the orchestrator bmad to become any agent you have [configured](bmad-agent/bmad-orchestrator.ide.cfg.md).
[General IDE Custom Mode Setup](./docs/ide-setup.md). [General IDE Custom Mode Setup](./docs/ide-setup.md).
@@ -58,8 +58,8 @@ See the detailed [Web Orchestration Setup and Usage Instructions](./docs/instruc
There are dedicated self contained agents that are stand alone, and also an IDE version of an orchestrator. For there standalone, there are: There are dedicated self contained agents that are stand alone, and also an IDE version of an orchestrator. For there standalone, there are:
- [Dev IDE Agent](./bmad-agent/personas/dev.ide.md) - [Dev IDE Agent](bmad-agent/personas/dev.ide.md)
- [Story Generating SM Agent](./bmad-agent/personas/sm.ide.md) - [Story Generating SM Agent](bmad-agent/personas/sm.ide.md)
If you want to use the other agents, you can use the other agents from that folder - but some will be larger than Windsurf allows - and there are many agents. So its recommended to either use 1 off tasks - OR even better - use the IDE Orchestrator Agent. See these [set up and Usage instructions for IDE Orchestrator](./docs/instruction.md#ide-agent-setup-and-usage). If you want to use the other agents, you can use the other agents from that folder - but some will be larger than Windsurf allows - and there are many agents. So its recommended to either use 1 off tasks - OR even better - use the IDE Orchestrator Agent. See these [set up and Usage instructions for IDE Orchestrator](./docs/instruction.md#ide-agent-setup-and-usage).

28
bmad-agent/data/bmad-kb.md
View File

@@ -103,20 +103,20 @@ Effective use of the BMAD Method relies on understanding where key tools, config
- **BMAD Knowledge Base:** This document (`bmad-agent/data/bmad-kb.md`) serves as the central repository for understanding the BMAD method, its principles, agent roles, and workflows. - **BMAD Knowledge Base:** This document (`bmad-agent/data/bmad-kb.md`) serves as the central repository for understanding the BMAD method, its principles, agent roles, and workflows.
- **Orchestrator Agents:** A key feature of V3 is the Orchestrator agent (e.g., "BMAD"), a master agent capable of embodying any specialized agent role. - **Orchestrator Agents:** A key feature of V3 is the Orchestrator agent (e.g., "BMAD"), a master agent capable of embodying any specialized agent role.
- **Web Agent Orchestrator:** - **Web Agent Orchestrator:**
- **Setup:** Utilizes a Node.js build script (`build-bmad-web-orchestrator.js`) configured by `build-agent-cfg.js`. - **Setup:** Utilizes a Node.js build script (`build-web-agent.js`) configured by `build-web-agent.cfg.js`.
- **Process:** Consolidates assets (personas, tasks, templates, checklists, data) from an `asset_root` (e.g., `./bmad-agent/`) into a `build_dir` (e.g., `./bmad-agent/build/`). - **Process:** Consolidates assets (personas, tasks, templates, checklists, data) from an `asset_root` (e.g., `./bmad-agent/`) into a `build_dir` (e.g., `./bmad-agent/build/`).
- **Output:** Produces bundled asset files (e.g., `personas.txt`, `tasks.txt`), an `agent-prompt.txt` (from `orchestrator_agent_prompt`), and an `agent-config.txt` (from `agent_cfg` like `web-bmad-orchestrator-agent-cfg.md`). - **Output:** Produces bundled asset files (e.g., `personas.txt`, `tasks.txt`), an `agent-prompt.txt` (from `orchestrator_agent_prompt`), and an `agent-config.txt` (from `agent_cfg` like `web-bmad-orchestrator-agent.cfg.md`).
- **Usage:** The `agent-prompt.txt` is used for the main custom web agent instruction set (e.g., Gemini 2.5 Gem or OpenAI Custom GPT), and the other build files are attached as knowledge/files. - **Usage:** The `agent-prompt.txt` is used for the main custom web agent instruction set (e.g., Gemini 2.5 Gem or OpenAI Custom GPT), and the other build files are attached as knowledge/files.
- **IDE Agent Orchestrator (`ide-bmad-orchestrator.md`):** - **IDE Agent Orchestrator (`ide-bmad-orchestrator.md`):**
- **Setup:** Works without a build step, dynamically loading its configuration. - **Setup:** Works without a build step, dynamically loading its configuration.
- **Configuration (`ide-bmad-orchestrator-cfg.md`):** Contains a `Data Resolution` section (defining base paths for assets like personas, tasks) and `Agent Definitions` (Title, Name, Customize, Persona file, Tasks). - **Configuration (`ide-bmad-orchestrator.cfg.md`):** Contains a `Data Resolution` section (defining base paths for assets like personas, tasks) and `Agent Definitions` (Title, Name, Customize, Persona file, Tasks).
- **Operation:** Loads its config, lists available personas, and upon user request, embodies the chosen agent by loading its persona file and applying customizations. - **Operation:** Loads its config, lists available personas, and upon user request, embodies the chosen agent by loading its persona file and applying customizations.
- **Standalone IDE Agents:** - **Standalone IDE Agents:**
- Optimized for IDE environments (e.g., Windsurf, Cursor), often under 6K characters (e.g., `dev.ide.md`, `sm.ide.md`). - Optimized for IDE environments (e.g., Windsurf, Cursor), often under 6K characters (e.g., `dev.ide.md`, `sm.ide.md`).
- Can directly reference and execute tasks. - Can directly reference and execute tasks.
- **Agent Configuration Files:** - **Agent Configuration Files:**
- `web-bmad-orchestrator-agent-cfg.md`: Defines agents the Web Orchestrator can embody, including references to personas, tasks, checklists, and templates (e.g., `personas#pm`, `tasks#create-prd`). - `web-bmad-orchestrator-agent.cfg.md`: Defines agents the Web Orchestrator can embody, including references to personas, tasks, checklists, and templates (e.g., `personas#pm`, `tasks#create-prd`).
- `ide-bmad-orchestrator-cfg.md`: Configures the IDE Orchestrator, defining `Data Resolution` paths (e.g., `(project-root)/bmad-agent/personas`) and agent definitions with persona file names (e.g., `analyst.md`) and task file names (e.g., `create-prd.md`). - `ide-bmad-orchestrator.cfg.md`: Configures the IDE Orchestrator, defining `Data Resolution` paths (e.g., `(project-root)/bmad-agent/personas`) and agent definitions with persona file names (e.g., `analyst.md`) and task file names (e.g., `create-prd.md`).
- `web-bmad-orchestrator-agent.md`: Main prompt for the Web Orchestrator. - `web-bmad-orchestrator-agent.md`: Main prompt for the Web Orchestrator.
- `ide-bmad-orchestrator.md`: Main prompt/definition of the IDE Orchestrator agent. - `ide-bmad-orchestrator.md`: Main prompt/definition of the IDE Orchestrator agent.
- **Task Files:** - **Task Files:**
@@ -181,7 +181,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
## AGENT ROLES AND RESPONSIBILITIES ## AGENT ROLES AND RESPONSIBILITIES
Understanding the distinct roles and responsibilities of each agent is key to effectively navigating the BMAD workflow. While the "Vibe CEO" provides overall direction, each agent specializes in different aspects of the project lifecycle. V3 introduces Orchestrator agents that can embody these roles, with configurations specified in `web-bmad-orchestrator-agent-cfg.md` for web and `ide-bmad-orchestrator-cfg.md` for IDE environments. Understanding the distinct roles and responsibilities of each agent is key to effectively navigating the BMAD workflow. While the "Vibe CEO" provides overall direction, each agent specializes in different aspects of the project lifecycle. V3 introduces Orchestrator agents that can embody these roles, with configurations specified in `web-bmad-orchestrator-agent.cfg.md` for web and `ide-bmad-orchestrator.cfg.md` for IDE environments.
- **Orchestrator Agent (BMAD):** - **Orchestrator Agent (BMAD):**
@@ -189,8 +189,8 @@ Understanding the distinct roles and responsibilities of each agent is key to ef
- **Persona Reference:** `personas#bmad` (Web) or implicitly the core of `ide-bmad-orchestrator.md` (IDE). - **Persona Reference:** `personas#bmad` (Web) or implicitly the core of `ide-bmad-orchestrator.md` (IDE).
- **Key Data/Knowledge:** Accesses `data#bmad-kb-data` (Web) for its knowledge base. - **Key Data/Knowledge:** Accesses `data#bmad-kb-data` (Web) for its knowledge base.
- **Types:** - **Types:**
- **Web Orchestrator:** Built using a script, leverages large context windows of platforms like Gemini 2.5 or OpenAI GPTs. Uses bundled assets. Its behavior and available agents are defined in `web-bmad-orchestrator-agent-cfg.md`. - **Web Orchestrator:** Built using a script, leverages large context windows of platforms like Gemini 2.5 or OpenAI GPTs. Uses bundled assets. Its behavior and available agents are defined in `web-bmad-orchestrator-agent.cfg.md`.
- **IDE Orchestrator:** Operates directly in IDEs like Cursor or Windsurf without a build step, loading persona and task files dynamically based on its configuration (`ide-bmad-orchestrator-cfg.md`). The orchestrator itself is defined in `ide-bmad-orchestrator.md`. - **IDE Orchestrator:** Operates directly in IDEs like Cursor or Windsurf without a build step, loading persona and task files dynamically based on its configuration (`ide-bmad-orchestrator.cfg.md`). The orchestrator itself is defined in `ide-bmad-orchestrator.md`.
- **Key Feature:** Simplifies agent management, especially in environments with limitations on the number of custom agents. - **Key Feature:** Simplifies agent management, especially in environments with limitations on the number of custom agents.
- **Analyst:** - **Analyst:**
@@ -240,7 +240,7 @@ Understanding the distinct roles and responsibilities of each agent is key to ef
- **IDE Personas:** Multiple configurations can exist, using the `dev.ide.md` persona file (optimized for <6K characters for IDEs). Examples: - **IDE Personas:** Multiple configurations can exist, using the `dev.ide.md` persona file (optimized for <6K characters for IDEs). Examples:
- `Frontend Dev (DevFE)`: Specialized in NextJS, React, Typescript, HTML, Tailwind. - `Frontend Dev (DevFE)`: Specialized in NextJS, React, Typescript, HTML, Tailwind.
- `Dev (Dev)`: Master Generalist Expert Senior Full Stack Developer. - `Dev (Dev)`: Master Generalist Expert Senior Full Stack Developer.
- **Configuration:** Specialized agents can be configured in `ide-bmad-orchestrator-cfg.md` for the IDE Orchestrator, or defined for the Web Orchestrator. Standalone IDE developer agents (e.g., `dev.ide.md`) are also available. - **Configuration:** Specialized agents can be configured in `ide-bmad-orchestrator.cfg.md` for the IDE Orchestrator, or defined for the Web Orchestrator. Standalone IDE developer agents (e.g., `dev.ide.md`) are also available.
- **When to Use:** During the implementation phase, typically working within an IDE. - **When to Use:** During the implementation phase, typically working within an IDE.
## NAVIGATING THE BMAD WORKFLOW - INITIAL GUIDANCE ## NAVIGATING THE BMAD WORKFLOW - INITIAL GUIDANCE
@@ -270,7 +270,7 @@ Understanding the distinct roles and responsibilities of each agent is key to ef
6. **Design Architect (If project has a UI)** - Optionally create a prompt to generate a UI from AI services such as Lovable or V0 from Vercel. 6. **Design Architect (If project has a UI)** - Optionally create a prompt to generate a UI from AI services such as Lovable or V0 from Vercel.
7. **PO**: Validate documents are aligned, sequencing makes sense, runs a final master checklist. The PO can also help midstream development replan or course correct if major changes occur. 7. **PO**: Validate documents are aligned, sequencing makes sense, runs a final master checklist. The PO can also help midstream development replan or course correct if major changes occur.
8. **PO or SM**: Generate Stories 1 at a time (or multiple but not recommended) - this is generally done in the IDE after each story is completed by the Developer Agents. 8. **PO or SM**: Generate Stories 1 at a time (or multiple but not recommended) - this is generally done in the IDE after each story is completed by the Developer Agents.
9. **Developer Agents**: Implement Stories 1 at a time. You can craft different specialized Developer Agents, or use a generic developer agent. It is recommended to create specialized developer agents and configure them in the `ide-bmad-orchestrator-cfg`. 9. **Developer Agents**: Implement Stories 1 at a time. You can craft different specialized Developer Agents, or use a generic developer agent. It is recommended to create specialized developer agents and configure them in the `ide-bmad-orchestrator.cfg`.
## HANDLING MAJOR CHANGES ## HANDLING MAJOR CHANGES
@@ -296,13 +296,13 @@ The BMAD method can be orchestrated through different interfaces, typically a we
### TECHNICAL DESIGN, DOCUMENTATION MANAGEMENT & IMPLEMENTATION PHASES ### TECHNICAL DESIGN, DOCUMENTATION MANAGEMENT & IMPLEMENTATION PHASES
- **Interface:** Primarily within the Integrated Development Environment (IDE), leveraging specialized agents (standalone or via the **IDE Agent Orchestrator** configured with `ide-bmad-orchestrator-cfg.md`). - **Interface:** Primarily within the Integrated Development Environment (IDE), leveraging specialized agents (standalone or via the **IDE Agent Orchestrator** configured with `ide-bmad-orchestrator.cfg.md`).
- **Agents Involved:** - **Agents Involved:**
- **Architect / Design Architect (UI):** Detailed technical design and specification. - **Architect / Design Architect (UI):** Detailed technical design and specification.
- **POSM Agent:** Ongoing documentation management and organization. - **POSM Agent:** Ongoing documentation management and organization.
- **PO (Product Owner) / SM (Scrum Master):** Detailed story generation, backlog refinement, often directly in the IDE or tools integrated with it. - **PO (Product Owner) / SM (Scrum Master):** Detailed story generation, backlog refinement, often directly in the IDE or tools integrated with it.
- **Developer Agents:** Code implementation for stories, working directly with the codebase in the IDE. - **Developer Agents:** Code implementation for stories, working directly with the codebase in the IDE.
- **Activities:** Detailed architecture, front-end/back-end design, code development, testing, leveraging IDE tasks (see "LEVERAGING IDE TASKS FOR EFFICIENCY"), using configurations like `ide-bmad-orchestrator-cfg.md`. - **Activities:** Detailed architecture, front-end/back-end design, code development, testing, leveraging IDE tasks (see "LEVERAGING IDE TASKS FOR EFFICIENCY"), using configurations like `ide-bmad-orchestrator.cfg.md`.
### BMAD METHOD FILES ### BMAD METHOD FILES
@@ -310,9 +310,9 @@ Understanding key files helps in navigating and customizing the BMAD process:
- **Knowledge & Configuration:** - **Knowledge & Configuration:**
- `bmad-agent/data/bmad-kb.md`: This central knowledge base. - `bmad-agent/data/bmad-kb.md`: This central knowledge base.
- `ide-bmad-orchestrator-cfg.md`: Configuration for IDE developer agents. - `ide-bmad-orchestrator.cfg.md`: Configuration for IDE developer agents.
- `ide-bmad-orchestrator.md`: Definition of the IDE orchestrator agent. - `ide-bmad-orchestrator.md`: Definition of the IDE orchestrator agent.
- `web-bmad-orchestrator-agent-cfg.md`: Configuration for the web orchestrator agent. - `web-bmad-orchestrator-agent.cfg.md`: Configuration for the web orchestrator agent.
- `web-bmad-orchestrator-agent.md`: Definition of the web orchestrator agent. - `web-bmad-orchestrator-agent.md`: Definition of the web orchestrator agent.
- **Task Definitions:** - **Task Definitions:**
- Files in `bmad-agent/tasks/` or `bmad-agent/checklists/` (e.g., `checklist-run-task.md`): Reusable prompts for specific actions and also used by agents to keep agent persona files lean. - Files in `bmad-agent/tasks/` or `bmad-agent/checklists/` (e.g., `checklist-run-task.md`): Reusable prompts for specific actions and also used by agents to keep agent persona files lean.

32
bmad-agent/ide-bmad-orchestrator-cfg.md → bmad-agent/ide-bmad-orchestrator.cfg.md
View File

@@ -14,8 +14,8 @@ Example: If above cfg has `agent-root: root/foo/` and `tasks: (agent-root)/tasks
## Title: Analyst ## Title: Analyst
- Name: Larry - Name: Wendy
- Customize: "You are a bit of a know-it-all, and like to verbalize and emote as if you were a physical person." - Customize: ""
- Description: "Research assistant, brain storming coach, requirements gathering, project briefs." - Description: "Research assistant, brain storming coach, requirements gathering, project briefs."
- Persona: "analyst.md" - Persona: "analyst.md"
- Tasks: - Tasks:
@@ -25,7 +25,7 @@ Example: If above cfg has `agent-root: root/foo/` and `tasks: (agent-root)/tasks
## Title: Product Owner AKA PO ## Title: Product Owner AKA PO
- Name: Curly - Name: Jimmy
- Customize: "" - Customize: ""
- Description: "Jack of many trades, from PRD Generation and maintenance to the mid sprint Course Correct. Also able to draft masterful stories for the dev agent." - Description: "Jack of many trades, from PRD Generation and maintenance to the mid sprint Course Correct. Also able to draft masterful stories for the dev agent."
- Persona: "po.md" - Persona: "po.md"
@@ -37,8 +37,8 @@ Example: If above cfg has `agent-root: root/foo/` and `tasks: (agent-root)/tasks
## Title: Architect ## Title: Architect
- Name: Mo - Name: Timmy
- Customize: "Cold, Calculating, Brains behind the agent crew" - Customize: ""
- Description: "Generates Architecture, Can help plan a story, and will also help update PRD level epic and stories." - Description: "Generates Architecture, Can help plan a story, and will also help update PRD level epic and stories."
- Persona: "architect.md" - Persona: "architect.md"
- Tasks: - Tasks:
@@ -48,8 +48,8 @@ Example: If above cfg has `agent-root: root/foo/` and `tasks: (agent-root)/tasks
## Title: Design Architect ## Title: Design Architect
- Name: Millie - Name: Karen
- Customize: "Fun and carefree, but a frontend design master both for UX and Technical" - Customize: ""
- Description: "Help design a website or web application, produce prompts for UI GEneration AI's, and plan a full comprehensive front end architecture." - Description: "Help design a website or web application, produce prompts for UI GEneration AI's, and plan a full comprehensive front end architecture."
- Persona: "design-architect.md" - Persona: "design-architect.md"
- Tasks: - Tasks:
@@ -59,7 +59,7 @@ Example: If above cfg has `agent-root: root/foo/` and `tasks: (agent-root)/tasks
## Title: Product Manager (PM) ## Title: Product Manager (PM)
- Name: Jack - Name: Bill
- Customize: "" - Customize: ""
- Description: "Jack has only one goal - to produce or maintain the best possible PRD - or discuss the product with you to ideate or plan current or future efforts related to the product." - Description: "Jack has only one goal - to produce or maintain the best possible PRD - or discuss the product with you to ideate or plan current or future efforts related to the product."
- Persona: "pm.md" - Persona: "pm.md"
@@ -68,21 +68,23 @@ Example: If above cfg has `agent-root: root/foo/` and `tasks: (agent-root)/tasks
## Title: Frontend Dev ## Title: Frontend Dev
- Name: Perry - Name: Rodney
- Customize: "Specialized in NextJS, React, Typescript, HTML, Tailwind" - Customize: "Specialized in NextJS, React, Typescript, HTML, Tailwind"
- Description: "Master Front End Web Application Developer" - Description: "Master Front End Web Application Developer"
- Persona: "dev.ide.md" - Persona: "dev.md"
## Title: Full Stack Dev ## Title: Full Stack Dev
- Name: Rodney - Name: James
- Customize: "" - Customize: ""
- Description: "Master Generalist Expert Senior Senior Full Stack Developer" - Description: "Master Generalist Expert Senior Senior Full Stack Developer"
- Persona: "dev.ide.md" - Persona: "dev.md"
## Title: Scrum Master: SM ## Title: Scrum Master: SM
- Name: Sally - Name: Fran
- Customize: "Super Technical and Detail Oriented" - Customize: ""
- Description: "Specialized in Next Story Generation" - Description: "Specialized in Next Story Generation"
- Persona: "sm.ide.md" - Persona: "sm.md"
- Tasks:
- [Draft Story](create-next-story-task.md)

2
bmad-agent/ide-bmad-orchestrator.md
View File

@@ -1,6 +1,6 @@
# Role: BMad - IDE Orchestrator # Role: BMad - IDE Orchestrator
`configFile`: `(project-root)/bmad-agent/ide-bmad-orchestrator-cfg.md` `configFile`: `(project-root)/bmad-agent/ide-bmad-orchestrator.cfg.md`
`kb`: `(project-root)/bmad-agent/data/bmad-kb.md` `kb`: `(project-root)/bmad-agent/data/bmad-kb.md`
## Core Orchestrator Principles ## Core Orchestrator Principles

15
bmad-agent/personas/dev.ide.md
View File

@@ -70,7 +70,7 @@ MUST review and use:
5. **Pre-Completion DoD Review & Cleanup:** 5. **Pre-Completion DoD Review & Cleanup:**
- Ensure all story tasks/subtasks are marked complete. Verify all tests pass. - Ensure all story tasks & subtasks are marked complete. Verify all tests pass.
- <critical_rule>Review `Debug Log`. Meticulously revert all temporary changes for this story. Any change proposed as permanent requires user approval & full standards adherence. `Debug Log` must be clean of unaddressed temporary changes for this story.</critical_rule> - <critical_rule>Review `Debug Log`. Meticulously revert all temporary changes for this story. Any change proposed as permanent requires user approval & full standards adherence. `Debug Log` must be clean of unaddressed temporary changes for this story.</critical_rule>
- <critical_rule>Meticulously verify story against each item in `docs/checklists/story-dod-checklist.txt`.</critical_rule> - <critical_rule>Meticulously verify story against each item in `docs/checklists/story-dod-checklist.txt`.</critical_rule>
- Address any unmet checklist items. - Address any unmet checklist items.
@@ -78,13 +78,14 @@ MUST review and use:
6. **Final Handoff for User Approval:** 6. **Final Handoff for User Approval:**
- <important_note>Final confirmation: Code/tests meet `Operational Guidelines` & all DoD items are verifiably met (incl. approvals for new dependencies and debug code).</important_note> - <important_note>Final confirmation: Code/tests meet `Operational Guidelines` & all DoD items are verifiably met (incl. approvals for new dependencies and debug code).</important_note>
- Present "Story DoD Checklist Report" to user. - Present "Story DoD Checklist Report" summary to user.
- <critical_rule>Only after presenting DoD report (all items 'Done'), update story `Status: Review` in story file.</critical_rule> - <critical_rule>Update story `Status: Review` in story file if DoD, Tasks and Subtasks are complete.</critical_rule>
- State story is complete per DoD: HALT! - State story is complete & HALT!
## Commands: ## Commands:
- /help - list these commands - /help - list these commands
- /core-dump (ensure story tasks and notes are recorded as of now, and then run bmad-agent/tasks/core-dump.md) - /core-dump - ensure story tasks and notes are recorded as of now, and then run bmad-agent/tasks/core-dump.md
- /run-tests (exe all tests) - /run-tests - exe all tests
- - /lint - find/fix lint issues
- /explain {something} - teach or inform {something}

0
bmad-agent/web-bmad-orchestrator-agent-cfg.md → bmad-agent/web-bmad-orchestrator-agent.cfg.md
View File

9
build-agent-cfg.js
View File

@@ -1,9 +0,0 @@
// build-agent-cfg.js
// This file contains the configuration for the build-bmad-web-orchestrator.js script.
module.exports = {
orchestrator_agent_prompt: "./bmad-agent/web-bmad-orchestrator-agent.md",
agent_cfg: "./bmad-agent/web-bmad-orchestrator-agent-cfg.md",
asset_root: "./bmad-agent/",
build_dir: "./bmad-agent/build/",
};

9
build-web-agent.cfg.js Normal file
View File

@@ -0,0 +1,9 @@
// build-web-agent.cfg.js
// This file contains the configuration for the build-web-agent.js script.
module.exports = {
orchestrator_agent_prompt: "./bmad-agent/web-bmad-orchestrator-agent.md",
agent_cfg: "./bmad-agent/web-bmad-orchestrator-agent.cfg.md",
asset_root: "./bmad-agent/",
build_dir: "./build/",
};

2
build-bmad-web-orchestrator.js → build-web-agent.js
View File

@@ -3,7 +3,7 @@ const fs = require("fs");
const path = require("path"); const path = require("path");
// --- Configuration --- // --- Configuration ---
const configFilePath = "./build-agent-cfg.js"; // Path relative to this script (__dirname) const configFilePath = "./build-web-agent.cfg.js"; // Path relative to this script (__dirname)
let config; let config;
try { try {
config = require(configFilePath); config = require(configFilePath);

32
docs/instruction.md
View File

@@ -10,7 +10,7 @@ The Agent Orchestrator in V3 utilizes a build script to package various agent as
### Overview ### Overview
The build process is managed by the `build-bmad-orchestrator.js` Node.js script. This script reads its configuration from `build-agent-cfg.js`, processes files from an asset directory, and outputs the bundled assets into a designated build directory. The build process is managed by the `build-bmad-orchestrator.js` Node.js script. This script reads its configuration from `build-web-agent.cfg.js`, processes files from an asset directory, and outputs the bundled assets into a designated build directory.
Quickstart: see [this below](#running-the-build-script) Quickstart: see [this below](#running-the-build-script)
@@ -18,9 +18,9 @@ Quickstart: see [this below](#running-the-build-script)
- **Node.js**: Ensure you have Node.js installed to run the build script. Python version coming soon... - **Node.js**: Ensure you have Node.js installed to run the build script. Python version coming soon...
### Configuration (`build-agent-cfg.js`) ### Configuration (`build-web-agent.cfg.js`)
The build process is configured via `build-agent-cfg.js`. Key parameters include: The build process is configured via `build-web-agent.cfg.js`. Key parameters include:
- `orchestrator_agent_prompt`: Specifies the path to the main prompt file for the orchestrator agent, such as `bmad-agent/web-bmad-orchestrator-agent.md`. This file will be copied to `agent-prompt.txt` in the build directory. - `orchestrator_agent_prompt`: Specifies the path to the main prompt file for the orchestrator agent, such as `bmad-agent/web-bmad-orchestrator-agent.md`. This file will be copied to `agent-prompt.txt` in the build directory.
- Example: `./bmad-agent/web-bmad-orchestrator-agent.md` - Example: `./bmad-agent/web-bmad-orchestrator-agent.md`
@@ -29,9 +29,9 @@ The build process is configured via `build-agent-cfg.js`. Key parameters include
- `build_dir`: Specifies the directory where the bundled output files and the `agent-prompt.txt` will be created. - `build_dir`: Specifies the directory where the bundled output files and the `agent-prompt.txt` will be created.
- Example: `./bmad-agent/build/` - Example: `./bmad-agent/build/`
- `agent_cfg`: Specifies the path to the md cfg file that defines the agents the Orchestrator can embody. - `agent_cfg`: Specifies the path to the md cfg file that defines the agents the Orchestrator can embody.
- Example: `./bmad-agent/web-bmad-orchestrator-agent-cfg.md` - Example: `./bmad-agent/web-bmad-orchestrator-agent.cfg.md`
Paths in the configuration file (`build-agent-cfg.js`) are relative to the `BETA-V3` directory (where `build-agent-cfg.js` and the build script `build-bmad-orchestrator.js` are located). Paths in the configuration file (`build-web-agent.cfg.js`) are relative to the `BETA-V3` directory (where `build-web-agent.cfg.js` and the build script `build-bmad-orchestrator.js` are located).
### Asset Directory Structure ### Asset Directory Structure
@@ -52,7 +52,7 @@ The script expects a specific structure within the `asset_root` directory:
NOTE the build will skip any files with the `.ide.<extension>` - so you can have ide specific agents or files also that do not make sense for the web, such as `dev.ide.md` - or a specific ide `sm.ide.md`. NOTE the build will skip any files with the `.ide.<extension>` - so you can have ide specific agents or files also that do not make sense for the web, such as `dev.ide.md` - or a specific ide `sm.ide.md`.
1. ```cmd 1. ```cmd
node build-bmad-web-orchestrator.js node build-web-agent.js
``` ```
The script will log its progress, including discovered source directories, any issues found (like duplicate base filenames), and the output files being generated. The script will log its progress, including discovered source directories, any issues found (like duplicate base filenames), and the output files being generated.
@@ -73,9 +73,9 @@ These bundled files and the agent prompt are then ready to be used by the Agent
The text in agent-prompt.txt gets entered into the window of the main custom web agent instruction set. The other files in the build folder all need to be attached as files for the Gem or GPT. The text in agent-prompt.txt gets entered into the window of the main custom web agent instruction set. The other files in the build folder all need to be attached as files for the Gem or GPT.
### Orchestrator Agent Configuration (e.g., `BETA-V3/bmad-agent/web-bmad-orchestrator-agent-cfg.md`) ### Orchestrator Agent Configuration (e.g., `BETA-V3/bmad-agent/web-bmad-orchestrator-agent.cfg.md`)
While `build-bmad-orchestrator.js` packages assets, the Orchestrator's core behavior, agent definitions, and personality are defined in a Markdown configuration file. An example is `bmad-agent/web-bmad-orchestrator-agent-cfg.md` (path relative to `BETA-V3/`, specified in `build-agent-cfg.js` via `agent_cfg`). This file is key to the Orchestrator's adaptability. While `build-bmad-orchestrator.js` packages assets, the Orchestrator's core behavior, agent definitions, and personality are defined in a Markdown configuration file. An example is `bmad-agent/web-bmad-orchestrator-agent.cfg.md` (path relative to `BETA-V3/`, specified in `build-web-agent.cfg.js` via `agent_cfg`). This file is key to the Orchestrator's adaptability.
**Key Features and Configurability:** **Key Features and Configurability:**
@@ -113,7 +113,7 @@ While `build-bmad-orchestrator.js` packages assets, the Orchestrator's core beha
**How it Works (Conceptual Flow from `orchestrator-agent.md`):** **How it Works (Conceptual Flow from `orchestrator-agent.md`):**
1. The Orchestrator (initially BMad) loads and parses the Markdown agent configuration file (e.g., `web-bmad-orchestrator-agent-cfg.md`). 1. The Orchestrator (initially BMad) loads and parses the Markdown agent configuration file (e.g., `web-bmad-orchestrator-agent.cfg.md`).
2. When a user request matches an agent's `title`, `name`, `description`, or `classification_label`, the Orchestrator identifies the target agent. 2. When a user request matches an agent's `title`, `name`, `description`, or `classification_label`, the Orchestrator identifies the target agent.
3. It then loads the agent's `persona` and any associated `templates`, `checklists`, `data_sources`, and `tasks` by: 3. It then loads the agent's `persona` and any associated `templates`, `checklists`, `data_sources`, and `tasks` by:
- Identifying the correct bundled `.txt` file (e.g., `personas.txt` for `personas#pm`). - Identifying the correct bundled `.txt` file (e.g., `personas.txt` for `personas#pm`).
@@ -121,7 +121,7 @@ While `build-bmad-orchestrator.js` packages assets, the Orchestrator's core beha
4. The `Customize` instructions from the Markdown configuration are applied, potentially modifying the agent's behavior. 4. The `Customize` instructions from the Markdown configuration are applied, potentially modifying the agent's behavior.
5. The Orchestrator then _becomes_ that agent, adopting its complete persona, knowledge, and operational parameters defined in the Markdown configuration and the loaded asset sections. 5. The Orchestrator then _becomes_ that agent, adopting its complete persona, knowledge, and operational parameters defined in the Markdown configuration and the loaded asset sections.
This system makes the Agent Orchestrator highly adaptable. You can easily define new agents, modify existing ones, tweak personalities with the `Customize` field (in the Markdown agent configuration file like `web-bmad-orchestrator-agent-cfg.md`), or change their knowledge base, main prompt, and asset paths (in `build-agent-cfg.js` and the corresponding asset files), then re-running the build script if asset content was changed. This system makes the Agent Orchestrator highly adaptable. You can easily define new agents, modify existing ones, tweak personalities with the `Customize` field (in the Markdown agent configuration file like `web-bmad-orchestrator-agent.cfg.md`), or change their knowledge base, main prompt, and asset paths (in `build-web-agent.cfg.js` and the corresponding asset files), then re-running the build script if asset content was changed.
## IDE Agent Setup and Usage ## IDE Agent Setup and Usage
@@ -137,8 +137,8 @@ A powerful alternative is the `ide-bmad-orchestrator.md`. This agent provides th
#### How the IDE Orchestrator Works #### How the IDE Orchestrator Works
1. **Configuration (`ide-bmad-orchestrator-cfg.md`):** 1. **Configuration (`ide-bmad-orchestrator.cfg.md`):**
The orchestrator's behavior is primarily driven by a Markdown configuration file (e.g., `BETA-V3/bmad-agent/ide-bmad-orchestrator-cfg.md`, the path to which is specified within the `ide-bmad-orchestrator.md` itself). This config file has two main parts: The orchestrator's behavior is primarily driven by a Markdown configuration file (e.g., `BETA-V3/bmad-agent/ide-bmad-orchestrator.cfg.md`, the path to which is specified within the `ide-bmad-orchestrator.md` itself). This config file has two main parts:
- **Data Resolution:** - **Data Resolution:**
Located at the top of the config file, this section defines key-value pairs for base paths. These paths tell the orchestrator where to find different types of asset files (personas, tasks, checklists, templates, data). Located at the top of the config file, this section defines key-value pairs for base paths. These paths tell the orchestrator where to find different types of asset files (personas, tasks, checklists, templates, data).
@@ -186,7 +186,7 @@ A powerful alternative is the `ide-bmad-orchestrator.md`. This agent provides th
``` ```
2. **Operational Workflow (inside `ide-bmad-orchestrator.md`):** 2. **Operational Workflow (inside `ide-bmad-orchestrator.md`):**
- **Initialization:** Upon activation in your IDE, the `ide-bmad-orchestrator.md` first loads and parses its specified configuration file (`ide-bmad-orchestrator-cfg.md`). If this fails, it will inform you and halt. - **Initialization:** Upon activation in your IDE, the `ide-bmad-orchestrator.md` first loads and parses its specified configuration file (`ide-bmad-orchestrator.cfg.md`). If this fails, it will inform you and halt.
- **Greeting & Persona Listing:** It will greet you. If your initial instruction isn't clear or if you ask, it will list the available specialist personas (by `Title`, `Name`, and `Description`) and the `Tasks` each can perform, all derived from the loaded configuration. - **Greeting & Persona Listing:** It will greet you. If your initial instruction isn't clear or if you ask, it will list the available specialist personas (by `Title`, `Name`, and `Description`) and the `Tasks` each can perform, all derived from the loaded configuration.
- **Persona Activation:** When you request a specific persona (e.g., "Become the Analyst" or "I need Larry to help with research"), the orchestrator: - **Persona Activation:** When you request a specific persona (e.g., "Become the Analyst" or "I need Larry to help with research"), the orchestrator:
- Finds the persona in its configuration. - Finds the persona in its configuration.
@@ -201,8 +201,8 @@ A powerful alternative is the `ide-bmad-orchestrator.md`. This agent provides th
#### Usage Instructions for IDE Orchestrator #### Usage Instructions for IDE Orchestrator
1. **Set up your configuration (`ide-bmad-orchestrator-cfg.md`):** 1. **Set up your configuration (`ide-bmad-orchestrator.cfg.md`):**
- Ensure you have an `ide-bmad-orchestrator-cfg.md` file. You can use the one located in `BETA-V3/bmad-agent/` as a template or starting point. - Ensure you have an `ide-bmad-orchestrator.cfg.md` file. You can use the one located in `BETA-V3/bmad-agent/` as a template or starting point.
- Verify that the `Data Resolution` paths at the top correctly point to your asset folders (personas, tasks, templates, checklists, data) relative to your project structure. - Verify that the `Data Resolution` paths at the top correctly point to your asset folders (personas, tasks, templates, checklists, data) relative to your project structure.
- Define your desired agents with their `Title`, `Name`, `Customize` instructions, `Persona` file, and `Tasks`. Ensure the referenced persona and task files exist in the locations specified by your `Data Resolution` paths. - Define your desired agents with their `Title`, `Name`, `Customize` instructions, `Persona` file, and `Tasks`. Ensure the referenced persona and task files exist in the locations specified by your `Data Resolution` paths.
2. **Set up your persona and task files:** 2. **Set up your persona and task files:**
@@ -222,7 +222,7 @@ A powerful alternative is the `ide-bmad-orchestrator.md`. This agent provides th
- **Switching Personas:** - **Switching Personas:**
- If you need to switch: "I need to talk to the Architect now." - If you need to switch: "I need to talk to the Architect now."
- The orchestrator will advise a new chat. If you want to switch in the current chat, you'll need to give an explicit override command when prompted (e.g., "Override safety protocol and switch to Architect"). - The orchestrator will advise a new chat. If you want to switch in the current chat, you'll need to give an explicit override command when prompted (e.g., "Override safety protocol and switch to Architect").
- **Follow Persona Instructions:** Once a persona is active, it will guide you based on its definition and the task it's performing. Remember that resource files like templates or checklists referenced by a task will be resolved using the global `Data Resolution` paths in the `ide-bmad-orchestrator-cfg.md`. - **Follow Persona Instructions:** Once a persona is active, it will guide you based on its definition and the task it's performing. Remember that resource files like templates or checklists referenced by a task will be resolved using the global `Data Resolution` paths in the `ide-bmad-orchestrator.cfg.md`.
This setup allows for a highly flexible and dynamically configured multi-persona agent directly within your IDE, streamlining various development and project management workflows. This setup allows for a highly flexible and dynamically configured multi-persona agent directly within your IDE, streamlining various development and project management workflows.

28
web-build-sample/data.txt
View File

@@ -104,20 +104,20 @@ Effective use of the BMAD Method relies on understanding where key tools, config
- **BMAD Knowledge Base:** This document (`bmad-agent/data/bmad-kb.md`) serves as the central repository for understanding the BMAD method, its principles, agent roles, and workflows. - **BMAD Knowledge Base:** This document (`bmad-agent/data/bmad-kb.md`) serves as the central repository for understanding the BMAD method, its principles, agent roles, and workflows.
- **Orchestrator Agents:** A key feature of V3 is the Orchestrator agent (e.g., "BMAD"), a master agent capable of embodying any specialized agent role. - **Orchestrator Agents:** A key feature of V3 is the Orchestrator agent (e.g., "BMAD"), a master agent capable of embodying any specialized agent role.
- **Web Agent Orchestrator:** - **Web Agent Orchestrator:**
- **Setup:** Utilizes a Node.js build script (`build-bmad-web-orchestrator.js`) configured by `build-agent-cfg.js`. - **Setup:** Utilizes a Node.js build script (`build-web-agent.js`) configured by `build-web-agent.cfg.js`.
- **Process:** Consolidates assets (personas, tasks, templates, checklists, data) from an `asset_root` (e.g., `./bmad-agent/`) into a `build_dir` (e.g., `./bmad-agent/build/`). - **Process:** Consolidates assets (personas, tasks, templates, checklists, data) from an `asset_root` (e.g., `./bmad-agent/`) into a `build_dir` (e.g., `./bmad-agent/build/`).
- **Output:** Produces bundled asset files (e.g., `personas.txt`, `tasks.txt`), an `agent-prompt.txt` (from `orchestrator_agent_prompt`), and an `agent-config.txt` (from `agent_cfg` like `web-bmad-orchestrator-agent-cfg.md`). - **Output:** Produces bundled asset files (e.g., `personas.txt`, `tasks.txt`), an `agent-prompt.txt` (from `orchestrator_agent_prompt`), and an `agent-config.txt` (from `agent_cfg` like `web-bmad-orchestrator-agent.cfg.md`).
- **Usage:** The `agent-prompt.txt` is used for the main custom web agent instruction set (e.g., Gemini 2.5 Gem or OpenAI Custom GPT), and the other build files are attached as knowledge/files. - **Usage:** The `agent-prompt.txt` is used for the main custom web agent instruction set (e.g., Gemini 2.5 Gem or OpenAI Custom GPT), and the other build files are attached as knowledge/files.
- **IDE Agent Orchestrator (`ide-bmad-orchestrator.md`):** - **IDE Agent Orchestrator (`ide-bmad-orchestrator.md`):**
- **Setup:** Works without a build step, dynamically loading its configuration. - **Setup:** Works without a build step, dynamically loading its configuration.
- **Configuration (`ide-bmad-orchestrator-cfg.md`):** Contains a `Data Resolution` section (defining base paths for assets like personas, tasks) and `Agent Definitions` (Title, Name, Customize, Persona file, Tasks). - **Configuration (`ide-bmad-orchestrator.cfg.md`):** Contains a `Data Resolution` section (defining base paths for assets like personas, tasks) and `Agent Definitions` (Title, Name, Customize, Persona file, Tasks).
- **Operation:** Loads its config, lists available personas, and upon user request, embodies the chosen agent by loading its persona file and applying customizations. - **Operation:** Loads its config, lists available personas, and upon user request, embodies the chosen agent by loading its persona file and applying customizations.
- **Standalone IDE Agents:** - **Standalone IDE Agents:**
- Optimized for IDE environments (e.g., Windsurf, Cursor), often under 6K characters (e.g., `dev.ide.md`, `sm.ide.md`). - Optimized for IDE environments (e.g., Windsurf, Cursor), often under 6K characters (e.g., `dev.ide.md`, `sm.ide.md`).
- Can directly reference and execute tasks. - Can directly reference and execute tasks.
- **Agent Configuration Files:** - **Agent Configuration Files:**
- `web-bmad-orchestrator-agent-cfg.md`: Defines agents the Web Orchestrator can embody, including references to personas, tasks, checklists, and templates (e.g., `personas#pm`, `tasks#create-prd`). - `web-bmad-orchestrator-agent.cfg.md`: Defines agents the Web Orchestrator can embody, including references to personas, tasks, checklists, and templates (e.g., `personas#pm`, `tasks#create-prd`).
- `ide-bmad-orchestrator-cfg.md`: Configures the IDE Orchestrator, defining `Data Resolution` paths (e.g., `(project-root)/bmad-agent/personas`) and agent definitions with persona file names (e.g., `analyst.md`) and task file names (e.g., `create-prd.md`). - `ide-bmad-orchestrator.cfg.md`: Configures the IDE Orchestrator, defining `Data Resolution` paths (e.g., `(project-root)/bmad-agent/personas`) and agent definitions with persona file names (e.g., `analyst.md`) and task file names (e.g., `create-prd.md`).
- `web-bmad-orchestrator-agent.md`: Main prompt for the Web Orchestrator. - `web-bmad-orchestrator-agent.md`: Main prompt for the Web Orchestrator.
- `ide-bmad-orchestrator.md`: Main prompt/definition of the IDE Orchestrator agent. - `ide-bmad-orchestrator.md`: Main prompt/definition of the IDE Orchestrator agent.
- **Task Files:** - **Task Files:**
@@ -182,7 +182,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
## AGENT ROLES AND RESPONSIBILITIES ## AGENT ROLES AND RESPONSIBILITIES
Understanding the distinct roles and responsibilities of each agent is key to effectively navigating the BMAD workflow. While the "Vibe CEO" provides overall direction, each agent specializes in different aspects of the project lifecycle. V3 introduces Orchestrator agents that can embody these roles, with configurations specified in `web-bmad-orchestrator-agent-cfg.md` for web and `ide-bmad-orchestrator-cfg.md` for IDE environments. Understanding the distinct roles and responsibilities of each agent is key to effectively navigating the BMAD workflow. While the "Vibe CEO" provides overall direction, each agent specializes in different aspects of the project lifecycle. V3 introduces Orchestrator agents that can embody these roles, with configurations specified in `web-bmad-orchestrator-agent.cfg.md` for web and `ide-bmad-orchestrator.cfg.md` for IDE environments.
- **Orchestrator Agent (BMAD):** - **Orchestrator Agent (BMAD):**
@@ -190,8 +190,8 @@ Understanding the distinct roles and responsibilities of each agent is key to ef
- **Persona Reference:** `personas#bmad` (Web) or implicitly the core of `ide-bmad-orchestrator.md` (IDE). - **Persona Reference:** `personas#bmad` (Web) or implicitly the core of `ide-bmad-orchestrator.md` (IDE).
- **Key Data/Knowledge:** Accesses `data#bmad-kb-data` (Web) for its knowledge base. - **Key Data/Knowledge:** Accesses `data#bmad-kb-data` (Web) for its knowledge base.
- **Types:** - **Types:**
- **Web Orchestrator:** Built using a script, leverages large context windows of platforms like Gemini 2.5 or OpenAI GPTs. Uses bundled assets. Its behavior and available agents are defined in `web-bmad-orchestrator-agent-cfg.md`. - **Web Orchestrator:** Built using a script, leverages large context windows of platforms like Gemini 2.5 or OpenAI GPTs. Uses bundled assets. Its behavior and available agents are defined in `web-bmad-orchestrator-agent.cfg.md`.
- **IDE Orchestrator:** Operates directly in IDEs like Cursor or Windsurf without a build step, loading persona and task files dynamically based on its configuration (`ide-bmad-orchestrator-cfg.md`). The orchestrator itself is defined in `ide-bmad-orchestrator.md`. - **IDE Orchestrator:** Operates directly in IDEs like Cursor or Windsurf without a build step, loading persona and task files dynamically based on its configuration (`ide-bmad-orchestrator.cfg.md`). The orchestrator itself is defined in `ide-bmad-orchestrator.md`.
- **Key Feature:** Simplifies agent management, especially in environments with limitations on the number of custom agents. - **Key Feature:** Simplifies agent management, especially in environments with limitations on the number of custom agents.
- **Analyst:** - **Analyst:**
@@ -241,7 +241,7 @@ Understanding the distinct roles and responsibilities of each agent is key to ef
- **IDE Personas:** Multiple configurations can exist, using the `dev.ide.md` persona file (optimized for <6K characters for IDEs). Examples: - **IDE Personas:** Multiple configurations can exist, using the `dev.ide.md` persona file (optimized for <6K characters for IDEs). Examples:
- `Frontend Dev (DevFE)`: Specialized in NextJS, React, Typescript, HTML, Tailwind. - `Frontend Dev (DevFE)`: Specialized in NextJS, React, Typescript, HTML, Tailwind.
- `Dev (Dev)`: Master Generalist Expert Senior Full Stack Developer. - `Dev (Dev)`: Master Generalist Expert Senior Full Stack Developer.
- **Configuration:** Specialized agents can be configured in `ide-bmad-orchestrator-cfg.md` for the IDE Orchestrator, or defined for the Web Orchestrator. Standalone IDE developer agents (e.g., `dev.ide.md`) are also available. - **Configuration:** Specialized agents can be configured in `ide-bmad-orchestrator.cfg.md` for the IDE Orchestrator, or defined for the Web Orchestrator. Standalone IDE developer agents (e.g., `dev.ide.md`) are also available.
- **When to Use:** During the implementation phase, typically working within an IDE. - **When to Use:** During the implementation phase, typically working within an IDE.
## NAVIGATING THE BMAD WORKFLOW - INITIAL GUIDANCE ## NAVIGATING THE BMAD WORKFLOW - INITIAL GUIDANCE
@@ -271,7 +271,7 @@ Understanding the distinct roles and responsibilities of each agent is key to ef
6. **Design Architect (If project has a UI)** - Optionally create a prompt to generate a UI from AI services such as Lovable or V0 from Vercel. 6. **Design Architect (If project has a UI)** - Optionally create a prompt to generate a UI from AI services such as Lovable or V0 from Vercel.
7. **PO**: Validate documents are aligned, sequencing makes sense, runs a final master checklist. The PO can also help midstream development replan or course correct if major changes occur. 7. **PO**: Validate documents are aligned, sequencing makes sense, runs a final master checklist. The PO can also help midstream development replan or course correct if major changes occur.
8. **PO or SM**: Generate Stories 1 at a time (or multiple but not recommended) - this is generally done in the IDE after each story is completed by the Developer Agents. 8. **PO or SM**: Generate Stories 1 at a time (or multiple but not recommended) - this is generally done in the IDE after each story is completed by the Developer Agents.
9. **Developer Agents**: Implement Stories 1 at a time. You can craft different specialized Developer Agents, or use a generic developer agent. It is recommended to create specialized developer agents and configure them in the `ide-bmad-orchestrator-cfg`. 9. **Developer Agents**: Implement Stories 1 at a time. You can craft different specialized Developer Agents, or use a generic developer agent. It is recommended to create specialized developer agents and configure them in the `ide-bmad-orchestrator.cfg`.
## HANDLING MAJOR CHANGES ## HANDLING MAJOR CHANGES
@@ -297,13 +297,13 @@ The BMAD method can be orchestrated through different interfaces, typically a we
### TECHNICAL DESIGN, DOCUMENTATION MANAGEMENT & IMPLEMENTATION PHASES ### TECHNICAL DESIGN, DOCUMENTATION MANAGEMENT & IMPLEMENTATION PHASES
- **Interface:** Primarily within the Integrated Development Environment (IDE), leveraging specialized agents (standalone or via the **IDE Agent Orchestrator** configured with `ide-bmad-orchestrator-cfg.md`). - **Interface:** Primarily within the Integrated Development Environment (IDE), leveraging specialized agents (standalone or via the **IDE Agent Orchestrator** configured with `ide-bmad-orchestrator.cfg.md`).
- **Agents Involved:** - **Agents Involved:**
- **Architect / Design Architect (UI):** Detailed technical design and specification. - **Architect / Design Architect (UI):** Detailed technical design and specification.
- **POSM Agent:** Ongoing documentation management and organization. - **POSM Agent:** Ongoing documentation management and organization.
- **PO (Product Owner) / SM (Scrum Master):** Detailed story generation, backlog refinement, often directly in the IDE or tools integrated with it. - **PO (Product Owner) / SM (Scrum Master):** Detailed story generation, backlog refinement, often directly in the IDE or tools integrated with it.
- **Developer Agents:** Code implementation for stories, working directly with the codebase in the IDE. - **Developer Agents:** Code implementation for stories, working directly with the codebase in the IDE.
- **Activities:** Detailed architecture, front-end/back-end design, code development, testing, leveraging IDE tasks (see "LEVERAGING IDE TASKS FOR EFFICIENCY"), using configurations like `ide-bmad-orchestrator-cfg.md`. - **Activities:** Detailed architecture, front-end/back-end design, code development, testing, leveraging IDE tasks (see "LEVERAGING IDE TASKS FOR EFFICIENCY"), using configurations like `ide-bmad-orchestrator.cfg.md`.
### BMAD METHOD FILES ### BMAD METHOD FILES
@@ -311,9 +311,9 @@ Understanding key files helps in navigating and customizing the BMAD process:
- **Knowledge & Configuration:** - **Knowledge & Configuration:**
- `bmad-agent/data/bmad-kb.md`: This central knowledge base. - `bmad-agent/data/bmad-kb.md`: This central knowledge base.
- `ide-bmad-orchestrator-cfg.md`: Configuration for IDE developer agents. - `ide-bmad-orchestrator.cfg.md`: Configuration for IDE developer agents.
- `ide-bmad-orchestrator.md`: Definition of the IDE orchestrator agent. - `ide-bmad-orchestrator.md`: Definition of the IDE orchestrator agent.
- `web-bmad-orchestrator-agent-cfg.md`: Configuration for the web orchestrator agent. - `web-bmad-orchestrator-agent.cfg.md`: Configuration for the web orchestrator agent.
- `web-bmad-orchestrator-agent.md`: Definition of the web orchestrator agent. - `web-bmad-orchestrator-agent.md`: Definition of the web orchestrator agent.
- **Task Definitions:** - **Task Definitions:**
- Files in `bmad-agent/tasks/` or `bmad-agent/checklists/` (e.g., `checklist-run-task.md`): Reusable prompts for specific actions and also used by agents to keep agent persona files lean. - Files in `bmad-agent/tasks/` or `bmad-agent/checklists/` (e.g., `checklist-run-task.md`): Reusable prompts for specific actions and also used by agents to keep agent persona files lean.