rebuild sample with merged fixes
This commit is contained in:
Brian Madison
@@ -64,7 +64,7 @@ When these commands are used, perform the listed action
|
||||
- `/{agent}`: If in BMad Orchestrator mode, immediate switch to selected agent (if there is a match) - if already in another agent persona - confirm the switch.
|
||||
- `/exit`: Immediately abandon the current agent or party-mode and drop to base BMad Orchestrator
|
||||
- `/doc-out`: If a doc is being talked about or refined, output the full document untruncated.
|
||||
- `/agent-{agent}`: Immediate swap to a new agent persona - which will great on change.
|
||||
- `/agent-{agent}`: Immediate swap to a new agent persona - which will greet on change.
|
||||
- `/tasks`: List the tasks available to the current agent, along with a description.
|
||||
- `/bmad {query}`: Even if in an agent - you can talk to base BMad with your query. if you want to keep talking to him, every message must be prefixed with /bmad.
|
||||
- `/{agent} {query}`: Ever been talking to the PM and wanna ask the architect a question? Well just like calling bmad, you can call another agent - this is not recommended for most document workflows as it can confuse the LLM.
|
||||
|
||||
@@ -3,27 +3,29 @@
|
||||
|
||||
## INDEX OF TOPICS
|
||||
|
||||
- [BMAD METHOD - CORE PHILOSOPHY](#bmad-method---core-philosophy)
|
||||
- [BMAD METHOD - AGILE METHODOLOGIES OVERVIEW](#bmad-method---agile-methodologies-overview)
|
||||
- [BMAD Knowledge Base](#bmad-knowledge-base)
|
||||
- [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)
|
||||
- [KEY PRACTICES IN AGILE](#key-practices-in-agile)
|
||||
- [BENEFITS OF AGILE](#benefits-of-agile)
|
||||
- [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 - COMMUNITY AND CONTRIBUTIONS](#bmad-method---community-and-contributions)
|
||||
- [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 - COMMUNITY AND CONTRIBUTIONS](#bmad-method---community-and-contributions)
|
||||
- [Licensing](#licensing)
|
||||
- [BMAD METHOD - ETHOS & BEST PRACTICES](#bmad-method---ethos--best-practices)
|
||||
- [AGENT ROLES](#agent-roles)
|
||||
- [NAVIGATING THE BMAD WORKFLOW - INITIAL GUIDANCE](#navigating-the-bmad-workflow---initial-guidance)
|
||||
- [BMAD METHOD - ETHOS \& BEST PRACTICES](#bmad-method---ethos--best-practices)
|
||||
- [AGENT ROLES AND RESPONSIBILITIES](#agent-roles-and-responsibilities)
|
||||
- [NAVIGATING THE BMAD WORKFLOW - INITIAL GUIDANCE](#navigating-the-bmad-workflow---initial-guidance)
|
||||
- [STARTING YOUR PROJECT - ANALYST OR PM?](#starting-your-project---analyst-or-pm)
|
||||
- [UNDERSTANDING EPICS - SINGLE OR MULTIPLE?](#understanding-epics---single-or-multiple)
|
||||
- [SUGGESTED ORDER OF AGENT ENGAGEMENT (TYPICAL FLOW)](#suggested-order-of-agent-engagement-typical-flow)
|
||||
- [HANDLING MAJOR CHANGES](#handling-major-changes)
|
||||
- [IDE VS UI USAGE - GENERAL RECOMMENDATIONS](#ide-vs-ui-usage---general-recommendations)
|
||||
- [SUGGESTED ORDER OF AGENT ENGAGEMENT (TYPICAL FLOW)](#suggested-order-of-agent-engagement-typical-flow)
|
||||
- [HANDLING MAJOR CHANGES](#handling-major-changes)
|
||||
- [IDE VS UI USAGE - GENERAL RECOMMENDATIONS](#ide-vs-ui-usage---general-recommendations)
|
||||
- [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)
|
||||
- [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)
|
||||
- [EXAMPLES OF TASK FUNCTIONALITY](#examples-of-task-functionality)
|
||||
|
||||
@@ -178,7 +180,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.
|
||||
- **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.
|
||||
|
||||
|
||||
@@ -681,8 +681,8 @@ To identify the next logical story based on project progress and epic definition
|
||||
- Data Models Document (as referenced in Index Doc)
|
||||
- API Reference Document (as referenced in Index Doc)
|
||||
- UI/UX Specifications, Style Guides, Component Guides (if relevant, as referenced in Index Doc)
|
||||
- The `docs/templates/story-template.md` (hereafter "Story Template")
|
||||
- The `docs/checklists/story-draft-checklist.txt` (hereafter "Story Draft Checklist")
|
||||
- The `bmad-agent/templates/story-tmpl.md` (hereafter "Story Template")
|
||||
- The `bmad-agent/checklists/story-draft-checklist.md` (hereafter "Story Draft Checklist")
|
||||
- User confirmation to proceed with story identification and, if needed, to override warnings about incomplete prerequisite stories.
|
||||
|
||||
## Task Execution Instructions
|
||||
@@ -1085,7 +1085,7 @@ To collaboratively work with the user to define and document the User Interface
|
||||
|
||||
|
||||
==================== START: doc-sharding-task ====================
|
||||
# Paste the following prompt into your agent chat to have it run Doc Sharding
|
||||
# Doc Sharding Task
|
||||
|
||||
You are now operating as a Technical Documentation Librarian tasked with granulating large project documents into smaller, organized files. Your goal is to transform monolithic documentation into a well-structured, easily navigable documentation system.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user