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

web build optimization

Browse Source
This commit is contained in:
Brian Madison
2025-07-06 10:32:39 -05:00
parent 4b0a9235ab
commit 5fc69d773a
30 changed files with 1346 additions and 1360 deletions
Download Patch File Download Diff File Expand all files Collapse all files

145
dist/teams/team-ide-minimal.txt vendored
View File

@@ -8,14 +8,14 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
- `==================== START: .bmad-core/folder/filename.md ====================`
- `==================== END: .bmad-core/folder/filename.md ====================`
When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
These references map directly to bundle sections:
- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
@@ -38,7 +38,8 @@ These references map directly to bundle sections:
---
==================== START: agent-teams#team-ide-minimal ====================
==================== START: .bmad-core/agent-teams/team-ide-minimal.yaml ====================
bundle:
name: Team IDE Minimal
icon: ⚡
@@ -49,9 +50,9 @@ agents:
- dev
- qa
workflows: null
==================== END: agent-teams#team-ide-minimal ====================
==================== END: .bmad-core/agent-teams/team-ide-minimal.yaml ====================
==================== START: agents#bmad-orchestrator ====================
==================== START: .bmad-core/agents/bmad-orchestrator.md ====================
# bmad-orchestrator
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -82,7 +83,7 @@ startup:
- Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows
- IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
- Mention *help shows all available commands and options
- Check for active workflow plan using utils#plan-management
- Check for active workflow plan using .bmad-core/utils/plan-management.md
- 'If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details.'
- 'If plan exists: Suggest next action based on plan progress'
- Assess user goal against available agents and workflows in this bundle
@@ -188,9 +189,9 @@ dependencies:
- workflow-management
- template-format
```
==================== END: agents#bmad-orchestrator ====================
==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
==================== START: agents#po ====================
==================== START: .bmad-core/agents/po.md ====================
# po
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -254,9 +255,9 @@ dependencies:
utils:
- template-format
```
==================== END: agents#po ====================
==================== END: .bmad-core/agents/po.md ====================
==================== START: agents#sm ====================
==================== START: .bmad-core/agents/sm.md ====================
# sm
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -304,9 +305,9 @@ dependencies:
utils:
- template-format
```
==================== END: agents#sm ====================
==================== END: .bmad-core/agents/sm.md ====================
==================== START: agents#dev ====================
==================== START: .bmad-core/agents/dev.md ====================
# dev
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -321,7 +322,7 @@ agent:
customization: null
startup:
- Announce: Greet the user with your name and role, and inform of the *help command.
- CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - {root}/core-config.yaml devLoadAlwaysFiles list
- CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - .bmad-core/core-config.yaml devLoadAlwaysFiles list
- CRITICAL: Do NOT load any other files during startup aside from the assigned story and devLoadAlwaysFiles items, unless user requested you do or the following contradicts
- CRITICAL: Do NOT begin development until a story is not in draft mode and you are told to proceed
persona:
@@ -355,9 +356,9 @@ dependencies:
checklists:
- story-dod-checklist
```
==================== END: agents#dev ====================
==================== END: .bmad-core/agents/dev.md ====================
==================== START: agents#qa ====================
==================== START: .bmad-core/agents/qa.md ====================
# qa
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -410,9 +411,9 @@ dependencies:
utils:
- template-format
```
==================== END: agents#qa ====================
==================== END: .bmad-core/agents/qa.md ====================
==================== START: tasks#advanced-elicitation ====================
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
# Advanced Elicitation Task
## Purpose
@@ -530,9 +531,9 @@ Choose a number (0-8) or 9 to proceed:
- **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
- **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
- **Maintain Flow**: Keep the process moving efficiently
==================== END: tasks#advanced-elicitation ====================
==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
==================== START: tasks#create-doc ====================
==================== START: .bmad-core/tasks/create-doc.md ====================
# Create Document from Template Task
## Purpose
@@ -552,7 +553,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If `workflow.trackProgress: true`, check for active plan using .bmad-core/utils/plan-management.md
- If plan exists and this document creation is part of the plan:
- Verify this is the expected next step
- If out of sequence and `enforceSequence: true`, warn user and halt without user override
@@ -561,7 +562,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 1. Identify Template
- Load from `templates#*` or `{root}/templates directory`
- Load from `.bmad-core/templates/*.md` or `.bmad-core/templates directory`
- Agent-specific templates are listed in agent's dependencies
- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
@@ -579,14 +580,14 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 4. Key Execution Patterns
**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
**When you see:** `[[LLM: Draft X and immediately execute .bmad-core/tasks/advanced-elicitation.md]]`
- Draft the content
- Present it to user
- IMMEDIATELY execute the task
- Wait for completion before continuing
**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
**When you see:** `[[LLM: After section completion, apply .bmad-core/tasks/Y.md]]`
- Finish the section
- STOP and execute the task
@@ -624,9 +625,9 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
## Remember
Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
==================== END: tasks#create-doc ====================
==================== END: .bmad-core/tasks/create-doc.md ====================
==================== START: tasks#create-workflow-plan ====================
==================== START: .bmad-core/tasks/create-workflow-plan.md ====================
# Create Workflow Plan Task
## Purpose
@@ -916,9 +917,9 @@ BMad Orchestrator: "Based on your answers, I recommend the brownfield-fullstack
BMad Orchestrator: "I've created a workflow plan at docs/workflow-plan.md. This shows all the steps we'll go through, what documents will be created, and where you'll need to make decisions. Would you like to review it together?"
```
==================== END: tasks#create-workflow-plan ====================
==================== END: .bmad-core/tasks/create-workflow-plan.md ====================
==================== START: tasks#kb-mode-interaction ====================
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
# KB Mode Interaction Task
## Purpose
@@ -989,9 +990,9 @@ Or ask me about anything else related to BMad-Method!
**User**: Tell me about workflows
**Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
==================== END: tasks#kb-mode-interaction ====================
==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
==================== START: tasks#update-workflow-plan ====================
==================== START: .bmad-core/tasks/update-workflow-plan.md ====================
# Update Workflow Plan Task
## Purpose
@@ -1240,9 +1241,9 @@ The update is successful when:
- Consider creating backup before major updates
- Updates should enhance, not complicate, the workflow experience
- If plan becomes too cluttered, suggest creating fresh plan for next phase
==================== END: tasks#update-workflow-plan ====================
==================== END: .bmad-core/tasks/update-workflow-plan.md ====================
==================== START: data#bmad-kb ====================
==================== START: .bmad-core/data/bmad-kb.md ====================
# BMad Knowledge Base
## Overview
@@ -2053,9 +2054,9 @@ Use the **expansion-creator** pack to build your own:
- **Documentation**: Check `docs/` folder for project-specific context
- **Community**: Discord and GitHub resources available for support
- **Contributing**: See `CONTRIBUTING.md` for full guidelines
==================== END: data#bmad-kb ====================
==================== END: .bmad-core/data/bmad-kb.md ====================
==================== START: utils#plan-management ====================
==================== START: .bmad-core/utils/plan-management.md ====================
# Plan Management Utility
## Purpose
@@ -2275,9 +2276,9 @@ Would you like to:
- Malformed plan: Warn but continue, treat as no plan
- Update failures: Log but don't block task completion
- Parse errors: Fallback to basic text search
==================== END: utils#plan-management ====================
==================== END: .bmad-core/utils/plan-management.md ====================
==================== START: utils#workflow-management ====================
==================== START: .bmad-core/utils/workflow-management.md ====================
# Workflow Management
Enables BMad orchestrator to manage and execute team workflows.
@@ -2347,9 +2348,9 @@ Handle conditional paths by asking clarifying questions when needed.
## Agent Integration
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
==================== END: utils#workflow-management ====================
==================== END: .bmad-core/utils/workflow-management.md ====================
==================== START: utils#template-format ====================
==================== START: .bmad-core/utils/template-format.md ====================
# Template Format Conventions
Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
@@ -2376,16 +2377,16 @@ Templates in the BMad method use standardized markup for AI processing. These co
- Template elements are for AI processing only
- Focus on faithful template execution and clean output
- All template-specific instructions are embedded within templates
==================== END: utils#template-format ====================
==================== END: .bmad-core/utils/template-format.md ====================
==================== START: tasks#execute-checklist ====================
==================== START: .bmad-core/tasks/execute-checklist.md ====================
# Checklist Validation Task
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the .bmad-core/checklists folder to select the appropriate one to run.
## Instructions
@@ -2394,7 +2395,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from {root}/checklists/
- Load the appropriate checklist from .bmad-core/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder
@@ -2472,9 +2473,9 @@ The LLM will:
- Execute the complete checklist validation
- Present a final report with pass/fail rates and key findings
- Offer to provide detailed analysis of any section, especially those with warnings or failures
==================== END: tasks#execute-checklist ====================
==================== END: .bmad-core/tasks/execute-checklist.md ====================
==================== START: tasks#shard-doc ====================
==================== START: .bmad-core/tasks/shard-doc.md ====================
# Document Sharding Task
## Purpose
@@ -2666,9 +2667,9 @@ Document sharded successfully:
- Preserve ALL formatting, including whitespace where significant
- Handle edge cases like sections with code blocks containing ## symbols
- Ensure the sharding is reversible (could reconstruct the original from shards)
==================== END: tasks#shard-doc ====================
==================== END: .bmad-core/tasks/shard-doc.md ====================
==================== START: tasks#correct-course ====================
==================== START: .bmad-core/tasks/correct-course.md ====================
# Correct Course Task
## Purpose
@@ -2742,9 +2743,9 @@ Document sharded successfully:
- A summary of the `change-checklist` analysis (issue, impact, rationale for the chosen path).
- Specific, clearly drafted proposed edits for all affected project artifacts.
- **Implicit:** An annotated `change-checklist` (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
==================== END: tasks#correct-course ====================
==================== END: .bmad-core/tasks/correct-course.md ====================
==================== START: tasks#brownfield-create-epic ====================
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
# Create Brownfield Epic Task
## Purpose
@@ -2905,9 +2906,9 @@ The epic creation is successful when:
- If the scope grows beyond 3 stories, consider the full brownfield PRD process
- Always prioritize existing system integrity over new functionality
- When in doubt about scope or complexity, escalate to full brownfield planning
==================== END: tasks#brownfield-create-epic ====================
==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
==================== START: tasks#brownfield-create-story ====================
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
# Create Brownfield Story Task
## Purpose
@@ -3055,9 +3056,9 @@ The story creation is successful when:
- Always prioritize existing system integrity
- When in doubt about integration complexity, use brownfield-create-epic instead
- Stories should take no more than 4 hours of focused development work
==================== END: tasks#brownfield-create-story ====================
==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
==================== START: tasks#validate-next-story ====================
==================== START: .bmad-core/tasks/validate-next-story.md ====================
# Validate Next Story Task
## Purpose
@@ -3192,9 +3193,9 @@ Provide a structured validation report including:
- **NO-GO**: Story requires fixes before implementation
- **Implementation Readiness Score**: 1-10 scale
- **Confidence Level**: High/Medium/Low for successful implementation
==================== END: tasks#validate-next-story ====================
==================== END: .bmad-core/tasks/validate-next-story.md ====================
==================== START: templates#story-tmpl ====================
==================== START: .bmad-core/templates/story-tmpl.md ====================
---
defaultOutput: docs/stories/{{EpicNum}}.{{StoryNum}}.{{Short Title Copied from Epic File specific story}}.md
smAgent:
@@ -3253,9 +3254,9 @@ smAgent:
### File List
## QA Results
==================== END: templates#story-tmpl ====================
==================== END: .bmad-core/templates/story-tmpl.md ====================
==================== START: checklists#po-master-checklist ====================
==================== START: .bmad-core/checklists/po-master-checklist.md ====================
# Product Owner (PO) Master Validation Checklist
This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
@@ -3697,9 +3698,9 @@ After presenting the report, ask if the user wants:
- **APPROVED**: The plan is comprehensive, properly sequenced, and ready for implementation.
- **CONDITIONAL**: The plan requires specific adjustments before proceeding.
- **REJECTED**: The plan requires significant revision to address critical deficiencies.
==================== END: checklists#po-master-checklist ====================
==================== END: .bmad-core/checklists/po-master-checklist.md ====================
==================== START: checklists#change-checklist ====================
==================== START: .bmad-core/checklists/change-checklist.md ====================
# Change Navigation Checklist
**Purpose:** To systematically guide the selected 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.
@@ -3882,9 +3883,9 @@ Keep it action-oriented and forward-looking.]]
- [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
---
==================== END: checklists#change-checklist ====================
==================== END: .bmad-core/checklists/change-checklist.md ====================
==================== START: tasks#create-next-story ====================
==================== START: .bmad-core/tasks/create-next-story.md ====================
# Create Next Story Task
## Purpose
@@ -3999,9 +4000,9 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
- Any deviations or conflicts noted between epic and architecture
- Checklist Results
- Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `validate-next-story`
==================== END: tasks#create-next-story ====================
==================== END: .bmad-core/tasks/create-next-story.md ====================
==================== START: checklists#story-draft-checklist ====================
==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
# Story Draft Checklist
The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
@@ -4158,9 +4159,9 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
- READY: The story provides sufficient context for implementation
- NEEDS REVISION: The story requires updates (see issues)
- BLOCKED: External information required (specify what information)
==================== END: checklists#story-draft-checklist ====================
==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
==================== START: checklists#story-dod-checklist ====================
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
# Story Definition of Done (DoD) Checklist
## Instructions for Developer Agent
@@ -4262,9 +4263,9 @@ After completing the checklist:
Be honest - it's better to flag issues now than have them discovered later.]]
- [ ] I, the Developer Agent, confirm that all applicable items above have been addressed.
==================== END: checklists#story-dod-checklist ====================
==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
==================== START: tasks#review-story ====================
==================== START: .bmad-core/tasks/review-story.md ====================
# review-story
When a developer marks a story as "Ready for Review", perform a comprehensive senior developer code review with the ability to refactor and improve code directly.
@@ -4410,10 +4411,10 @@ After review:
1. If all items are checked and approved: Update story status to "Done"
2. If unchecked items remain: Keep status as "Review" for dev to address
3. Always provide constructive feedback and explanations for learning
==================== END: tasks#review-story ====================
==================== END: .bmad-core/tasks/review-story.md ====================
==================== START: data#technical-preferences ====================
==================== START: .bmad-core/data/technical-preferences.md ====================
# User-Defined Preferred Patterns and Preferences
None Listed
==================== END: data#technical-preferences ====================
==================== END: .bmad-core/data/technical-preferences.md ====================