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

refactor: standardize formatting and improve readability across core documents (#211)

Browse Source 
### CHANGES

- Add newlines and spacing for improved readability
- Standardize instructional text for consistency
- Renumber lists within tasks for better clarity
- Add language identifiers to various code blocks
- Update placeholder text for improved consistency
- Adjust descriptions and wording in multiple files
- Update VS Code settings and dictionary words
This commit is contained in:
Kayvan Sylvan
2025-06-14 06:33:59 -07:00
committed by GitHub
parent 726c3d35b6
commit 009c77f0f5
35 changed files with 515 additions and 349 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.bmad-core/agents/analyst.md
View File

@@ -60,4 +60,4 @@ dependencies:
- bmad-kb - bmad-kb
utils: utils:
- template-format - template-format
``` ```

4
.bmad-core/checklists/architect-checklist.md
View File

@@ -17,11 +17,13 @@ IMPORTANT: If any required documents are missing or inaccessible, immediately as
PROJECT TYPE DETECTION: PROJECT TYPE DETECTION:
First, determine the project type by checking: First, determine the project type by checking:
- Does the architecture include a frontend/UI component? - Does the architecture include a frontend/UI component?
- Is there a frontend-architecture.md document? - Is there a frontend-architecture.md document?
- Does the PRD mention user interfaces or frontend requirements? - Does the PRD mention user interfaces or frontend requirements?
If this is a backend-only or service-only project: If this is a backend-only or service-only project:
- Skip sections marked with [[FRONTEND ONLY]] - Skip sections marked with [[FRONTEND ONLY]]
- Focus extra attention on API design, service architecture, and integration patterns - Focus extra attention on API design, service architecture, and integration patterns
- Note in your final report that frontend sections were skipped due to project type - Note in your final report that frontend sections were skipped due to project type
@@ -433,4 +435,4 @@ Now that you've completed the checklist, generate a comprehensive validation rep
- UI/UX specification coverage - UI/UX specification coverage
- Component design clarity - 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.]] After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]

4
.bmad-core/checklists/pm-checklist.md
View File

@@ -363,11 +363,11 @@ After presenting the report, ask if the user wants:
### Critical Deficiencies ### Critical Deficiencies
_To be populated during validation_ (To be populated during validation)
### Recommendations ### Recommendations
_To be populated during validation_ (To be populated during validation)
### Final Decision ### Final Decision

6
.bmad-core/checklists/po-master-checklist.md
View File

@@ -407,7 +407,7 @@ Generate a comprehensive validation report that adapts to project type:
After presenting the report, ask if the user wants: After presenting the report, ask if the user wants:
- Detailed analysis of any failed sections - Detailed analysis of any failed sections
- Specific story resequencing suggestions - Specific story reordering suggestions
- Risk mitigation strategies - Risk mitigation strategies
- [BROWNFIELD] Integration risk deep-dive]] - [BROWNFIELD] Integration risk deep-dive]]
@@ -428,11 +428,11 @@ After presenting the report, ask if the user wants:
### Critical Deficiencies ### Critical Deficiencies
_To be populated during validation_ (To be populated during validation)
### Recommendations ### Recommendations
_To be populated during validation_ (To be populated during validation)
### Final Decision ### Final Decision

2
.bmad-core/schemas/agent-team-schema.yml
View File

@@ -24,7 +24,7 @@ properties:
- "Team Fullstack" - "Team Fullstack"
- "Team No UI" - "Team No UI"
- "Team All" - "Team All"
description: description:
type: string type: string
description: Detailed description of the team's purpose, capabilities, and use cases description: Detailed description of the team's purpose, capabilities, and use cases

45
.bmad-core/tasks/brainstorming-techniques.md
View File

@@ -53,17 +53,17 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
#### Structured Ideation Frameworks #### Structured Ideation Frameworks
5. **SCAMPER Method** 1. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]] [[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted? - **S** = Substitute: What can be substituted?
- **C**ombine: What can be combined or integrated? - **C** = Combine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere? - **A** = Adapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced? - **M** = Modify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for? - **P** = Put to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified? - **E** = Eliminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered? - **R**= Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats** 2. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]] [[LLM: Cycle through different thinking modes, spending focused time in each.]]
- White Hat: Facts and information - White Hat: Facts and information
- Red Hat: Emotions and intuition - Red Hat: Emotions and intuition
@@ -72,9 +72,10 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
- Green Hat: Creativity and alternatives - Green Hat: Creativity and alternatives
- Blue Hat: Process and control - Blue Hat: Process and control
7. **Mind Mapping** 3. **Mind Mapping**
[[LLM: Create text-based mind maps with clear hierarchical structure.]] [[LLM: Create text-based mind maps with clear hierarchical structure.]]
```
```plaintext
Central Concept Central Concept
├── Branch 1 ├── Branch 1
│ ├── Sub-idea 1.1 │ ├── Sub-idea 1.1
@@ -88,21 +89,21 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
#### Collaborative Techniques #### Collaborative Techniques
8. **"Yes, And..." Building** 1. **"Yes, And..." Building**
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]] [[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
- Accept the premise of each idea - Accept the premise of each idea
- Add to it with "Yes, and..." - Add to it with "Yes, and..."
- Build chains of connected ideas - Build chains of connected ideas
- Explore tangents freely - Explore tangents freely
9. **Brainwriting/Round Robin** 2. **Brainwriting/Round Robin**
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]] [[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
- Generate ideas from stakeholder perspectives - Generate ideas from stakeholder perspectives
- Build on previous ideas in rounds - Build on previous ideas in rounds
- Combine unrelated ideas - Combine unrelated ideas
- Cross-pollinate concepts - Cross-pollinate concepts
10. **Random Stimulation** 3. **Random Stimulation**
[[LLM: Use random words, images, or concepts as creative triggers.]] [[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association - Random word association
- Picture/metaphor inspiration - Picture/metaphor inspiration
@@ -111,21 +112,21 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
#### Deep Exploration Techniques #### Deep Exploration Techniques
11. **Five Whys** 1. **Five Whys**
[[LLM: Dig deeper into root causes and underlying motivations.]] [[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times) - Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions - Uncover hidden assumptions
- Find root causes, not symptoms - Find root causes, not symptoms
- Identify intervention points - Identify intervention points
12. **Morphological Analysis** 2. **Morphological Analysis**
[[LLM: Break down into parameters and systematically explore combinations.]] [[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions - List key parameters/dimensions
- Identify possible values for each - Identify possible values for each
- Create combination matrix - Create combination matrix
- Explore unusual combinations - Explore unusual combinations
13. **Provocation Technique (PO)** 3. **Provocation Technique (PO)**
[[LLM: Make deliberately provocative statements to jar thinking.]] [[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels - PO: Cars have square wheels
- PO: Customers pay us to take products - PO: Customers pay us to take products
@@ -137,26 +138,31 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Help user select appropriate techniques based on their needs.]] [[LLM: Help user select appropriate techniques based on their needs.]]
**For Initial Exploration:** **For Initial Exploration:**
- What If Scenarios - What If Scenarios
- First Principles - First Principles
- Mind Mapping - Mind Mapping
**For Stuck/Blocked Thinking:** **For Stuck/Blocked Thinking:**
- Random Stimulation - Random Stimulation
- Reversal/Inversion - Reversal/Inversion
- Provocation Technique - Provocation Technique
**For Systematic Coverage:** **For Systematic Coverage:**
- SCAMPER - SCAMPER
- Morphological Analysis - Morphological Analysis
- Six Thinking Hats - Six Thinking Hats
**For Deep Understanding:** **For Deep Understanding:**
- Five Whys - Five Whys
- Analogical Thinking - Analogical Thinking
- First Principles - First Principles
**For Team/Collaborative Settings:** **For Team/Collaborative Settings:**
- Brainwriting - Brainwriting
- "Yes, And..." - "Yes, And..."
- Six Thinking Hats - Six Thinking Hats
@@ -190,17 +196,20 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Present brainstorming results in an organized, actionable format.]] [[LLM: Present brainstorming results in an organized, actionable format.]]
**Session Summary:** **Session Summary:**
- Techniques used - Techniques used
- Number of ideas generated - Number of ideas generated
- Key themes identified - Key themes identified
**Idea Categories:** **Idea Categories:**
1. **Immediate Opportunities** - Ideas that could be implemented now 1. **Immediate Opportunities** - Ideas that could be implemented now
2. **Future Innovations** - Ideas requiring more development 2. **Future Innovations** - Ideas requiring more development
3. **Moonshots** - Ambitious, transformative ideas 3. **Moonshots** - Ambitious, transformative ideas
4. **Insights & Learnings** - Key realizations from the session 4. **Insights & Learnings** - Key realizations from the session
**Next Steps:** **Next Steps:**
- Which ideas to explore further - Which ideas to explore further
- Recommended follow-up techniques - Recommended follow-up techniques
- Suggested research areas - Suggested research areas
@@ -213,4 +222,4 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
- Build on ideas collaboratively - Build on ideas collaboratively
- Document everything - even "silly" ideas can spark breakthroughs - Document everything - even "silly" ideas can spark breakthroughs
- Take breaks if energy flags - Take breaks if energy flags
- End with clear next actions - End with clear next actions

4
.bmad-core/tasks/brownfield-create-story.md
View File

@@ -55,8 +55,8 @@ Create a single focused story following this structure:
#### User Story #### User Story
As a {{user type}}, As a {{user type}},
I want {{specific action/capability}}, I want {{specific action/capability}},
So that {{clear benefit/value}}. So that {{clear benefit/value}}.
#### Story Context #### Story Context

2
.bmad-core/tasks/create-deep-research-prompt.md
View File

@@ -187,7 +187,7 @@ Present these numbered options to the user:
**Research Prompt Template:** **Research Prompt Template:**
``` ```markdown
## Research Objective ## Research Objective
[Clear statement of what this research aims to achieve] [Clear statement of what this research aims to achieve]

48
.bmad-core/tasks/create-expansion-pack.md
View File

@@ -39,7 +39,7 @@ Request from the user:
#### 1.3 Create Planning Document #### 1.3 Create Planning Document
**STOP HERE AND CREATE PLAN FIRST** IMPORTANT: STOP HERE AND CREATE PLAN FIRST
Create `expansion-packs/{pack-name}/plan.md` with: Create `expansion-packs/{pack-name}/plan.md` with:
@@ -85,7 +85,7 @@ Create `expansion-packs/{pack-name}/plan.md` with:
User approval received: [ ] Yes User approval received: [ ] Yes
``` ```
**Wait for user approval before proceeding to Phase 2** Important: Wait for user approval before proceeding to Phase 2
### Phase 2: Component Design ### Phase 2: Component Design
@@ -142,7 +142,7 @@ For each checklist:
### Phase 3: Implementation ### Phase 3: Implementation
**Only proceed after plan.md is approved** IMPORTANT: Only proceed after plan.md is approved
#### 3.1 Create Directory Structure #### 3.1 Create Directory Structure
@@ -227,7 +227,7 @@ post_install_message: |
### Phase 4: Content Creation ### Phase 4: Content Creation
**Work through plan.md checklist systematically** IMPORTANT: Work through plan.md checklist systematically!
#### 4.1 Create Orchestrator First #### 4.1 Create Orchestrator First
@@ -308,12 +308,6 @@ For each required data file:
- **Example**: - **Example**:
``` ```
{sample content}
```
```
## Example: Healthcare Expansion Pack ## Example: Healthcare Expansion Pack
```text ```text
@@ -362,38 +356,38 @@ Required user data files:
### Planning Phase ### Planning Phase
6. "Here's the proposed plan. Please review and approve before we continue." 1. "Here's the proposed plan. Please review and approve before we continue."
### Orchestrator Design ### Orchestrator Design
7. "What key commands should the {pack-name} orchestrator support?" 1. "What key commands should the {pack-name} orchestrator support?"
8. "What's the typical workflow from start to finish?" 2. "What's the typical workflow from start to finish?"
9. "How should it integrate with core BMAD agents?" 3. "How should it integrate with core BMAD agents?"
### Agent Planning ### Agent Planning
10. "For agent '{name}', what is their specific expertise?" 1. "For agent '{name}', what is their specific expertise?"
11. "What tasks will this agent reference? (I'll create them)" 2. "What tasks will this agent reference? (I'll create them)"
12. "What templates will this agent use? (I'll create them)" 3. "What templates will this agent use? (I'll create them)"
13. "What data files will this agent need? (You'll provide these)" 4. "What data files will this agent need? (You'll provide these)"
### Task Design ### Task Design
14. "Describe the '{task}' process step-by-step" 1. "Describe the '{task}' process step-by-step"
15. "What information is needed to complete this task?" 2. "What information is needed to complete this task?"
16. "What should the output look like?" 3. "What should the output look like?"
### Template Creation ### Template Creation
17. "What sections should the '{template}' document have?" 1. "What sections should the '{template}' document have?"
18. "Are there any required formats or standards?" 2. "Are there any required formats or standards?"
19. "Can you provide an example of a completed document?" 3. "Can you provide an example of a completed document?"
### Data Requirements ### Data Requirements
20. "For {data-file}, what information should it contain?" 1. "For {data-file}, what information should it contain?"
21. "What format should this data be in?" 2. "What format should this data be in?"
22. "Can you provide a sample?" 3. "Can you provide a sample?"
## Important Considerations ## Important Considerations

11
.bmad-core/tasks/create-ide-agent.md
View File

@@ -77,6 +77,7 @@ Required commands per schema:
``` ```
Add role-specific commands: Add role-specific commands:
- Use pattern: `^\\*[a-z][a-z0-9-]*( \\{[^}]+\\})?$` - Use pattern: `^\\*[a-z][a-z0-9-]*( \\{[^}]+\\})?$`
- Include clear descriptions (10+ chars) - Include clear descriptions (10+ chars)
- Reference tasks when appropriate - Reference tasks when appropriate
@@ -98,9 +99,10 @@ Analyze where this IDE agent fits in workflows:
- For specialized agents → specific workflow steps - For specialized agents → specific workflow steps
4. **Document recommendations**: 4. **Document recommendations**:
```markdown ```markdown
## Workflow Integration ## Workflow Integration
This agent enhances the following workflows: This agent enhances the following workflows:
- `greenfield-service`: API design phase (between architecture and implementation) - `greenfield-service`: API design phase (between architecture and implementation)
- `brownfield-service`: API refactoring and modernization - `brownfield-service`: API refactoring and modernization
@@ -118,9 +120,10 @@ Consider which teams benefit from this IDE agent:
- Domain experts → relevant specialized teams - Domain experts → relevant specialized teams
3. **Document integration**: 3. **Document integration**:
```markdown ```markdown
## Team Integration ## Team Integration
Recommended teams for this agent: Recommended teams for this agent:
- `team-fullstack`: Provides specialized {domain} expertise - `team-fullstack`: Provides specialized {domain} expertise
- `team-no-ui`: Enhances backend {capability} - `team-no-ui`: Enhances backend {capability}
@@ -243,7 +246,7 @@ Recommended teams for this agent:
- [ ] Persona has all 5 required fields - [ ] Persona has all 5 required fields
- [ ] Minimum 3 Core Principles including Numbered Options Protocol - [ ] Minimum 3 Core Principles including Numbered Options Protocol
- [ ] First startup instruction announces name/role with *help - [ ] First startup instruction announces name/role with *help
- [ ] Includes *help and *chat-mode commands - [ ] Includes *help and*chat-mode commands
- [ ] Commands follow pattern requirements - [ ] Commands follow pattern requirements
- [ ] Workflow integration documented - [ ] Workflow integration documented
- [ ] Team integration suggestions provided - [ ] Team integration suggestions provided
@@ -259,4 +262,4 @@ Recommended teams for this agent:
5. **Integration First**: Consider how agent enhances existing workflows 5. **Integration First**: Consider how agent enhances existing workflows
6. **Schema Compliance**: Always validate against the schema 6. **Schema Compliance**: Always validate against the schema
This schema-driven approach ensures IDE agents are consistent, integrated, and valuable additions to the BMAD ecosystem. This schema-driven approach ensures IDE agents are consistent, integrated, and valuable additions to the BMAD ecosystem.

16
.bmad-core/tasks/create-team.md
View File

@@ -45,6 +45,7 @@ Based on the schema requirements:
Based on team purpose, recommend agents: Based on team purpose, recommend agents:
**For Planning & Strategy Teams:** **For Planning & Strategy Teams:**
- `bmad` (required orchestrator) - `bmad` (required orchestrator)
- `analyst` - Requirements gathering and research - `analyst` - Requirements gathering and research
- `pm` - Product strategy and documentation - `pm` - Product strategy and documentation
@@ -52,6 +53,7 @@ Based on team purpose, recommend agents:
- `architect` - Technical planning (if technical planning needed) - `architect` - Technical planning (if technical planning needed)
**For Design & UX Teams:** **For Design & UX Teams:**
- `bmad` (required orchestrator) - `bmad` (required orchestrator)
- `ux-expert` - User experience design - `ux-expert` - User experience design
- `architect` - Frontend architecture - `architect` - Frontend architecture
@@ -59,6 +61,7 @@ Based on team purpose, recommend agents:
- `po` - Design validation - `po` - Design validation
**For Development Teams:** **For Development Teams:**
- `bmad` (required orchestrator) - `bmad` (required orchestrator)
- `sm` - Sprint coordination - `sm` - Sprint coordination
- `dev` - Implementation - `dev` - Implementation
@@ -66,6 +69,7 @@ Based on team purpose, recommend agents:
- `architect` - Technical guidance - `architect` - Technical guidance
**For Full-Stack Teams:** **For Full-Stack Teams:**
- `bmad` (required orchestrator) - `bmad` (required orchestrator)
- `analyst` - Initial planning - `analyst` - Initial planning
- `pm` - Product management - `pm` - Product management
@@ -128,7 +132,7 @@ workflows:
Before finalizing, verify: Before finalizing, verify:
1. **Role Coverage**: Does the team have all necessary skills for its workflows? 1. **Role Coverage**: Does the team have all necessary skills for its workflows?
2. **Size Optimization**: 2. **Size Optimization**:
- Minimum: 2 agents (bmad + 1) - Minimum: 2 agents (bmad + 1)
- Recommended: 3-7 agents - Recommended: 3-7 agents
- Maximum with wildcard: bmad + "*" - Maximum with wildcard: bmad + "*"
@@ -159,8 +163,8 @@ Document how this team integrates with existing system:
bundle: bundle:
name: "Team API" name: "Team API"
description: >- description: >-
Specialized team for API and backend service development. Focuses on Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI robust service architecture, implementation, and testing without UI
components. Ideal for microservices, REST APIs, and backend systems. components. Ideal for microservices, REST APIs, and backend systems.
agents: agents:
@@ -182,8 +186,8 @@ workflows:
bundle: bundle:
name: "Team Prototype" name: "Team Prototype"
description: >- description: >-
Agile team for rapid prototyping and proof of concept development. Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations Combines planning, design, and implementation for quick iterations
on new ideas and experimental features. on new ideas and experimental features.
agents: agents:
@@ -220,4 +224,4 @@ workflows:
5. **Test Integration**: Verify team works well with selected workflows 5. **Test Integration**: Verify team works well with selected workflows
6. **Iterate**: Refine team composition based on usage 6. **Iterate**: Refine team composition based on usage
This schema-driven approach ensures teams are well-structured, purposeful, and integrate seamlessly with the BMAD ecosystem. This schema-driven approach ensures teams are well-structured, purposeful, and integrate seamlessly with the BMAD ecosystem.

2
.bmad-core/tasks/index-docs.md
View File

@@ -174,4 +174,4 @@ Please provide:
4. Any files or directories to exclude from indexing (e.g., `.git`, `node_modules`) 4. Any files or directories to exclude from indexing (e.g., `.git`, `node_modules`)
5. Whether to include hidden files/folders (starting with `.`) 5. Whether to include hidden files/folders (starting with `.`)
Would you like to proceed with documentation indexing? Please provide the required input above. Would you like to proceed with documentation indexing? Please provide the required input above.

63
.bmad-core/templates/architecture-tmpl.md
View File

@@ -19,34 +19,35 @@ If the project includes a significant user interface, a separate Frontend Archit
1. Review the PRD and brainstorming brief for any mentions of: 1. Review the PRD and brainstorming brief for any mentions of:
- Starter templates (e.g., Create React App, Next.js, Vue CLI, Angular CLI, etc.) - Starter templates (e.g., Create React App, Next.js, Vue CLI, Angular CLI, etc.)
- Existing projects or codebases being used as a foundation - Existing projects or codebases being used as a foundation
- Boilerplate projects or scaffolding tools - Boilerplate projects or scaffolding tools
- Previous projects to be cloned or adapted - Previous projects to be cloned or adapted
2. If a starter template or existing project is mentioned: 2. If a starter template or existing project is mentioned:
- Ask the user to provide access via one of these methods: - Ask the user to provide access via one of these methods:
- Link to the starter template documentation - Link to the starter template documentation
- Upload/attach the project files (for small projects) - Upload/attach the project files (for small projects)
- Share a link to the project repository (GitHub, GitLab, etc.) - Share a link to the project repository (GitHub, GitLab, etc.)
- Analyze the starter/existing project to understand: - Analyze the starter/existing project to understand:
- Pre-configured technology stack and versions - Pre-configured technology stack and versions
- Project structure and organization patterns - Project structure and organization patterns
- Built-in scripts and tooling - Built-in scripts and tooling
- Existing architectural patterns and conventions - Existing architectural patterns and conventions
- Any limitations or constraints imposed by the starter - Any limitations or constraints imposed by the starter
- Use this analysis to inform and align your architecture decisions - Use this analysis to inform and align your architecture decisions
3. If no starter template is mentioned but this is a greenfield project: 3. If no starter template is mentioned but this is a greenfield project:
- Suggest appropriate starter templates based on the tech stack preferences - Suggest appropriate starter templates based on the tech stack preferences
- Explain the benefits (faster setup, best practices, community support) - Explain the benefits (faster setup, best practices, community support)
- Let the user decide whether to use one - Let the user decide whether to use one
4. If the user confirms no starter template will be used: 4. If the user confirms no starter template will be used:
- Proceed with architecture design from scratch
- Note that manual setup will be required for all tooling and configuration - Proceed with architecture design from scratch
- Note that manual setup will be required for all tooling and configuration
Document the decision here before proceeding with the architecture design. In none, just say N/A Document the decision here before proceeding with the architecture design. In none, just say N/A
@@ -222,10 +223,12 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
2. Consider the repository structure (monorepo/polyrepo) from PRD 2. Consider the repository structure (monorepo/polyrepo) from PRD
3. Define clear boundaries and interfaces between components 3. Define clear boundaries and interfaces between components
4. For each component, specify: 4. For each component, specify:
- Primary responsibility
- Key interfaces/APIs exposed - Primary responsibility
- Dependencies on other components - Key interfaces/APIs exposed
- Technology specifics based on tech stack choices - Dependencies on other components
- Technology specifics based on tech stack choices
5. Create component diagrams where helpful 5. Create component diagrams where helpful
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]] 6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
@@ -734,15 +737,15 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
1. If project has UI components: 1. If project has UI components:
- Recommend engaging Design Architect agent - Recommend engaging Design Architect agent
- Use "Frontend Architecture Mode" - Use "Frontend Architecture Mode"
- Provide this document as input - Provide this document as input
2. For all projects: 2. For all projects:
- Review with Product Owner - Review with Product Owner
- Begin story implementation with Dev agent - Begin story implementation with Dev agent
- Set up infrastructure with DevOps agent - Set up infrastructure with DevOps agent
3. Include specific prompts for next agents if needed]] 3. Include specific prompts for next agents if needed]]

72
.bmad-core/templates/competitor-analysis-tmpl.md
View File

@@ -9,7 +9,9 @@
## Analysis Scope & Methodology ## Analysis Scope & Methodology
### Analysis Purpose ### Analysis Purpose
{{Define the primary purpose: {{Define the primary purpose:
- New market entry assessment - New market entry assessment
- Product positioning strategy - Product positioning strategy
- Feature gap analysis - Feature gap analysis
@@ -18,7 +20,9 @@
- Competitive threat assessment}} - Competitive threat assessment}}
### Competitor Categories Analyzed ### Competitor Categories Analyzed
{{List categories included: {{List categories included:
- Direct Competitors: Same product/service, same target market - Direct Competitors: Same product/service, same target market
- Indirect Competitors: Different product, same need/problem - Indirect Competitors: Different product, same need/problem
- Potential Competitors: Could enter market easily - Potential Competitors: Could enter market easily
@@ -26,7 +30,9 @@
- Aspirational Competitors: Best-in-class examples}} - Aspirational Competitors: Best-in-class examples}}
### Research Methodology ### Research Methodology
{{Describe approach: {{Describe approach:
- Information sources used - Information sources used
- Analysis timeframe - Analysis timeframe
- Confidence levels - Confidence levels
@@ -35,7 +41,9 @@
## Competitive Landscape Overview ## Competitive Landscape Overview
### Market Structure ### Market Structure
{{Describe the competitive environment: {{Describe the competitive environment:
- Number of active competitors - Number of active competitors
- Market concentration (fragmented/consolidated) - Market concentration (fragmented/consolidated)
- Competitive dynamics - Competitive dynamics
@@ -46,8 +54,9 @@
[[LLM: Help categorize competitors by market share and strategic threat level]] [[LLM: Help categorize competitors by market share and strategic threat level]]
{{Create a 2x2 matrix: {{Create a 2x2 matrix:
- Priority 1 (Core Competitors): High Market Share + High Threat - Priority 1 (Core Competitors): High Market Share + High Threat
- Priority 2 (Emerging Threats): Low Market Share + High Threat - Priority 2 (Emerging Threats): Low Market Share + High Threat
- Priority 3 (Established Players): High Market Share + Low Threat - Priority 3 (Established Players): High Market Share + Low Threat
- Priority 4 (Monitor Only): Low Market Share + Low Threat}} - Priority 4 (Monitor Only): Low Market Share + Low Threat}}
@@ -58,6 +67,7 @@
### {{Competitor Name}} - Priority {{1/2/3/4}} ### {{Competitor Name}} - Priority {{1/2/3/4}}
#### Company Overview #### Company Overview
- **Founded:** {{Year, founders}} - **Founded:** {{Year, founders}}
- **Headquarters:** {{Location}} - **Headquarters:** {{Location}}
- **Company Size:** {{Employees, revenue if known}} - **Company Size:** {{Employees, revenue if known}}
@@ -65,6 +75,7 @@
- **Leadership:** {{Key executives}} - **Leadership:** {{Key executives}}
#### Business Model & Strategy #### Business Model & Strategy
- **Revenue Model:** {{How they make money}} - **Revenue Model:** {{How they make money}}
- **Target Market:** {{Primary customer segments}} - **Target Market:** {{Primary customer segments}}
- **Value Proposition:** {{Core value promise}} - **Value Proposition:** {{Core value promise}}
@@ -72,6 +83,7 @@
- **Strategic Focus:** {{Current priorities}} - **Strategic Focus:** {{Current priorities}}
#### Product/Service Analysis #### Product/Service Analysis
- **Core Offerings:** {{Main products/services}} - **Core Offerings:** {{Main products/services}}
- **Key Features:** {{Standout capabilities}} - **Key Features:** {{Standout capabilities}}
- **User Experience:** {{UX strengths/weaknesses}} - **User Experience:** {{UX strengths/weaknesses}}
@@ -81,16 +93,19 @@
#### Strengths & Weaknesses #### Strengths & Weaknesses
**Strengths:** **Strengths:**
- {{Strength 1}} - {{Strength 1}}
- {{Strength 2}} - {{Strength 2}}
- {{Strength 3}} - {{Strength 3}}
**Weaknesses:** **Weaknesses:**
- {{Weakness 1}} - {{Weakness 1}}
- {{Weakness 2}} - {{Weakness 2}}
- {{Weakness 3}} - {{Weakness 3}}
#### Market Position & Performance #### Market Position & Performance
- **Market Share:** {{Estimate if available}} - **Market Share:** {{Estimate if available}}
- **Customer Base:** {{Size, notable clients}} - **Customer Base:** {{Size, notable clients}}
- **Growth Trajectory:** {{Trending up/down/stable}} - **Growth Trajectory:** {{Trending up/down/stable}}
@@ -104,32 +119,34 @@
[[LLM: Create a detailed comparison table of key features across competitors]] [[LLM: Create a detailed comparison table of key features across competitors]]
| Feature Category | {{Your Company}} | {{Competitor 1}} | {{Competitor 2}} | {{Competitor 3}} | | Feature Category | {{Your Company}} | {{Competitor 1}} | {{Competitor 2}} | {{Competitor 3}} |
|-----------------|------------------|------------------|------------------|------------------| | --------------------------- | ------------------- | ------------------- | ------------------- | ------------------- |
| **Core Functionality** | | **Core Functionality** |
| Feature A | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | | Feature A | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} |
| Feature B | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | | Feature B | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} |
| **User Experience** | | **User Experience** |
| Mobile App | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} | | Mobile App | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} |
| Onboarding Time | {{Time}} | {{Time}} | {{Time}} | {{Time}} | | Onboarding Time | {{Time}} | {{Time}} | {{Time}} | {{Time}} |
| **Integration & Ecosystem** | | **Integration & Ecosystem** |
| API Availability | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} | | API Availability | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} |
| Third-party Integrations | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} | | Third-party Integrations | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} |
| **Pricing & Plans** | | **Pricing & Plans** |
| Starting Price | {{$X}} | {{$X}} | {{$X}} | {{$X}} | | Starting Price | {{$X}} | {{$X}} | {{$X}} | {{$X}} |
| Free Tier | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} | | Free Tier | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} |
### SWOT Comparison ### SWOT Comparison
[[LLM: Create SWOT analysis for your solution vs. top competitors]] [[LLM: Create SWOT analysis for your solution vs. top competitors]]
#### Your Solution #### Your Solution
- **Strengths:** {{List key strengths}} - **Strengths:** {{List key strengths}}
- **Weaknesses:** {{List key weaknesses}} - **Weaknesses:** {{List key weaknesses}}
- **Opportunities:** {{List opportunities}} - **Opportunities:** {{List opportunities}}
- **Threats:** {{List threats}} - **Threats:** {{List threats}}
#### vs. {{Main Competitor}} #### vs. {{Main Competitor}}
- **Competitive Advantages:** {{Where you're stronger}} - **Competitive Advantages:** {{Where you're stronger}}
- **Competitive Disadvantages:** {{Where they're stronger}} - **Competitive Disadvantages:** {{Where they're stronger}}
- **Differentiation Opportunities:** {{How to stand out}} - **Differentiation Opportunities:** {{How to stand out}}
@@ -139,6 +156,7 @@
[[LLM: Describe competitor positions on key dimensions]] [[LLM: Describe competitor positions on key dimensions]]
{{Create a positioning description using 2 key dimensions relevant to the market, such as: {{Create a positioning description using 2 key dimensions relevant to the market, such as:
- Price vs. Features - Price vs. Features
- Ease of Use vs. Power - Ease of Use vs. Power
- Specialization vs. Breadth - Specialization vs. Breadth
@@ -149,7 +167,9 @@
### Competitive Advantages Assessment ### Competitive Advantages Assessment
#### Sustainable Advantages #### Sustainable Advantages
{{Identify moats and defensible positions: {{Identify moats and defensible positions:
- Network effects - Network effects
- Switching costs - Switching costs
- Brand strength - Brand strength
@@ -157,7 +177,9 @@
- Regulatory advantages}} - Regulatory advantages}}
#### Vulnerable Points #### Vulnerable Points
{{Where competitors could be challenged: {{Where competitors could be challenged:
- Weak customer segments - Weak customer segments
- Missing features - Missing features
- Poor user experience - Poor user experience
@@ -169,6 +191,7 @@
[[LLM: Identify uncontested market spaces]] [[LLM: Identify uncontested market spaces]]
{{List opportunities to create new market space: {{List opportunities to create new market space:
- Underserved segments - Underserved segments
- Unaddressed use cases - Unaddressed use cases
- New business models - New business models
@@ -178,7 +201,9 @@
## Strategic Recommendations ## Strategic Recommendations
### Differentiation Strategy ### Differentiation Strategy
{{How to position against competitors: {{How to position against competitors:
- Unique value propositions to emphasize - Unique value propositions to emphasize
- Features to prioritize - Features to prioritize
- Segments to target - Segments to target
@@ -187,19 +212,25 @@
### Competitive Response Planning ### Competitive Response Planning
#### Offensive Strategies #### Offensive Strategies
{{How to gain market share: {{How to gain market share:
- Target competitor weaknesses - Target competitor weaknesses
- Win competitive deals - Win competitive deals
- Capture their customers}} - Capture their customers}}
#### Defensive Strategies #### Defensive Strategies
{{How to protect your position: {{How to protect your position:
- Strengthen vulnerable areas - Strengthen vulnerable areas
- Build switching costs - Build switching costs
- Deepen customer relationships}} - Deepen customer relationships}}
### Partnership & Ecosystem Strategy ### Partnership & Ecosystem Strategy
{{Potential collaboration opportunities: {{Potential collaboration opportunities:
- Complementary players - Complementary players
- Channel partners - Channel partners
- Technology integrations - Technology integrations
@@ -208,10 +239,13 @@
## Monitoring & Intelligence Plan ## Monitoring & Intelligence Plan
### Key Competitors to Track ### Key Competitors to Track
{{Priority list with rationale}} {{Priority list with rationale}}
### Monitoring Metrics ### Monitoring Metrics
{{What to track: {{What to track:
- Product updates - Product updates
- Pricing changes - Pricing changes
- Customer wins/losses - Customer wins/losses
@@ -219,7 +253,9 @@
- Market messaging}} - Market messaging}}
### Intelligence Sources ### Intelligence Sources
{{Where to gather ongoing intelligence: {{Where to gather ongoing intelligence:
- Company websites/blogs - Company websites/blogs
- Customer reviews - Customer reviews
- Industry reports - Industry reports
@@ -227,7 +263,9 @@
- Patent filings}} - Patent filings}}
### Update Cadence ### Update Cadence
{{Recommended review schedule: {{Recommended review schedule:
- Weekly: {{What to check}} - Weekly: {{What to check}}
- Monthly: {{What to review}} - Monthly: {{What to review}}
- Quarterly: {{Deep analysis}}}} - Quarterly: {{Deep analysis}}}}
@@ -236,8 +274,8 @@
[[LLM: After completing the document, offer advanced elicitation with these custom options for competitive analysis: [[LLM: After completing the document, offer advanced elicitation with these custom options for competitive analysis:
**Competitive Analysis Elicitation Actions** **Competitive Analysis Elicitation Actions** 0. Deep dive on a specific competitor's strategy
0. Deep dive on a specific competitor's strategy
1. Analyze competitive dynamics in a specific segment 1. Analyze competitive dynamics in a specific segment
2. War game competitive responses to your moves 2. War game competitive responses to your moves
3. Explore partnership vs. competition scenarios 3. Explore partnership vs. competition scenarios
@@ -248,4 +286,4 @@
8. If only we had known about [competitor X's plan]... 8. If only we had known about [competitor X's plan]...
9. Proceed to next section 9. Proceed to next section
These replace the standard elicitation options when working on competitive analysis documents.]] These replace the standard elicitation options when working on competitive analysis documents.]]

3
.bmad-core/templates/front-end-architecture-tmpl.md
View File

@@ -29,7 +29,8 @@
- Routing configuration - Routing configuration
- Testing setup and patterns - Testing setup and patterns
- Build and development scripts - Build and development scripts
- Use this analysis to ensure your frontend architecture aligns with the starter's patterns
- Use this analysis to ensure your frontend architecture aligns with the starter's patterns
3. If no frontend starter is mentioned but this is a new UI, ensure we know what the ui language and framework is: 3. If no frontend starter is mentioned but this is a new UI, ensure we know what the ui language and framework is:

32
.bmad-core/templates/fullstack-architecture-tmpl.md
View File

@@ -18,23 +18,23 @@ This unified approach combines what would traditionally be separate backend and
1. Review the PRD and other documents for mentions of: 1. Review the PRD and other documents for mentions of:
- Fullstack starter templates (e.g., T3 Stack, MEAN/MERN starters, Django + React templates) - Fullstack starter templates (e.g., T3 Stack, MEAN/MERN starters, Django + React templates)
- Monorepo templates (e.g., Nx, Turborepo starters) - Monorepo templates (e.g., Nx, Turborepo starters)
- Platform-specific starters (e.g., Vercel templates, AWS Amplify starters) - Platform-specific starters (e.g., Vercel templates, AWS Amplify starters)
- Existing projects being extended or cloned - Existing projects being extended or cloned
2. If starter templates or existing projects are mentioned: 2. If starter templates or existing projects are mentioned:
- Ask the user to provide access (links, repos, or files) - Ask the user to provide access (links, repos, or files)
- Analyze to understand pre-configured choices and constraints - Analyze to understand pre-configured choices and constraints
- Note any architectural decisions already made - Note any architectural decisions already made
- Identify what can be modified vs what must be retained - Identify what can be modified vs what must be retained
3. If no starter is mentioned but this is greenfield: 3. If no starter is mentioned but this is greenfield:
- Suggest appropriate fullstack starters based on tech preferences - Suggest appropriate fullstack starters based on tech preferences
- Consider platform-specific options (Vercel, AWS, etc.) - Consider platform-specific options (Vercel, AWS, etc.)
- Let user decide whether to use one - Let user decide whether to use one
4. Document the decision and any constraints it imposes 4. Document the decision and any constraints it imposes
@@ -333,10 +333,12 @@ servers:
2. Consider both frontend and backend components 2. Consider both frontend and backend components
3. Define clear boundaries and interfaces between components 3. Define clear boundaries and interfaces between components
4. For each component, specify: 4. For each component, specify:
- Primary responsibility
- Key interfaces/APIs exposed - Primary responsibility
- Dependencies on other components - Key interfaces/APIs exposed
- Technology specifics based on tech stack choices - Dependencies on other components
- Technology specifics based on tech stack choices
5. Create component diagrams where helpful 5. Create component diagrams where helpful
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]] 6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]

48
.bmad-core/templates/market-research-tmpl.md
View File

@@ -9,13 +9,17 @@
## Research Objectives & Methodology ## Research Objectives & Methodology
### Research Objectives ### Research Objectives
{{List the primary objectives of this market research: {{List the primary objectives of this market research:
- What decisions will this research inform? - What decisions will this research inform?
- What specific questions need to be answered? - What specific questions need to be answered?
- What are the success criteria for this research?}} - What are the success criteria for this research?}}
### Research Methodology ### Research Methodology
{{Describe the research approach: {{Describe the research approach:
- Data sources used (primary/secondary) - Data sources used (primary/secondary)
- Analysis frameworks applied - Analysis frameworks applied
- Data collection timeframe - Data collection timeframe
@@ -24,7 +28,9 @@
## Market Overview ## Market Overview
### Market Definition ### Market Definition
{{Define the market being analyzed: {{Define the market being analyzed:
- Product/service category - Product/service category
- Geographic scope - Geographic scope
- Customer segments included - Customer segments included
@@ -33,17 +39,21 @@
### Market Size & Growth ### Market Size & Growth
[[LLM: Guide through TAM, SAM, SOM calculations with clear assumptions. Use one or more approaches: [[LLM: Guide through TAM, SAM, SOM calculations with clear assumptions. Use one or more approaches:
- Top-down: Start with industry data, narrow down - Top-down: Start with industry data, narrow down
- Bottom-up: Build from customer/unit economics - Bottom-up: Build from customer/unit economics
- Value theory: Based on value provided vs. alternatives]] - Value theory: Based on value provided vs. alternatives]]
#### Total Addressable Market (TAM) #### Total Addressable Market (TAM)
{{Calculate and explain the total market opportunity}} {{Calculate and explain the total market opportunity}}
#### Serviceable Addressable Market (SAM) #### Serviceable Addressable Market (SAM)
{{Define the portion of TAM you can realistically reach}} {{Define the portion of TAM you can realistically reach}}
#### Serviceable Obtainable Market (SOM) #### Serviceable Obtainable Market (SOM)
{{Estimate the portion you can realistically capture}} {{Estimate the portion you can realistically capture}}
### Market Trends & Drivers ### Market Trends & Drivers
@@ -51,15 +61,19 @@
[[LLM: Analyze key trends shaping the market using appropriate frameworks like PESTEL]] [[LLM: Analyze key trends shaping the market using appropriate frameworks like PESTEL]]
#### Key Market Trends #### Key Market Trends
{{List and explain 3-5 major trends: {{List and explain 3-5 major trends:
- Trend 1: Description and impact - Trend 1: Description and impact
- Trend 2: Description and impact - Trend 2: Description and impact
- etc.}} - etc.}}
#### Growth Drivers #### Growth Drivers
{{Identify primary factors driving market growth}} {{Identify primary factors driving market growth}}
#### Market Inhibitors #### Market Inhibitors
{{Identify factors constraining market growth}} {{Identify factors constraining market growth}}
## Customer Analysis ## Customer Analysis
@@ -69,6 +83,7 @@
[[LLM: For each segment, create detailed profiles including demographics/firmographics, psychographics, behaviors, needs, and willingness to pay]] [[LLM: For each segment, create detailed profiles including demographics/firmographics, psychographics, behaviors, needs, and willingness to pay]]
#### Segment 1: {{Segment Name}} #### Segment 1: {{Segment Name}}
- **Description:** {{Brief overview}} - **Description:** {{Brief overview}}
- **Size:** {{Number of customers/market value}} - **Size:** {{Number of customers/market value}}
- **Characteristics:** {{Key demographics/firmographics}} - **Characteristics:** {{Key demographics/firmographics}}
@@ -83,12 +98,15 @@
[[LLM: Uncover what customers are really trying to accomplish]] [[LLM: Uncover what customers are really trying to accomplish]]
#### Functional Jobs #### Functional Jobs
{{List practical tasks and objectives customers need to complete}} {{List practical tasks and objectives customers need to complete}}
#### Emotional Jobs #### Emotional Jobs
{{Describe feelings and perceptions customers seek}} {{Describe feelings and perceptions customers seek}}
#### Social Jobs #### Social Jobs
{{Explain how customers want to be perceived by others}} {{Explain how customers want to be perceived by others}}
### Customer Journey Mapping ### Customer Journey Mapping
@@ -96,6 +114,7 @@
[[LLM: Map the end-to-end customer experience for primary segments]] [[LLM: Map the end-to-end customer experience for primary segments]]
{{For primary customer segment: {{For primary customer segment:
1. **Awareness:** How they discover solutions 1. **Awareness:** How they discover solutions
2. **Consideration:** Evaluation criteria and process 2. **Consideration:** Evaluation criteria and process
3. **Purchase:** Decision triggers and barriers 3. **Purchase:** Decision triggers and barriers
@@ -106,13 +125,17 @@
## Competitive Landscape ## Competitive Landscape
### Market Structure ### Market Structure
{{Describe the overall competitive environment: {{Describe the overall competitive environment:
- Number of competitors - Number of competitors
- Market concentration - Market concentration
- Competitive intensity}} - Competitive intensity}}
### Major Players Analysis ### Major Players Analysis
{{For top 3-5 competitors: {{For top 3-5 competitors:
- Company name and brief description - Company name and brief description
- Market share estimate - Market share estimate
- Key strengths and weaknesses - Key strengths and weaknesses
@@ -120,7 +143,9 @@
- Pricing strategy}} - Pricing strategy}}
### Competitive Positioning ### Competitive Positioning
{{Analyze how competitors are positioned: {{Analyze how competitors are positioned:
- Value propositions - Value propositions
- Differentiation strategies - Differentiation strategies
- Market gaps and opportunities}} - Market gaps and opportunities}}
@@ -132,22 +157,29 @@
[[LLM: Analyze each force with specific evidence and implications]] [[LLM: Analyze each force with specific evidence and implications]]
#### Supplier Power: {{Low/Medium/High}} #### Supplier Power: {{Low/Medium/High}}
{{Analysis and implications}} {{Analysis and implications}}
#### Buyer Power: {{Low/Medium/High}} #### Buyer Power: {{Low/Medium/High}}
{{Analysis and implications}} {{Analysis and implications}}
#### Competitive Rivalry: {{Low/Medium/High}} #### Competitive Rivalry: {{Low/Medium/High}}
{{Analysis and implications}} {{Analysis and implications}}
#### Threat of New Entry: {{Low/Medium/High}} #### Threat of New Entry: {{Low/Medium/High}}
{{Analysis and implications}} {{Analysis and implications}}
#### Threat of Substitutes: {{Low/Medium/High}} #### Threat of Substitutes: {{Low/Medium/High}}
{{Analysis and implications}} {{Analysis and implications}}
### Technology Adoption Lifecycle Stage ### Technology Adoption Lifecycle Stage
{{Identify where the market is in the adoption curve: {{Identify where the market is in the adoption curve:
- Current stage and evidence - Current stage and evidence
- Implications for strategy - Implications for strategy
- Expected progression timeline}} - Expected progression timeline}}
@@ -159,6 +191,7 @@
[[LLM: Identify specific opportunities based on the analysis]] [[LLM: Identify specific opportunities based on the analysis]]
#### Opportunity 1: {{Name}} #### Opportunity 1: {{Name}}
- **Description:** {{What is the opportunity?}} - **Description:** {{What is the opportunity?}}
- **Size/Potential:** {{Quantify if possible}} - **Size/Potential:** {{Quantify if possible}}
- **Requirements:** {{What's needed to capture it?}} - **Requirements:** {{What's needed to capture it?}}
@@ -169,21 +202,27 @@
### Strategic Recommendations ### Strategic Recommendations
#### Go-to-Market Strategy #### Go-to-Market Strategy
{{Recommend approach for market entry/expansion: {{Recommend approach for market entry/expansion:
- Target segment prioritization - Target segment prioritization
- Positioning strategy - Positioning strategy
- Channel strategy - Channel strategy
- Partnership opportunities}} - Partnership opportunities}}
#### Pricing Strategy #### Pricing Strategy
{{Based on willingness to pay analysis and competitive landscape: {{Based on willingness to pay analysis and competitive landscape:
- Recommended pricing model - Recommended pricing model
- Price points/ranges - Price points/ranges
- Value metric - Value metric
- Competitive positioning}} - Competitive positioning}}
#### Risk Mitigation #### Risk Mitigation
{{Key risks and mitigation strategies: {{Key risks and mitigation strategies:
- Market risks - Market risks
- Competitive risks - Competitive risks
- Execution risks - Execution risks
@@ -192,20 +231,23 @@
## Appendices ## Appendices
### A. Data Sources ### A. Data Sources
{{List all sources used in the research}} {{List all sources used in the research}}
### B. Detailed Calculations ### B. Detailed Calculations
{{Include any complex calculations or models}} {{Include any complex calculations or models}}
### C. Additional Analysis ### C. Additional Analysis
{{Any supplementary analysis not included in main body}} {{Any supplementary analysis not included in main body}}
--- ---
[[LLM: After completing the document, offer advanced elicitation with these custom options for market research: [[LLM: After completing the document, offer advanced elicitation with these custom options for market research:
**Market Research Elicitation Actions** **Market Research Elicitation Actions** 0. Expand market sizing calculations with sensitivity analysis
0. Expand market sizing calculations with sensitivity analysis
1. Deep dive into a specific customer segment 1. Deep dive into a specific customer segment
2. Analyze an emerging market trend in detail 2. Analyze an emerging market trend in detail
3. Compare this market to an analogous market 3. Compare this market to an analogous market
@@ -216,4 +258,4 @@
8. If only we had considered [X market factor]... 8. If only we had considered [X market factor]...
9. Proceed to next section 9. Proceed to next section
These replace the standard elicitation options when working on market research documents.]] These replace the standard elicitation options when working on market research documents.]]

37
.bmad-core/templates/project-brief-tmpl.md
View File

@@ -1,8 +1,9 @@
# Project Brief: {{Project Name}} # Project Brief: {{Project Name}}
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development. [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
Start by asking the user which mode they prefer: Start by asking the user which mode they prefer:
1. **Interactive Mode** - Work through each section collaboratively 1. **Interactive Mode** - Work through each section collaboratively
2. **YOLO Mode** - Generate complete draft for review and refinement 2. **YOLO Mode** - Generate complete draft for review and refinement
@@ -11,6 +12,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
## Executive Summary ## Executive Summary
[[LLM: Create a concise overview that captures the essence of the project. Include: [[LLM: Create a concise overview that captures the essence of the project. Include:
- Product concept in 1-2 sentences - Product concept in 1-2 sentences
- Primary problem being solved - Primary problem being solved
- Target market identification - Target market identification
@@ -21,6 +23,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
## Problem Statement ## Problem Statement
[[LLM: Articulate the problem with clarity and evidence. Address: [[LLM: Articulate the problem with clarity and evidence. Address:
- Current state and pain points - Current state and pain points
- Impact of the problem (quantify if possible) - Impact of the problem (quantify if possible)
- Why existing solutions fall short - Why existing solutions fall short
@@ -31,6 +34,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
## Proposed Solution ## Proposed Solution
[[LLM: Describe the solution approach at a high level. Include: [[LLM: Describe the solution approach at a high level. Include:
- Core concept and approach - Core concept and approach
- Key differentiators from existing solutions - Key differentiators from existing solutions
- Why this solution will succeed where others haven't - Why this solution will succeed where others haven't
@@ -41,15 +45,18 @@ Before beginning, understand what inputs are available (brainstorming results, m
## Target Users ## Target Users
[[LLM: Define and characterize the intended users with specificity. For each user segment include: [[LLM: Define and characterize the intended users with specificity. For each user segment include:
- Demographic/firmographic profile - Demographic/firmographic profile
- Current behaviors and workflows - Current behaviors and workflows
- Specific needs and pain points - Specific needs and pain points
- Goals they're trying to achieve]] - Goals they're trying to achieve]]
### Primary User Segment: {{Segment Name}} ### Primary User Segment: {{Segment Name}}
{{Detailed description of primary users}} {{Detailed description of primary users}}
### Secondary User Segment: {{Segment Name}} ### Secondary User Segment: {{Segment Name}}
{{Description of secondary users if applicable}} {{Description of secondary users if applicable}}
## Goals & Success Metrics ## Goals & Success Metrics
@@ -57,16 +64,19 @@ Before beginning, understand what inputs are available (brainstorming results, m
[[LLM: Establish clear objectives and how to measure success. Make goals SMART (Specific, Measurable, Achievable, Relevant, Time-bound)]] [[LLM: Establish clear objectives and how to measure success. Make goals SMART (Specific, Measurable, Achievable, Relevant, Time-bound)]]
### Business Objectives ### Business Objectives
- {{Objective 1 with metric}} - {{Objective 1 with metric}}
- {{Objective 2 with metric}} - {{Objective 2 with metric}}
- {{Objective 3 with metric}} - {{Objective 3 with metric}}
### User Success Metrics ### User Success Metrics
- {{How users will measure value}} - {{How users will measure value}}
- {{Engagement metrics}} - {{Engagement metrics}}
- {{Satisfaction indicators}} - {{Satisfaction indicators}}
### Key Performance Indicators (KPIs) ### Key Performance Indicators (KPIs)
- {{KPI 1: Definition and target}} - {{KPI 1: Definition and target}}
- {{KPI 2: Definition and target}} - {{KPI 2: Definition and target}}
- {{KPI 3: Definition and target}} - {{KPI 3: Definition and target}}
@@ -76,15 +86,18 @@ Before beginning, understand what inputs are available (brainstorming results, m
[[LLM: Define the minimum viable product clearly. Be specific about what's in and what's out. Help user distinguish must-haves from nice-to-haves.]] [[LLM: Define the minimum viable product clearly. Be specific about what's in and what's out. Help user distinguish must-haves from nice-to-haves.]]
### Core Features (Must Have) ### Core Features (Must Have)
- **Feature 1:** {{Brief description and why it's essential}} - **Feature 1:** {{Brief description and why it's essential}}
- **Feature 2:** {{Brief description and why it's essential}} - **Feature 2:** {{Brief description and why it's essential}}
- **Feature 3:** {{Brief description and why it's essential}} - **Feature 3:** {{Brief description and why it's essential}}
### Out of Scope for MVP ### Out of Scope for MVP
- {{Feature/capability explicitly not in MVP}} - {{Feature/capability explicitly not in MVP}}
- {{Feature/capability to be considered post-MVP}} - {{Feature/capability to be considered post-MVP}}
### MVP Success Criteria ### MVP Success Criteria
{{Define what constitutes a successful MVP launch}} {{Define what constitutes a successful MVP launch}}
## Post-MVP Vision ## Post-MVP Vision
@@ -92,12 +105,15 @@ Before beginning, understand what inputs are available (brainstorming results, m
[[LLM: Outline the longer-term product direction without overcommitting to specifics]] [[LLM: Outline the longer-term product direction without overcommitting to specifics]]
### Phase 2 Features ### Phase 2 Features
{{Next priority features after MVP success}} {{Next priority features after MVP success}}
### Long-term Vision ### Long-term Vision
{{Where this product could go in 1-2 years}} {{Where this product could go in 1-2 years}}
### Expansion Opportunities ### Expansion Opportunities
{{Potential new markets, use cases, or integrations}} {{Potential new markets, use cases, or integrations}}
## Technical Considerations ## Technical Considerations
@@ -105,17 +121,20 @@ Before beginning, understand what inputs are available (brainstorming results, m
[[LLM: Document known technical constraints and preferences. Note these are initial thoughts, not final decisions.]] [[LLM: Document known technical constraints and preferences. Note these are initial thoughts, not final decisions.]]
### Platform Requirements ### Platform Requirements
- **Target Platforms:** {{Web, mobile, desktop, etc.}} - **Target Platforms:** {{Web, mobile, desktop, etc.}}
- **Browser/OS Support:** {{Specific requirements}} - **Browser/OS Support:** {{Specific requirements}}
- **Performance Requirements:** {{Load times, concurrent users, etc.}} - **Performance Requirements:** {{Load times, concurrent users, etc.}}
### Technology Preferences ### Technology Preferences
- **Frontend:** {{If any preferences exist}} - **Frontend:** {{If any preferences exist}}
- **Backend:** {{If any preferences exist}} - **Backend:** {{If any preferences exist}}
- **Database:** {{If any preferences exist}} - **Database:** {{If any preferences exist}}
- **Hosting/Infrastructure:** {{Cloud preferences, on-prem requirements}} - **Hosting/Infrastructure:** {{Cloud preferences, on-prem requirements}}
### Architecture Considerations ### Architecture Considerations
- **Repository Structure:** {{Initial thoughts on monorepo vs. polyrepo}} - **Repository Structure:** {{Initial thoughts on monorepo vs. polyrepo}}
- **Service Architecture:** {{Initial thoughts on monolith vs. microservices}} - **Service Architecture:** {{Initial thoughts on monolith vs. microservices}}
- **Integration Requirements:** {{Third-party services, APIs}} - **Integration Requirements:** {{Third-party services, APIs}}
@@ -126,12 +145,14 @@ Before beginning, understand what inputs are available (brainstorming results, m
[[LLM: Clearly state limitations and assumptions to set realistic expectations]] [[LLM: Clearly state limitations and assumptions to set realistic expectations]]
### Constraints ### Constraints
- **Budget:** {{If known}} - **Budget:** {{If known}}
- **Timeline:** {{Target launch date or development timeframe}} - **Timeline:** {{Target launch date or development timeframe}}
- **Resources:** {{Team size, skill constraints}} - **Resources:** {{Team size, skill constraints}}
- **Technical:** {{Legacy systems, required tech stack}} - **Technical:** {{Legacy systems, required tech stack}}
### Key Assumptions ### Key Assumptions
- {{Assumption about users, market, or technology}} - {{Assumption about users, market, or technology}}
- {{Assumption about resources or support}} - {{Assumption about resources or support}}
- {{Assumption about external dependencies}} - {{Assumption about external dependencies}}
@@ -141,37 +162,45 @@ Before beginning, understand what inputs are available (brainstorming results, m
[[LLM: Identify unknowns and potential challenges proactively]] [[LLM: Identify unknowns and potential challenges proactively]]
### Key Risks ### Key Risks
- **Risk 1:** {{Description and potential impact}} - **Risk 1:** {{Description and potential impact}}
- **Risk 2:** {{Description and potential impact}} - **Risk 2:** {{Description and potential impact}}
- **Risk 3:** {{Description and potential impact}} - **Risk 3:** {{Description and potential impact}}
### Open Questions ### Open Questions
- {{Question needing research or decision}} - {{Question needing research or decision}}
- {{Question about technical approach}} - {{Question about technical approach}}
- {{Question about market or users}} - {{Question about market or users}}
### Areas Needing Further Research ### Areas Needing Further Research
- {{Topic requiring deeper investigation}} - {{Topic requiring deeper investigation}}
- {{Validation needed before proceeding}} - {{Validation needed before proceeding}}
## Appendices ## Appendices
### A. Research Summary ### A. Research Summary
{{If applicable, summarize key findings from: {{If applicable, summarize key findings from:
- Market research - Market research
- Competitive analysis - Competitive analysis
- User interviews - User interviews
- Technical feasibility studies}} - Technical feasibility studies}}
### B. Stakeholder Input ### B. Stakeholder Input
{{Key feedback or requirements from stakeholders}} {{Key feedback or requirements from stakeholders}}
### C. References ### C. References
{{Links to relevant documents, research, or examples}} {{Links to relevant documents, research, or examples}}
## Next Steps ## Next Steps
### Immediate Actions ### Immediate Actions
1. {{First concrete next step}} 1. {{First concrete next step}}
2. {{Second concrete next step}} 2. {{Second concrete next step}}
3. {{Third concrete next step}} 3. {{Third concrete next step}}
@@ -184,8 +213,8 @@ This Project Brief provides the full context for {{Project Name}}. Please start
[[LLM: After completing each major section (not subsections), offer advanced elicitation with these custom options for project briefs: [[LLM: After completing each major section (not subsections), offer advanced elicitation with these custom options for project briefs:
**Project Brief Elicitation Actions** **Project Brief Elicitation Actions** 0. Expand section with more specific details
0. Expand section with more specific details
1. Validate against similar successful products 1. Validate against similar successful products
2. Stress test assumptions with edge cases 2. Stress test assumptions with edge cases
3. Explore alternative solution approaches 3. Explore alternative solution approaches

37
.bmad-core/templates/web-agent-startup-instructions-template.md
View File

@@ -7,27 +7,30 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly. 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like: 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================` - `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
When you need to reference a resource mentioned in your instructions: 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
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example: - 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
```yaml **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
dependencies:
utils:
- template-format
tasks:
- create-story
```
These references map directly to bundle sections: ```yaml
- `utils: template-format` → Look for `==================== START: utils#template-format ====================` dependencies:
- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================` utils:
- template-format
tasks:
- create-story
```
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 ====================`
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. 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.

4
.bmad-core/utils/template-format.md
View File

@@ -6,7 +6,7 @@ Templates in the BMAD method use standardized markup for AI processing. These co
- **{{placeholders}}**: Variables to be replaced with actual content - **{{placeholders}}**: Variables to be replaced with actual content
- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users) - **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
- **<<REPEAT>>** sections: Content blocks that may be repeated as needed - **REPEAT** sections: Content blocks that may be repeated as needed
- **^^CONDITION^^** blocks: Conditional content included only if criteria are met - **^^CONDITION^^** blocks: Conditional content included only if criteria are met
- **@{examples}**: Example content for guidance (never output to users) - **@{examples}**: Example content for guidance (never output to users)
@@ -23,4 +23,4 @@ Templates in the BMAD method use standardized markup for AI processing. These co
- **NEVER display template markup, LLM instructions, or examples to users** - **NEVER display template markup, LLM instructions, or examples to users**
- Template elements are for AI processing only - Template elements are for AI processing only
- Focus on faithful template execution and clean output - Focus on faithful template execution and clean output
- All template-specific instructions are embedded within templates - All template-specific instructions are embedded within templates

12
.bmad-core/utils/workflow-management.md
View File

@@ -41,11 +41,11 @@ The actual list depends on which team bundle is loaded. When responding to this
Example response format: Example response format:
``` ```text
Available workflows for [Team Name]: Available workflows for [Team Name]:
1. [workflow-id] - [Brief description based on workflow type] 1. [workflow-id] - [Brief description based on workflow type]
2. [workflow-id] - [Brief description based on workflow type] 2. [workflow-id] - [Brief description based on workflow type]
... [... etc. ...]
Use /workflow-start {number or id} to begin a workflow. Use /workflow-start {number or id} to begin a workflow.
``` ```
@@ -62,7 +62,7 @@ Shows current workflow progress, completed artifacts, and next steps.
Example response: Example response:
``` ```text
Current Workflow: Greenfield Full-Stack Development Current Workflow: Greenfield Full-Stack Development
Stage: Product Planning (2 of 6) Stage: Product Planning (2 of 6)
Completed: Completed:
@@ -82,7 +82,7 @@ Resumes a workflow from where it left off, useful when starting a new chat.
User can provide completed artifacts: User can provide completed artifacts:
``` ```text
User: /workflow-resume greenfield-fullstack User: /workflow-resume greenfield-fullstack
I have completed: project-brief, PRD I have completed: project-brief, PRD
BMad: I see you've completed Discovery and part of Product Planning. BMad: I see you've completed Discovery and part of Product Planning.
@@ -150,7 +150,7 @@ When user returns after interruption:
Example: Example:
``` ```text
User: I'm working on a new app. Here's my PRD and architecture doc. User: I'm working on a new app. Here's my PRD and architecture doc.
BMad: I see you have a PRD and architecture document. Based on these artifacts, BMad: I see you have a PRD and architecture document. Based on these artifacts,
it looks like you're following the greenfield-fullstack workflow and have completed it looks like you're following the greenfield-fullstack workflow and have completed
@@ -173,7 +173,7 @@ When transitioning between agents, pass:
Example transition: Example transition:
``` ```text
BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow, BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
the next step is UX Strategy with Sally. the next step is UX Strategy with Sally.

25
.bmad-core/web-bundles/agents/analyst.txt
View File

@@ -9,7 +9,7 @@ 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: 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================` - `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================` - `==================== END: folder#filename ====================`
When you need to reference a resource mentioned in your instructions: When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags - Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`) - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
@@ -159,13 +159,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
5. **SCAMPER Method** 5. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]] [[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted? - **S** = Substitute: What can be substituted?
- **C**ombine: What can be combined or integrated? - **C** = Combine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere? - **A** = Adapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced? - **M** = Modify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for? - **P** = Put to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified? - **E** = Eliminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered? - **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats** 6. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]] [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -178,7 +178,8 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
7. **Mind Mapping** 7. **Mind Mapping**
[[LLM: Create text-based mind maps with clear hierarchical structure.]] [[LLM: Create text-based mind maps with clear hierarchical structure.]]
```
```text
Central Concept Central Concept
├── Branch 1 ├── Branch 1
│ ├── Sub-idea 1.1 │ ├── Sub-idea 1.1
@@ -787,7 +788,7 @@ Choose an action (0-9 - 9 to bypass - HELP for explanation of these options):
==================== START: templates#project-brief-tmpl ==================== ==================== START: templates#project-brief-tmpl ====================
# Project Brief: {{Project Name}} # Project Brief: {{Project Name}}
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development. [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
Start by asking the user which mode they prefer: Start by asking the user which mode they prefer:
1. **Interactive Mode** - Work through each section collaboratively 1. **Interactive Mode** - Work through each section collaboratively
@@ -946,7 +947,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
### A. Research Summary ### A. Research Summary
{{If applicable, summarize key findings from: {{If applicable, summarize key findings from:
- Market research - Market research
- Competitive analysis - Competitive analysis
- User interviews - User interviews
- Technical feasibility studies}} - Technical feasibility studies}}
@@ -1258,7 +1259,7 @@ These replace the standard elicitation options when working on market research d
{{Create a 2x2 matrix: {{Create a 2x2 matrix:
- Priority 1 (Core Competitors): High Market Share + High Threat - Priority 1 (Core Competitors): High Market Share + High Threat
- Priority 2 (Emerging Threats): Low Market Share + High Threat - Priority 2 (Emerging Threats): Low Market Share + High Threat
- Priority 3 (Established Players): High Market Share + Low Threat - Priority 3 (Established Players): High Market Share + Low Threat
- Priority 4 (Monitor Only): Low Market Share + Low Threat}} - Priority 4 (Monitor Only): Low Market Share + Low Threat}}

2
.bmad-core/web-bundles/agents/architect.txt
View File

@@ -9,7 +9,7 @@ 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: 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================` - `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================` - `==================== END: folder#filename ====================`
When you need to reference a resource mentioned in your instructions: When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags - Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`) - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)

49
.bmad-core/web-bundles/agents/bmad-master.txt
View File

@@ -7,9 +7,10 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly. 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like: 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================` - `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
When you need to reference a resource mentioned in your instructions: When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags - Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`) - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
@@ -296,13 +297,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
5. **SCAMPER Method** 5. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]] [[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted? - **S** = Substitute: What can be substituted?
- **C**ombine: What can be combined or integrated? - **C** = Combine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere? - **A** = Adapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced? - **M** = Modify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for? - **P** = Put to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified? - **E** = Eliminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered? - **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats** 6. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]] [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -678,8 +679,8 @@ Create a single focused story following this structure:
#### User Story #### User Story
As a {{user type}}, As a {{user type}},
I want {{specific action/capability}}, I want {{specific action/capability}},
So that {{clear benefit/value}}. So that {{clear benefit/value}}.
#### Story Context #### Story Context
@@ -1829,7 +1830,7 @@ Analyze where this IDE agent fits in workflows:
4. **Document recommendations**: 4. **Document recommendations**:
```markdown ```markdown
## Workflow Integration ## Workflow Integration
This agent enhances the following workflows: This agent enhances the following workflows:
- `greenfield-service`: API design phase (between architecture and implementation) - `greenfield-service`: API design phase (between architecture and implementation)
- `brownfield-service`: API refactoring and modernization - `brownfield-service`: API refactoring and modernization
@@ -1849,7 +1850,7 @@ Consider which teams benefit from this IDE agent:
3. **Document integration**: 3. **Document integration**:
```markdown ```markdown
## Team Integration ## Team Integration
Recommended teams for this agent: Recommended teams for this agent:
- `team-fullstack`: Provides specialized {domain} expertise - `team-fullstack`: Provides specialized {domain} expertise
- `team-no-ui`: Enhances backend {capability} - `team-no-ui`: Enhances backend {capability}
@@ -2331,7 +2332,7 @@ workflows:
Before finalizing, verify: Before finalizing, verify:
1. **Role Coverage**: Does the team have all necessary skills for its workflows? 1. **Role Coverage**: Does the team have all necessary skills for its workflows?
2. **Size Optimization**: 2. **Size Optimization**:
- Minimum: 2 agents (bmad + 1) - Minimum: 2 agents (bmad + 1)
- Recommended: 3-7 agents - Recommended: 3-7 agents
- Maximum with wildcard: bmad + "*" - Maximum with wildcard: bmad + "*"
@@ -2362,8 +2363,8 @@ Document how this team integrates with existing system:
bundle: bundle:
name: "Team API" name: "Team API"
description: >- description: >-
Specialized team for API and backend service development. Focuses on Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI robust service architecture, implementation, and testing without UI
components. Ideal for microservices, REST APIs, and backend systems. components. Ideal for microservices, REST APIs, and backend systems.
agents: agents:
@@ -2385,8 +2386,8 @@ workflows:
bundle: bundle:
name: "Team Prototype" name: "Team Prototype"
description: >- description: >-
Agile team for rapid prototyping and proof of concept development. Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations Combines planning, design, and implementation for quick iterations
on new ideas and experimental features. on new ideas and experimental features.
agents: agents:
@@ -4613,7 +4614,7 @@ so that {{benefit}}.
{{Create a 2x2 matrix: {{Create a 2x2 matrix:
- Priority 1 (Core Competitors): High Market Share + High Threat - Priority 1 (Core Competitors): High Market Share + High Threat
- Priority 2 (Emerging Threats): Low Market Share + High Threat - Priority 2 (Emerging Threats): Low Market Share + High Threat
- Priority 3 (Established Players): High Market Share + Low Threat - Priority 3 (Established Players): High Market Share + Low Threat
- Priority 4 (Monitor Only): Low Market Share + Low Threat}} - Priority 4 (Monitor Only): Low Market Share + Low Threat}}
@@ -6963,7 +6964,7 @@ so that {{benefit}}.
==================== START: templates#project-brief-tmpl ==================== ==================== START: templates#project-brief-tmpl ====================
# Project Brief: {{Project Name}} # Project Brief: {{Project Name}}
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development. [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
Start by asking the user which mode they prefer: Start by asking the user which mode they prefer:
1. **Interactive Mode** - Work through each section collaboratively 1. **Interactive Mode** - Work through each section collaboratively
@@ -7122,7 +7123,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
### A. Research Summary ### A. Research Summary
{{If applicable, summarize key findings from: {{If applicable, summarize key findings from:
- Market research - Market research
- Competitive analysis - Competitive analysis
- User interviews - User interviews
- Technical feasibility studies}} - Technical feasibility studies}}
@@ -7238,7 +7239,7 @@ 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: 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================` - `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================` - `==================== END: folder#filename ====================`
When you need to reference a resource mentioned in your instructions: When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags - Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`) - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
@@ -8677,7 +8678,7 @@ Generate a comprehensive validation report that adapts to project type:
After presenting the report, ask if the user wants: After presenting the report, ask if the user wants:
- Detailed analysis of any failed sections - Detailed analysis of any failed sections
- Specific story resequencing suggestions - Specific story reordering suggestions
- Risk mitigation strategies - Risk mitigation strategies
- [BROWNFIELD] Integration risk deep-dive]] - [BROWNFIELD] Integration risk deep-dive]]

91
.bmad-core/web-bundles/teams/team-all.txt
View File

@@ -7,9 +7,10 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly. 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like: 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================` - `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
When you need to reference a resource mentioned in your instructions: When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags - Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`) - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
@@ -754,7 +755,7 @@ Analyze where this IDE agent fits in workflows:
4. **Document recommendations**: 4. **Document recommendations**:
```markdown ```markdown
## Workflow Integration ## Workflow Integration
This agent enhances the following workflows: This agent enhances the following workflows:
- `greenfield-service`: API design phase (between architecture and implementation) - `greenfield-service`: API design phase (between architecture and implementation)
- `brownfield-service`: API refactoring and modernization - `brownfield-service`: API refactoring and modernization
@@ -774,7 +775,7 @@ Consider which teams benefit from this IDE agent:
3. **Document integration**: 3. **Document integration**:
```markdown ```markdown
## Team Integration ## Team Integration
Recommended teams for this agent: Recommended teams for this agent:
- `team-fullstack`: Provides specialized {domain} expertise - `team-fullstack`: Provides specialized {domain} expertise
- `team-no-ui`: Enhances backend {capability} - `team-no-ui`: Enhances backend {capability}
@@ -1047,7 +1048,7 @@ workflows:
Before finalizing, verify: Before finalizing, verify:
1. **Role Coverage**: Does the team have all necessary skills for its workflows? 1. **Role Coverage**: Does the team have all necessary skills for its workflows?
2. **Size Optimization**: 2. **Size Optimization**:
- Minimum: 2 agents (bmad + 1) - Minimum: 2 agents (bmad + 1)
- Recommended: 3-7 agents - Recommended: 3-7 agents
- Maximum with wildcard: bmad + "*" - Maximum with wildcard: bmad + "*"
@@ -1078,8 +1079,8 @@ Document how this team integrates with existing system:
bundle: bundle:
name: "Team API" name: "Team API"
description: >- description: >-
Specialized team for API and backend service development. Focuses on Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI robust service architecture, implementation, and testing without UI
components. Ideal for microservices, REST APIs, and backend systems. components. Ideal for microservices, REST APIs, and backend systems.
agents: agents:
@@ -1101,8 +1102,8 @@ workflows:
bundle: bundle:
name: "Team Prototype" name: "Team Prototype"
description: >- description: >-
Agile team for rapid prototyping and proof of concept development. Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations Combines planning, design, and implementation for quick iterations
on new ideas and experimental features. on new ideas and experimental features.
agents: agents:
@@ -2101,13 +2102,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
5. **SCAMPER Method** 5. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]] [[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted? - **S** = Substitute: What can be substituted?
- **C**ombine: What can be combined or integrated? - **C** = Combine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere? - **A** = Adapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced? - **M** = Modify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for? - **P** = Put to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified? - **E** = Eliminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered? - **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats** 6. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]] [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -2557,7 +2558,7 @@ Present these numbered options to the user:
==================== START: templates#project-brief-tmpl ==================== ==================== START: templates#project-brief-tmpl ====================
# Project Brief: {{Project Name}} # Project Brief: {{Project Name}}
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development. [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
Start by asking the user which mode they prefer: Start by asking the user which mode they prefer:
1. **Interactive Mode** - Work through each section collaboratively 1. **Interactive Mode** - Work through each section collaboratively
@@ -2716,7 +2717,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
### A. Research Summary ### A. Research Summary
{{If applicable, summarize key findings from: {{If applicable, summarize key findings from:
- Market research - Market research
- Competitive analysis - Competitive analysis
- User interviews - User interviews
- Technical feasibility studies}} - Technical feasibility studies}}
@@ -3028,7 +3029,7 @@ These replace the standard elicitation options when working on market research d
{{Create a 2x2 matrix: {{Create a 2x2 matrix:
- Priority 1 (Core Competitors): High Market Share + High Threat - Priority 1 (Core Competitors): High Market Share + High Threat
- Priority 2 (Emerging Threats): Low Market Share + High Threat - Priority 2 (Emerging Threats): Low Market Share + High Threat
- Priority 3 (Established Players): High Market Share + Low Threat - Priority 3 (Established Players): High Market Share + Low Threat
- Priority 4 (Monitor Only): Low Market Share + Low Threat}} - Priority 4 (Monitor Only): Low Market Share + Low Threat}}
@@ -6704,8 +6705,8 @@ Create a single focused story following this structure:
#### User Story #### User Story
As a {{user type}}, As a {{user type}},
I want {{specific action/capability}}, I want {{specific action/capability}},
So that {{clear benefit/value}}. So that {{clear benefit/value}}.
#### Story Context #### Story Context
@@ -8455,7 +8456,7 @@ Generate a comprehensive validation report that adapts to project type:
After presenting the report, ask if the user wants: After presenting the report, ask if the user wants:
- Detailed analysis of any failed sections - Detailed analysis of any failed sections
- Specific story resequencing suggestions - Specific story reordering suggestions
- Risk mitigation strategies - Risk mitigation strategies
- [BROWNFIELD] Integration risk deep-dive]] - [BROWNFIELD] Integration risk deep-dive]]
@@ -9337,7 +9338,7 @@ workflow:
id: brownfield-fullstack id: brownfield-fullstack
name: Brownfield Full-Stack Enhancement name: Brownfield Full-Stack Enhancement
description: >- description: >-
Agent workflow for enhancing existing full-stack applications with new features, Agent workflow for enhancing existing full-stack applications with new features,
modernization, or significant changes. Handles existing system analysis and safe integration. modernization, or significant changes. Handles existing system analysis and safe integration.
type: brownfield type: brownfield
project_types: project_types:
@@ -9405,7 +9406,7 @@ workflow:
A[Start: Brownfield Enhancement] --> B{Enhancement Complexity?} A[Start: Brownfield Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing project] B -->|Complex/Significant| C[analyst: analyze existing project]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md] E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist] F --> G[po: validate with po-master-checklist]
@@ -9413,12 +9414,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes] H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment] H -->|No| J[Move to IDE Environment]
I --> G I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story] D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment] K --> M[Move to IDE Environment]
L --> M L --> M
style J fill:#90EE90 style J fill:#90EE90
style M fill:#90EE90 style M fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5
@@ -9525,7 +9526,7 @@ workflow:
A[Start: Service Enhancement] --> B{Enhancement Complexity?} A[Start: Service Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing service] B -->|Complex/Significant| C[analyst: analyze existing service]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md] E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist] F --> G[po: validate with po-master-checklist]
@@ -9533,12 +9534,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes] H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment] H -->|No| J[Move to IDE Environment]
I --> G I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story] D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment] K --> M[Move to IDE Environment]
L --> M L --> M
style J fill:#90EE90 style J fill:#90EE90
style M fill:#90EE90 style M fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5
@@ -9652,7 +9653,7 @@ workflow:
A[Start: UI Enhancement] --> B{Enhancement Complexity?} A[Start: UI Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing UI] B -->|Complex/Significant| C[analyst: analyze existing UI]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[ux-expert: front-end-spec.md] E --> F[ux-expert: front-end-spec.md]
F --> G[architect: brownfield-architecture.md] F --> G[architect: brownfield-architecture.md]
@@ -9661,12 +9662,12 @@ workflow:
I -->|Yes| J[Return to relevant agent for fixes] I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K[Move to IDE Environment] I -->|No| K[Move to IDE Environment]
J --> H J --> H
D -->|1 Story| L[pm/po/sm: brownfield-create-story] D -->|1 Story| L[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| M[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| M[pm/po/sm: brownfield-create-epic]
L --> N[Move to IDE Environment] L --> N[Move to IDE Environment]
M --> N M --> N
style K fill:#90EE90 style K fill:#90EE90
style N fill:#90EE90 style N fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5
@@ -9810,7 +9811,7 @@ workflow:
A[Start: Greenfield Project] --> B{Project Complexity?} A[Start: Greenfield Project] --> B{Project Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md] E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?} F --> F2{Generate v0 prompt?}
@@ -9826,16 +9827,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes] K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment] K -->|No| M[Move to IDE Environment]
L --> J L --> J
D --> N[pm: simple epic or story] D --> N[pm: simple epic or story]
N --> O[Move to IDE Environment] N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research] F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research] G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style M fill:#90EE90 style M fill:#90EE90
style O fill:#90EE90 style O fill:#90EE90
style F3 fill:#E6E6FA style F3 fill:#E6E6FA
@@ -9966,7 +9967,7 @@ workflow:
A[Start: Service Development] --> B{Service Complexity?} A[Start: Service Development] --> B{Service Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[architect: architecture.md] E --> F[architect: architecture.md]
F --> G{Architecture suggests PRD changes?} F --> G{Architecture suggests PRD changes?}
@@ -9977,15 +9978,15 @@ workflow:
J -->|Yes| K[Return to relevant agent for fixes] J -->|Yes| K[Return to relevant agent for fixes]
J -->|No| L[Move to IDE Environment] J -->|No| L[Move to IDE Environment]
K --> I K --> I
D --> M[pm: simple epic or story] D --> M[pm: simple epic or story]
M --> N[Move to IDE Environment] M --> N[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: technical research] F -.-> F1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style L fill:#90EE90 style L fill:#90EE90
style N fill:#90EE90 style N fill:#90EE90
style C fill:#FFE4B5 style C fill:#FFE4B5
@@ -10131,7 +10132,7 @@ workflow:
A[Start: UI Development] --> B{UI Complexity?} A[Start: UI Development] --> B{UI Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md] E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?} F --> F2{Generate v0 prompt?}
@@ -10147,16 +10148,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes] K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment] K -->|No| M[Move to IDE Environment]
L --> J L --> J
D --> N[ux-expert: simple wireframes] D --> N[ux-expert: simple wireframes]
N --> O[Move to IDE Environment] N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research] F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research] G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style M fill:#90EE90 style M fill:#90EE90
style O fill:#90EE90 style O fill:#90EE90
style F3 fill:#E6E6FA style F3 fill:#E6E6FA

101
.bmad-core/web-bundles/teams/team-fullstack.txt
View File

@@ -7,9 +7,10 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly. 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like: 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================` - `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
When you need to reference a resource mentioned in your instructions: When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags - Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`) - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
@@ -39,11 +40,11 @@ When you need to reference a resource mentioned in your instructions:
bundle: bundle:
name: Team Fullstack name: Team Fullstack
description: >- description: >-
Comprehensive full-stack development team capable of handling both greenfield Comprehensive full-stack development team capable of handling both greenfield
application development and brownfield enhancement projects. This team combines application development and brownfield enhancement projects. This team combines
strategic planning, user experience design, and holistic system architecture strategic planning, user experience design, and holistic system architecture
to deliver complete solutions from concept to deployment. Specializes in to deliver complete solutions from concept to deployment. Specializes in
full-stack applications, SaaS platforms, enterprise apps, feature additions, full-stack applications, SaaS platforms, enterprise apps, feature additions,
refactoring, and system modernization. refactoring, and system modernization.
agents: agents:
@@ -580,7 +581,7 @@ Analyze where this IDE agent fits in workflows:
4. **Document recommendations**: 4. **Document recommendations**:
```markdown ```markdown
## Workflow Integration ## Workflow Integration
This agent enhances the following workflows: This agent enhances the following workflows:
- `greenfield-service`: API design phase (between architecture and implementation) - `greenfield-service`: API design phase (between architecture and implementation)
- `brownfield-service`: API refactoring and modernization - `brownfield-service`: API refactoring and modernization
@@ -600,7 +601,7 @@ Consider which teams benefit from this IDE agent:
3. **Document integration**: 3. **Document integration**:
```markdown ```markdown
## Team Integration ## Team Integration
Recommended teams for this agent: Recommended teams for this agent:
- `team-fullstack`: Provides specialized {domain} expertise - `team-fullstack`: Provides specialized {domain} expertise
- `team-no-ui`: Enhances backend {capability} - `team-no-ui`: Enhances backend {capability}
@@ -873,7 +874,7 @@ workflows:
Before finalizing, verify: Before finalizing, verify:
1. **Role Coverage**: Does the team have all necessary skills for its workflows? 1. **Role Coverage**: Does the team have all necessary skills for its workflows?
2. **Size Optimization**: 2. **Size Optimization**:
- Minimum: 2 agents (bmad + 1) - Minimum: 2 agents (bmad + 1)
- Recommended: 3-7 agents - Recommended: 3-7 agents
- Maximum with wildcard: bmad + "*" - Maximum with wildcard: bmad + "*"
@@ -904,8 +905,8 @@ Document how this team integrates with existing system:
bundle: bundle:
name: "Team API" name: "Team API"
description: >- description: >-
Specialized team for API and backend service development. Focuses on Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI robust service architecture, implementation, and testing without UI
components. Ideal for microservices, REST APIs, and backend systems. components. Ideal for microservices, REST APIs, and backend systems.
agents: agents:
@@ -927,8 +928,8 @@ workflows:
bundle: bundle:
name: "Team Prototype" name: "Team Prototype"
description: >- description: >-
Agile team for rapid prototyping and proof of concept development. Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations Combines planning, design, and implementation for quick iterations
on new ideas and experimental features. on new ideas and experimental features.
agents: agents:
@@ -1927,13 +1928,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
5. **SCAMPER Method** 5. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]] [[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted? - **S** = Substitute: What can be substituted?
- **C**ombine: What can be combined or integrated? - **C** = Combine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere? - **A** = Adapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced? - **M** = Modify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for? - **P** = Put to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified? - **E** = Eliminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered? - **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats** 6. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]] [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -2383,7 +2384,7 @@ Present these numbered options to the user:
==================== START: templates#project-brief-tmpl ==================== ==================== START: templates#project-brief-tmpl ====================
# Project Brief: {{Project Name}} # Project Brief: {{Project Name}}
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development. [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
Start by asking the user which mode they prefer: Start by asking the user which mode they prefer:
1. **Interactive Mode** - Work through each section collaboratively 1. **Interactive Mode** - Work through each section collaboratively
@@ -2542,7 +2543,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
### A. Research Summary ### A. Research Summary
{{If applicable, summarize key findings from: {{If applicable, summarize key findings from:
- Market research - Market research
- Competitive analysis - Competitive analysis
- User interviews - User interviews
- Technical feasibility studies}} - Technical feasibility studies}}
@@ -2854,7 +2855,7 @@ These replace the standard elicitation options when working on market research d
{{Create a 2x2 matrix: {{Create a 2x2 matrix:
- Priority 1 (Core Competitors): High Market Share + High Threat - Priority 1 (Core Competitors): High Market Share + High Threat
- Priority 2 (Emerging Threats): Low Market Share + High Threat - Priority 2 (Emerging Threats): Low Market Share + High Threat
- Priority 3 (Established Players): High Market Share + Low Threat - Priority 3 (Established Players): High Market Share + Low Threat
- Priority 4 (Monitor Only): Low Market Share + Low Threat}} - Priority 4 (Monitor Only): Low Market Share + Low Threat}}
@@ -3355,8 +3356,8 @@ Create a single focused story following this structure:
#### User Story #### User Story
As a {{user type}}, As a {{user type}},
I want {{specific action/capability}}, I want {{specific action/capability}},
So that {{clear benefit/value}}. So that {{clear benefit/value}}.
#### Story Context #### Story Context
@@ -8652,7 +8653,7 @@ Generate a comprehensive validation report that adapts to project type:
After presenting the report, ask if the user wants: After presenting the report, ask if the user wants:
- Detailed analysis of any failed sections - Detailed analysis of any failed sections
- Specific story resequencing suggestions - Specific story reordering suggestions
- Risk mitigation strategies - Risk mitigation strategies
- [BROWNFIELD] Integration risk deep-dive]] - [BROWNFIELD] Integration risk deep-dive]]
@@ -8691,7 +8692,7 @@ workflow:
id: brownfield-fullstack id: brownfield-fullstack
name: Brownfield Full-Stack Enhancement name: Brownfield Full-Stack Enhancement
description: >- description: >-
Agent workflow for enhancing existing full-stack applications with new features, Agent workflow for enhancing existing full-stack applications with new features,
modernization, or significant changes. Handles existing system analysis and safe integration. modernization, or significant changes. Handles existing system analysis and safe integration.
type: brownfield type: brownfield
project_types: project_types:
@@ -8759,7 +8760,7 @@ workflow:
A[Start: Brownfield Enhancement] --> B{Enhancement Complexity?} A[Start: Brownfield Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing project] B -->|Complex/Significant| C[analyst: analyze existing project]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md] E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist] F --> G[po: validate with po-master-checklist]
@@ -8767,12 +8768,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes] H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment] H -->|No| J[Move to IDE Environment]
I --> G I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story] D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment] K --> M[Move to IDE Environment]
L --> M L --> M
style J fill:#90EE90 style J fill:#90EE90
style M fill:#90EE90 style M fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5
@@ -8879,7 +8880,7 @@ workflow:
A[Start: Service Enhancement] --> B{Enhancement Complexity?} A[Start: Service Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing service] B -->|Complex/Significant| C[analyst: analyze existing service]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md] E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist] F --> G[po: validate with po-master-checklist]
@@ -8887,12 +8888,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes] H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment] H -->|No| J[Move to IDE Environment]
I --> G I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story] D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment] K --> M[Move to IDE Environment]
L --> M L --> M
style J fill:#90EE90 style J fill:#90EE90
style M fill:#90EE90 style M fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5
@@ -9006,7 +9007,7 @@ workflow:
A[Start: UI Enhancement] --> B{Enhancement Complexity?} A[Start: UI Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing UI] B -->|Complex/Significant| C[analyst: analyze existing UI]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[ux-expert: front-end-spec.md] E --> F[ux-expert: front-end-spec.md]
F --> G[architect: brownfield-architecture.md] F --> G[architect: brownfield-architecture.md]
@@ -9015,12 +9016,12 @@ workflow:
I -->|Yes| J[Return to relevant agent for fixes] I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K[Move to IDE Environment] I -->|No| K[Move to IDE Environment]
J --> H J --> H
D -->|1 Story| L[pm/po/sm: brownfield-create-story] D -->|1 Story| L[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| M[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| M[pm/po/sm: brownfield-create-epic]
L --> N[Move to IDE Environment] L --> N[Move to IDE Environment]
M --> N M --> N
style K fill:#90EE90 style K fill:#90EE90
style N fill:#90EE90 style N fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5
@@ -9164,7 +9165,7 @@ workflow:
A[Start: Greenfield Project] --> B{Project Complexity?} A[Start: Greenfield Project] --> B{Project Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md] E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?} F --> F2{Generate v0 prompt?}
@@ -9180,16 +9181,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes] K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment] K -->|No| M[Move to IDE Environment]
L --> J L --> J
D --> N[pm: simple epic or story] D --> N[pm: simple epic or story]
N --> O[Move to IDE Environment] N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research] F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research] G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style M fill:#90EE90 style M fill:#90EE90
style O fill:#90EE90 style O fill:#90EE90
style F3 fill:#E6E6FA style F3 fill:#E6E6FA
@@ -9320,7 +9321,7 @@ workflow:
A[Start: Service Development] --> B{Service Complexity?} A[Start: Service Development] --> B{Service Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[architect: architecture.md] E --> F[architect: architecture.md]
F --> G{Architecture suggests PRD changes?} F --> G{Architecture suggests PRD changes?}
@@ -9331,15 +9332,15 @@ workflow:
J -->|Yes| K[Return to relevant agent for fixes] J -->|Yes| K[Return to relevant agent for fixes]
J -->|No| L[Move to IDE Environment] J -->|No| L[Move to IDE Environment]
K --> I K --> I
D --> M[pm: simple epic or story] D --> M[pm: simple epic or story]
M --> N[Move to IDE Environment] M --> N[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: technical research] F -.-> F1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style L fill:#90EE90 style L fill:#90EE90
style N fill:#90EE90 style N fill:#90EE90
style C fill:#FFE4B5 style C fill:#FFE4B5
@@ -9485,7 +9486,7 @@ workflow:
A[Start: UI Development] --> B{UI Complexity?} A[Start: UI Development] --> B{UI Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md] E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?} F --> F2{Generate v0 prompt?}
@@ -9501,16 +9502,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes] K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment] K -->|No| M[Move to IDE Environment]
L --> J L --> J
D --> N[ux-expert: simple wireframes] D --> N[ux-expert: simple wireframes]
N --> O[Move to IDE Environment] N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research] F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research] G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style M fill:#90EE90 style M fill:#90EE90
style O fill:#90EE90 style O fill:#90EE90
style F3 fill:#E6E6FA style F3 fill:#E6E6FA

61
.bmad-core/web-bundles/teams/team-no-ui.txt
View File

@@ -7,9 +7,10 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly. 1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like: 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================` - `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
When you need to reference a resource mentioned in your instructions: When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags - Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`) - The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
@@ -502,7 +503,7 @@ Analyze where this IDE agent fits in workflows:
4. **Document recommendations**: 4. **Document recommendations**:
```markdown ```markdown
## Workflow Integration ## Workflow Integration
This agent enhances the following workflows: This agent enhances the following workflows:
- `greenfield-service`: API design phase (between architecture and implementation) - `greenfield-service`: API design phase (between architecture and implementation)
- `brownfield-service`: API refactoring and modernization - `brownfield-service`: API refactoring and modernization
@@ -522,7 +523,7 @@ Consider which teams benefit from this IDE agent:
3. **Document integration**: 3. **Document integration**:
```markdown ```markdown
## Team Integration ## Team Integration
Recommended teams for this agent: Recommended teams for this agent:
- `team-fullstack`: Provides specialized {domain} expertise - `team-fullstack`: Provides specialized {domain} expertise
- `team-no-ui`: Enhances backend {capability} - `team-no-ui`: Enhances backend {capability}
@@ -795,7 +796,7 @@ workflows:
Before finalizing, verify: Before finalizing, verify:
1. **Role Coverage**: Does the team have all necessary skills for its workflows? 1. **Role Coverage**: Does the team have all necessary skills for its workflows?
2. **Size Optimization**: 2. **Size Optimization**:
- Minimum: 2 agents (bmad + 1) - Minimum: 2 agents (bmad + 1)
- Recommended: 3-7 agents - Recommended: 3-7 agents
- Maximum with wildcard: bmad + "*" - Maximum with wildcard: bmad + "*"
@@ -826,8 +827,8 @@ Document how this team integrates with existing system:
bundle: bundle:
name: "Team API" name: "Team API"
description: >- description: >-
Specialized team for API and backend service development. Focuses on Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI robust service architecture, implementation, and testing without UI
components. Ideal for microservices, REST APIs, and backend systems. components. Ideal for microservices, REST APIs, and backend systems.
agents: agents:
@@ -849,8 +850,8 @@ workflows:
bundle: bundle:
name: "Team Prototype" name: "Team Prototype"
description: >- description: >-
Agile team for rapid prototyping and proof of concept development. Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations Combines planning, design, and implementation for quick iterations
on new ideas and experimental features. on new ideas and experimental features.
agents: agents:
@@ -1849,13 +1850,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
5. **SCAMPER Method** 5. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]] [[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted? - **S** = Substitute: What can be substituted?
- **C**ombine: What can be combined or integrated? - **C** = Combine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere? - **A** = Adapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced? - **M** = Modify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for? - **P** = Put to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified? - **E** = Eliminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered? - **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats** 6. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]] [[LLM: Cycle through different thinking modes, spending focused time in each.]]
@@ -2305,7 +2306,7 @@ Present these numbered options to the user:
==================== START: templates#project-brief-tmpl ==================== ==================== START: templates#project-brief-tmpl ====================
# Project Brief: {{Project Name}} # Project Brief: {{Project Name}}
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development. [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
Start by asking the user which mode they prefer: Start by asking the user which mode they prefer:
1. **Interactive Mode** - Work through each section collaboratively 1. **Interactive Mode** - Work through each section collaboratively
@@ -2464,7 +2465,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
### A. Research Summary ### A. Research Summary
{{If applicable, summarize key findings from: {{If applicable, summarize key findings from:
- Market research - Market research
- Competitive analysis - Competitive analysis
- User interviews - User interviews
- Technical feasibility studies}} - Technical feasibility studies}}
@@ -2776,7 +2777,7 @@ These replace the standard elicitation options when working on market research d
{{Create a 2x2 matrix: {{Create a 2x2 matrix:
- Priority 1 (Core Competitors): High Market Share + High Threat - Priority 1 (Core Competitors): High Market Share + High Threat
- Priority 2 (Emerging Threats): Low Market Share + High Threat - Priority 2 (Emerging Threats): Low Market Share + High Threat
- Priority 3 (Established Players): High Market Share + Low Threat - Priority 3 (Established Players): High Market Share + Low Threat
- Priority 4 (Monitor Only): Low Market Share + Low Threat}} - Priority 4 (Monitor Only): Low Market Share + Low Threat}}
@@ -3277,8 +3278,8 @@ Create a single focused story following this structure:
#### User Story #### User Story
As a {{user type}}, As a {{user type}},
I want {{specific action/capability}}, I want {{specific action/capability}},
So that {{clear benefit/value}}. So that {{clear benefit/value}}.
#### Story Context #### Story Context
@@ -8099,7 +8100,7 @@ Generate a comprehensive validation report that adapts to project type:
After presenting the report, ask if the user wants: After presenting the report, ask if the user wants:
- Detailed analysis of any failed sections - Detailed analysis of any failed sections
- Specific story resequencing suggestions - Specific story reordering suggestions
- Risk mitigation strategies - Risk mitigation strategies
- [BROWNFIELD] Integration risk deep-dive]] - [BROWNFIELD] Integration risk deep-dive]]
@@ -8218,7 +8219,7 @@ workflow:
A[Start: Service Development] --> B{Service Complexity?} A[Start: Service Development] --> B{Service Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[architect: architecture.md] E --> F[architect: architecture.md]
F --> G{Architecture suggests PRD changes?} F --> G{Architecture suggests PRD changes?}
@@ -8229,15 +8230,15 @@ workflow:
J -->|Yes| K[Return to relevant agent for fixes] J -->|Yes| K[Return to relevant agent for fixes]
J -->|No| L[Move to IDE Environment] J -->|No| L[Move to IDE Environment]
K --> I K --> I
D --> M[pm: simple epic or story] D --> M[pm: simple epic or story]
M --> N[Move to IDE Environment] M --> N[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: technical research] F -.-> F1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style L fill:#90EE90 style L fill:#90EE90
style N fill:#90EE90 style N fill:#90EE90
style C fill:#FFE4B5 style C fill:#FFE4B5
@@ -8353,7 +8354,7 @@ workflow:
A[Start: Service Enhancement] --> B{Enhancement Complexity?} A[Start: Service Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing service] B -->|Complex/Significant| C[analyst: analyze existing service]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md] E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist] F --> G[po: validate with po-master-checklist]
@@ -8361,12 +8362,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes] H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment] H -->|No| J[Move to IDE Environment]
I --> G I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story] D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment] K --> M[Move to IDE Environment]
L --> M L --> M
style J fill:#90EE90 style J fill:#90EE90
style M fill:#90EE90 style M fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5

8
.bmad-core/workflows/brownfield-fullstack.yml
View File

@@ -2,7 +2,7 @@ workflow:
id: brownfield-fullstack id: brownfield-fullstack
name: Brownfield Full-Stack Enhancement name: Brownfield Full-Stack Enhancement
description: >- description: >-
Agent workflow for enhancing existing full-stack applications with new features, Agent workflow for enhancing existing full-stack applications with new features,
modernization, or significant changes. Handles existing system analysis and safe integration. modernization, or significant changes. Handles existing system analysis and safe integration.
type: brownfield type: brownfield
project_types: project_types:
@@ -70,7 +70,7 @@ workflow:
A[Start: Brownfield Enhancement] --> B{Enhancement Complexity?} A[Start: Brownfield Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing project] B -->|Complex/Significant| C[analyst: analyze existing project]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md] E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist] F --> G[po: validate with po-master-checklist]
@@ -78,12 +78,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes] H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment] H -->|No| J[Move to IDE Environment]
I --> G I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story] D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment] K --> M[Move to IDE Environment]
L --> M L --> M
style J fill:#90EE90 style J fill:#90EE90
style M fill:#90EE90 style M fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5

6
.bmad-core/workflows/brownfield-service.yml
View File

@@ -71,7 +71,7 @@ workflow:
A[Start: Service Enhancement] --> B{Enhancement Complexity?} A[Start: Service Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing service] B -->|Complex/Significant| C[analyst: analyze existing service]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md] E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist] F --> G[po: validate with po-master-checklist]
@@ -79,12 +79,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes] H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment] H -->|No| J[Move to IDE Environment]
I --> G I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story] D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment] K --> M[Move to IDE Environment]
L --> M L --> M
style J fill:#90EE90 style J fill:#90EE90
style M fill:#90EE90 style M fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5

6
.bmad-core/workflows/brownfield-ui.yml
View File

@@ -78,7 +78,7 @@ workflow:
A[Start: UI Enhancement] --> B{Enhancement Complexity?} A[Start: UI Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing UI] B -->|Complex/Significant| C[analyst: analyze existing UI]
B -->|Simple| D{1 Story or 2-3 Stories?} B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md] C --> E[pm: brownfield-prd.md]
E --> F[ux-expert: front-end-spec.md] E --> F[ux-expert: front-end-spec.md]
F --> G[architect: brownfield-architecture.md] F --> G[architect: brownfield-architecture.md]
@@ -87,12 +87,12 @@ workflow:
I -->|Yes| J[Return to relevant agent for fixes] I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K[Move to IDE Environment] I -->|No| K[Move to IDE Environment]
J --> H J --> H
D -->|1 Story| L[pm/po/sm: brownfield-create-story] D -->|1 Story| L[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| M[pm/po/sm: brownfield-create-epic] D -->|2-3 Stories| M[pm/po/sm: brownfield-create-epic]
L --> N[Move to IDE Environment] L --> N[Move to IDE Environment]
M --> N M --> N
style K fill:#90EE90 style K fill:#90EE90
style N fill:#90EE90 style N fill:#90EE90
style E fill:#FFE4B5 style E fill:#FFE4B5

8
.bmad-core/workflows/greenfield-fullstack.yml
View File

@@ -106,7 +106,7 @@ workflow:
A[Start: Greenfield Project] --> B{Project Complexity?} A[Start: Greenfield Project] --> B{Project Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md] E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?} F --> F2{Generate v0 prompt?}
@@ -122,16 +122,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes] K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment] K -->|No| M[Move to IDE Environment]
L --> J L --> J
D --> N[pm: simple epic or story] D --> N[pm: simple epic or story]
N --> O[Move to IDE Environment] N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research] F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research] G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style M fill:#90EE90 style M fill:#90EE90
style O fill:#90EE90 style O fill:#90EE90
style F3 fill:#E6E6FA style F3 fill:#E6E6FA

8
.bmad-core/workflows/greenfield-service.yml
View File

@@ -82,7 +82,7 @@ workflow:
A[Start: Service Development] --> B{Service Complexity?} A[Start: Service Development] --> B{Service Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[architect: architecture.md] E --> F[architect: architecture.md]
F --> G{Architecture suggests PRD changes?} F --> G{Architecture suggests PRD changes?}
@@ -93,15 +93,15 @@ workflow:
J -->|Yes| K[Return to relevant agent for fixes] J -->|Yes| K[Return to relevant agent for fixes]
J -->|No| L[Move to IDE Environment] J -->|No| L[Move to IDE Environment]
K --> I K --> I
D --> M[pm: simple epic or story] D --> M[pm: simple epic or story]
M --> N[Move to IDE Environment] M --> N[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: technical research] F -.-> F1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style L fill:#90EE90 style L fill:#90EE90
style N fill:#90EE90 style N fill:#90EE90
style C fill:#FFE4B5 style C fill:#FFE4B5

8
.bmad-core/workflows/greenfield-ui.yml
View File

@@ -101,7 +101,7 @@ workflow:
A[Start: UI Development] --> B{UI Complexity?} A[Start: UI Development] --> B{UI Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md] B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md] B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md] C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md] E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?} F --> F2{Generate v0 prompt?}
@@ -117,16 +117,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes] K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment] K -->|No| M[Move to IDE Environment]
L --> J L --> J
D --> N[ux-expert: simple wireframes] D --> N[ux-expert: simple wireframes]
N --> O[Move to IDE Environment] N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming] C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research] C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research] F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research] G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming] D -.-> D1[Optional: brainstorming]
style M fill:#90EE90 style M fill:#90EE90
style O fill:#90EE90 style O fill:#90EE90
style F3 fill:#E6E6FA style F3 fill:#E6E6FA

36
.vscode/settings.json vendored
View File

@@ -2,26 +2,42 @@
"cSpell.words": [ "cSpell.words": [
"agentic", "agentic",
"Axios", "Axios",
"biomimicry",
"BMAD", "BMAD",
"Brainwriting",
"Centricity", "Centricity",
"cicd",
"dataclass", "dataclass",
"docstrings", "docstrings",
"emergently", "emergently",
"explorative", "explorative",
"fintech",
"firmographic",
"firmographics",
"frontends", "frontends",
"gamedev",
"golint", "golint",
"Goroutines", "Goroutines",
"hotspots",
"HSTS", "HSTS",
"httpx", "httpx",
"Immer", "Immer",
"implementability", "implementability",
"Inclusivity", "Inclusivity",
"Luxon", "Luxon",
"MERN",
"mgmt",
"Nuxt",
"overcommitting",
"pasteable", "pasteable",
"pentest",
"PESTEL",
"Pino", "Pino",
"Polyrepo", "Polyrepo",
"psychographics",
"Pydantic", "Pydantic",
"pyproject", "pyproject",
"reqs",
"rescope", "rescope",
"roadmaps", "roadmaps",
"roleplay", "roleplay",
@@ -29,12 +45,28 @@
"Serilog", "Serilog",
"shadcn", "shadcn",
"structlog", "structlog",
"subfolders",
"Supabase",
"Systemization", "Systemization",
"taskroot", "taskroot",
"Testcontainers", "Testcontainers",
"tmpl", "tmpl",
"tmplv",
"touchpoints",
"trpc",
"Turborepo",
"Underserved",
"unredacted",
"VARCHAR", "VARCHAR",
"venv", "venv",
"WCAG" "vercel",
] "Vite",
"WCAG",
"wireframes"
],
"markdownlint.config": {
"MD033": {
"allowed_elements": ["br", "div", "img", "rule", "sub"]
}
}
} }

1
README.md
View File

@@ -241,4 +241,3 @@ Created by Brian (BMad) Madison
[![Contributors](https://contrib.rocks/image?repo=bmadcode/bmad-method)](https://github.com/bmadcode/bmad-method/graphs/contributors) [![Contributors](https://contrib.rocks/image?repo=bmadcode/bmad-method)](https://github.com/bmadcode/bmad-method/graphs/contributors)
<sub>Built with ❤️ for the AI-assisted development community</sub> <sub>Built with ❤️ for the AI-assisted development community</sub>