doc: functional change: fix agent responsibilities link

This commit is contained in:
Kayvan Sylvan 2025-05-18 15:23:14 -07:00
parent fb9c6d0339
commit 2e41b7157b
1 changed files with 42 additions and 40 deletions

View File

@ -2,27 +2,29 @@
## INDEX OF TOPICS ## INDEX OF TOPICS
- [BMAD METHOD - CORE PHILOSOPHY](#bmad-method---core-philosophy) - [BMAD Knowledge Base](#bmad-knowledge-base)
- [BMAD METHOD - AGILE METHODOLOGIES OVERVIEW](#bmad-method---agile-methodologies-overview) - [INDEX OF TOPICS](#index-of-topics)
- [BMAD METHOD - CORE PHILOSOPHY](#bmad-method---core-philosophy)
- [BMAD METHOD - AGILE METHODOLOGIES OVERVIEW](#bmad-method---agile-methodologies-overview)
- [CORE PRINCIPLES OF AGILE](#core-principles-of-agile) - [CORE PRINCIPLES OF AGILE](#core-principles-of-agile)
- [KEY PRACTICES IN AGILE](#key-practices-in-agile) - [KEY PRACTICES IN AGILE](#key-practices-in-agile)
- [BENEFITS OF AGILE](#benefits-of-agile) - [BENEFITS OF AGILE](#benefits-of-agile)
- [BMAD METHOD - ANALOGIES WITH AGILE PRINCIPLES](#bmad-method---analogies-with-agile-principles) - [BMAD METHOD - ANALOGIES WITH AGILE PRINCIPLES](#bmad-method---analogies-with-agile-principles)
- [BMAD METHOD - TOOLING AND RESOURCE LOCATIONS](#bmad-method---tooling-and-resource-locations) - [BMAD METHOD - TOOLING AND RESOURCE LOCATIONS](#bmad-method---tooling-and-resource-locations)
- [BMAD METHOD - COMMUNITY AND CONTRIBUTIONS](#bmad-method---community-and-contributions) - [BMAD METHOD - COMMUNITY AND CONTRIBUTIONS](#bmad-method---community-and-contributions)
- [Licensing](#licensing) - [Licensing](#licensing)
- [BMAD METHOD - ETHOS & BEST PRACTICES](#bmad-method---ethos--best-practices) - [BMAD METHOD - ETHOS \& BEST PRACTICES](#bmad-method---ethos--best-practices)
- [AGENT ROLES](#agent-roles) - [AGENT ROLES AND RESPONSIBILITIES](#agent-roles-and-responsibilities)
- [NAVIGATING THE BMAD WORKFLOW - INITIAL GUIDANCE](#navigating-the-bmad-workflow---initial-guidance) - [NAVIGATING THE BMAD WORKFLOW - INITIAL GUIDANCE](#navigating-the-bmad-workflow---initial-guidance)
- [STARTING YOUR PROJECT - ANALYST OR PM?](#starting-your-project---analyst-or-pm) - [STARTING YOUR PROJECT - ANALYST OR PM?](#starting-your-project---analyst-or-pm)
- [UNDERSTANDING EPICS - SINGLE OR MULTIPLE?](#understanding-epics---single-or-multiple) - [UNDERSTANDING EPICS - SINGLE OR MULTIPLE?](#understanding-epics---single-or-multiple)
- [SUGGESTED ORDER OF AGENT ENGAGEMENT (TYPICAL FLOW)](#suggested-order-of-agent-engagement-typical-flow) - [SUGGESTED ORDER OF AGENT ENGAGEMENT (TYPICAL FLOW)](#suggested-order-of-agent-engagement-typical-flow)
- [HANDLING MAJOR CHANGES](#handling-major-changes) - [HANDLING MAJOR CHANGES](#handling-major-changes)
- [IDE VS UI USAGE - GENERAL RECOMMENDATIONS](#ide-vs-ui-usage---general-recommendations) - [IDE VS UI USAGE - GENERAL RECOMMENDATIONS](#ide-vs-ui-usage---general-recommendations)
- [CONCEPTUAL AND PLANNING PHASES](#conceptual-and-planning-phases) - [CONCEPTUAL AND PLANNING PHASES](#conceptual-and-planning-phases)
- [TECHNICAL DESIGN, DOCUMENTATION MANAGEMENT & IMPLEMENTATION PHASES](#technical-design-documentation-management--implementation-phases) - [TECHNICAL DESIGN, DOCUMENTATION MANAGEMENT \& IMPLEMENTATION PHASES](#technical-design-documentation-management--implementation-phases)
- [BMAD METHOD FILES](#bmad-method-files) - [BMAD METHOD FILES](#bmad-method-files)
- [LEVERAGING IDE TASKS FOR EFFICIENCY](#leveraging-ide-tasks-for-efficiency) - [LEVERAGING IDE TASKS FOR EFFICIENCY](#leveraging-ide-tasks-for-efficiency)
- [PURPOSE OF IDE TASKS](#purpose-of-ide-tasks) - [PURPOSE OF IDE TASKS](#purpose-of-ide-tasks)
- [EXAMPLES OF TASK FUNCTIONALITY](#examples-of-task-functionality) - [EXAMPLES OF TASK FUNCTIONALITY](#examples-of-task-functionality)
@ -177,7 +179,7 @@ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLI
- **EMBRACE_THE_CHAOS:** Pioneering new methods is messy. Adapt and overcome. - **EMBRACE_THE_CHAOS:** Pioneering new methods is messy. Adapt and overcome.
- **ADAPT & EXPERIMENT:** The BMAD Method provides a structure, but feel free to adapt its principles, agent order, or templates to fit your specific project needs and working style. Experiment to find what works best for you. **Define agile the BMad way - or your way!** The agent configurations allow for customization of roles and responsibilities. - **ADAPT & EXPERIMENT:** The BMAD Method provides a structure, but feel free to adapt its principles, agent order, or templates to fit your specific project needs and working style. Experiment to find what works best for you. **Define agile the BMad way - or your way!** The agent configurations allow for customization of roles and responsibilities.
## AGENT ROLES ## 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.