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

259
dist/teams/team-no-ui.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-no-ui ====================
==================== START: .bmad-core/agent-teams/team-no-ui.yaml ====================
bundle:
name: Team No UI
icon: 🔧
@@ -52,9 +53,9 @@ agents:
workflows:
- greenfield-service
- brownfield-service
==================== END: agent-teams#team-no-ui ====================
==================== END: .bmad-core/agent-teams/team-no-ui.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:
@@ -85,7 +86,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
@@ -191,9 +192,9 @@ dependencies:
- workflow-management
- template-format
```
==================== END: agents#bmad-orchestrator ====================
==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
==================== START: agents#analyst ====================
==================== START: .bmad-core/agents/analyst.md ====================
# analyst
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:
@@ -259,9 +260,9 @@ dependencies:
utils:
- template-format
```
==================== END: agents#analyst ====================
==================== END: .bmad-core/agents/analyst.md ====================
==================== START: agents#pm ====================
==================== START: .bmad-core/agents/pm.md ====================
# pm
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,9 +322,9 @@ dependencies:
utils:
- template-format
```
==================== END: agents#pm ====================
==================== END: .bmad-core/agents/pm.md ====================
==================== START: agents#architect ====================
==================== START: .bmad-core/agents/architect.md ====================
# architect
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:
@@ -386,9 +387,9 @@ dependencies:
utils:
- template-format
```
==================== END: agents#architect ====================
==================== END: .bmad-core/agents/architect.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:
@@ -452,9 +453,9 @@ dependencies:
utils:
- template-format
```
==================== END: agents#po ====================
==================== END: .bmad-core/agents/po.md ====================
==================== START: tasks#advanced-elicitation ====================
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
# Advanced Elicitation Task
## Purpose
@@ -572,9 +573,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
@@ -594,7 +595,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
@@ -603,7 +604,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
@@ -621,14 +622,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
@@ -666,9 +667,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
@@ -958,9 +959,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
@@ -1031,9 +1032,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
@@ -1282,9 +1283,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
@@ -2095,9 +2096,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
@@ -2317,9 +2318,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.
@@ -2389,9 +2390,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.
@@ -2418,9 +2419,9 @@ 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#facilitate-brainstorming-session ====================
==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
---
docOutputLocation: docs/brainstorming-session-results.md
template: brainstorming-output-tmpl
@@ -2557,9 +2558,9 @@ Generate structured document with these sections:
- Always ask before switching techniques: "Ready to try a different approach?"
- Offer options: "Should we explore this idea deeper or generate more alternatives?"
- Respect their process and timing
==================== END: tasks#facilitate-brainstorming-session ====================
==================== END: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
==================== START: tasks#create-deep-research-prompt ====================
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
# Create Deep Research Prompt Task
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -2861,9 +2862,9 @@ Present these numbered options to the user:
- Balance comprehensiveness with focus
- Document assumptions and limitations clearly
- Plan for iterative refinement based on initial findings
==================== END: tasks#create-deep-research-prompt ====================
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
==================== START: tasks#document-project ====================
==================== START: .bmad-core/tasks/document-project.md ====================
# Document an Existing Project
## Purpose
@@ -3181,9 +3182,9 @@ Apply the advanced elicitation task after major sections to refine based on user
- Documents technical debt, workarounds, and constraints honestly
- For brownfield projects with PRD: Provides clear enhancement impact analysis
- The goal is PRACTICAL documentation for AI agents doing real work
==================== END: tasks#document-project ====================
==================== END: .bmad-core/tasks/document-project.md ====================
==================== START: templates#project-brief-tmpl ====================
==================== START: .bmad-core/templates/project-brief-tmpl.md ====================
---
defaultOutput: docs/brief.md
---
@@ -3416,9 +3417,9 @@ This Project Brief provides the full context for {{Project Name}}. Please start
9. Proceed to next section
These replace the standard elicitation options when working on project brief documents.]]
==================== END: templates#project-brief-tmpl ====================
==================== END: .bmad-core/templates/project-brief-tmpl.md ====================
==================== START: templates#market-research-tmpl ====================
==================== START: .bmad-core/templates/market-research-tmpl.md ====================
# Market Research Report: {{Project/Product Name}}
[[LLM: The default path and filename unless specified is docs/market-research.md]]
@@ -3682,9 +3683,9 @@ These replace the standard elicitation options when working on project brief doc
9. Proceed to next section
These replace the standard elicitation options when working on market research documents.]]
==================== END: templates#market-research-tmpl ====================
==================== END: .bmad-core/templates/market-research-tmpl.md ====================
==================== START: templates#competitor-analysis-tmpl ====================
==================== START: .bmad-core/templates/competitor-analysis-tmpl.md ====================
# Competitive Analysis Report: {{Project/Product Name}}
[[LLM: The default path and filename unless specified is docs/competitor-analysis.md]]
@@ -3976,9 +3977,9 @@ These replace the standard elicitation options when working on market research d
9. Proceed to next section
These replace the standard elicitation options when working on competitive analysis documents.]]
==================== END: templates#competitor-analysis-tmpl ====================
==================== END: .bmad-core/templates/competitor-analysis-tmpl.md ====================
==================== START: templates#brainstorming-output-tmpl ====================
==================== START: .bmad-core/templates/brainstorming-output-tmpl.md ====================
---
defaultOutput: docs/brainstorming-session-results.md
---
@@ -4128,9 +4129,9 @@ defaultOutput: docs/brainstorming-session-results.md
---
*Session facilitated using the BMAD-METHOD brainstorming framework*
==================== END: templates#brainstorming-output-tmpl ====================
==================== END: .bmad-core/templates/brainstorming-output-tmpl.md ====================
==================== START: data#brainstorming-techniques ====================
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
# Brainstorming Techniques Data
## Creative Expansion
@@ -4167,9 +4168,9 @@ defaultOutput: docs/brainstorming-session-results.md
18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
19. **Metaphor Mapping**: Use extended metaphors to explore solutions
20. **Question Storming**: Generate questions instead of answers first
==================== END: data#brainstorming-techniques ====================
==================== END: .bmad-core/data/brainstorming-techniques.md ====================
==================== START: tasks#correct-course ====================
==================== START: .bmad-core/tasks/correct-course.md ====================
# Correct Course Task
## Purpose
@@ -4243,9 +4244,9 @@ defaultOutput: docs/brainstorming-session-results.md
- 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
@@ -4406,9 +4407,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
@@ -4556,16 +4557,16 @@ 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#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
@@ -4574,7 +4575,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
@@ -4652,9 +4653,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
@@ -4846,9 +4847,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: templates#prd-tmpl ====================
==================== START: .bmad-core/templates/prd-tmpl.md ====================
# {{Project Name}} Product Requirements Document (PRD)
[[LLM: The default path and filename unless specified is docs/prd.md]]
@@ -4876,7 +4877,7 @@ Document sharded successfully:
## Requirements
[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute tasks#advanced-elicitation display]]
[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute .bmad-core/tasks/advanced-elicitation.md display]]
### Functional
@@ -4899,7 +4900,7 @@ Document sharded successfully:
3. Clearly let the user know where assumptions were made
4. Ask targeted questions for unclear/missing elements or areas needing more specification
5. This is NOT detailed UI spec - focus on product vision and user goals
6. After section completion, immediately apply `tasks#advanced-elicitation` protocol]]
6. After section completion, immediately apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
### Overall UX Vision
@@ -4941,12 +4942,12 @@ Document sharded successfully:
[[LLM: Gather technical decisions that will guide the Architect. Steps:
1. Check if `data#technical-preferences` or an attached `technical-preferences` file exists - use it to pre-populate choices
1. Check if `.bmad-core/data/technical-preferences.yaml` or an attached `technical-preferences` file exists - use it to pre-populate choices
2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
3. For unknowns, offer guidance based on project goals and MVP scope
4. Document ALL technical choices with rationale (why this choice fits the project)
5. These become constraints for the Architect - be specific and complete
6. After section completion, apply `tasks#advanced-elicitation` protocol.]]
6. After section completion, apply `.bmad-core/tasks/advanced-elicitation.md` protocol.]]
### Repository Structure: { Monorepo, Polyrepo, etc...}
@@ -4964,7 +4965,7 @@ Document sharded successfully:
## Epics
[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute tasks#advanced-elicitation display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute .bmad-core/tasks/advanced-elicitation.md display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
CRITICAL: Epics MUST be logically sequential following agile best practices:
@@ -4990,7 +4991,7 @@ CRITICAL: Epics MUST be logically sequential following agile best practices:
@{/example}
[[LLM: After the epic list is approved, present each `epic_details` with all its stories and acceptance criteria as a complete review unit and immediately execute tasks#advanced-elicitation display, before moving on to the next epic.]]
[[LLM: After the epic list is approved, present each `epic_details` with all its stories and acceptance criteria as a complete review unit and immediately execute .bmad-core/tasks/advanced-elicitation.md display, before moving on to the next epic.]]
<<REPEAT: epic_details>>
@@ -5051,9 +5052,9 @@ so that {{benefit}}.
### Architect Prompt
[[LLM: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]
==================== END: templates#prd-tmpl ====================
==================== END: .bmad-core/templates/prd-tmpl.md ====================
==================== START: templates#brownfield-prd-tmpl ====================
==================== START: .bmad-core/templates/brownfield-prd-tmpl.md ====================
# {{Project Name}} Brownfield Enhancement PRD
[[LLM: The default path and filename unless specified is docs/prd.md]]
@@ -5320,9 +5321,9 @@ so that {{benefit}}.
- IV3: [[LLM: Performance impact verification requirement]]
<</REPEAT>>
==================== END: templates#brownfield-prd-tmpl ====================
==================== END: .bmad-core/templates/brownfield-prd-tmpl.md ====================
==================== START: checklists#pm-checklist ====================
==================== START: .bmad-core/checklists/pm-checklist.md ====================
# Product Manager (PM) Requirements Checklist
This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
@@ -5698,9 +5699,9 @@ After presenting the report, ask if the user wants:
- **READY FOR ARCHITECT**: The PRD and epics are comprehensive, properly structured, and ready for architectural design.
- **NEEDS REFINEMENT**: The requirements documentation requires additional work to address the identified deficiencies.
==================== END: checklists#pm-checklist ====================
==================== END: .bmad-core/checklists/pm-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.
@@ -5883,15 +5884,15 @@ 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: 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 ====================
==================== START: templates#architecture-tmpl ====================
==================== START: .bmad-core/templates/architecture-tmpl.md ====================
# {{Project Name}} Architecture Document
[[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. If at a minimum you cannot local `docs/prd.md` ask the user what docs will provide the basis for the architecture.]]
@@ -5902,7 +5903,7 @@ None Listed
[[LLM: This section establishes the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
After presenting this section, apply `tasks#advanced-elicitation` protocol]]
After presenting this section, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
This document outlines the overall project architecture for {{Project Name}}, including backend systems, shared services, and non-UI specific concerns. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development, ensuring consistency and adherence to chosen patterns and technologies.
@@ -5947,7 +5948,7 @@ If the project includes a significant user interface, a separate Frontend Archit
Document the decision here before proceeding with the architecture design. In none, just say N/A
After presenting this starter template section, apply `tasks#advanced-elicitation` protocol]]
After presenting this starter template section, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
### Change Log
@@ -5958,7 +5959,7 @@ After presenting this starter template section, apply `tasks#advanced-elicitatio
## High Level Architecture
[[LLM: This section contains multiple subsections that establish the foundation of the architecture. Present all subsections together (Introduction, Technical Summary, High Level Overview, Project Diagram, and Architectural Patterns), then apply `tasks#advanced-elicitation` protocol to the complete High Level Architecture section. The user can choose to refine the entire section or specific subsections.]]
[[LLM: This section contains multiple subsections that establish the foundation of the architecture. Present all subsections together (Introduction, Technical Summary, High Level Overview, Project Diagram, and Architectural Patterns), then apply `.bmad-core/tasks/advanced-elicitation.md` protocol to the complete High Level Architecture section. The user can choose to refine the entire section or specific subsections.]]
### Technical Summary
@@ -5980,7 +5981,7 @@ After presenting this starter template section, apply `tasks#advanced-elicitatio
4. Primary user interaction flow or data flow at a conceptual level
5. Key architectural decisions and their rationale
After presenting this section, apply `tasks#advanced-elicitation` protocol]]
After presenting this section, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
### High Level Project Diagram
@@ -5994,7 +5995,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
Use appropriate Mermaid diagram type (graph TD, C4, sequence) based on what best represents the architecture
After presenting the diagram, apply `tasks#advanced-elicitation` protocol]]
After presenting the diagram, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
### Architectural and Design Patterns
@@ -6026,13 +6027,13 @@ Common patterns to consider:
@{/example}
[[LLM: After presenting the patterns, apply `tasks#advanced-elicitation` protocol]]
[[LLM: After presenting the patterns, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Tech Stack
[[LLM: This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
1. Review PRD technical assumptions and any preferences from `data#technical-preferences` or an attached `technical-preferences`
1. Review PRD technical assumptions and any preferences from `.bmad-core/data/technical-preferences.yaml` or an attached `technical-preferences`
2. For each category, present 2-3 viable options with pros/cons
3. Make a clear recommendation based on project needs
4. Get explicit user approval for each selection
@@ -6048,7 +6049,7 @@ Key decisions to finalize - before displaying the table, ensure you are aware of
- Database and storage solutions - if unclear suggest sql or nosql or other types depending on the project and depending on cloud provider offer a suggestion
- Development tools
Upon render of the table, ensure the user is aware of the importance of this sections choices, should also look for gaps or disagreements with anything, ask for any clarifications if something is unclear why its in the list, and also right away apply `tasks#advanced-elicitation` display - this statement and the options should be rendered and then prompt right all before allowing user input.]]
Upon render of the table, ensure the user is aware of the importance of this sections choices, should also look for gaps or disagreements with anything, ask for any clarifications if something is unclear why its in the list, and also right away apply `.bmad-core/tasks/advanced-elicitation.md` display - this statement and the options should be rendered and then prompt right all before allowing user input.]]
### Cloud Infrastructure
@@ -6092,7 +6093,7 @@ Upon render of the table, ensure the user is aware of the importance of this sec
Create a clear conceptual model before moving to database schema.
After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
After presenting all data models, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
<<REPEAT: data_model>>
@@ -6126,7 +6127,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
- Technology specifics based on tech stack choices
5. Create component diagrams where helpful
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
6. After presenting all components, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
<<REPEAT: component>>
@@ -6153,7 +6154,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
- Sequence diagrams for complex interactions
Choose the most appropriate for clarity
After presenting the diagrams, apply `tasks#advanced-elicitation` protocol]]
After presenting the diagrams, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## External APIs
@@ -6207,7 +6208,7 @@ If no external APIs are needed, state this explicitly and skip to next section.]
^^/CONDITION: has_external_apis^^
[[LLM: After presenting external APIs (or noting their absence), apply `tasks#advanced-elicitation` protocol]]
[[LLM: After presenting external APIs (or noting their absence), apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Core Workflows
@@ -6221,7 +6222,7 @@ If no external APIs are needed, state this explicitly and skip to next section.]
Focus on workflows that clarify architecture decisions or complex interactions.
After presenting the workflow diagrams, apply `tasks#advanced-elicitation` protocol]]
After presenting the workflow diagrams, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## REST API Spec
@@ -6255,7 +6256,7 @@ servers:
^^/CONDITION: has_rest_api^^
[[LLM: After presenting the REST API spec (or noting its absence if not applicable), apply `tasks#advanced-elicitation` protocol]]
[[LLM: After presenting the REST API spec (or noting its absence if not applicable), apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Database Schema
@@ -6269,7 +6270,7 @@ servers:
Present schema in format appropriate to database type (SQL DDL, JSON schema, etc.)
After presenting the database schema, apply `tasks#advanced-elicitation` protocol]]
After presenting the database schema, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Source Tree
@@ -6284,7 +6285,7 @@ After presenting the database schema, apply `tasks#advanced-elicitation` protoco
Adapt the structure based on project needs. For monorepos, show service separation. For serverless, show function organization. Include language-specific conventions.
After presenting the structure, apply `tasks#advanced-elicitation` protocol to refine based on user feedback.]]
After presenting the structure, apply `.bmad-core/tasks/advanced-elicitation.md` protocol to refine based on user feedback.]]
```plaintext
{{project-root}}/
@@ -6327,7 +6328,7 @@ project-root/
@{/example}
```
[[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]
[[LLM: After presenting the source tree structure, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Infrastructure and Deployment
@@ -6372,7 +6373,7 @@ Get user input on deployment preferences and CI/CD tool choices.]]
- **Trigger Conditions:** {{rollback_triggers}}
- **Recovery Time Objective:** {{rto}}
[[LLM: After presenting the infrastructure and deployment section, apply `tasks#advanced-elicitation` protocol]]
[[LLM: After presenting the infrastructure and deployment section, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Error Handling Strategy
@@ -6423,7 +6424,7 @@ This section guides both AI and human developers in consistent error handling.]]
- **Compensation Logic:** {{compensation_patterns}}
- **Idempotency:** {{idempotency_approach}}
[[LLM: After presenting the error handling strategy, apply `tasks#advanced-elicitation` protocol]]
[[LLM: After presenting the error handling strategy, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Coding Standards
@@ -6484,7 +6485,7 @@ Avoid obvious rules like "use SOLID principles" or "write clean code"]]
^^/CONDITION: has_language_specifics^^
[[LLM: After presenting the coding standards, apply `tasks#advanced-elicitation` protocol]]
[[LLM: After presenting the coding standards, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Test Strategy and Standards
@@ -6497,7 +6498,7 @@ Avoid obvious rules like "use SOLID principles" or "write clean code"]]
5. Determine integration test infrastructure
6. Plan for test data and external dependencies
Note: Basic info goes in Coding Standards for dev agent. This detailed section is for QA agent and team reference. Apply `tasks#advanced-elicitation` after initial draft.]]
Note: Basic info goes in Coding Standards for dev agent. This detailed section is for QA agent and team reference. Apply `.bmad-core/tasks/advanced-elicitation.md` after initial draft.]]
### Testing Philosophy
@@ -6558,7 +6559,7 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
- **Performance Tests:** {{perf_test_approach}}
- **Security Tests:** {{security_test_approach}}
[[LLM: After presenting the test strategy section, apply `tasks#advanced-elicitation` protocol]]
[[LLM: After presenting the test strategy section, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Security
@@ -6622,7 +6623,7 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
- **DAST Tool:** {{dynamic_analysis}}
- **Penetration Testing:** {{pentest_schedule}}
[[LLM: After presenting the security section, apply `tasks#advanced-elicitation` protocol]]
[[LLM: After presenting the security section, apply `.bmad-core/tasks/advanced-elicitation.md` protocol]]
## Checklist Results Report
@@ -6668,9 +6669,9 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
- Reference to this architecture and coding standards
- First epic/story to implement
- Key technical decisions to follow]]
==================== END: templates#architecture-tmpl ====================
==================== END: .bmad-core/templates/architecture-tmpl.md ====================
==================== START: templates#front-end-architecture-tmpl ====================
==================== START: .bmad-core/templates/front-end-architecture-tmpl.md ====================
# {{Project Name}} Frontend Architecture Document
[[LLM: The default path and filename unless specified is docs/ui-architecture.md]]
@@ -6846,9 +6847,9 @@ Document the starter template decision and any constraints it imposes before pro
- Key import patterns
- File naming conventions
- Project-specific patterns and utilities]]
==================== END: templates#front-end-architecture-tmpl ====================
==================== END: .bmad-core/templates/front-end-architecture-tmpl.md ====================
==================== START: templates#fullstack-architecture-tmpl ====================
==================== START: .bmad-core/templates/fullstack-architecture-tmpl.md ====================
# {{Project Name}} Fullstack Architecture Document
[[LLM: The default path and filename unless specified is docs/architecture.md]]
@@ -7867,9 +7868,9 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
## Checklist Results Report
[[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
==================== END: templates#fullstack-architecture-tmpl ====================
==================== END: .bmad-core/templates/fullstack-architecture-tmpl.md ====================
==================== START: templates#brownfield-architecture-tmpl ====================
==================== START: .bmad-core/templates/brownfield-architecture-tmpl.md ====================
# {{Project Name}} Brownfield Enhancement Architecture
[[LLM: The default path and filename unless specified is docs/architecture.md]]
@@ -8414,9 +8415,9 @@ Present risk assessment and apply `tasks#advanced-elicitation` protocol]]
- Key technical decisions based on real project constraints
- Existing system compatibility requirements with specific verification steps
- Clear sequencing of implementation to minimize risk to existing functionality]]
==================== END: templates#brownfield-architecture-tmpl ====================
==================== END: .bmad-core/templates/brownfield-architecture-tmpl.md ====================
==================== START: checklists#architect-checklist ====================
==================== START: .bmad-core/checklists/architect-checklist.md ====================
# Architect Solution Validation Checklist
This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
@@ -8860,9 +8861,9 @@ Now that you've completed the checklist, generate a comprehensive validation rep
- Component design clarity
After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]
==================== END: checklists#architect-checklist ====================
==================== END: .bmad-core/checklists/architect-checklist.md ====================
==================== START: tasks#validate-next-story ====================
==================== START: .bmad-core/tasks/validate-next-story.md ====================
# Validate Next Story Task
## Purpose
@@ -8997,9 +8998,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:
@@ -9058,9 +9059,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.
@@ -9502,9 +9503,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: workflows#greenfield-service ====================
==================== START: .bmad-core/workflows/greenfield-service.yaml ====================
workflow:
id: greenfield-service
name: Greenfield Service/API Development
@@ -9643,7 +9644,7 @@ workflow:
All stories implemented and reviewed!
Service development phase complete.
Reference: data#bmad-kb:IDE Development Workflow
Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
flow_diagram: |
```mermaid
@@ -9711,9 +9712,9 @@ workflow:
updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
==================== END: workflows#greenfield-service ====================
==================== END: .bmad-core/workflows/greenfield-service.yaml ====================
==================== START: workflows#brownfield-service ====================
==================== START: .bmad-core/workflows/brownfield-service.yaml ====================
workflow:
id: brownfield-service
name: Brownfield Service/API Enhancement
@@ -9901,4 +9902,4 @@ workflow:
architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety."
po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
==================== END: workflows#brownfield-service ====================
==================== END: .bmad-core/workflows/brownfield-service.yaml ====================