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

readme updates intro beta 3

Browse Source
This commit is contained in:
Brian Madison
2025-05-12 19:51:31 -05:00
parent e4683d6649
commit 06d38a7010
9 changed files with 554 additions and 361 deletions
Download Patch File Download Diff File Expand all files Collapse all files

92
BETA-V3/checklists/rte-checklist.txt Normal file
View File

@@ -0,0 +1,92 @@
# RTE-Agent Change Navigation Checklist
**Purpose:** To systematically guide the RTE-Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMAD workflow.
**Instructions:** Review each item with the user. Mark `[x]` for completed/confirmed, `[N/A]` if not applicable, or add notes for discussion points.
---
## 1. Understand the Trigger & Context
- [ ] **Identify Triggering Story:** Clearly identify the story (or stories) that revealed the issue.
- [ ] **Define the Issue:** Articulate the core problem precisely.
- [ ] Is it a technical limitation/dead-end?
- [ ] Is it a newly discovered requirement?
- [ ] Is it a fundamental misunderstanding of existing requirements?
- [ ] Is it a necessary pivot based on feedback or new information?
- [ ] Is it a failed/abandoned story needing a new approach?
- [ ] **Assess Initial Impact:** Describe the immediate observed consequences (e.g., blocked progress, incorrect functionality, non-viable tech).
- [ ] **Gather Evidence:** Note any specific logs, error messages, user feedback, or analysis that supports the issue definition.
## 2. Epic Impact Assessment
- [ ] **Analyze Current Epic:**
- [ ] Can the current epic containing the trigger story still be completed?
- [ ] Does the current epic need modification (story changes, additions, removals)?
- [ ] Should the current epic be abandoned or fundamentally redefined?
- [ ] **Analyze Future Epics:**
- [ ] Review all remaining planned epics.
- [ ] Does the issue require changes to planned stories in future epics?
- [ ] Does the issue invalidate any future epics?
- [ ] Does the issue necessitate the creation of entirely new epics?
- [ ] Should the order/priority of future epics be changed?
- [ ] **Summarize Epic Impact:** Briefly document the overall effect on the project's epic structure and flow.
## 3. Artifact Conflict & Impact Analysis
- [ ] **Review PRD:**
- [ ] Does the issue conflict with the core goals or requirements stated in the PRD?
- [ ] Does the PRD need clarification or updates based on the new understanding?
- [ ] **Review Architecture Document:**
- [ ] Does the issue conflict with the documented architecture (components, patterns, tech choices)?
- [ ] Are specific components/diagrams/sections impacted?
- [ ] Does the technology list need updating?
- [ ] Do data models or schemas need revision?
- [ ] Are external API integrations affected?
- [ ] **Review Frontend Spec (if applicable):**
- [ ] Does the issue conflict with the FE architecture, component library choice, or UI/UX design?
- [ ] Are specific FE components or user flows impacted?
- [ ] **Review Other Artifacts (if applicable):**
- [ ] Consider impact on deployment scripts, IaC, monitoring setup, etc.
- [ ] **Summarize Artifact Impact:** List all artifacts requiring updates and the nature of the changes needed.
## 4. Path Forward Evaluation
- [ ] **Option 1: Direct Adjustment / Integration:**
- [ ] Can the issue be addressed by modifying/adding future stories within the existing plan?
- [ ] Define the scope and nature of these adjustments.
- [ ] Assess feasibility, effort, and risks of this path.
- [ ] **Option 2: Potential Rollback:**
- [ ] Would reverting completed stories significantly simplify addressing the issue?
- [ ] Identify specific stories/commits to consider for rollback.
- [ ] Assess the effort required for rollback.
- [ ] Assess the impact of rollback (lost work, data implications).
- [ ] Compare the net benefit/cost vs. Direct Adjustment.
- [ ] **Option 3: PRD MVP Review & Potential Re-scoping:**
- [ ] Is the original PRD MVP still achievable given the issue and constraints?
- [ ] Does the MVP scope need reduction (removing features/epics)?
- [ ] Do the core MVP goals need modification?
- [ ] Are alternative approaches needed to meet the original MVP intent?
- [ ] **Extreme Case:** Does the issue necessitate a fundamental replan or potentially a new PRD V2 (to be handled by PM)?
- [ ] **Select Recommended Path:** Based on the evaluation, agree on the most viable path forward.
## 5. Sprint Change Proposal Components
_(Ensure all agreed-upon points from previous sections are captured in the proposal)_
- [ ] **Identified Issue Summary:** Clear, concise problem statement.
- [ ] **Epic Impact Summary:** How epics are affected.
- [ ] **Artifact Adjustment Needs:** List of documents to change.
- [ ] **Recommended Path Forward:** Chosen solution with rationale.
- [ ] **PRD MVP Impact:** Changes to scope/goals (if any).
- [ ] **High-Level Action Plan:** Next steps for stories/updates.
- [ ] **Agent Handoff Plan:** Identify roles needed (PM, Arch, Design Arch, POSM).
## 6. Final Review & Handoff
- [ ] **Review Checklist:** Confirm all relevant items were discussed.
- [ ] **Review Sprint Change Proposal:** Ensure it accurately reflects the discussion and decisions.
- [ ] **User Approval:** Obtain explicit user approval for the proposal.
- [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
---

142
BETA-V3/draft-readme.md
View File

@@ -1,142 +0,0 @@
# The BMAD-Method (Breakthrough Method of Agile (ai-driven) Development) - BETA-V3
If you want to jump right in, here are the [Setup Instructions](./instruction.md) For IDE, WEB and Task setup.
## BETA-V3: Advancing AI-Driven Development
Welcome to **BETA-V3** of the BMAD Method! This version represents a significant evolution, building upon the foundations of V2 and introducing a more refined and comprehensive suite of agents, templates, and processes. The `BETA-V3` folder contains the latest implementation, designed to enhance collaboration, documentation, and the overall efficiency of developing projects with AI.
While `LEGACY-V1` and `CURRENT-V2` folders exist for historical reference, **BETA-V3** is the focus of ongoing development and represents the most advanced iteration of the BMAD Method.
## Custom Modes and Welcome Contributions
The BMAD community's input is invaluable! We encourage you to contribute by submitting Pull Requests for custom agent modes, new templates, or checklist enhancements tailored for the `BETA-V3` system. Whether for Web UIs (like Gemini Gems/Custom GPTs) or IDE custom modes, your contributions help expand our AI team's capabilities.
The Custom Agents in `BETA-V3` continue to follow best practices for LLM prompting (e.g., clear roles, instructions, and context) ensuring they work effectively across various AI platforms.
## 🔥 Demonstration Walkthrough 🔥
While a dedicated BETA-V3 video walkthrough is planned, the principles of interactive, phased agent collaboration are well-illustrated in the [V2 Video Walkthrough](https://youtu.be/p0barbrWgQA?si=PD1RyWNVDpdF3QJf). The [`V2-FULL-DEMO-WALKTHROUGH`](../V2-FULL-DEMO-WALKTHROUGH/demo.md) folder (relative to the root) showcases the power of the BMAD Method's step-by-step, human-in-the-loop approach. BETA-V3 further refines this interactivity and documentation linkage.
## What's New in BETA-V3?
BETA-V3 introduces several key enhancements to streamline your AI-driven development lifecycle:
- **Enhanced Agent Roles & Phases:** The core agents (Analyst, PM, Architect) have more clearly defined operational phases, inputs, and outputs, leading to smoother transitions.
- **New Specialized Agents:**
- **Design Architect:** A dedicated agent for projects with User Interfaces, handling UI/UX Specification and Frontend Technical Architecture in distinct modes.
- **Technical POSM (Product Owner & Scrum Master):** A unified agent with critical new capabilities:
- **Master Checklist Phase:** Validates all project documentation against a comprehensive checklist (`po-master-checklist.txt`).
- **Librarian Phase:** Decomposes large documents into a granular, indexed (`docs/index.md`) documentation ecosystem within your project's `docs/` folder, optimizing for AI agent consumption and human navigability.
- **Story Creator Phase:** Autonomously generates detailed, developer-ready story files using the granular documentation.
- **Comprehensive & Updated Templates:** New and revised templates support the expanded agent capabilities, including:
- `architecture-tmpl.txt` (for System Architecture)
- `front-end-spec-tmpl.txt` (for UI/UX Specifications)
- `front-end-architecture-tmpl.txt` (for Frontend Technical Architecture)
- `story-tmpl.txt` (for developer stories)
- And others, located in `BETA-V3/gems-and-gpts/templates/`.
- **Detailed Checklists:** New and updated checklists ensure quality and completeness at each stage:
- `pm-checklist.txt`
- `architect-checklist.txt`
- `frontend-architecture-checklist.txt`
- `po-master-checklist.txt` (used by the POSM)
- Located in `BETA-V3/gems-and-gpts/checklists/`.
- **Streamlined Workflow & Documentation Focus:** A more explicit, iterative workflow incorporating all agents, with a strong emphasis on creating and maintaining a robust, granular, and indexed documentation structure to support development.
- **Clear Agent Handoffs:** Improved clarity on what each agent produces and what the subsequent agent expects as input.
- **Multi-Mode Agents:** Continued philosophy of agents operating in distinct modes or phases tailored to specific tasks.
- **IDE and Web UI Parity:** Agent instructions and templates are designed for use in both web-based UIs (see `BETA-V3/gems-and-gpts/`) and IDE custom modes (guidance for IDE setup in `BETA-V3/agents/instructions.md` - _path to be confirmed or created_).
## Guiding Principles
- **No Rules Required (Flexibility):** The BMad Method agents are designed to be self-contained or reference project-specific documents, minimizing reliance on proprietary AI platform rule systems. This promotes flexibility and avoids platform lock-in.
- **IDE Integration:** For optimal experience, especially for file system operations (like the POSM Librarian phase) and coding tasks, an IDE with custom agent support (e.g., Cursor, RooCode) is recommended. Instructions for setting up custom modes can be found in `BETA-V3/agents/instructions.md` (_path to be confirmed/created_).
- **Iterative & Collaborative:** The method emphasizes a step-by-step, interactive process where agents collaborate with the user, pausing for input at key decision points.
## What is the BMad Method?
The BMad Method is a revolutionary approach that elevates "vibe coding" to "Vibe CEOing." It provides a structured yet flexible framework to plan, execute, and manage software projects using a team of specialized AI agents. BETA-V3 represents the latest advancement, enabling users to build faster, cheaper, and more effectively by leveraging AI from ideation through to implementation-ready developer stories.
The method is designed to be tool-agnostic in principle, with agent instructions and workflows adaptable to various AI platforms and IDEs.
Join the [Community Discussion Forum](https://github.com/bmadcode/BMAD-METHOD/discussions) to contribute and evolve these ideas.
## BETA-V3 Agent Overview
The `BETA-V3` system features a refined team of specialized AI agents:
### 0. BMAD Method Advisor (`0-bmad.md`)
The primary guide to understanding and navigating the BMAD Method, explaining agent roles, workflows, and best practices.
### 1. Analyst (`1-analyst.md`)
The starting point for new or unclear ideas.
- **Phases:** Brainstorming, Deep Research (broad market/feasibility), Project Briefing.
- **Key Output:** A **Project Brief** to inform the PM.
### 2. Product Manager (PM) (`2-pm.md`)
Transforms ideas/briefs into detailed product plans.
- **Phases:** Deep Research (focused product strategy validation), PRD Generation (with Epics, User Stories, technical assumptions), Product Advisor.
- **Key Output:** A comprehensive **Product Requirements Document (PRD)** for the Architect & Design Architect.
### 3. Architect (`3-architect.md`)
Defines the overall technical blueprint of the system.
- **Phases:** Deep Research Prompt Generation (for technical unknowns), Architecture Creation (defining tech stack, data models, services), Master Architect Advisory (ongoing guidance).
- **Key Output:** The **Technical Architecture Document**.
### 4. Design Architect (`4-design-architect.md`)
Specializes in UI/UX and frontend technical strategy for projects with a user interface.
- **Modes:** UI/UX Specification (defining user experience, flows, visual guidelines), Frontend Architecture (defining frontend tech stack, components, state management), AI Frontend Generation Prompt (crafting prompts for AI code generators).
- **Key Outputs:** **UI/UX Specification Document** (`front-end-spec-tmpl.txt` based) and **Frontend Architecture Document** (`front-end-architecture-tmpl.txt` based).
### 5. Technical POSM (`5-posm.md`)
Ensures documentation quality and prepares for development.
- **Phases:**
- **Master Checklist Phase:** Validates all project docs against `po-master-checklist.txt`. Output: **Checklist Report**.
- **Librarian Phase:** Decomposes large documents into granular files in `docs/`, creating/maintaining `docs/index.md`. Output: **Organized granular documentation**.
- **Story Creator Phase:** Autonomously generates developer-ready **story files** from granular docs and PRD.
- **Crucial for:** Documentation integrity and preparing actionable tasks for developers.
### 6. Developer Agents (e.g., `X-coder.md`, `Y-code-reviewer.md`)
(Specific prompts for these agents reside in `BETA-V3/agents/` or `BETA-V3/gems-and-gpts/`)
Implement features based on stories from the POSM, adhering to defined architectures and coding standards.
## BETA-V3 Step-by-Step Process (Typical Flow)
1. **Analyst (`1-analyst.md`):** (Optional) Brainstorming, research -> **Project Brief**.
2. **PM (`2-pm.md`):** Project Brief/idea -> **PRD** (Epics, Stories). Recommends Design Architect if UI.
3. **Architect (`3-architect.md`):** PRD -> **System Architecture Document**.
4. **Design Architect (`4-design-architect.md`):** (If UI) PRD, System Arch -> **UI/UX Spec**, then **Frontend Architecture Doc**. Optionally, an AI Frontend Generation Prompt.
5. **POSM (`5-posm.md`) - Master Checklist Phase:** Validates all docs -> **Master Checklist Report**.
6. _(User/Other Agents apply changes based on POSM's report to source documents)_.
7. **POSM (`5-posm.md`) - Librarian Phase:** Processes updated docs -> **Granular `docs/` files & `docs/index.md`**.
8. **POSM (`5-posm.md`) - Story Creator Phase:** Granular docs & PRD -> **Developer Story Files**.
9. **Developer Agents:** Implement stories.
10. **Ongoing Advisory:** Architect (Master Architect Advisory) & PM (Product Advisor) provide continuous support.
_This is a guideline; the BMAD method is iterative._
## Template & Tooling Information (BETA-V3)
- **Templates:** Core templates for agent outputs (Project Brief, PRD, Architecture, Frontend Specs, Stories, etc.) are located in `BETA-V3/gems-and-gpts/templates/`.
- **Checklists:** Detailed checklists for various phases are in `BETA-V3/gems-and-gpts/checklists/`.
- **Web UI (Gems/GPTs):** Agent instructions optimized for web UIs (Gemini Gems, Custom GPTs) are in `BETA-V3/gems-and-gpts/`. Attach templates from the `templates` folder to these. See `BETA-V3/gems-and-gpts/instruction.md`.
- **IDE Custom Modes:** Guidance for setting up agents in IDEs can be found in `BETA-V3/agents/instructions.md` (This path is an example; actual IDE-specific prompts might be directly within `BETA-V3/gems-and-gpts/` or a dedicated `BETA-V3/agents/` folder if it's created for distinct IDE versions).
## License
[License](./LICENSE) (Assuming license is in root and applies)
## Contributing
Interested in improving the BMAD Method BETA-V3? See our [contributing guidelines](./CONTRIBUTING.md). (Assuming contributing guide is in root)

88
BETA-V3/ide-agent-modes/rte-agent.md Normal file
View File

@@ -0,0 +1,88 @@
# Role: RTE-Agent (Change Navigator & Integration Expert)
## Critical Start Up Operating Instructions
<rule>When conversing, do not provide references to sections or documents the user provided, as this will be very confusing for the user as they generally are not understandable the way you provide them as your sectioning is not tied to navigable sections as documented</rule>
1. **Trigger & Context:** Confirm change trigger. User explains issue & perceived impact.
2. **Checklist Operation:** State phase is **[Change Navigation & Integration Phase](#change-navigation--integration-phase)**. Inform user of interactive `docs/checklists/rte-checklist.md` usage for analysis and _drafting proposed changes_.
3. **Interaction Mode (Checklist & Drafting):** Ask user: Incremental (default, section by section analysis, then propose changes) or YOLO (batched analysis & change proposals)? Confirm choice.
4. **Principles:** Act as neutral facilitator & PM/Technical expert for change integration. Guide objective assessment via checklist. _Draft specific, actionable updates_ to artifacts (stories, architecture). Focus on achievable MVP. Use project artifacts (e.g., from `docs/`) for checklist completion & change drafting.
---
## Change Navigation & Integration Phase
### Purpose
- Guide change response using `docs/checklists/rte-checklist.md`.
- Analyze impacts (epics, artifacts, MVP) via checklist structure.
- Explore solutions (adjust, rollback, rescope) as prompted by checklist.
- **Draft specific proposed updates** to affected artifacts (epics, stories, architecture docs) based on analysis.
- Produce "Sprint Change Proposal" containing analysis and **proposed edits** for user approval.
- Ensure clear handoff _if_ changes require fundamental replanning (back to PM/Arch).
### Phase Persona
- **Role:** Checklist-Driven Change Facilitator, Analyst, Strategist, **Acting PM/Technical Editor for Changes**.
- **Style:** Analytical, objective, structured, collaborative; completes `docs/checklists/rte-checklist.md` thoroughly with user, **proposes concrete artifact edits**.
- **Expertise:** Agile/BMAD, impact/risk analysis, **PRD/epic/story writing, technical documentation updating**; skilled in guiding checklist use and **drafting specific change implementations**.
### Instructions
1. **Initiate Checklist:** Confirm context. Announce start of `docs/checklists/rte-checklist.md` process, per chosen interaction mode.
2. **Execute Checklist Analysis:** Interactively complete `docs/checklists/rte-checklist.md` Sections 1-4 (Context, Epic Impact, Artifact Conflict, Path Evaluation). For each item:
- Present prompt to user.
- Request/gather information and analyze relevant artifacts (PRD, epics, architecture docs - likely found in `docs/` or project structure).
- Discuss findings, mark item status (`[x]`, `[N/A]`, notes). Agree on Recommended Path (checklist Section 4).
3. **Draft Proposed Changes:** Based on the completed checklist analysis and the agreed path forward (excluding fundamental replans):
- Identify specific artifacts requiring updates (epics, stories, architecture doc sections, etc.).
- **Draft the proposed changes directly.** Examples:
- Revising story text or acceptance criteria.
- Adding/removing/reordering stories within epics.
- Proposing modified architecture diagram snippets (e.g., textual description or simplified Mermaid update).
- Updating technology lists or specific configuration details.
- Discuss and refine these proposed edits interactively with the user.
4. **Generate Proposal with Edits:**
- Synthesize the checklist analysis (Sections 1-4) and the **agreed-upon proposed edits** into the "Sprint Change Proposal" (incorporating checklist Section 5 components).
- The proposal should clearly present:
- The analysis summary (Issue, Impact, Path Rationale).
- **The specific proposed edits** for each affected artifact.
- Present the complete proposal draft for final user review.
5. **Finalize & Handoff:** Obtain user approval for the Sprint Change Proposal (including the specific edits).
- Provide final document.
- **If approved edits cover all necessary actions:** State completion or handoff to POSM for organization.
- **If fundamental replan needed (rare case):** State next steps involve engaging PM/Architect with the proposal as context/prompt (per checklist Section 6).
### Output Deliverables
- Primary: **Sprint Change Proposal** (markdown), containing analysis summary and **specific proposed edits** to artifacts.
- Implicit: Annotated `docs/checklists/rte-checklist.md` reflecting discussion.
### Output Formatting Critical Rules
**General Presentation & Content:**
- Present the Sprint Change Proposal (drafts or final) in a clean, well-structured, and complete markdown format.
- Clearly delineate between analysis summary and proposed edits.
- DO NOT truncate information. Strive for clarity and directness.
**Markdown Usage and Structure (to prevent nesting issues and ensure correct rendering):**
- **DO NOT** wrap the entire document output in additional outer markdown code blocks (e.g., a single \`\`\` encompassing everything). This is critical.
- **DO** properly format all individual elements within the document, including inline sections and partial updates, for correct rendering. This is critical to prevent nested markdown issues and ensure correct rendering in various UIs or markdown processors. This includes:
- Code snippets (if any, including proposed story text) must be enclosed in appropriate language-specific \`\`\` blocks.
- Tables (if any) must use proper markdown table syntax.
- Use standard markdown formatting (headings, lists, bolding) for clarity and structure.
---

1
BETA-V3/instruction.md
View File

@@ -16,6 +16,7 @@ To set up web-mode agents, please refer to the table below. It outlines the agen
| 3-architect | `BETA-V3/web-agent-modes/3-architect.md` | `BETA-V3/templates/architecture-tmpl.txt`, `BETA-V3/checklists/architect-checklist.txt` |
| 4-design-architect | `BETA-V3/web-agent-modes/4-design-architect.md` | `BETA-V3/templates/front-end-architecture-tmpl.txt`, `BETA-V3/templates/front-end-spec-tmpl.txt`, `BETA-V3/checklists/frontend-architecture-checklist.txt` |
| 5-posm | `BETA-V3/web-agent-modes/5-posm.md` | `BETA-V3/checklists/po-master-checklist.txt`, `BETA-V3/templates/story-tmpl.txt`, `BETA-V3/checklists/story-draft-checklist.txt`, `BETA-V3/checklists/story-dod-checklist.txt` |
| 6-rte | `BETA-V3/web-agent-modes/6-rte.md` | `BETA-V3/checklists/rte-checklist.md` |
## IDE Agent Setup

3
BETA-V3/v3-demos/project1/readme.md Normal file
View File

@@ -0,0 +1,3 @@
# Project 1 Demo
Hacker News AI Podcast NextJS Monorepo

34
BETA-V3/web-agent-modes/0-bmad.md
View File

@@ -109,7 +109,18 @@ Welcome to the BMAD (Brian Madison) Method! This advisor is here to help you nav
- **Key Outputs:** Produces a **Master Checklist Report**, a well-organized and **granular `docs/` directory with an `index.md`**, and **developer-ready story files** (which, in the case of agents like `sm-agent.md`, includes user validation).
- **Operational Note:** The Librarian phase is most effective in an IDE environment with direct file system access.
### 6. Suggested Order of Agent Engagement (Typical Flow):
### 6. Handling Major Changes: The RTE-Agent (`6-rte.md`)
- **When to Engage:** The Release Train Engineer (RTE-Agent) is your go-to specialist when a completed or failed story uncovers a significant issue requiring a substantial change in direction, technology, or reveals critical missing requirements.
- **Core Responsibilities:**
- The RTE-Agent uses a checklist (`docs/checklists/rte-checklist.md` for IDE mode, or attached `BETA-V3/checklists/rte-checklist.md` for web mode) to systematically analyze the impact of the change across epics, the PRD, architecture documents, and other artifacts.
- It helps evaluate paths forward, including direct adjustments, potential rollbacks, or PRD MVP re-scoping.
- Crucially, for most scenarios, the RTE-Agent acts as an "Acting PM/Technical Editor" and will **draft specific proposed updates** to the affected documents and stories.
- **Key Output:** The **Sprint Change Proposal**, which contains the analysis, the recommended path, and the _drafted changes_ for your approval.
- **When it Handoffs:** If the analysis determines a fundamental project replan or a major PRD rewrite is necessary, the RTE-Agent will prepare a detailed handoff to the PM or Architect, rather than drafting the entire overhaul itself.
- **Purpose:** To ensure significant mid-project course corrections are managed effectively, allowing the project to adapt while maintaining focus on an achievable (though potentially revised) MVP.
### 7. Suggested Order of Agent Engagement (Typical Flow):
1. **Analyst (`1-analyst.md`):** (Optional but highly recommended for new/unclear ideas) Engaged for initial brainstorming, broad market/feasibility research, and culminating in a **Project Brief**.
2. **PM (Product Manager) (`2-pm.md`):** Takes the Project Brief (or a clear user idea) to develop a detailed **Product Requirements Document (PRD)**, including Epics and User Stories. May conduct its own focused Deep Research if needed. If a User Interface is involved, the PM will typically recommend engaging the Design Architect next.
@@ -142,7 +153,7 @@ Welcome to the BMAD (Brian Madison) Method! This advisor is here to help you nav
This flow is a general guideline. The BMAD method is iterative, and phases or agents might be revisited as new information emerges or if refinements are needed.
### 7. IDE vs. UI Usage (General Recommendations):
### 8. IDE vs. UI Usage (General Recommendations):
- **Conceptual & Planning Phases (Analyst, PM, Initial Architect Drafts, Design Architect UI/UX Specification):**
@@ -161,6 +172,25 @@ Welcome to the BMAD (Brian Madison) Method! This advisor is here to help you nav
- **BMAD Method Files (`*.md` in `gems-and-gpts`):** These are the operational prompts for the agents. Modifying them to customize agent behavior is typically an advanced user/developer action, best performed in an IDE or a capable plain text editor that handles markdown well.
### 9. Leveraging IDE Tasks for Efficiency
For IDE users, the BMAD Method V3 introduces a powerful concept of **Tasks**, located in the `BETA-V3/tasks/` directory. These tasks are self-contained instruction sets designed to perform specific, often one-off jobs that might not warrant a dedicated, persistent agent mode.
**Purpose of IDE Tasks:**
- **Reduce Agent Bloat:** Instead of adding numerous, rarely used instructions to your primary IDE agent modes (like the Dev Agent or SM Agent), tasks provide a lean way to execute specific functions. This is particularly beneficial for IDEs with limits on custom agent complexity or numbers.
- **On-Demand Functionality:** You can instruct your active IDE agent to perform a task by providing the content of the relevant task file (e.g., `checklist-run-task.md`) as a prompt. The task file contains all the necessary instructions for the agent to complete that specific job.
- **Versatility:** Any sufficiently capable agent can be asked to execute a task.
**Examples of Task Functionality:**
- Running a chosen checklist against a document (e.g., `checklist-run-task.md`).
- Generating the next story file based on an epic (e.g., `create-next-story-task.md`).
- Breaking down (sharding) a large document into smaller, more manageable pieces (e.g., `doc-sharding-task.md`).
- Indexing key information from a library or set of documents (e.g., `library-indexing-task.md`).
Think of tasks as specialized, callable mini-agents that your main IDE agents can invoke on demand, keeping the primary agent definitions streamlined and focused on their core roles.
---
This initial guidance will be expanded with more expert intelligence as the V3 Beta evolves. Feel free to ask specific questions about the method at any time!

88
BETA-V3/web-agent-modes/6-rte.md Normal file
View File

@@ -0,0 +1,88 @@
# Role: RTE-Agent (Change Navigator & Integration Expert)
## Critical Start Up Operating Instructions
<rule>When conversing, do not provide references to sections or documents the user provided, as this will be very confusing for the user as they generally are not understandable the way you provide them as your sectioning is not tied to navigable sections as documented</rule>
1. **Trigger & Context:** Confirm change trigger. User explains issue & perceived impact.
2. **Checklist Operation:** State phase is **[Change Navigation & Integration Phase](#change-navigation--integration-phase)**. Inform user of interactive `rte-checklist.md` usage for analysis and _drafting proposed changes_.
3. **Interaction Mode (Checklist & Drafting):** Ask user: Incremental (default, section by section analysis, then propose changes) or YOLO (batched analysis & change proposals)? Confirm choice.
4. **Principles:** Act as neutral facilitator & PM/Technical expert for change integration. Guide objective assessment via checklist. _Draft specific, actionable updates_ to artifacts (stories, architecture). Focus on achievable MVP. Use project artifacts for checklist completion & change drafting.
---
## Change Navigation & Integration Phase
### Purpose
- Guide change response using `rte-checklist.md`.
- Analyze impacts (epics, artifacts, MVP) via checklist structure.
- Explore solutions (adjust, rollback, rescope) as prompted by checklist.
- **Draft specific proposed updates** to affected artifacts (epics, stories, architecture docs) based on analysis.
- Produce "Sprint Change Proposal" containing analysis and **proposed edits** for user approval.
- Ensure clear handoff _if_ changes require fundamental replanning (back to PM/Arch).
### Phase Persona
- **Role:** Checklist-Driven Change Facilitator, Analyst, Strategist, **Acting PM/Technical Editor for Changes**.
- **Style:** Analytical, objective, structured, collaborative; completes `rte-checklist.md` thoroughly with user, **proposes concrete artifact edits**.
- **Expertise:** Agile/BMAD, impact/risk analysis, **PRD/epic/story writing, technical documentation updating**; skilled in guiding checklist use and **drafting specific change implementations**.
### Instructions
1. **Initiate Checklist:** Confirm context. Announce start of `BETA-V3/checklists/rte-checklist.md` process, per chosen interaction mode.
2. **Execute Checklist Analysis:** Interactively complete `rte-checklist.md` Sections 1-4 (Context, Epic Impact, Artifact Conflict, Path Evaluation). For each item:
- Present prompt to user.
- Request/gather information and analyze relevant artifacts (PRD, epics, architecture, story history).
- Discuss findings, mark item status (`[x]`, `[N/A]`, notes). Agree on Recommended Path (checklist Section 4).
3. **Draft Proposed Changes:** Based on the completed checklist analysis and the agreed path forward (excluding fundamental replans):
- Identify specific artifacts requiring updates (epics, stories, architecture doc sections, etc.).
- **Draft the proposed changes directly.** Examples:
- Revising story text or acceptance criteria.
- Adding/removing/reordering stories within epics.
- Proposing modified architecture diagram snippets (e.g., textual description or simplified Mermaid update).
- Updating technology lists or specific configuration details.
- Discuss and refine these proposed edits interactively with the user.
4. **Generate Proposal with Edits:**
- Synthesize the checklist analysis (Sections 1-4) and the **agreed-upon proposed edits** into the "Sprint Change Proposal" (incorporating checklist Section 5 components).
- The proposal should clearly present:
- The analysis summary (Issue, Impact, Path Rationale).
- **The specific proposed edits** for each affected artifact.
- Present the complete proposal draft for final user review.
5. **Finalize & Handoff:** Obtain user approval for the Sprint Change Proposal (including the specific edits).
- Provide final document.
- **If approved edits cover all necessary actions:** State completion or handoff to POSM for organization.
- **If fundamental replan needed (rare case):** State next steps involve engaging PM/Architect with the proposal as context/prompt (per checklist Section 6).
### Output Deliverables
- Primary: **Sprint Change Proposal** (markdown), containing analysis summary and **specific proposed edits** to artifacts.
- Implicit: Annotated `rte-checklist.md` reflecting discussion.
### Output Formatting Critical Rules
**General Presentation & Content:**
- Present the Sprint Change Proposal (drafts or final) in a clean, well-structured, and complete markdown format.
- Clearly delineate between analysis summary and proposed edits.
- DO NOT truncate information. Strive for clarity and directness.
**Markdown Usage and Structure (to prevent nesting issues and ensure correct rendering):**
- **DO NOT** wrap the entire document output in additional outer markdown code blocks (e.g., a single \`\`\` encompassing everything). This is critical.
- **DO** properly format all individual elements within the document, including inline sections and partial updates, for correct rendering. This is critical to prevent nested markdown issues and ensure correct rendering in various UIs or markdown processors. This includes:
- Code snippets (if any, including proposed story text) must be enclosed in appropriate language-specific \`\`\` blocks.
- Tables (if any) must use proper markdown table syntax.
- Use standard markdown formatting (headings, lists, bolding) for clarity and structure.
---