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

formatter updates

Browse Source
This commit is contained in:
Brian Madison
2025-06-14 18:11:16 -05:00
parent 2cbbf61d92
commit fcbfc608f1
37 changed files with 2244 additions and 794 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
.bmad-core/agents/po.md
View File

@@ -4,25 +4,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
agent:
name: Sarah
id: po
title: Product Owner
icon: 📝
whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
customization:
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
customization: null
persona:
role: Technical Product Owner & Process Steward
style: Meticulous, analytical, detail-oriented, systematic, collaborative
identity: Product Owner who validates artifacts cohesion and coaches significant changes
focus: Plan integrity, documentation quality, actionable development tasks, process adherence
core_principles:
- Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
- Clarity & Actionability for Development - Make requirements unambiguous and testable
@@ -34,21 +31,18 @@ persona:
- User Collaboration for Validation - Seek input at critical checkpoints
- Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
- Documentation Ecosystem Integrity - Maintain consistency across all documents
startup:
- Greet the user with your name and role, and inform of the *help command.
commands:
- "*help" - Show: numbered list of the following commands to allow selection
- "*chat-mode" - (Default) Product Owner consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)
- "*shard-doc {document}" - Break down document into actionable parts
- "*correct-course" - Analyze and suggest project course corrections
- "*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)
- "*create-story" - Create user story from requirements (task brownfield-create-story)
- "*exit" - Say Goodbye, You are no longer this Agent
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
- '*shard-doc {document}" - Break down document into actionable parts'
- '*correct-course" - Analyze and suggest project course corrections'
- '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
- '*create-story" - Create user story from requirements (task brownfield-create-story)'
- '*exit" - Say Goodbye, You are no longer this Agent'
dependencies:
tasks:
- execute-checklist

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

@@ -403,28 +403,33 @@ Ask the user if they want to work through the checklist:
Now that you've completed the checklist, generate a comprehensive validation report that includes:
1. Executive Summary
- Overall architecture readiness (High/Medium/Low)
- Critical risks identified
- Key strengths of the architecture
- Project type (Full-stack/Frontend/Backend) and sections evaluated
2. Section Analysis
- Pass rate for each major section (percentage of items passed)
- Most concerning failures or gaps
- Sections requiring immediate attention
- Note any sections skipped due to project type
3. Risk Assessment
- Top 5 risks by severity
- Mitigation recommendations for each
- Timeline impact of addressing issues
4. Recommendations
- Must-fix items before development
- Should-fix items for better quality
- Nice-to-have improvements
5. AI Implementation Readiness
- Specific concerns for AI agent implementation
- Areas needing additional clarification
- Complexity hotspots to address

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

@@ -9,6 +9,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
1. **Establish Context**
- Understand the problem space or opportunity area
- Identify any constraints or parameters
- Determine session goals (divergent exploration vs. focused ideation)
@@ -25,6 +26,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"What If" Scenarios**
[[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
- What if we had unlimited resources?
- What if this problem didn't exist?
- What if we approached this from a child's perspective?
@@ -32,6 +34,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Analogical Thinking**
[[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
- "How might this work like [X] but for [Y]?"
- Nature-inspired solutions (biomimicry)
- Cross-industry pattern matching
@@ -39,6 +42,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
3. **Reversal/Inversion**
[[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
- What if we did the exact opposite?
- How could we make this problem worse? (then reverse)
- Start from the end goal and work backward
@@ -55,6 +59,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
@@ -65,6 +70,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]]
- White Hat: Facts and information
- Red Hat: Emotions and intuition
- Black Hat: Caution and critical thinking
@@ -91,6 +97,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"Yes, And..." Building**
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
- Accept the premise of each idea
- Add to it with "Yes, and..."
- Build chains of connected ideas
@@ -98,40 +105,43 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Brainwriting/Round Robin**
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
- Generate ideas from stakeholder perspectives
- Build on previous ideas in rounds
- Combine unrelated ideas
- Cross-pollinate concepts
3. **Random Stimulation**
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
#### Deep Exploration Techniques
1. **Five Whys**
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
2. **Morphological Analysis**
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
3. **Provocation Technique (PO)**
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
### 3. Technique Selection Guide
@@ -172,16 +182,19 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
1. **Warm-up Phase** (5-10 min)
- Start with accessible techniques
- Build creative confidence
- Establish "no judgment" atmosphere
2. **Divergent Phase** (20-30 min)
- Use expansion techniques
- Generate quantity over quality
- Encourage wild ideas
3. **Convergent Phase** (15-20 min)
- Group and categorize ideas
- Identify patterns and themes
- Select promising directions

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

@@ -189,53 +189,65 @@ Present these numbered options to the user:
```markdown
## Research Objective
[Clear statement of what this research aims to achieve]
## Background Context
[Relevant information from project brief, brainstorming, or other inputs]
## Research Questions
### Primary Questions (Must Answer)
1. [Specific, actionable question]
2. [Specific, actionable question]
...
...
### Secondary Questions (Nice to Have)
1. [Supporting question]
2. [Supporting question]
...
...
## Research Methodology
### Information Sources
- [Specific source types and priorities]
### Analysis Frameworks
- [Specific frameworks to apply]
### Data Requirements
- [Quality, recency, credibility needs]
## Expected Deliverables
### Executive Summary
- Key findings and insights
- Critical implications
- Recommended actions
### Detailed Analysis
[Specific sections needed based on research type]
### Supporting Materials
- Data tables
- Comparison matrices
- Source documentation
## Success Criteria
[How to evaluate if research achieved its objectives]
## Timeline and Priority
[If applicable, any time constraints or phasing]
```

20
.bmad-core/tasks/doc-migration-task.md
View File

@@ -39,19 +39,23 @@ Migrate BMAD-METHOD documents to match V4 template structure exactly, preserving
### Content Migration Process
1. **Read Template Structure**
- Extract all Level 2 headings from the V4 template
- These are the ONLY Level 2 headings allowed in the final document
2. **Analyze Original Document**
- Identify all content blocks
- Note original section organization
- Flag any custom sections
3. **Create Backup First**
- Rename original file: `mv filename.md filename.md.bak`
- This preserves the original completely
4. **Create New File**
- Create new `filename.md` from scratch
- Start with template structure (all Level 2 headings)
- For each content block from original:
@@ -72,23 +76,37 @@ Migrate BMAD-METHOD documents to match V4 template structure exactly, preserving
```markdown
Original (prd.md):
## Executive Summary
[content...]
## Custom Feature Section
## Custom Feature Section
[content...]
## Table of Contents
[toc...]
Template (prd-tmpl.md):
## Goals and Background Context
## Functional Requirements
## Success Metrics and KPIs
Result (prd.md):
## Goals and Background Context
[executive summary content moved here]
### Custom Feature Section
[content preserved but demoted to Level 3]
## Functional Requirements
## Success Metrics and KPIs

72
.bmad-core/tasks/generate-ai-frontend-prompt.md
View File

@@ -15,44 +15,44 @@ To generate a masterful, comprehensive, and optimized prompt that can be used wi
1. **Confirm Target AI Generation Platform:**
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
2. **Synthesize Inputs into a Structured Prompt:**
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
3. **Present and Refine the Master Prompt:**
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>

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

@@ -88,7 +88,7 @@ Documents within the `another-folder/` directory:
### [Nested Document](./another-folder/document.md)
Description of nested document.
```
```text
### Index Entry Format
@@ -156,6 +156,7 @@ For each file referenced in the index but not found in the filesystem:
### Special Cases
1. **Sharded Documents**: If a folder contains an `index.md` file, treat it as a sharded document:
- Use the folder's `index.md` title as the section title
- List the folder's documents as subsections
- Note in the description that this is a multi-part document

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

@@ -118,6 +118,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
1. **Establish Context**
- Understand the problem space or opportunity area
- Identify any constraints or parameters
- Determine session goals (divergent exploration vs. focused ideation)
@@ -134,6 +135,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"What If" Scenarios**
[[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
- What if we had unlimited resources?
- What if this problem didn't exist?
- What if we approached this from a child's perspective?
@@ -141,6 +143,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Analogical Thinking**
[[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
- "How might this work like [X] but for [Y]?"
- Nature-inspired solutions (biomimicry)
- Cross-industry pattern matching
@@ -148,6 +151,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
3. **Reversal/Inversion**
[[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
- What if we did the exact opposite?
- How could we make this problem worse? (then reverse)
- Start from the end goal and work backward
@@ -164,6 +168,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
@@ -174,6 +179,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]]
- White Hat: Facts and information
- Red Hat: Emotions and intuition
- Black Hat: Caution and critical thinking
@@ -200,6 +206,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"Yes, And..." Building**
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
- Accept the premise of each idea
- Add to it with "Yes, and..."
- Build chains of connected ideas
@@ -207,40 +214,43 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Brainwriting/Round Robin**
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
- Generate ideas from stakeholder perspectives
- Build on previous ideas in rounds
- Combine unrelated ideas
- Cross-pollinate concepts
3. **Random Stimulation**
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
#### Deep Exploration Techniques
1. **Five Whys**
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
2. **Morphological Analysis**
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
3. **Provocation Technique (PO)**
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
### 3. Technique Selection Guide
@@ -281,16 +291,19 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
1. **Warm-up Phase** (5-10 min)
- Start with accessible techniques
- Build creative confidence
- Establish "no judgment" atmosphere
2. **Divergent Phase** (20-30 min)
- Use expansion techniques
- Generate quantity over quality
- Encourage wild ideas
3. **Convergent Phase** (15-20 min)
- Group and categorize ideas
- Identify patterns and themes
- Select promising directions
@@ -526,53 +539,65 @@ Present these numbered options to the user:
```markdown
## Research Objective
[Clear statement of what this research aims to achieve]
## Background Context
[Relevant information from project brief, brainstorming, or other inputs]
## Research Questions
### Primary Questions (Must Answer)
1. [Specific, actionable question]
2. [Specific, actionable question]
...
...
### Secondary Questions (Nice to Have)
1. [Supporting question]
2. [Supporting question]
...
...
## Research Methodology
### Information Sources
- [Specific source types and priorities]
### Analysis Frameworks
- [Specific frameworks to apply]
### Data Requirements
- [Quality, recency, credibility needs]
## Expected Deliverables
### Executive Summary
- Key findings and insights
- Critical implications
- Recommended actions
### Detailed Analysis
[Specific sections needed based on research type]
### Supporting Materials
- Data tables
- Comparison matrices
- Source documentation
## Success Criteria
[How to evaluate if research achieved its objectives]
## Timeline and Priority
[If applicable, any time constraints or phasing]
```

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

@@ -476,53 +476,65 @@ Present these numbered options to the user:
```markdown
## Research Objective
[Clear statement of what this research aims to achieve]
## Background Context
[Relevant information from project brief, brainstorming, or other inputs]
## Research Questions
### Primary Questions (Must Answer)
1. [Specific, actionable question]
2. [Specific, actionable question]
...
...
### Secondary Questions (Nice to Have)
1. [Supporting question]
2. [Supporting question]
...
...
## Research Methodology
### Information Sources
- [Specific source types and priorities]
### Analysis Frameworks
- [Specific frameworks to apply]
### Data Requirements
- [Quality, recency, credibility needs]
## Expected Deliverables
### Executive Summary
- Key findings and insights
- Critical implications
- Recommended actions
### Detailed Analysis
[Specific sections needed based on research type]
### Supporting Materials
- Data tables
- Comparison matrices
- Source documentation
## Success Criteria
[How to evaluate if research achieved its objectives]
## Timeline and Priority
[If applicable, any time constraints or phasing]
```
@@ -3514,28 +3526,33 @@ Ask the user if they want to work through the checklist:
Now that you've completed the checklist, generate a comprehensive validation report that includes:
1. Executive Summary
- Overall architecture readiness (High/Medium/Low)
- Critical risks identified
- Key strengths of the architecture
- Project type (Full-stack/Frontend/Backend) and sections evaluated
2. Section Analysis
- Pass rate for each major section (percentage of items passed)
- Most concerning failures or gaps
- Sections requiring immediate attention
- Note any sections skipped due to project type
3. Risk Assessment
- Top 5 risks by severity
- Mitigation recommendations for each
- Timeline impact of addressing issues
4. Recommendations
- Must-fix items before development
- Should-fix items for better quality
- Nice-to-have improvements
5. AI Implementation Readiness
- Specific concerns for AI agent implementation
- Areas needing additional clarification
- Complexity hotspots to address

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

@@ -255,6 +255,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
1. **Establish Context**
- Understand the problem space or opportunity area
- Identify any constraints or parameters
- Determine session goals (divergent exploration vs. focused ideation)
@@ -271,6 +272,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"What If" Scenarios**
[[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
- What if we had unlimited resources?
- What if this problem didn't exist?
- What if we approached this from a child's perspective?
@@ -278,6 +280,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Analogical Thinking**
[[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
- "How might this work like [X] but for [Y]?"
- Nature-inspired solutions (biomimicry)
- Cross-industry pattern matching
@@ -285,6 +288,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
3. **Reversal/Inversion**
[[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
- What if we did the exact opposite?
- How could we make this problem worse? (then reverse)
- Start from the end goal and work backward
@@ -301,6 +305,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
@@ -311,6 +316,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]]
- White Hat: Facts and information
- Red Hat: Emotions and intuition
- Black Hat: Caution and critical thinking
@@ -337,6 +343,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"Yes, And..." Building**
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
- Accept the premise of each idea
- Add to it with "Yes, and..."
- Build chains of connected ideas
@@ -344,40 +351,43 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Brainwriting/Round Robin**
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
- Generate ideas from stakeholder perspectives
- Build on previous ideas in rounds
- Combine unrelated ideas
- Cross-pollinate concepts
3. **Random Stimulation**
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
#### Deep Exploration Techniques
1. **Five Whys**
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
2. **Morphological Analysis**
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
3. **Provocation Technique (PO)**
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
### 3. Technique Selection Guide
@@ -418,16 +428,19 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
1. **Warm-up Phase** (5-10 min)
- Start with accessible techniques
- Build creative confidence
- Establish "no judgment" atmosphere
2. **Divergent Phase** (20-30 min)
- Use expansion techniques
- Generate quantity over quality
- Encourage wild ideas
3. **Convergent Phase** (15-20 min)
- Group and categorize ideas
- Identify patterns and themes
- Select promising directions
@@ -1129,53 +1142,65 @@ Present these numbered options to the user:
```markdown
## Research Objective
[Clear statement of what this research aims to achieve]
## Background Context
[Relevant information from project brief, brainstorming, or other inputs]
## Research Questions
### Primary Questions (Must Answer)
1. [Specific, actionable question]
2. [Specific, actionable question]
...
...
### Secondary Questions (Nice to Have)
1. [Supporting question]
2. [Supporting question]
...
...
## Research Methodology
### Information Sources
- [Specific source types and priorities]
### Analysis Frameworks
- [Specific frameworks to apply]
### Data Requirements
- [Quality, recency, credibility needs]
## Expected Deliverables
### Executive Summary
- Key findings and insights
- Critical implications
- Recommended actions
### Detailed Analysis
[Specific sections needed based on research type]
### Supporting Materials
- Data tables
- Comparison matrices
- Source documentation
## Success Criteria
[How to evaluate if research achieved its objectives]
## Timeline and Priority
[If applicable, any time constraints or phasing]
```
@@ -2498,47 +2523,47 @@ To generate a masterful, comprehensive, and optimized prompt that can be used wi
1. **Confirm Target AI Generation Platform:**
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
2. **Synthesize Inputs into a Structured Prompt:**
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
3. **Present and Refine the Master Prompt:**
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>
==================== END: tasks#generate-ai-frontend-prompt ====================
==================== START: tasks#index-docs ====================
@@ -2700,6 +2725,7 @@ For each file referenced in the index but not found in the filesystem:
### Special Cases
1. **Sharded Documents**: If a folder contains an `index.md` file, treat it as a sharded document:
- Use the folder's `index.md` title as the section title
- List the folder's documents as subsections
- Note in the description that this is a multi-part document
@@ -7743,28 +7769,33 @@ Ask the user if they want to work through the checklist:
Now that you've completed the checklist, generate a comprehensive validation report that includes:
1. Executive Summary
- Overall architecture readiness (High/Medium/Low)
- Critical risks identified
- Key strengths of the architecture
- Project type (Full-stack/Frontend/Backend) and sections evaluated
2. Section Analysis
- Pass rate for each major section (percentage of items passed)
- Most concerning failures or gaps
- Sections requiring immediate attention
- Note any sections skipped due to project type
3. Risk Assessment
- Top 5 risks by severity
- Mitigation recommendations for each
- Timeline impact of addressing issues
4. Recommendations
- Must-fix items before development
- Should-fix items for better quality
- Nice-to-have improvements
5. AI Implementation Readiness
- Specific concerns for AI agent implementation
- Areas needing additional clarification
- Complexity hotspots to address

16
.bmad-core/web-bundles/agents/pm.txt
View File

@@ -450,53 +450,65 @@ Present these numbered options to the user:
```markdown
## Research Objective
[Clear statement of what this research aims to achieve]
## Background Context
[Relevant information from project brief, brainstorming, or other inputs]
## Research Questions
### Primary Questions (Must Answer)
1. [Specific, actionable question]
2. [Specific, actionable question]
...
...
### Secondary Questions (Nice to Have)
1. [Supporting question]
2. [Supporting question]
...
...
## Research Methodology
### Information Sources
- [Specific source types and priorities]
### Analysis Frameworks
- [Specific frameworks to apply]
### Data Requirements
- [Quality, recency, credibility needs]
## Expected Deliverables
### Executive Summary
- Key findings and insights
- Critical implications
- Recommended actions
### Detailed Analysis
[Specific sections needed based on research type]
### Supporting Materials
- Data tables
- Comparison matrices
- Source documentation
## Success Criteria
[How to evaluate if research achieved its objectives]
## Timeline and Priority
[If applicable, any time constraints or phasing]
```

36
.bmad-core/web-bundles/agents/po.txt
View File

@@ -45,25 +45,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
agent:
name: Sarah
id: po
title: Product Owner
icon: 📝
whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
customization:
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
customization: null
persona:
role: Technical Product Owner & Process Steward
style: Meticulous, analytical, detail-oriented, systematic, collaborative
identity: Product Owner who validates artifacts cohesion and coaches significant changes
focus: Plan integrity, documentation quality, actionable development tasks, process adherence
core_principles:
- Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
- Clarity & Actionability for Development - Make requirements unambiguous and testable
@@ -75,21 +72,18 @@ persona:
- User Collaboration for Validation - Seek input at critical checkpoints
- Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
- Documentation Ecosystem Integrity - Maintain consistency across all documents
startup:
- Greet the user with your name and role, and inform of the *help command.
commands:
- "*help" - Show: numbered list of the following commands to allow selection
- "*chat-mode" - (Default) Product Owner consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)
- "*shard-doc {document}" - Break down document into actionable parts
- "*correct-course" - Analyze and suggest project course corrections
- "*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)
- "*create-story" - Create user story from requirements (task brownfield-create-story)
- "*exit" - Say Goodbye, You are no longer this Agent
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
- '*shard-doc {document}" - Break down document into actionable parts'
- '*correct-course" - Analyze and suggest project course corrections'
- '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
- '*create-story" - Create user story from requirements (task brownfield-create-story)'
- '*exit" - Say Goodbye, You are no longer this Agent'
dependencies:
tasks:
- execute-checklist

88
.bmad-core/web-bundles/agents/ux-expert.txt
View File

@@ -125,47 +125,47 @@ To generate a masterful, comprehensive, and optimized prompt that can be used wi
1. **Confirm Target AI Generation Platform:**
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
2. **Synthesize Inputs into a Structured Prompt:**
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
3. **Present and Refine the Master Prompt:**
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>
==================== END: tasks#generate-ai-frontend-prompt ====================
==================== START: tasks#create-deep-research-prompt ====================
@@ -360,53 +360,65 @@ Present these numbered options to the user:
```markdown
## Research Objective
[Clear statement of what this research aims to achieve]
## Background Context
[Relevant information from project brief, brainstorming, or other inputs]
## Research Questions
### Primary Questions (Must Answer)
1. [Specific, actionable question]
2. [Specific, actionable question]
...
...
### Secondary Questions (Nice to Have)
1. [Supporting question]
2. [Supporting question]
...
...
## Research Methodology
### Information Sources
- [Specific source types and priorities]
### Analysis Frameworks
- [Specific frameworks to apply]
### Data Requirements
- [Quality, recency, credibility needs]
## Expected Deliverables
### Executive Summary
- Key findings and insights
- Critical implications
- Recommended actions
### Detailed Analysis
[Specific sections needed based on research type]
### Supporting Materials
- Data tables
- Comparison matrices
- Source documentation
## Success Criteria
[How to evaluate if research achieved its objectives]
## Timeline and Priority
[If applicable, any time constraints or phasing]
```

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

@@ -424,25 +424,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
agent:
name: Sarah
id: po
title: Product Owner
icon: 📝
whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
customization:
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
customization: null
persona:
role: Technical Product Owner & Process Steward
style: Meticulous, analytical, detail-oriented, systematic, collaborative
identity: Product Owner who validates artifacts cohesion and coaches significant changes
focus: Plan integrity, documentation quality, actionable development tasks, process adherence
core_principles:
- Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
- Clarity & Actionability for Development - Make requirements unambiguous and testable
@@ -454,21 +451,18 @@ persona:
- User Collaboration for Validation - Seek input at critical checkpoints
- Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
- Documentation Ecosystem Integrity - Maintain consistency across all documents
startup:
- Greet the user with your name and role, and inform of the *help command.
commands:
- "*help" - Show: numbered list of the following commands to allow selection
- "*chat-mode" - (Default) Product Owner consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)
- "*shard-doc {document}" - Break down document into actionable parts
- "*correct-course" - Analyze and suggest project course corrections
- "*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)
- "*create-story" - Create user story from requirements (task brownfield-create-story)
- "*exit" - Say Goodbye, You are no longer this Agent
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
- '*shard-doc {document}" - Break down document into actionable parts'
- '*correct-course" - Analyze and suggest project course corrections'
- '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
- '*create-story" - Create user story from requirements (task brownfield-create-story)'
- '*exit" - Say Goodbye, You are no longer this Agent'
dependencies:
tasks:
- execute-checklist
@@ -2017,6 +2011,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
1. **Establish Context**
- Understand the problem space or opportunity area
- Identify any constraints or parameters
- Determine session goals (divergent exploration vs. focused ideation)
@@ -2033,6 +2028,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"What If" Scenarios**
[[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
- What if we had unlimited resources?
- What if this problem didn't exist?
- What if we approached this from a child's perspective?
@@ -2040,6 +2036,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Analogical Thinking**
[[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
- "How might this work like [X] but for [Y]?"
- Nature-inspired solutions (biomimicry)
- Cross-industry pattern matching
@@ -2047,6 +2044,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
3. **Reversal/Inversion**
[[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
- What if we did the exact opposite?
- How could we make this problem worse? (then reverse)
- Start from the end goal and work backward
@@ -2063,6 +2061,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
@@ -2073,6 +2072,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]]
- White Hat: Facts and information
- Red Hat: Emotions and intuition
- Black Hat: Caution and critical thinking
@@ -2099,6 +2099,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"Yes, And..." Building**
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
- Accept the premise of each idea
- Add to it with "Yes, and..."
- Build chains of connected ideas
@@ -2106,40 +2107,43 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Brainwriting/Round Robin**
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
- Generate ideas from stakeholder perspectives
- Build on previous ideas in rounds
- Combine unrelated ideas
- Cross-pollinate concepts
3. **Random Stimulation**
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
#### Deep Exploration Techniques
1. **Five Whys**
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
2. **Morphological Analysis**
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
3. **Provocation Technique (PO)**
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
### 3. Technique Selection Guide
@@ -2180,16 +2184,19 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
1. **Warm-up Phase** (5-10 min)
- Start with accessible techniques
- Build creative confidence
- Establish "no judgment" atmosphere
2. **Divergent Phase** (20-30 min)
- Use expansion techniques
- Generate quantity over quality
- Encourage wild ideas
3. **Convergent Phase** (15-20 min)
- Group and categorize ideas
- Identify patterns and themes
- Select promising directions
@@ -2425,53 +2432,65 @@ Present these numbered options to the user:
```markdown
## Research Objective
[Clear statement of what this research aims to achieve]
## Background Context
[Relevant information from project brief, brainstorming, or other inputs]
## Research Questions
### Primary Questions (Must Answer)
1. [Specific, actionable question]
2. [Specific, actionable question]
...
...
### Secondary Questions (Nice to Have)
1. [Supporting question]
2. [Supporting question]
...
...
## Research Methodology
### Information Sources
- [Specific source types and priorities]
### Analysis Frameworks
- [Specific frameworks to apply]
### Data Requirements
- [Quality, recency, credibility needs]
## Expected Deliverables
### Executive Summary
- Key findings and insights
- Critical implications
- Recommended actions
### Detailed Analysis
[Specific sections needed based on research type]
### Supporting Materials
- Data tables
- Comparison matrices
- Source documentation
## Success Criteria
[How to evaluate if research achieved its objectives]
## Timeline and Priority
[If applicable, any time constraints or phasing]
```
@@ -6350,28 +6369,33 @@ Ask the user if they want to work through the checklist:
Now that you've completed the checklist, generate a comprehensive validation report that includes:
1. Executive Summary
- Overall architecture readiness (High/Medium/Low)
- Critical risks identified
- Key strengths of the architecture
- Project type (Full-stack/Frontend/Backend) and sections evaluated
2. Section Analysis
- Pass rate for each major section (percentage of items passed)
- Most concerning failures or gaps
- Sections requiring immediate attention
- Note any sections skipped due to project type
3. Risk Assessment
- Top 5 risks by severity
- Mitigation recommendations for each
- Timeline impact of addressing issues
4. Recommendations
- Must-fix items before development
- Should-fix items for better quality
- Nice-to-have improvements
5. AI Implementation Readiness
- Specific concerns for AI agent implementation
- Areas needing additional clarification
- Complexity hotspots to address
@@ -8963,47 +8987,47 @@ To generate a masterful, comprehensive, and optimized prompt that can be used wi
1. **Confirm Target AI Generation Platform:**
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
2. **Synthesize Inputs into a Structured Prompt:**
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
3. **Present and Refine the Master Prompt:**
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>
==================== END: tasks#generate-ai-frontend-prompt ====================
==================== START: templates#front-end-spec-tmpl ====================

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

@@ -431,25 +431,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
agent:
name: Sarah
id: po
title: Product Owner
icon: 📝
whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
customization:
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
customization: null
persona:
role: Technical Product Owner & Process Steward
style: Meticulous, analytical, detail-oriented, systematic, collaborative
identity: Product Owner who validates artifacts cohesion and coaches significant changes
focus: Plan integrity, documentation quality, actionable development tasks, process adherence
core_principles:
- Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
- Clarity & Actionability for Development - Make requirements unambiguous and testable
@@ -461,21 +458,18 @@ persona:
- User Collaboration for Validation - Seek input at critical checkpoints
- Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
- Documentation Ecosystem Integrity - Maintain consistency across all documents
startup:
- Greet the user with your name and role, and inform of the *help command.
commands:
- "*help" - Show: numbered list of the following commands to allow selection
- "*chat-mode" - (Default) Product Owner consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)
- "*shard-doc {document}" - Break down document into actionable parts
- "*correct-course" - Analyze and suggest project course corrections
- "*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)
- "*create-story" - Create user story from requirements (task brownfield-create-story)
- "*exit" - Say Goodbye, You are no longer this Agent
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
- '*shard-doc {document}" - Break down document into actionable parts'
- '*correct-course" - Analyze and suggest project course corrections'
- '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
- '*create-story" - Create user story from requirements (task brownfield-create-story)'
- '*exit" - Say Goodbye, You are no longer this Agent'
dependencies:
tasks:
- execute-checklist
@@ -1837,6 +1831,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
1. **Establish Context**
- Understand the problem space or opportunity area
- Identify any constraints or parameters
- Determine session goals (divergent exploration vs. focused ideation)
@@ -1853,6 +1848,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"What If" Scenarios**
[[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
- What if we had unlimited resources?
- What if this problem didn't exist?
- What if we approached this from a child's perspective?
@@ -1860,6 +1856,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Analogical Thinking**
[[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
- "How might this work like [X] but for [Y]?"
- Nature-inspired solutions (biomimicry)
- Cross-industry pattern matching
@@ -1867,6 +1864,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
3. **Reversal/Inversion**
[[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
- What if we did the exact opposite?
- How could we make this problem worse? (then reverse)
- Start from the end goal and work backward
@@ -1883,6 +1881,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
@@ -1893,6 +1892,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]]
- White Hat: Facts and information
- Red Hat: Emotions and intuition
- Black Hat: Caution and critical thinking
@@ -1919,6 +1919,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"Yes, And..." Building**
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
- Accept the premise of each idea
- Add to it with "Yes, and..."
- Build chains of connected ideas
@@ -1926,40 +1927,43 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Brainwriting/Round Robin**
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
- Generate ideas from stakeholder perspectives
- Build on previous ideas in rounds
- Combine unrelated ideas
- Cross-pollinate concepts
3. **Random Stimulation**
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
#### Deep Exploration Techniques
1. **Five Whys**
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
2. **Morphological Analysis**
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
3. **Provocation Technique (PO)**
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
### 3. Technique Selection Guide
@@ -2000,16 +2004,19 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
1. **Warm-up Phase** (5-10 min)
- Start with accessible techniques
- Build creative confidence
- Establish "no judgment" atmosphere
2. **Divergent Phase** (20-30 min)
- Use expansion techniques
- Generate quantity over quality
- Encourage wild ideas
3. **Convergent Phase** (15-20 min)
- Group and categorize ideas
- Identify patterns and themes
- Select promising directions
@@ -2245,53 +2252,65 @@ Present these numbered options to the user:
```markdown
## Research Objective
[Clear statement of what this research aims to achieve]
## Background Context
[Relevant information from project brief, brainstorming, or other inputs]
## Research Questions
### Primary Questions (Must Answer)
1. [Specific, actionable question]
2. [Specific, actionable question]
...
...
### Secondary Questions (Nice to Have)
1. [Supporting question]
2. [Supporting question]
...
...
## Research Methodology
### Information Sources
- [Specific source types and priorities]
### Analysis Frameworks
- [Specific frameworks to apply]
### Data Requirements
- [Quality, recency, credibility needs]
## Expected Deliverables
### Executive Summary
- Key findings and insights
- Critical implications
- Recommended actions
### Detailed Analysis
[Specific sections needed based on research type]
### Supporting Materials
- Data tables
- Comparison matrices
- Source documentation
## Success Criteria
[How to evaluate if research achieved its objectives]
## Timeline and Priority
[If applicable, any time constraints or phasing]
```
@@ -4830,47 +4849,47 @@ To generate a masterful, comprehensive, and optimized prompt that can be used wi
1. **Confirm Target AI Generation Platform:**
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
- Ask the user to specify which AI frontend generation tool/platform they intend to use (e.g., "Lovable.ai", "Vercel v0", "GPT-4 with direct code generation instructions", etc.).
- Explain that prompt optimization might differ slightly based on the platform's capabilities and preferred input format.
2. **Synthesize Inputs into a Structured Prompt:**
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
- **Overall Project Context:**
- Briefly state the project's purpose (from brief/PRD).
- Specify the chosen frontend framework, core libraries, and UI component library (from `front-end-architecture` and main `architecture`).
- Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
- **Design System & Visuals:**
- Reference the primary design files (e.g., Figma link).
- If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl`).
- List any global UI components or design tokens that should be defined or adhered to.
- **Application Structure & Routing:**
- Describe the main pages/views and their routes (from `front-end-architecture` - Routing Strategy).
- Outline the navigation structure (from `front-end-spec-tmpl`).
- **Key User Flows & Page-Level Interactions:**
- For a few critical user flows (from `front-end-spec-tmpl`):
- Describe the sequence of user actions and expected UI changes on each relevant page.
- Specify API calls to be made (referencing API endpoints from the main `architecture`) and how data should be displayed or used.
- **Component Generation Instructions (Iterative or Key Components):**
- Based on the chosen AI tool's capabilities, decide on a strategy:
- **Option 1 (Scaffolding):** Prompt for the generation of main page structures, layouts, and placeholders for components.
- **Option 2 (Key Component Generation):** Select a few critical or complex components from the `front-end-architecture` (Component Breakdown) and provide detailed specifications for them (props, state, basic behavior, key UI elements).
- **Option 3 (Holistic, if tool supports):** Attempt to describe the entire application structure and key components more broadly.
- <important_note>Advise the user that generating an entire complex application perfectly in one go is rare. Iterative prompting or focusing on sections/key components is often more effective.</important_note>
- **State Management (High-Level Pointers):**
- Mention the chosen state management solution (e.g., "Use Redux Toolkit").
- For key pieces of data, indicate if they should be managed in global state.
- **API Integration Points:**
- For pages/components that fetch or submit data, clearly state the relevant API endpoints (from `architecture`) and the expected data shapes (can reference schemas in `data-models` or `api-reference` sections of the architecture doc).
- **Critical "Don'ts" or Constraints:**
- e.g., "Do not use deprecated libraries." "Ensure all forms have basic client-side validation."
- **Platform-Specific Optimizations:**
- If the chosen AI tool has known best practices for prompting (e.g., specific keywords, structure, level of detail), incorporate them. (This might require the agent to have some general knowledge or to ask the user if they know any such specific prompt modifiers for their chosen tool).
3. **Present and Refine the Master Prompt:**
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>
- Output the generated prompt in a clear, copy-pasteable format (e.g., a large code block).
- Explain the structure of the prompt and why certain information was included.
- Work with the user to refine the prompt based on their knowledge of the target AI tool and any specific nuances they want to emphasize.
- <important_note>Remind the user that the generated code from the AI tool will likely require review, testing, and further refinement by developers.</important_note>
==================== END: tasks#generate-ai-frontend-prompt ====================
==================== START: templates#front-end-spec-tmpl ====================
@@ -8225,28 +8244,33 @@ Ask the user if they want to work through the checklist:
Now that you've completed the checklist, generate a comprehensive validation report that includes:
1. Executive Summary
- Overall architecture readiness (High/Medium/Low)
- Critical risks identified
- Key strengths of the architecture
- Project type (Full-stack/Frontend/Backend) and sections evaluated
2. Section Analysis
- Pass rate for each major section (percentage of items passed)
- Most concerning failures or gaps
- Sections requiring immediate attention
- Note any sections skipped due to project type
3. Risk Assessment
- Top 5 risks by severity
- Mitigation recommendations for each
- Timeline impact of addressing issues
4. Recommendations
- Must-fix items before development
- Should-fix items for better quality
- Nice-to-have improvements
5. AI Implementation Readiness
- Specific concerns for AI agent implementation
- Areas needing additional clarification
- Complexity hotspots to address

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

@@ -351,25 +351,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
agent:
name: Sarah
id: po
title: Product Owner
icon: 📝
whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
customization:
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
customization: null
persona:
role: Technical Product Owner & Process Steward
style: Meticulous, analytical, detail-oriented, systematic, collaborative
identity: Product Owner who validates artifacts cohesion and coaches significant changes
focus: Plan integrity, documentation quality, actionable development tasks, process adherence
core_principles:
- Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
- Clarity & Actionability for Development - Make requirements unambiguous and testable
@@ -381,21 +378,18 @@ persona:
- User Collaboration for Validation - Seek input at critical checkpoints
- Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
- Documentation Ecosystem Integrity - Maintain consistency across all documents
startup:
- Greet the user with your name and role, and inform of the *help command.
commands:
- "*help" - Show: numbered list of the following commands to allow selection
- "*chat-mode" - (Default) Product Owner consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)
- "*shard-doc {document}" - Break down document into actionable parts
- "*correct-course" - Analyze and suggest project course corrections
- "*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)
- "*create-story" - Create user story from requirements (task brownfield-create-story)
- "*exit" - Say Goodbye, You are no longer this Agent
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
- '*shard-doc {document}" - Break down document into actionable parts'
- '*correct-course" - Analyze and suggest project course corrections'
- '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
- '*create-story" - Create user story from requirements (task brownfield-create-story)'
- '*exit" - Say Goodbye, You are no longer this Agent'
dependencies:
tasks:
- execute-checklist
@@ -1757,6 +1751,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
1. **Establish Context**
- Understand the problem space or opportunity area
- Identify any constraints or parameters
- Determine session goals (divergent exploration vs. focused ideation)
@@ -1773,6 +1768,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"What If" Scenarios**
[[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
- What if we had unlimited resources?
- What if this problem didn't exist?
- What if we approached this from a child's perspective?
@@ -1780,6 +1776,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Analogical Thinking**
[[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
- "How might this work like [X] but for [Y]?"
- Nature-inspired solutions (biomimicry)
- Cross-industry pattern matching
@@ -1787,6 +1784,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
3. **Reversal/Inversion**
[[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
- What if we did the exact opposite?
- How could we make this problem worse? (then reverse)
- Start from the end goal and work backward
@@ -1803,6 +1801,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **SCAMPER Method**
[[LLM: Guide through each SCAMPER prompt systematically.]]
- **S** = Substitute: What can be substituted?
- **C** = Combine: What can be combined or integrated?
- **A** = Adapt: What can be adapted from elsewhere?
@@ -1813,6 +1812,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Six Thinking Hats**
[[LLM: Cycle through different thinking modes, spending focused time in each.]]
- White Hat: Facts and information
- Red Hat: Emotions and intuition
- Black Hat: Caution and critical thinking
@@ -1839,6 +1839,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
1. **"Yes, And..." Building**
[[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
- Accept the premise of each idea
- Add to it with "Yes, and..."
- Build chains of connected ideas
@@ -1846,40 +1847,43 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
2. **Brainwriting/Round Robin**
[[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
- Generate ideas from stakeholder perspectives
- Build on previous ideas in rounds
- Combine unrelated ideas
- Cross-pollinate concepts
3. **Random Stimulation**
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
[[LLM: Use random words, images, or concepts as creative triggers.]]
- Random word association
- Picture/metaphor inspiration
- Forced connections between unrelated items
- Constraint-based creativity
#### Deep Exploration Techniques
1. **Five Whys**
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
[[LLM: Dig deeper into root causes and underlying motivations.]]
- Why does this problem exist? → Answer → Why? (repeat 5 times)
- Uncover hidden assumptions
- Find root causes, not symptoms
- Identify intervention points
2. **Morphological Analysis**
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
[[LLM: Break down into parameters and systematically explore combinations.]]
- List key parameters/dimensions
- Identify possible values for each
- Create combination matrix
- Explore unusual combinations
3. **Provocation Technique (PO)**
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
[[LLM: Make deliberately provocative statements to jar thinking.]]
- PO: Cars have square wheels
- PO: Customers pay us to take products
- PO: The problem solves itself
- Extract useful ideas from provocations
### 3. Technique Selection Guide
@@ -1920,16 +1924,19 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
1. **Warm-up Phase** (5-10 min)
- Start with accessible techniques
- Build creative confidence
- Establish "no judgment" atmosphere
2. **Divergent Phase** (20-30 min)
- Use expansion techniques
- Generate quantity over quality
- Encourage wild ideas
3. **Convergent Phase** (15-20 min)
- Group and categorize ideas
- Identify patterns and themes
- Select promising directions
@@ -2165,53 +2172,65 @@ Present these numbered options to the user:
```markdown
## Research Objective
[Clear statement of what this research aims to achieve]
## Background Context
[Relevant information from project brief, brainstorming, or other inputs]
## Research Questions
### Primary Questions (Must Answer)
1. [Specific, actionable question]
2. [Specific, actionable question]
...
...
### Secondary Questions (Nice to Have)
1. [Supporting question]
2. [Supporting question]
...
...
## Research Methodology
### Information Sources
- [Specific source types and priorities]
### Analysis Frameworks
- [Specific frameworks to apply]
### Data Requirements
- [Quality, recency, credibility needs]
## Expected Deliverables
### Executive Summary
- Key findings and insights
- Critical implications
- Recommended actions
### Detailed Analysis
[Specific sections needed based on research type]
### Supporting Materials
- Data tables
- Comparison matrices
- Source documentation
## Success Criteria
[How to evaluate if research achieved its objectives]
## Timeline and Priority
[If applicable, any time constraints or phasing]
```
@@ -7670,28 +7689,33 @@ Ask the user if they want to work through the checklist:
Now that you've completed the checklist, generate a comprehensive validation report that includes:
1. Executive Summary
- Overall architecture readiness (High/Medium/Low)
- Critical risks identified
- Key strengths of the architecture
- Project type (Full-stack/Frontend/Backend) and sections evaluated
2. Section Analysis
- Pass rate for each major section (percentage of items passed)
- Most concerning failures or gaps
- Sections requiring immediate attention
- Note any sections skipped due to project type
3. Risk Assessment
- Top 5 risks by severity
- Mitigation recommendations for each
- Timeline impact of addressing issues
4. Recommendations
- Must-fix items before development
- Should-fix items for better quality
- Nice-to-have improvements
5. AI Implementation Readiness
- Specific concerns for AI agent implementation
- Areas needing additional clarification
- Complexity hotspots to address

36
.claude/commands/po.md
View File

@@ -8,25 +8,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
agent:
name: Sarah
id: po
title: Product Owner
icon: 📝
whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
customization:
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
customization: null
persona:
role: Technical Product Owner & Process Steward
style: Meticulous, analytical, detail-oriented, systematic, collaborative
identity: Product Owner who validates artifacts cohesion and coaches significant changes
focus: Plan integrity, documentation quality, actionable development tasks, process adherence
core_principles:
- Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
- Clarity & Actionability for Development - Make requirements unambiguous and testable
@@ -38,21 +35,18 @@ persona:
- User Collaboration for Validation - Seek input at critical checkpoints
- Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
- Documentation Ecosystem Integrity - Maintain consistency across all documents
startup:
- Greet the user with your name and role, and inform of the *help command.
commands:
- "*help" - Show: numbered list of the following commands to allow selection
- "*chat-mode" - (Default) Product Owner consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)
- "*shard-doc {document}" - Break down document into actionable parts
- "*correct-course" - Analyze and suggest project course corrections
- "*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)
- "*create-story" - Create user story from requirements (task brownfield-create-story)
- "*exit" - Say Goodbye, You are no longer this Agent
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
- '*shard-doc {document}" - Break down document into actionable parts'
- '*correct-course" - Analyze and suggest project course corrections'
- '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
- '*create-story" - Create user story from requirements (task brownfield-create-story)'
- '*exit" - Say Goodbye, You are no longer this Agent'
dependencies:
tasks:
- execute-checklist

36
.cursor/rules/po.mdc
View File

@@ -14,25 +14,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
agent:
name: Sarah
id: po
title: Product Owner
icon: 📝
whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
customization:
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
customization: null
persona:
role: Technical Product Owner & Process Steward
style: Meticulous, analytical, detail-oriented, systematic, collaborative
identity: Product Owner who validates artifacts cohesion and coaches significant changes
focus: Plan integrity, documentation quality, actionable development tasks, process adherence
core_principles:
- Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
- Clarity & Actionability for Development - Make requirements unambiguous and testable
@@ -44,21 +41,18 @@ persona:
- User Collaboration for Validation - Seek input at critical checkpoints
- Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
- Documentation Ecosystem Integrity - Maintain consistency across all documents
startup:
- Greet the user with your name and role, and inform of the *help command.
commands:
- "*help" - Show: numbered list of the following commands to allow selection
- "*chat-mode" - (Default) Product Owner consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)
- "*shard-doc {document}" - Break down document into actionable parts
- "*correct-course" - Analyze and suggest project course corrections
- "*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)
- "*create-story" - Create user story from requirements (task brownfield-create-story)
- "*exit" - Say Goodbye, You are no longer this Agent
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
- '*shard-doc {document}" - Break down document into actionable parts'
- '*correct-course" - Analyze and suggest project course corrections'
- '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
- '*create-story" - Create user story from requirements (task brownfield-create-story)'
- '*exit" - Say Goodbye, You are no longer this Agent'
dependencies:
tasks:
- execute-checklist

5
.husky/pre-commit Executable file
View File

@@ -0,0 +1,5 @@
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"
# Run lint-staged to format and lint YAML files
npx lint-staged

188
.roo/.roomodes
View File

@@ -1,95 +1,95 @@
customModes:
- slug: bmad-analyst
name: '📊 Business Analyst'
roleDefinition: You are a Business Analyst specializing in business analyst tasks and responsibilities.
whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/analyst.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt)$
description: Documentation and text files
- slug: bmad-architect
name: '🏗️ Architect'
roleDefinition: You are a Architect specializing in architect tasks and responsibilities.
whenToUse: Use for system design, architecture documents, technology selection, API design, and infrastructure planning
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/architect.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt|yml|yaml|json)$
description: Architecture docs and configs
- slug: bmad-bmad-master
name: '🧙 BMAD Master Task Executor'
roleDefinition: You are a BMAD Master Task Executor specializing in bmad master task executor tasks and responsibilities.
whenToUse: Use when you need comprehensive expertise across all domains or rapid context switching between multiple agent capabilities
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/bmad-master.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- edit
- slug: bmad-bmad-orchestrator
name: '🎭 BMAD Master Orchestrator'
roleDefinition: You are a BMAD Master Orchestrator specializing in bmad master orchestrator tasks and responsibilities.
whenToUse: Use for workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/bmad-orchestrator.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- edit
- slug: bmad-dev
name: '💻 Full Stack Developer'
roleDefinition: You are a Full Stack Developer specializing in full stack developer tasks and responsibilities.
whenToUse: Use for code implementation, debugging, refactoring, and development best practices
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/dev.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- edit
- slug: bmad-pm
name: '📋 Product Manager'
roleDefinition: You are a Product Manager specializing in product manager tasks and responsibilities.
whenToUse: Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/pm.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt)$
description: Product documentation
- slug: bmad-po
name: '📝 Product Owner'
roleDefinition: You are a Product Owner specializing in product owner tasks and responsibilities.
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/po.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt)$
description: Story and requirement docs
- slug: bmad-qa
name: '🧪 Quality Assurance Test Architect'
roleDefinition: You are a Quality Assurance Test Architect specializing in quality assurance test architect tasks and responsibilities.
whenToUse: Use for test planning, test case creation, quality assurance, bug reporting, and testing strategy
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/qa.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(test|spec)\.(js|ts|jsx|tsx)$|\.md$
description: Test files and documentation
- slug: bmad-sm
name: '🏃 Scrum Master'
roleDefinition: You are a Scrum Master specializing in scrum master tasks and responsibilities.
whenToUse: Use for story creation, epic management, retrospectives in party-mode, and agile process guidance
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/sm.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt)$
description: Process and planning docs
- slug: bmad-ux-expert
name: '🎨 UX Expert'
roleDefinition: You are a UX Expert specializing in ux expert tasks and responsibilities.
whenToUse: Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/ux-expert.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|css|scss|html|jsx|tsx)$
description: Design-related files
- slug: bmad-analyst
name: 📊 Business Analyst
roleDefinition: You are a Business Analyst specializing in business analyst tasks and responsibilities.
whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/analyst.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt)$
description: Documentation and text files
- slug: bmad-architect
name: 🏗️ Architect
roleDefinition: You are a Architect specializing in architect tasks and responsibilities.
whenToUse: Use for system design, architecture documents, technology selection, API design, and infrastructure planning
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/architect.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt|yml|yaml|json)$
description: Architecture docs and configs
- slug: bmad-bmad-master
name: 🧙 BMAD Master Task Executor
roleDefinition: You are a BMAD Master Task Executor specializing in bmad master task executor tasks and responsibilities.
whenToUse: Use when you need comprehensive expertise across all domains or rapid context switching between multiple agent capabilities
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/bmad-master.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- edit
- slug: bmad-bmad-orchestrator
name: 🎭 BMAD Master Orchestrator
roleDefinition: You are a BMAD Master Orchestrator specializing in bmad master orchestrator tasks and responsibilities.
whenToUse: Use for workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/bmad-orchestrator.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- edit
- slug: bmad-dev
name: 💻 Full Stack Developer
roleDefinition: You are a Full Stack Developer specializing in full stack developer tasks and responsibilities.
whenToUse: Use for code implementation, debugging, refactoring, and development best practices
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/dev.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- edit
- slug: bmad-pm
name: 📋 Product Manager
roleDefinition: You are a Product Manager specializing in product manager tasks and responsibilities.
whenToUse: Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/pm.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt)$
description: Product documentation
- slug: bmad-po
name: 📝 Product Owner
roleDefinition: You are a Product Owner specializing in product owner tasks and responsibilities.
whenToUse: Use for Product Owner tasks
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/po.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt)$
description: Story and requirement docs
- slug: bmad-qa
name: 🧪 Quality Assurance Test Architect
roleDefinition: You are a Quality Assurance Test Architect specializing in quality assurance test architect tasks and responsibilities.
whenToUse: Use for test planning, test case creation, quality assurance, bug reporting, and testing strategy
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/qa.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(test|spec)\.(js|ts|jsx|tsx)$|\.md$
description: Test files and documentation
- slug: bmad-sm
name: 🏃 Scrum Master
roleDefinition: You are a Scrum Master specializing in scrum master tasks and responsibilities.
whenToUse: Use for story creation, epic management, retrospectives in party-mode, and agile process guidance
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/sm.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|txt)$
description: Process and planning docs
- slug: bmad-ux-expert
name: 🎨 UX Expert
roleDefinition: You are a UX Expert specializing in ux expert tasks and responsibilities.
whenToUse: Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization
customInstructions: CRITICAL Read the full YML from .bmad-core/agents/ux-expert.md start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode
groups:
- read
- - edit
- fileRegex: \.(md|css|scss|html|jsx|tsx)$
description: Design-related files

2
.roo/README.md
View File

@@ -22,6 +22,7 @@ The `.roomodes` file defines all BMAD agents as custom modes using the proper `c
## Usage
In Roo Code:
1. Open the mode selector (usually in the status bar)
2. Select any BMAD agent mode
3. The AI will adopt that agent's personality and expertise
@@ -29,6 +30,7 @@ In Roo Code:
## File Permissions
Each agent has specific file access permissions:
- **Analysts, PM, PO, SM**: Limited to documentation files (.md, .txt)
- **Architect**: Architecture docs and configs (.md, .txt, .yml, .yaml, .json)
- **QA**: Test files and documentation

36
.windsurf/rules/po.md
View File

@@ -8,25 +8,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
agent:
name: Sarah
id: po
title: Product Owner
icon: 📝
whenToUse: "Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions"
customization:
whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
customization: null
persona:
role: Technical Product Owner & Process Steward
style: Meticulous, analytical, detail-oriented, systematic, collaborative
identity: Product Owner who validates artifacts cohesion and coaches significant changes
focus: Plan integrity, documentation quality, actionable development tasks, process adherence
core_principles:
- Guardian of Quality & Completeness - Ensure all artifacts are comprehensive and consistent
- Clarity & Actionability for Development - Make requirements unambiguous and testable
@@ -38,21 +35,18 @@ persona:
- User Collaboration for Validation - Seek input at critical checkpoints
- Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
- Documentation Ecosystem Integrity - Maintain consistency across all documents
startup:
- Greet the user with your name and role, and inform of the *help command.
commands:
- "*help" - Show: numbered list of the following commands to allow selection
- "*chat-mode" - (Default) Product Owner consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)
- "*shard-doc {document}" - Break down document into actionable parts
- "*correct-course" - Analyze and suggest project course corrections
- "*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)
- "*create-story" - Create user story from requirements (task brownfield-create-story)
- "*exit" - Say Goodbye, You are no longer this Agent
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
- '*shard-doc {document}" - Break down document into actionable parts'
- '*correct-course" - Analyze and suggest project course corrections'
- '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
- '*create-story" - Create user story from requirements (task brownfield-create-story)'
- '*exit" - Say Goodbye, You are no longer this Agent'
dependencies:
tasks:
- execute-checklist

12
expansion-packs/README.md
View File

@@ -8,10 +8,10 @@ Expansion packs extend BMAD Method with specialized capabilities for specific us
The original BMAD Method follows a simple, proven flow:
```text
````text
Analyst → PM → Architect → SM → Dev
(Brief) → (PRD) → (Architecture) → (Stories) → (Implementation)
```
```text
This core flow remains clean and focused on getting from business requirements to working software.
@@ -62,21 +62,21 @@ expansion-pack-name/
├── templates/ # Document templates (.md)
├── tasks/ # Specialized tasks (.md)
└── checklists/ # Validation checklists (.md)
```
````
## Installing an Expansion Pack
### Method 1: NPM Script
```bash
````bash
npm run install:expansion <pack-name>
```
```text
### Method 2: Direct Script
```bash
node tools/install-expansion-pack.js <pack-name>
```
````
### Method 3: Manual

36
expansion-packs/infrastructure-devops/agents/infra-devops-platform.md
View File

@@ -4,23 +4,20 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
```yml
activation-instructions:
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
- The customization field ALWAYS takes precedence over any conflicting instructions
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
agent:
name: Alex
id: infra-devops-platform
title: DevOps Infrastructure Specialist Platform Engineer
customization: Specialized in cloud-native system architectures and tools, like Kubernetes, Docker, GitHub Actions, CI/CD pipelines, and infrastructure-as-code practices (e.g., Terraform, CloudFormation, Bicep, etc.).
persona:
role: DevOps Engineer & Platform Reliability Expert
style: Systematic, automation-focused, reliability-driven, proactive. Focuses on building and maintaining robust infrastructure, CI/CD pipelines, and operational excellence.
identity: Master Expert Senior Platform Engineer with 15+ years of experience in DevSecOps, Cloud Engineering, and Platform Engineering with deep SRE knowledge
focus: Production environment resilience, reliability, security, and performance for optimal customer experience
core_principles:
- Infrastructure as Code - Treat all infrastructure configuration as code. Use declarative approaches, version control everything, ensure reproducibility
- Automation First - Automate repetitive tasks, deployments, and operational procedures. Build self-healing and self-scaling systems
@@ -32,22 +29,19 @@ persona:
- CI/CD Excellence - Build robust pipelines for fast, safe, reliable software delivery through automation and testing
- Disaster Recovery - Plan for worst-case scenarios with backup strategies and regularly tested recovery procedures
- Collaborative Operations - Work closely with development teams fostering shared responsibility for system reliability
startup:
- Announce: "Hey! I'm Alex, your DevOps Infrastructure Specialist. I love when things run secure, stable, reliable and performant. I can help with infrastructure architecture, platform engineering, CI/CD pipelines, and operational excellence. What infrastructure challenge can I help you with today?"
- List available tasks: review-infrastructure, validate-infrastructure, create infrastructure documentation
- List available templates: infrastructure-architecture, infrastructure-platform-from-arch
- Announce: Hey! I'm Alex, your DevOps Infrastructure Specialist. I love when things run secure, stable, reliable and performant. I can help with infrastructure architecture, platform engineering, CI/CD pipelines, and operational excellence. What infrastructure challenge can I help you with today?
- 'List available tasks: review-infrastructure, validate-infrastructure, create infrastructure documentation'
- 'List available templates: infrastructure-architecture, infrastructure-platform-from-arch'
- Execute selected task or stay in persona to help guided by Core DevOps Principles
commands:
- "*help" - Show: numbered list of the following commands to allow selection
- "*chat-mode" - (Default) Conversational mode for infrastructure and DevOps guidance
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*review-infrastructure" - Review existing infrastructure for best practices
- "*validate-infrastructure" - Validate infrastructure against security and reliability standards
- "*checklist" - Run infrastructure checklist for comprehensive review
- "*exit" - Say goodbye as Alex, the DevOps Infrastructure Specialist, and then abandon inhabiting this persona
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Conversational mode for infrastructure and DevOps guidance'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*review-infrastructure" - Review existing infrastructure for best practices'
- '*validate-infrastructure" - Validate infrastructure against security and reliability standards'
- '*checklist" - Run infrastructure checklist for comprehensive review'
- '*exit" - Say goodbye as Alex, the DevOps Infrastructure Specialist, and then abandon inhabiting this persona'
dependencies:
tasks:
- create-doc
@@ -62,4 +56,4 @@ dependencies:
- technical-preferences
utils:
- template-format
```
```

32
expansion-packs/infrastructure-devops/manifest.yml
View File

@@ -2,59 +2,37 @@ name: infrastructure
version: 1.0.0
description: Infrastructure & DevOps expansion pack for BMAD Method
author: BMAD Team
# Files to install and their destinations
files:
# Agent configuration
- source: agents/infra-devops-platform.yml
destination: .bmad-core/agents/infra-devops-platform.yml
# Persona definition
- source: personas/infra-devops-platform.md
destination: .bmad-core/personas/infra-devops-platform.md
# IDE agent configuration
- source: ide-agents/infra-devops-platform.ide.md
destination: .bmad-core/ide-agents/infra-devops-platform.ide.md
# Templates
- source: templates/infrastructure-architecture-tmpl.md
destination: .bmad-core/templates/infrastructure-architecture-tmpl.md
- source: templates/infrastructure-platform-from-arch-tmpl.md
destination: .bmad-core/templates/infrastructure-platform-from-arch-tmpl.md
# Tasks
- source: tasks/validate-infrastructure.md
destination: .bmad-core/tasks/validate-infrastructure.md
- source: tasks/review-infrastructure.md
destination: .bmad-core/tasks/review-infrastructure.md
# Checklists
- source: checklists/infrastructure-checklist.md
destination: .bmad-core/checklists/infrastructure-checklist.md
# Team configurations to update (add devops agent)
team_updates:
- team: team-technical.yml
add_agent: infra-devops-platform
- team: team-all.yml
add_agent: infra-devops-platform
# Dependencies on core BMAD components
dependencies:
- architect # Infrastructure design depends on main architecture
- create-doc # Uses template system
# Post-install instructions
- architect
- create-doc
post_install_message: |
Infrastructure expansion pack installed successfully!
The DevOps agent is now available. To use:
- For infrastructure architecture: Use architect agent with '*create-infrastructure'
- For implementation: Use 'npm run agent devops'
- For validation: Use devops agent with '*validate-infra'
- "For infrastructure architecture: Use architect agent with '*create-infrastructure"
- "For implementation: Use 'npm run agent devops"
- "For validation: Use devops agent with '*validate-infra"
Remember to configure your cloud credentials and technical preferences before use.

1
expansion-packs/infrastructure-devops/tasks/review-infrastructure.md
View File

@@ -32,6 +32,7 @@ To conduct a thorough review of existing infrastructure to identify improvement
### 3. Conduct Systematic Review
- **If "Incremental Mode" was selected:**
- For each section of the infrastructure checklist:
- **a. Present Section Focus:** Explain what aspects of infrastructure this section reviews
- **b. Work Through Items:** Examine each checklist item against current infrastructure

1
expansion-packs/infrastructure-devops/tasks/validate-infrastructure.md
View File

@@ -55,6 +55,7 @@ To comprehensively validate platform infrastructure changes against security, re
### 4. Execute Comprehensive Platform Validation Process
- **If "Incremental Mode" was selected:**
- For each section of the infrastructure checklist (Sections 1-16):
- **a. Present Section Purpose:** Explain what this section validates and why it's important for platform operations
- **b. Work Through Items:** Present each checklist item, guide the user through validation, and document compliance or gaps

27
expansion-packs/infrastructure-devops/templates/infrastructure-architecture-tmpl.md
View File

@@ -36,6 +36,7 @@ Output file location: `docs/infrastructure-architecture.md`]]
[[LLM: Infrastructure Elicitation Options
Present user with domain-specific elicitation options:
"For the Infrastructure Overview section, I can explore:
1. **Multi-Cloud Strategy Analysis** - Evaluate cloud provider options and vendor lock-in considerations
2. **Regional Distribution Planning** - Analyze latency requirements and data residency needs
3. **Environment Isolation Strategy** - Design security boundaries and resource segregation
@@ -93,6 +94,7 @@ Select an option (1-7):"]]
[[LLM: Design network topology considering security zones, traffic patterns, and compliance requirements. Reference main architecture for service communication patterns.
Create Mermaid diagram showing:
- VPC/Network structure
- Security zones and boundaries
- Traffic flow patterns
@@ -158,6 +160,7 @@ graph TB
[[LLM: Design data infrastructure based on data architecture from main system design. Consider data volumes, access patterns, compliance, and recovery requirements.
Create data flow diagram showing:
- Database topology
- Replication patterns
- Backup flows
@@ -193,12 +196,12 @@ Create data flow diagram showing:
@{example: responsibility_matrix}
| Component | Cloud Provider | Platform Team | Dev Team | Security Team |
|-----------|---------------|---------------|----------|---------------|
| Physical Security | ✓ | - | - | Audit |
| Network Security | Partial | ✓ | Config | Audit |
| Application Security | - | Tools | ✓ | Review |
| Data Encryption | Engine | Config | Implementation | Standards |
| Component | Cloud Provider | Platform Team | Dev Team | Security Team |
| -------------------- | -------------- | ------------- | -------------- | ------------- |
| Physical Security | ✓ | - | - | Audit |
| Network Security | Partial | ✓ | Config | Audit |
| Application Security | - | Tools | ✓ | Review |
| Data Encryption | Engine | Config | Implementation | Standards |
@{/example}
@@ -217,6 +220,7 @@ Create data flow diagram showing:
[[LLM: Design deployment pipeline that balances speed with safety. Include progressive deployment strategies and automated quality gates.
Create pipeline diagram showing:
- Build stages
- Test gates
- Deployment stages
@@ -265,18 +269,21 @@ Create pipeline diagram showing:
[[LLM: Design infrastructure to specifically support other BMAD agents and their workflows. This ensures the infrastructure enables the entire BMAD methodology.]]
### Development Agent Support
- Container platform for development environments
- GitOps workflows for application deployment
- Service mesh integration for development testing
- Developer self-service platform capabilities
### Product & Architecture Alignment
- Infrastructure implementing PRD scalability requirements
- Deployment automation supporting product iteration speed
- Service reliability meeting product SLAs
- Architecture patterns properly implemented in infrastructure
### Cross-Agent Integration Points
- CI/CD pipelines supporting Frontend, Backend, and Full Stack development workflows
- Monitoring and observability data accessible to QA and DevOps agents
- Infrastructure enabling Design Architect's UI/UX performance requirements
@@ -333,6 +340,7 @@ The Platform Engineer should use the infrastructure checklist to systematically
### Architecture Decision Records (ADRs)
Create ADRs for key infrastructure decisions:
- Cloud provider selection rationale
- Container orchestration platform choice
- Networking architecture decisions
@@ -342,6 +350,7 @@ Create ADRs for key infrastructure decisions:
### Implementation Validation Criteria
Define specific criteria for validating correct implementation:
- Infrastructure as Code quality gates
- Security compliance checkpoints
- Performance benchmarks
@@ -401,6 +410,6 @@ Define specific criteria for validating correct implementation:
---
*Document Version: 1.0*
*Last Updated: {{current_date}}*
*Next Review: {{review_date}}*
_Document Version: 1.0_
_Last Updated: {{current_date}}_
_Next Review: {{review_date}}_

1084
package-lock.json generated
View File

File diff suppressed because it is too large Load Diff

29
package.json
View File

@@ -13,17 +13,19 @@
"build:teams": "node tools/cli.js build --teams-only",
"list:agents": "node tools/cli.js list:agents",
"validate": "node tools/cli.js validate",
"install:bmad": "node tools/installer/bin/bmad.js install"
"install:bmad": "node tools/installer/bin/bmad.js install",
"format": "prettier --write \"**/*.md\" && node tools/yaml-format.js **/*.md **/*.yml **/*.yaml .roo/.roomodes",
"prepare": "husky"
},
"dependencies": {
"commander": "^9.4.1",
"js-yaml": "^4.1.0",
"@kayvan/markdown-tree-parser": "^1.4.2",
"chalk": "^4.1.2",
"commander": "^9.4.1",
"fs-extra": "^11.1.0",
"glob": "^8.0.3",
"inquirer": "^8.2.5",
"ora": "^5.4.1",
"glob": "^8.0.3"
"js-yaml": "^4.1.0",
"ora": "^5.4.1"
},
"keywords": [
"agile",
@@ -42,5 +44,22 @@
},
"engines": {
"node": ">=14.0.0"
},
"devDependencies": {
"husky": "^9.1.7",
"lint-staged": "^16.1.1",
"prettier": "^3.5.3",
"yaml-lint": "^1.7.0"
},
"lint-staged": {
"*.{yml,yaml}": [
"node tools/yaml-format.js"
],
"*.md": [
"node tools/yaml-format.js"
],
".roomodes": [
"node tools/yaml-format.js"
]
}
}

6
tools/installer/README.md
View File

@@ -4,7 +4,7 @@ This directory contains the BMAD Method installer implementation.
## Structure
```
```text
installer/
├── bin/ # CLI entry points
│ └── bmad.js # Main CLI executable
@@ -42,7 +42,7 @@ npx bmad-method install --profile=minimal
# Update existing installation
npx bmad-method update
```
```text
## Development
@@ -55,4 +55,4 @@ npm test
# Lint code
npm run lint
```
```

231
tools/installer/config/install.config.yml
View File

@@ -1,178 +1,139 @@
# BMAD Method Installation Configuration
# Simplified installer with two options: full copy or single agent
installation-options:
full:
name: "Complete BMAD Core"
description: "Copy the entire .bmad-core folder with all agents, templates, and tools"
action: "copy-folder"
source: ".bmad-core"
name: Complete BMAD Core
description: Copy the entire .bmad-core folder with all agents, templates, and tools
action: copy-folder
source: .bmad-core
single-agent:
name: "Single Agent"
description: "Select and install a single agent with its dependencies"
action: "copy-agent"
# Agent dependency mappings
# These are the core files that should be included with any single agent installation
name: Single Agent
description: Select and install a single agent with its dependencies
action: copy-agent
agent-dependencies:
core-files:
# Only files that truly every agent needs should go here
# Most dependencies should be declared in the agent YAML itself
- ".bmad-core/utils/template-format.md"
# Agent-specific dependencies (parsed from agent files or explicitly defined)
- .bmad-core/utils/template-format.md
dev:
- ".bmad-core/templates/story-tmpl.md"
- ".bmad-core/checklists/story-dod-checklist.md"
- .bmad-core/templates/story-tmpl.md
- .bmad-core/checklists/story-dod-checklist.md
pm:
- ".bmad-core/templates/prd-tmpl.md"
- ".bmad-core/templates/brownfield-prd-tmpl.md"
- ".bmad-core/checklists/pm-checklist.md"
- ".bmad-core/checklists/change-checklist.md"
- ".bmad-core/tasks/advanced-elicitation.md"
- ".bmad-core/tasks/create-doc.md"
- ".bmad-core/tasks/correct-course.md"
- ".bmad-core/tasks/create-deep-research-prompt.md"
- ".bmad-core/tasks/brownfield-create-epic.md"
- ".bmad-core/tasks/brownfield-create-story.md"
- ".bmad-core/tasks/execute-checklist.md"
- ".bmad-core/tasks/shard-doc.md"
- .bmad-core/templates/prd-tmpl.md
- .bmad-core/templates/brownfield-prd-tmpl.md
- .bmad-core/checklists/pm-checklist.md
- .bmad-core/checklists/change-checklist.md
- .bmad-core/tasks/advanced-elicitation.md
- .bmad-core/tasks/create-doc.md
- .bmad-core/tasks/correct-course.md
- .bmad-core/tasks/create-deep-research-prompt.md
- .bmad-core/tasks/brownfield-create-epic.md
- .bmad-core/tasks/brownfield-create-story.md
- .bmad-core/tasks/execute-checklist.md
- .bmad-core/tasks/shard-doc.md
architect:
- ".bmad-core/templates/architecture-tmpl.md"
- ".bmad-core/checklists/architect-checklist.md"
- .bmad-core/templates/architecture-tmpl.md
- .bmad-core/checklists/architect-checklist.md
sm:
- ".bmad-core/templates/story-tmpl.md"
- ".bmad-core/checklists/story-draft-checklist.md"
- ".bmad-core/workflows/*.yml"
- .bmad-core/templates/story-tmpl.md
- .bmad-core/checklists/story-draft-checklist.md
- .bmad-core/workflows/*.yml
po:
- ".bmad-core/checklists/po-master-checklist.md"
- ".bmad-core/templates/acceptance-criteria-tmpl.md"
- .bmad-core/checklists/po-master-checklist.md
- .bmad-core/templates/acceptance-criteria-tmpl.md
analyst:
- ".bmad-core/templates/prd-tmpl.md"
- ".bmad-core/tasks/advanced-elicitation.md"
- .bmad-core/templates/prd-tmpl.md
- .bmad-core/tasks/advanced-elicitation.md
qa:
- ".bmad-core/checklists/story-dod-checklist.md"
- ".bmad-core/templates/test-plan-tmpl.md"
- .bmad-core/checklists/story-dod-checklist.md
- .bmad-core/templates/test-plan-tmpl.md
ux-expert:
- ".bmad-core/templates/ux-tmpl.md"
# Meta agents typically need access to more resources
- .bmad-core/templates/ux-tmpl.md
bmad-master:
- ".bmad-core/templates/*.md"
- ".bmad-core/tasks/*.md"
- ".bmad-core/schemas/*.yml"
- .bmad-core/templates/*.md
- .bmad-core/tasks/*.md
- .bmad-core/schemas/*.yml
bmad-orchestrator:
- ".bmad-core/agent-teams/*.yml"
- ".bmad-core/workflows/*.yml"
# IDE-specific configuration for generating rules/commands
- .bmad-core/agent-teams/*.yml
- .bmad-core/workflows/*.yml
ide-configurations:
cursor:
name: "Cursor"
rule-dir: ".cursor/rules/"
format: "multi-file"
command-suffix: ".mdc"
name: Cursor
rule-dir: .cursor/rules/
format: multi-file
command-suffix: .mdc
instructions: |
# To use BMAD agents in Cursor:
# 1. Press Ctrl+L (Cmd+L on Mac) to open the chat
# 2. Type @agent-name (e.g., "@dev", "@pm", "@architect")
# 3. The agent will adopt that persona for the conversation
claude-code:
name: "Claude Code"
rule-dir: ".claude/commands/"
format: "multi-file"
command-suffix: ".md"
name: Claude Code
rule-dir: .claude/commands/
format: multi-file
command-suffix: .md
instructions: |
# To use BMAD agents in Claude Code:
# 1. Type /agent-name (e.g., "/dev", "/pm", "/architect")
# 2. Claude will switch to that agent's persona
windsurf:
name: "Windsurf"
rule-dir: ".windsurf/rules/"
format: "multi-file"
command-suffix: ".md"
name: Windsurf
rule-dir: .windsurf/rules/
format: multi-file
command-suffix: .md
instructions: |
# To use BMAD agents in Windsurf:
# 1. Type @agent-name (e.g., "@dev", "@pm")
# 2. Windsurf will adopt that agent's persona
roo:
name: "Roo Code"
format: "custom-modes"
file: ".roomodes"
name: Roo Code
format: custom-modes
file: .roomodes
instructions: |
# To use BMAD agents in Roo Code:
# 1. Open the mode selector (usually in the status bar)
# 2. Select any bmad-{agent} mode (e.g., "bmad-dev", "bmad-pm")
# 3. The AI will adopt that agent's full personality and capabilities
cline:
name: "Cline"
# Configuration TBD - needs research
format: "unknown"
name: Cline
format: unknown
instructions: |
# Cline configuration coming soon
# Manual setup: Copy IDE agent files to your Cline configuration
# Available agents for single-agent installation
available-agents:
- id: "analyst"
name: "Business Analyst"
file: ".bmad-core/agents/analyst.md"
description: "Requirements gathering and analysis"
- id: "pm"
name: "Product Manager"
file: ".bmad-core/agents/pm.md"
description: "Product strategy and roadmap planning"
- id: "architect"
name: "Solution Architect"
file: ".bmad-core/agents/architect.md"
description: "Technical design and architecture"
- id: "po"
name: "Product Owner"
file: ".bmad-core/agents/po.md"
description: "Backlog management and prioritization"
- id: "sm"
name: "Scrum Master"
file: ".bmad-core/agents/sm.md"
description: "Agile process and story creation"
- id: "dev"
name: "Developer"
file: ".bmad-core/agents/dev.md"
description: "Code implementation and testing"
- id: "qa"
name: "QA Engineer"
file: ".bmad-core/agents/qa.md"
description: "Quality assurance and testing"
- id: "ux-expert"
name: "UX Expert"
file: ".bmad-core/agents/ux-expert.md"
description: "User experience design"
- id: "bmad-master"
name: "BMAD Master"
file: ".bmad-core/agents/bmad-master.md"
description: "BMAD framework expert and guide"
- id: "bmad-orchestrator"
name: "BMAD Orchestrator"
file: ".bmad-core/agents/bmad-orchestrator.md"
description: "Multi-agent workflow coordinator"
- id: analyst
name: Business Analyst
file: .bmad-core/agents/analyst.md
description: Requirements gathering and analysis
- id: pm
name: Product Manager
file: .bmad-core/agents/pm.md
description: Product strategy and roadmap planning
- id: architect
name: Solution Architect
file: .bmad-core/agents/architect.md
description: Technical design and architecture
- id: po
name: Product Owner
file: .bmad-core/agents/po.md
description: Backlog management and prioritization
- id: sm
name: Scrum Master
file: .bmad-core/agents/sm.md
description: Agile process and story creation
- id: dev
name: Developer
file: .bmad-core/agents/dev.md
description: Code implementation and testing
- id: qa
name: QA Engineer
file: .bmad-core/agents/qa.md
description: Quality assurance and testing
- id: ux-expert
name: UX Expert
file: .bmad-core/agents/ux-expert.md
description: User experience design
- id: bmad-master
name: BMAD Master
file: .bmad-core/agents/bmad-master.md
description: BMAD framework expert and guide
- id: bmad-orchestrator
name: BMAD Orchestrator
file: .bmad-core/agents/bmad-orchestrator.md
description: Multi-agent workflow coordinator

2
tools/installer/lib/ide-setup.js
View File

@@ -331,7 +331,7 @@ class IdeSetup {
? roleDefinitionMatch[1].trim()
: `You are a ${title} specializing in ${title.toLowerCase()} tasks and responsibilities.`;
// Build mode entry with proper formatting
// Build mode entry with proper formatting (matching exact indentation)
newModesContent += ` - slug: bmad-${agentId}\n`;
newModesContent += ` name: '${icon} ${title}'\n`;
newModesContent += ` roleDefinition: ${roleDefinition}\n`;

2
tools/installer/templates/claude-commands.md
View File

@@ -4,4 +4,4 @@
---
This is a BMAD Method agent. For more information, visit: https://github.com/your-org/bmad-method
This is a BMAD Method agent. For more information, visit: https://github.com/your-org/bmad-method

3
tools/installer/templates/cursor-rules.md
View File

@@ -15,7 +15,8 @@ This file contains all BMAD Method agent personas. To use an agent, type its nam
# Agent Switching
To switch between agents during a conversation:
1. Simply type the new agent name (e.g., "architect" or "dev")
2. The AI will adopt that agent's persona
For more information about BMAD Method, visit: https://github.com/your-org/bmad-method
For more information about BMAD Method, visit: https://github.com/your-org/bmad-method

2
tools/installer/templates/windsurf-rules.md
View File

@@ -19,4 +19,4 @@ This file contains all BMAD Method agent commands for Windsurf. Use /agent-name
- Type `/architect` to switch to Architect persona
- And so on for other agents...
For more information about BMAD Method, visit: https://github.com/your-org/bmad-method
For more information about BMAD Method, visit: https://github.com/your-org/bmad-method

211
tools/yaml-format.js Executable file
View File

@@ -0,0 +1,211 @@
#!/usr/bin/env node
const fs = require('fs');
const path = require('path');
const yaml = require('js-yaml');
const { execSync } = require('child_process');
const chalk = require('chalk');
/**
* YAML Formatter and Linter for BMAD-METHOD
* Formats and validates YAML files and YAML embedded in Markdown
*/
function formatYamlContent(content, filename) {
try {
// First try to fix common YAML issues
let fixedContent = content
// Fix "commands :" -> "commands:"
.replace(/^(\s*)(\w+)\s+:/gm, '$1$2:')
// Fix inconsistent list indentation
.replace(/^(\s*)-\s{3,}/gm, '$1- ');
// Skip auto-fixing for .roomodes files - they have special nested structure
if (!filename.includes('.roomodes')) {
fixedContent = fixedContent
// Fix unquoted list items that contain special characters or multiple parts
.replace(/^(\s*)-\s+(.*)$/gm, (match, indent, content) => {
// Skip if already quoted
if (content.startsWith('"') && content.endsWith('"')) {
return match;
}
// If the content contains special YAML characters or looks complex, quote it
// BUT skip if it looks like a proper YAML key-value pair (like "key: value")
if ((content.includes(':') || content.includes('-') || content.includes('{') || content.includes('}')) &&
!content.match(/^\w+:\s/)) {
// Remove any existing quotes first, escape internal quotes, then add proper quotes
const cleanContent = content.replace(/^["']|["']$/g, '').replace(/"/g, '\\"');
return `${indent}- "${cleanContent}"`;
}
return match;
});
}
// Debug: show what we're trying to parse
if (fixedContent !== content) {
console.log(chalk.blue(`🔧 Applied YAML fixes to ${filename}`));
}
// Parse and re-dump YAML to format it
const parsed = yaml.load(fixedContent);
const formatted = yaml.dump(parsed, {
indent: 2,
lineWidth: -1, // Disable line wrapping
noRefs: true,
sortKeys: false // Preserve key order
});
return formatted;
} catch (error) {
console.error(chalk.red(`❌ YAML syntax error in ${filename}:`), error.message);
console.error(chalk.yellow(`💡 Try manually fixing the YAML structure first`));
return null;
}
}
function processMarkdownFile(filePath) {
const content = fs.readFileSync(filePath, 'utf8');
let modified = false;
let newContent = content;
// Fix untyped code blocks by adding 'text' type
// Match ``` at start of line followed by newline, but only if it's an opening fence
newContent = newContent.replace(/^```\n([\s\S]*?)\n```$/gm, '```text\n$1\n```');
if (newContent !== content) {
modified = true;
console.log(chalk.blue(`🔧 Added 'text' type to untyped code blocks in ${filePath}`));
}
// Find YAML code blocks
const yamlBlockRegex = /```ya?ml\n([\s\S]*?)\n```/g;
newContent = newContent.replace(yamlBlockRegex, (match, yamlContent) => {
const formatted = formatYamlContent(yamlContent, filePath);
if (formatted === null) {
return match; // Keep original if parsing failed
}
// Remove trailing newline that js-yaml adds
const trimmedFormatted = formatted.replace(/\n$/, '');
if (trimmedFormatted !== yamlContent) {
modified = true;
}
return `\`\`\`yml\n${trimmedFormatted}\n\`\`\``;
});
if (modified) {
fs.writeFileSync(filePath, newContent);
return true;
}
return false;
}
function processYamlFile(filePath) {
const content = fs.readFileSync(filePath, 'utf8');
const formatted = formatYamlContent(content, filePath);
if (formatted === null) {
return false; // Syntax error
}
if (formatted !== content) {
fs.writeFileSync(filePath, formatted);
return true;
}
return false;
}
function lintYamlFile(filePath) {
try {
// Use yaml-lint for additional validation
execSync(`npx yaml-lint "${filePath}"`, { stdio: 'pipe' });
return true;
} catch (error) {
console.error(chalk.red(`❌ YAML lint error in ${filePath}:`));
console.error(error.stdout?.toString() || error.message);
return false;
}
}
function main() {
const args = process.argv.slice(2);
const glob = require('glob');
if (args.length === 0) {
console.error('Usage: node yaml-format.js <file1> [file2] ...');
process.exit(1);
}
let hasErrors = false;
let hasChanges = false;
let filesProcessed = [];
// Expand glob patterns and collect all files
const allFiles = [];
for (const arg of args) {
if (arg.includes('*')) {
// It's a glob pattern
const matches = glob.sync(arg);
allFiles.push(...matches);
} else {
// It's a direct file path
allFiles.push(arg);
}
}
for (const filePath of allFiles) {
if (!fs.existsSync(filePath)) {
// Skip silently for glob patterns that don't match anything
if (!args.some(arg => arg.includes('*') && filePath === arg)) {
console.error(chalk.red(`❌ File not found: ${filePath}`));
hasErrors = true;
}
continue;
}
const ext = path.extname(filePath).toLowerCase();
const basename = path.basename(filePath).toLowerCase();
try {
let changed = false;
if (ext === '.md') {
changed = processMarkdownFile(filePath);
} else if (ext === '.yml' || ext === '.yaml' || basename.includes('roomodes') || basename.includes('.yml') || basename.includes('.yaml')) {
// Handle YAML files and special cases like .roomodes
changed = processYamlFile(filePath);
// Also run linting
const lintPassed = lintYamlFile(filePath);
if (!lintPassed) hasErrors = true;
} else {
// Skip silently for unsupported files
continue;
}
if (changed) {
hasChanges = true;
filesProcessed.push(filePath);
}
} catch (error) {
console.error(chalk.red(`❌ Error processing ${filePath}:`), error.message);
hasErrors = true;
}
}
if (hasChanges) {
console.log(chalk.green(`\n✨ YAML formatting completed! Modified ${filesProcessed.length} files:`));
filesProcessed.forEach(file => console.log(chalk.blue(` 📝 ${file}`)));
}
if (hasErrors) {
console.error(chalk.red('\n💥 Some files had errors. Please fix them before committing.'));
process.exit(1);
}
}
if (require.main === module) {
main();
}
module.exports = { formatYamlContent, processMarkdownFile, processYamlFile };