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

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:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
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`)
@@ -159,13 +159,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
5. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted?
- **C**ombine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered?
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
- **M** = Modify/Magnify: What can be emphasized or reduced?
- **P** = Put to other uses: What else could this be used for?
- **E** = Eliminate: What can be removed or simplified?
- **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats**
[[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**
[[LLM: Create text-based mind maps with clear hierarchical structure.]]
```
```text
Central Concept
├── Branch 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 ====================
# 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:
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
{{If applicable, summarize key findings from:
- Market research
- Competitive analysis
- Competitive analysis
- User interviews
- Technical feasibility studies}}
@@ -1258,7 +1259,7 @@ These replace the standard elicitation options when working on market research d
{{Create a 2x2 matrix:
- 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 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:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
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`)

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.
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:
- Look for the corresponding START/END tags
- 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**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted?
- **C**ombine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered?
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
- **M** = Modify/Magnify: What can be emphasized or reduced?
- **P** = Put to other uses: What else could this be used for?
- **E** = Eliminate: What can be removed or simplified?
- **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats**
[[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
As a {{user type}},
I want {{specific action/capability}},
As a {{user type}},
I want {{specific action/capability}},
So that {{clear benefit/value}}.
#### Story Context
@@ -1829,7 +1830,7 @@ Analyze where this IDE agent fits in workflows:
4. **Document recommendations**:
```markdown
## Workflow Integration
This agent enhances the following workflows:
- `greenfield-service`: API design phase (between architecture and implementation)
- `brownfield-service`: API refactoring and modernization
@@ -1849,7 +1850,7 @@ Consider which teams benefit from this IDE agent:
3. **Document integration**:
```markdown
## Team Integration
Recommended teams for this agent:
- `team-fullstack`: Provides specialized {domain} expertise
- `team-no-ui`: Enhances backend {capability}
@@ -2331,7 +2332,7 @@ workflows:
Before finalizing, verify:
1. **Role Coverage**: Does the team have all necessary skills for its workflows?
2. **Size Optimization**:
2. **Size Optimization**:
- Minimum: 2 agents (bmad + 1)
- Recommended: 3-7 agents
- Maximum with wildcard: bmad + "*"
@@ -2362,8 +2363,8 @@ Document how this team integrates with existing system:
bundle:
name: "Team API"
description: >-
Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI
Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI
components. Ideal for microservices, REST APIs, and backend systems.
agents:
@@ -2385,8 +2386,8 @@ workflows:
bundle:
name: "Team Prototype"
description: >-
Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations
Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations
on new ideas and experimental features.
agents:
@@ -4613,7 +4614,7 @@ so that {{benefit}}.
{{Create a 2x2 matrix:
- 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 4 (Monitor Only): Low Market Share + Low Threat}}
@@ -6963,7 +6964,7 @@ so that {{benefit}}.
==================== START: templates#project-brief-tmpl ====================
# 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:
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
{{If applicable, summarize key findings from:
- Market research
- Competitive analysis
- Competitive analysis
- User interviews
- 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:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
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`)
@@ -8677,7 +8678,7 @@ Generate a comprehensive validation report that adapts to project type:
After presenting the report, ask if the user wants:
- Detailed analysis of any failed sections
- Specific story resequencing suggestions
- Specific story reordering suggestions
- Risk mitigation strategies
- [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.
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:
- Look for the corresponding START/END tags
- 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**:
```markdown
## Workflow Integration
This agent enhances the following workflows:
- `greenfield-service`: API design phase (between architecture and implementation)
- `brownfield-service`: API refactoring and modernization
@@ -774,7 +775,7 @@ Consider which teams benefit from this IDE agent:
3. **Document integration**:
```markdown
## Team Integration
Recommended teams for this agent:
- `team-fullstack`: Provides specialized {domain} expertise
- `team-no-ui`: Enhances backend {capability}
@@ -1047,7 +1048,7 @@ workflows:
Before finalizing, verify:
1. **Role Coverage**: Does the team have all necessary skills for its workflows?
2. **Size Optimization**:
2. **Size Optimization**:
- Minimum: 2 agents (bmad + 1)
- Recommended: 3-7 agents
- Maximum with wildcard: bmad + "*"
@@ -1078,8 +1079,8 @@ Document how this team integrates with existing system:
bundle:
name: "Team API"
description: >-
Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI
Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI
components. Ideal for microservices, REST APIs, and backend systems.
agents:
@@ -1101,8 +1102,8 @@ workflows:
bundle:
name: "Team Prototype"
description: >-
Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations
Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations
on new ideas and experimental features.
agents:
@@ -2101,13 +2102,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
5. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted?
- **C**ombine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered?
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
- **M** = Modify/Magnify: What can be emphasized or reduced?
- **P** = Put to other uses: What else could this be used for?
- **E** = Eliminate: What can be removed or simplified?
- **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats**
[[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 ====================
# 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:
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
{{If applicable, summarize key findings from:
- Market research
- Competitive analysis
- Competitive analysis
- User interviews
- Technical feasibility studies}}
@@ -3028,7 +3029,7 @@ These replace the standard elicitation options when working on market research d
{{Create a 2x2 matrix:
- 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 4 (Monitor Only): Low Market Share + Low Threat}}
@@ -6704,8 +6705,8 @@ Create a single focused story following this structure:
#### User Story
As a {{user type}},
I want {{specific action/capability}},
As a {{user type}},
I want {{specific action/capability}},
So that {{clear benefit/value}}.
#### 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:
- Detailed analysis of any failed sections
- Specific story resequencing suggestions
- Specific story reordering suggestions
- Risk mitigation strategies
- [BROWNFIELD] Integration risk deep-dive]]
@@ -9337,7 +9338,7 @@ workflow:
id: brownfield-fullstack
name: Brownfield Full-Stack Enhancement
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.
type: brownfield
project_types:
@@ -9405,7 +9406,7 @@ workflow:
A[Start: Brownfield Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing project]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist]
@@ -9413,12 +9414,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment]
I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment]
L --> M
style J fill:#90EE90
style M fill:#90EE90
style E fill:#FFE4B5
@@ -9525,7 +9526,7 @@ workflow:
A[Start: Service Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing service]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist]
@@ -9533,12 +9534,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment]
I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment]
L --> M
style J fill:#90EE90
style M fill:#90EE90
style E fill:#FFE4B5
@@ -9652,7 +9653,7 @@ workflow:
A[Start: UI Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing UI]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[ux-expert: front-end-spec.md]
F --> G[architect: brownfield-architecture.md]
@@ -9661,12 +9662,12 @@ workflow:
I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K[Move to IDE Environment]
J --> H
D -->|1 Story| L[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| M[pm/po/sm: brownfield-create-epic]
L --> N[Move to IDE Environment]
M --> N
style K fill:#90EE90
style N fill:#90EE90
style E fill:#FFE4B5
@@ -9810,7 +9811,7 @@ workflow:
A[Start: Greenfield Project] --> B{Project Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?}
@@ -9826,16 +9827,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment]
L --> J
D --> N[pm: simple epic or story]
N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style M fill:#90EE90
style O fill:#90EE90
style F3 fill:#E6E6FA
@@ -9966,7 +9967,7 @@ workflow:
A[Start: Service Development] --> B{Service Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md]
E --> F[architect: architecture.md]
F --> G{Architecture suggests PRD changes?}
@@ -9977,15 +9978,15 @@ workflow:
J -->|Yes| K[Return to relevant agent for fixes]
J -->|No| L[Move to IDE Environment]
K --> I
D --> M[pm: simple epic or story]
M --> N[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style L fill:#90EE90
style N fill:#90EE90
style C fill:#FFE4B5
@@ -10131,7 +10132,7 @@ workflow:
A[Start: UI Development] --> B{UI Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?}
@@ -10147,16 +10148,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment]
L --> J
D --> N[ux-expert: simple wireframes]
N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style M fill:#90EE90
style O fill:#90EE90
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.
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:
- Look for the corresponding START/END tags
- 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:
name: Team Fullstack
description: >-
Comprehensive full-stack development team capable of handling both greenfield
application development and brownfield enhancement projects. This team combines
strategic planning, user experience design, and holistic system architecture
to deliver complete solutions from concept to deployment. Specializes in
full-stack applications, SaaS platforms, enterprise apps, feature additions,
Comprehensive full-stack development team capable of handling both greenfield
application development and brownfield enhancement projects. This team combines
strategic planning, user experience design, and holistic system architecture
to deliver complete solutions from concept to deployment. Specializes in
full-stack applications, SaaS platforms, enterprise apps, feature additions,
refactoring, and system modernization.
agents:
@@ -580,7 +581,7 @@ Analyze where this IDE agent fits in workflows:
4. **Document recommendations**:
```markdown
## Workflow Integration
This agent enhances the following workflows:
- `greenfield-service`: API design phase (between architecture and implementation)
- `brownfield-service`: API refactoring and modernization
@@ -600,7 +601,7 @@ Consider which teams benefit from this IDE agent:
3. **Document integration**:
```markdown
## Team Integration
Recommended teams for this agent:
- `team-fullstack`: Provides specialized {domain} expertise
- `team-no-ui`: Enhances backend {capability}
@@ -873,7 +874,7 @@ workflows:
Before finalizing, verify:
1. **Role Coverage**: Does the team have all necessary skills for its workflows?
2. **Size Optimization**:
2. **Size Optimization**:
- Minimum: 2 agents (bmad + 1)
- Recommended: 3-7 agents
- Maximum with wildcard: bmad + "*"
@@ -904,8 +905,8 @@ Document how this team integrates with existing system:
bundle:
name: "Team API"
description: >-
Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI
Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI
components. Ideal for microservices, REST APIs, and backend systems.
agents:
@@ -927,8 +928,8 @@ workflows:
bundle:
name: "Team Prototype"
description: >-
Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations
Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations
on new ideas and experimental features.
agents:
@@ -1927,13 +1928,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
5. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted?
- **C**ombine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered?
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
- **M** = Modify/Magnify: What can be emphasized or reduced?
- **P** = Put to other uses: What else could this be used for?
- **E** = Eliminate: What can be removed or simplified?
- **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats**
[[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 ====================
# 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:
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
{{If applicable, summarize key findings from:
- Market research
- Competitive analysis
- Competitive analysis
- User interviews
- Technical feasibility studies}}
@@ -2854,7 +2855,7 @@ These replace the standard elicitation options when working on market research d
{{Create a 2x2 matrix:
- 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 4 (Monitor Only): Low Market Share + Low Threat}}
@@ -3355,8 +3356,8 @@ Create a single focused story following this structure:
#### User Story
As a {{user type}},
I want {{specific action/capability}},
As a {{user type}},
I want {{specific action/capability}},
So that {{clear benefit/value}}.
#### 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:
- Detailed analysis of any failed sections
- Specific story resequencing suggestions
- Specific story reordering suggestions
- Risk mitigation strategies
- [BROWNFIELD] Integration risk deep-dive]]
@@ -8691,7 +8692,7 @@ workflow:
id: brownfield-fullstack
name: Brownfield Full-Stack Enhancement
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.
type: brownfield
project_types:
@@ -8759,7 +8760,7 @@ workflow:
A[Start: Brownfield Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing project]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist]
@@ -8767,12 +8768,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment]
I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment]
L --> M
style J fill:#90EE90
style M fill:#90EE90
style E fill:#FFE4B5
@@ -8879,7 +8880,7 @@ workflow:
A[Start: Service Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing service]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist]
@@ -8887,12 +8888,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment]
I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment]
L --> M
style J fill:#90EE90
style M fill:#90EE90
style E fill:#FFE4B5
@@ -9006,7 +9007,7 @@ workflow:
A[Start: UI Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing UI]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[ux-expert: front-end-spec.md]
F --> G[architect: brownfield-architecture.md]
@@ -9015,12 +9016,12 @@ workflow:
I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K[Move to IDE Environment]
J --> H
D -->|1 Story| L[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| M[pm/po/sm: brownfield-create-epic]
L --> N[Move to IDE Environment]
M --> N
style K fill:#90EE90
style N fill:#90EE90
style E fill:#FFE4B5
@@ -9164,7 +9165,7 @@ workflow:
A[Start: Greenfield Project] --> B{Project Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?}
@@ -9180,16 +9181,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment]
L --> J
D --> N[pm: simple epic or story]
N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style M fill:#90EE90
style O fill:#90EE90
style F3 fill:#E6E6FA
@@ -9320,7 +9321,7 @@ workflow:
A[Start: Service Development] --> B{Service Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md]
E --> F[architect: architecture.md]
F --> G{Architecture suggests PRD changes?}
@@ -9331,15 +9332,15 @@ workflow:
J -->|Yes| K[Return to relevant agent for fixes]
J -->|No| L[Move to IDE Environment]
K --> I
D --> M[pm: simple epic or story]
M --> N[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style L fill:#90EE90
style N fill:#90EE90
style C fill:#FFE4B5
@@ -9485,7 +9486,7 @@ workflow:
A[Start: UI Development] --> B{UI Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?}
@@ -9501,16 +9502,16 @@ workflow:
K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment]
L --> J
D --> N[ux-expert: simple wireframes]
N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style M fill:#90EE90
style O fill:#90EE90
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.
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:
- Look for the corresponding START/END tags
- 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**:
```markdown
## Workflow Integration
This agent enhances the following workflows:
- `greenfield-service`: API design phase (between architecture and implementation)
- `brownfield-service`: API refactoring and modernization
@@ -522,7 +523,7 @@ Consider which teams benefit from this IDE agent:
3. **Document integration**:
```markdown
## Team Integration
Recommended teams for this agent:
- `team-fullstack`: Provides specialized {domain} expertise
- `team-no-ui`: Enhances backend {capability}
@@ -795,7 +796,7 @@ workflows:
Before finalizing, verify:
1. **Role Coverage**: Does the team have all necessary skills for its workflows?
2. **Size Optimization**:
2. **Size Optimization**:
- Minimum: 2 agents (bmad + 1)
- Recommended: 3-7 agents
- Maximum with wildcard: bmad + "*"
@@ -826,8 +827,8 @@ Document how this team integrates with existing system:
bundle:
name: "Team API"
description: >-
Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI
Specialized team for API and backend service development. Focuses on
robust service architecture, implementation, and testing without UI
components. Ideal for microservices, REST APIs, and backend systems.
agents:
@@ -849,8 +850,8 @@ workflows:
bundle:
name: "Team Prototype"
description: >-
Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations
Agile team for rapid prototyping and proof of concept development.
Combines planning, design, and implementation for quick iterations
on new ideas and experimental features.
agents:
@@ -1849,13 +1850,13 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
5. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S**ubstitute: What can be substituted?
- **C**ombine: What can be combined or integrated?
- **A**dapt: What can be adapted from elsewhere?
- **M**odify/Magnify: What can be emphasized or reduced?
- **P**ut to other uses: What else could this be used for?
- **E**liminate: What can be removed or simplified?
- **R**everse/Rearrange: What can be reversed or reordered?
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
- **M** = Modify/Magnify: What can be emphasized or reduced?
- **P** = Put to other uses: What else could this be used for?
- **E** = Eliminate: What can be removed or simplified?
- **R** = Reverse/Rearrange: What can be reversed or reordered?
6. **Six Thinking Hats**
[[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 ====================
# 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:
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
{{If applicable, summarize key findings from:
- Market research
- Competitive analysis
- Competitive analysis
- User interviews
- Technical feasibility studies}}
@@ -2776,7 +2777,7 @@ These replace the standard elicitation options when working on market research d
{{Create a 2x2 matrix:
- 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 4 (Monitor Only): Low Market Share + Low Threat}}
@@ -3277,8 +3278,8 @@ Create a single focused story following this structure:
#### User Story
As a {{user type}},
I want {{specific action/capability}},
As a {{user type}},
I want {{specific action/capability}},
So that {{clear benefit/value}}.
#### 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:
- Detailed analysis of any failed sections
- Specific story resequencing suggestions
- Specific story reordering suggestions
- Risk mitigation strategies
- [BROWNFIELD] Integration risk deep-dive]]
@@ -8218,7 +8219,7 @@ workflow:
A[Start: Service Development] --> B{Service Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
C --> E[pm: prd.md]
E --> F[architect: architecture.md]
F --> G{Architecture suggests PRD changes?}
@@ -8229,15 +8230,15 @@ workflow:
J -->|Yes| K[Return to relevant agent for fixes]
J -->|No| L[Move to IDE Environment]
K --> I
D --> M[pm: simple epic or story]
M --> N[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style L fill:#90EE90
style N fill:#90EE90
style C fill:#FFE4B5
@@ -8353,7 +8354,7 @@ workflow:
A[Start: Service Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing service]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with po-master-checklist]
@@ -8361,12 +8362,12 @@ workflow:
H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment]
I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment]
L --> M
style J fill:#90EE90
style M fill:#90EE90
style E fill:#FFE4B5