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

checklist standardization and improvement with llm eliciatation

Browse Source
This commit is contained in:
Brian Madison
2025-06-08 20:34:07 -05:00
parent 460c47f5c8
commit 8788c1d20f
24 changed files with 2419 additions and 884 deletions
Download Patch File Download Diff File Expand all files Collapse all files

269
agent-team-workflows/brownfield-fullstack.yml
View File

@@ -2,192 +2,115 @@ workflow:
id: brownfield-fullstack
name: Brownfield Full-Stack Enhancement
description: >-
Workflow for adding features, refactoring, or modernizing existing applications.
Handles legacy code analysis and incremental improvements.
Agent workflow for enhancing existing full-stack applications with new features,
modernization, or significant changes. Handles existing system analysis and safe integration.
type: brownfield
project_types:
- feature-addition
- refactoring
- modernization
- bug-fix
- integration-enhancement
stages:
- id: system-analysis
name: Existing System Analysis
description: Understand current system and identify improvement areas
steps:
- agent: analyst
action: System Assessment
description: >-
Analyze existing system, codebase, and identify pain points
inputs:
- existing-documentation
- codebase-access
outputs:
- system-assessment
- improvement-opportunities
- technical-debt-analysis
prompts:
- "Let's analyze the existing system architecture"
- "What are the main pain points and technical debt?"
- "Share any existing documentation or system diagrams"
- "You can also share the codebase if you have access to it"
# For Complex Enhancements (Multiple Stories, Architectural Changes)
complex_enhancement_sequence:
- step: scope_assessment
agent: any
action: assess complexity
notes: "First, assess if this is a simple change (use simple_enhancement_sequence) or complex enhancement requiring full planning."
- agent: fullstack-architect
action: Code Analysis
description: >-
Deep dive into codebase quality and structure
inputs:
- codebase-access
outputs:
- code-quality-report
- dependency-analysis
- refactoring-candidates
prompts:
- "Let me analyze the code structure and quality"
- "Identifying areas that need refactoring"
- step: project_analysis
agent: analyst
action: analyze existing project
notes: "Review existing documentation, codebase structure, and identify integration points. Document current system understanding before proceeding."
- id: enhancement-planning
name: Enhancement Planning
description: Plan improvements and new features
steps:
- agent: pm
action: Enhancement Strategy
description: >-
Define enhancement goals and success criteria
inputs:
- system-assessment
- improvement-opportunities
outputs:
- enhancement-prd
- success-metrics
- risk-assessment
prompts:
- "What specific enhancements are we targeting?"
- "Define success metrics for these improvements"
- agent: pm
creates: brownfield-prd.md
uses: brownfield-prd-tmpl
requires: existing_project_analysis
notes: "Creates comprehensive brownfield PRD with existing system analysis and enhancement planning. SAVE OUTPUT: Copy final brownfield-prd.md to your project's docs/ folder."
- agent: fullstack-architect
action: Integration Architecture
description: >-
Design how new features integrate with existing system
inputs:
- enhancement-prd
- system-assessment
outputs:
- integration-architecture
- migration-strategy
- compatibility-matrix
prompts:
- "How will new features integrate with existing code?"
- "Design migration strategy for gradual rollout"
- agent: fullstack-architect
creates: brownfield-architecture.md
uses: brownfield-architecture-tmpl
requires: brownfield-prd.md
notes: "Creates brownfield architecture with integration strategy and existing system constraints. SAVE OUTPUT: Copy final brownfield-architecture.md to your project's docs/ folder."
- id: incremental-design
name: Incremental Design
description: Design changes that don't break existing functionality
steps:
- agent: fullstack-architect
action: Incremental Architecture
description: >-
Design architecture that allows gradual migration
inputs:
- integration-architecture
- technical-debt-analysis
outputs:
- incremental-architecture
- feature-flags-design
- rollback-strategy
prompts:
- "Design architecture for incremental deployment"
- "How do we maintain backward compatibility?"
- agent: po
validates: all_artifacts
uses: brownfield-checklist
notes: "Validates all brownfield documents for integration safety and completeness. May require updates to any document."
- agent: devops
action: Deployment Strategy
description: >-
Plan zero-downtime deployment and rollback procedures
inputs:
- incremental-architecture
outputs:
- deployment-strategy
- canary-release-plan
- monitoring-upgrades
prompts:
- "Design blue-green or canary deployment"
- "Upgrade monitoring for new features"
- agent: various
updates: any_flagged_documents
condition: po_checklist_issues
notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
- id: risk-mitigation
name: Risk Assessment & Mitigation
description: Identify and plan for risks in brownfield changes
steps:
- agent: qa
action: Regression Risk Analysis
description: >-
Identify regression risks and test coverage gaps
inputs:
- code-quality-report
- integration-architecture
outputs:
- regression-risk-matrix
- test-gap-analysis
- test-automation-plan
prompts:
- "What existing functionality might break?"
- "Where do we need additional test coverage?"
- workflow_end:
action: move_to_ide
notes: "All planning artifacts complete. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
- agent: po
action: Change Impact Review
description: >-
Review all changes for business impact
inputs:
- enhancement-prd
- risk-assessment
- regression-risk-matrix
outputs:
- impact-analysis
- stakeholder-communication
- approval-checklist
prompts:
- "Review impact on existing users and workflows"
- "Prepare stakeholder communication plan"
# For Simple Enhancements (1-3 Stories, Following Existing Patterns)
simple_enhancement_sequence:
- step: enhancement_type
action: choose approach
notes: "Choose between creating single story (very small change) or epic (1-3 related stories)."
- id: implementation-planning
name: Phased Implementation
description: Create phased implementation plan
steps:
- agent: sm
action: Phased Story Creation
description: >-
Create stories for incremental implementation
inputs:
- incremental-architecture
- impact-analysis
outputs:
- implementation-phases
- user-stories
- dependency-map
prompts:
- "Break down into safe, incremental phases"
- "Map dependencies between stories"
- agent: pm|po|sm
creates: brownfield_epic OR brownfield_story
uses: brownfield-create-epic OR brownfield-create-story
notes: "Create focused enhancement with existing system integration. Choose agent based on team preference and context."
transitions:
- from: system-analysis
to: enhancement-planning
condition: assessment complete
- from: enhancement-planning
to: incremental-design
condition: strategy defined
- from: incremental-design
to: risk-mitigation
condition: architecture approved
- from: risk-mitigation
to: implementation-planning
condition: risks assessed
- workflow_end:
action: move_to_ide
notes: "Enhancement defined. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
special_considerations:
- name: Legacy Code
description: Handle undocumented or poorly structured code
- name: Data Migration
description: Plan for data structure changes
- name: User Training
description: Consider impact on existing users
- name: Rollback Plan
description: Always have a way to revert changes
flow_diagram: |
```mermaid
graph TD
A[Start: Brownfield Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing project]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[fullstack-architect: brownfield-architecture.md]
F --> G[po: validate with brownfield-checklist]
G --> H{PO finds issues?}
H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment]
I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment]
L --> M
style J fill:#90EE90
style M fill:#90EE90
style E fill:#FFE4B5
style F fill:#FFE4B5
style K fill:#FFB6C1
style L fill:#FFB6C1
```
decision_guidance:
use_complex_sequence_when:
- Enhancement requires multiple coordinated stories (4+)
- Architectural changes are needed
- Significant integration work required
- Risk assessment and mitigation planning necessary
- Multiple team members will work on related changes
use_simple_sequence_when:
- Enhancement can be completed in 1-3 stories
- Follows existing project patterns
- Integration complexity is minimal
- Risk to existing system is low
- Change is isolated with clear boundaries
handoff_prompts:
analyst_to_pm: "Existing project analysis complete. Create comprehensive brownfield PRD with integration strategy."
pm_to_architect: "Brownfield PRD ready. Save it as docs/brownfield-prd.md, then create the integration architecture."
architect_to_po: "Architecture complete. Save it as docs/brownfield-architecture.md. Please validate all artifacts for integration safety."
po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
simple_to_ide: "Enhancement defined with existing system integration. Move to IDE environment to begin development."
complex_complete: "All brownfield planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."

324
agent-team-workflows/brownfield-service.yml
View File

@@ -2,252 +2,116 @@ workflow:
id: brownfield-service
name: Brownfield Service/API Enhancement
description: >-
Workflow for modernizing, refactoring, or enhancing existing backend services and APIs.
Handles performance optimization, API versioning, microservice extraction, and technical debt.
Agent workflow for enhancing existing backend services and APIs with new features,
modernization, or performance improvements. Handles existing system analysis and safe integration.
type: brownfield
project_types:
- service-modernization
- api-enhancement
- microservice-extraction
- performance-optimization
- technical-debt-reduction
- integration-enhancement
stages:
- id: service-analysis
name: Service Assessment
description: Analyze existing service and identify improvement areas
steps:
- agent: analyst
action: Service Assessment
description: >-
Analyze current service architecture, performance, and technical debt
inputs:
- existing-service-code
- performance-metrics
- error-logs
outputs:
- service-assessment
- performance-bottlenecks
- technical-debt-analysis
- integration-dependencies
prompts:
- "Let's analyze the current service architecture"
- "What performance issues are you experiencing?"
- "Share service metrics, logs, or documentation"
# For Complex Service Enhancements (Multiple Stories, Architectural Changes)
complex_enhancement_sequence:
- step: scope_assessment
agent: any
action: assess complexity
notes: "First, assess if this is a simple service change (use simple_enhancement_sequence) or complex enhancement requiring full planning."
- agent: fullstack-architect
action: Architecture Analysis
description: >-
Deep dive into service architecture and identify improvement opportunities
inputs:
- service-assessment
- existing-service-code
outputs:
- architecture-assessment
- refactoring-opportunities
- modernization-candidates
prompts:
- "Analyze the service architecture patterns"
- "Identify areas for modernization"
- step: service_analysis
agent: analyst
action: analyze existing service
notes: "Review existing service documentation, codebase, performance metrics, and identify integration dependencies."
- id: enhancement-planning
name: Service Enhancement Strategy
description: Plan service improvements and modernization approach
steps:
- agent: pm
action: Enhancement Strategy
description: >-
Define enhancement goals, priorities, and migration strategy
inputs:
- service-assessment
- architecture-assessment
outputs:
- enhancement-strategy
- migration-roadmap
- risk-assessment
prompts:
- "What are the primary enhancement goals?"
- "Define the migration strategy and timeline"
- agent: pm
creates: brownfield-prd.md
uses: brownfield-prd-tmpl
requires: existing_service_analysis
notes: "Creates comprehensive brownfield PRD focused on service enhancement with existing system analysis. SAVE OUTPUT: Copy final brownfield-prd.md to your project's docs/ folder."
- agent: fullstack-architect
action: Modernization Architecture
description: >-
Design target architecture for service modernization
inputs:
- enhancement-strategy
- modernization-candidates
outputs:
- target-architecture
- migration-patterns
- backward-compatibility-plan
prompts:
- "Design the target service architecture"
- "Plan for backward compatibility during migration"
- agent: architect
creates: brownfield-architecture.md
uses: brownfield-architecture-tmpl
requires: brownfield-prd.md
notes: "Creates brownfield architecture with service integration strategy and API evolution planning. SAVE OUTPUT: Copy final brownfield-architecture.md to your project's docs/ folder."
- id: incremental-refactoring
name: Incremental Refactoring Design
description: Design safe, incremental refactoring approach
steps:
- agent: fullstack-architect
action: Refactoring Strategy
description: >-
Design strangler fig pattern or other safe refactoring approaches
inputs:
- target-architecture
- integration-dependencies
outputs:
- refactoring-strategy
- service-extraction-plan
- data-migration-strategy
prompts:
- "Design strangler fig or parallel run strategy"
- "Plan service extraction and data migration"
- agent: po
validates: all_artifacts
uses: brownfield-checklist
notes: "Validates all brownfield documents for service integration safety and API compatibility. May require updates to any document."
- agent: devops
action: Infrastructure Evolution
description: >-
Plan infrastructure changes and deployment strategy
inputs:
- refactoring-strategy
- target-architecture
outputs:
- infrastructure-migration
- deployment-strategy
- monitoring-evolution
- scaling-improvements
prompts:
- "Plan infrastructure for new architecture"
- "Design zero-downtime deployment strategy"
- agent: various
updates: any_flagged_documents
condition: po_checklist_issues
notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
- id: api-evolution
name: API Versioning & Evolution
description: Plan API changes and versioning strategy
steps:
- agent: fullstack-architect
action: API Evolution Strategy
description: >-
Design API versioning and backward compatibility
inputs:
- target-architecture
- integration-dependencies
outputs:
- api-versioning-strategy
- contract-evolution-plan
- deprecation-timeline
prompts:
- "Design API versioning strategy"
- "Plan contract evolution and deprecation"
- workflow_end:
action: move_to_ide
notes: "All planning artifacts complete. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
- id: data-strategy
name: Data Migration & Consistency
description: Plan data migration and consistency strategies
steps:
- agent: fullstack-architect
action: Data Migration Planning
description: >-
Plan data migration, consistency, and synchronization
inputs:
- refactoring-strategy
- data-migration-strategy
outputs:
- data-migration-plan
- consistency-strategy
- rollback-procedures
prompts:
- "Plan data migration with zero data loss"
- "Design data consistency during transition"
# For Simple Service Enhancements (1-3 Stories, Following Existing Patterns)
simple_enhancement_sequence:
- step: enhancement_type
action: choose approach
notes: "Choose between creating single story (simple API endpoint) or epic (1-3 related service changes)."
- id: quality-assurance
name: Testing & Quality Strategy
description: Plan comprehensive testing for service changes
steps:
- agent: qa
action: Service Testing Strategy
description: >-
Design testing approach for service modernization
inputs:
- refactoring-strategy
- api-versioning-strategy
outputs:
- service-test-strategy
- contract-testing-plan
- performance-testing-plan
- chaos-testing-strategy
prompts:
- "Design comprehensive service testing"
- "Plan contract tests for API evolution"
- "Design chaos engineering tests"
- agent: pm|po|sm
creates: brownfield_epic OR brownfield_story
uses: brownfield-create-epic OR brownfield-create-story
notes: "Create focused service enhancement with existing API integration. Choose agent based on team preference and context."
- id: monitoring-observability
name: Enhanced Observability
description: Plan improved monitoring and observability
steps:
- agent: devops
action: Observability Enhancement
description: >-
Design enhanced monitoring, logging, and alerting
inputs:
- target-architecture
- performance-bottlenecks
outputs:
- observability-strategy
- sli-slo-definitions
- alerting-improvements
- dashboards-design
prompts:
- "Design comprehensive service observability"
- "Define SLIs and SLOs for the service"
- workflow_end:
action: move_to_ide
notes: "Service enhancement defined. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
- id: implementation-planning
name: Phased Implementation
description: Create detailed implementation plan
steps:
- agent: sm
action: Migration Story Planning
description: >-
Create stories for incremental service migration
inputs:
- migration-roadmap
- refactoring-strategy
outputs:
- migration-stories
- implementation-phases
- dependency-management
prompts:
- "Break down migration into safe phases"
- "Plan story dependencies and risks"
flow_diagram: |
```mermaid
graph TD
A[Start: Service Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing service]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[architect: brownfield-architecture.md]
F --> G[po: validate with brownfield-checklist]
G --> H{PO finds issues?}
H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment]
I --> G
D -->|1 Story| K[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
K --> M[Move to IDE Environment]
L --> M
style J fill:#90EE90
style M fill:#90EE90
style E fill:#FFE4B5
style F fill:#FFE4B5
style K fill:#FFB6C1
style L fill:#FFB6C1
```
transitions:
- from: service-analysis
to: enhancement-planning
condition: assessment complete
- from: enhancement-planning
to: incremental-refactoring
condition: strategy defined
- from: incremental-refactoring
to: api-evolution
condition: refactoring planned
- from: api-evolution
to: data-strategy
condition: api strategy defined
- from: data-strategy
to: quality-assurance
condition: data strategy planned
- from: quality-assurance
to: monitoring-observability
condition: testing planned
- from: monitoring-observability
to: implementation-planning
condition: observability designed
decision_guidance:
use_complex_sequence_when:
- Service enhancement requires multiple coordinated stories (4+)
- API versioning or breaking changes needed
- Database schema changes required
- Performance or scalability improvements needed
- Multiple integration points affected
special_considerations:
- name: Zero Downtime
description: Ensure service remains available during migration
- name: Data Integrity
description: Maintain data consistency throughout migration
- name: Client Impact
description: Minimize impact on service consumers
- name: Rollback Plan
description: Always have a way to revert changes safely
- name: Performance SLA
description: Maintain or improve existing performance SLAs
use_simple_sequence_when:
- Adding simple endpoints or modifying existing ones
- Enhancement follows existing service patterns
- API compatibility maintained
- Risk to existing service is low
- Change is isolated with clear boundaries
handoff_prompts:
analyst_to_pm: "Service analysis complete. Create comprehensive brownfield PRD with service integration strategy."
pm_to_architect: "Brownfield PRD ready. Save it as docs/brownfield-prd.md, then create the service architecture."
architect_to_po: "Architecture complete. Save it as docs/brownfield-architecture.md. Please validate all artifacts for service integration safety."
po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
simple_to_ide: "Service enhancement defined with existing API integration. Move to IDE environment to begin development."
complex_complete: "All brownfield planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."

302
agent-team-workflows/brownfield-ui.yml
View File

@@ -2,216 +2,126 @@ workflow:
id: brownfield-ui
name: Brownfield UI/Frontend Enhancement
description: >-
Workflow for modernizing, redesigning, or enhancing existing frontend applications.
Handles UI/UX improvements, framework migrations, and frontend refactoring.
Agent workflow for enhancing existing frontend applications with new features,
modernization, or design improvements. Handles existing UI analysis and safe integration.
type: brownfield
project_types:
- ui-modernization
- framework-migration
- design-refresh
- frontend-refactoring
- frontend-enhancement
stages:
- id: ui-analysis
name: Current UI Assessment
description: Analyze existing frontend and identify improvement areas
steps:
- agent: analyst
action: Frontend Assessment
description: >-
Analyze current frontend, user feedback, and performance issues
inputs:
- existing-frontend
- user-feedback
- analytics-data
outputs:
- frontend-assessment
- usability-issues
- performance-analysis
prompts:
- "Let's analyze the current frontend application"
- "What are users' main pain points with the current UI?"
- "Share analytics data or user feedback if available"
# For Complex UI Enhancements (Multiple Stories, Design Changes)
complex_enhancement_sequence:
- step: scope_assessment
agent: any
action: assess complexity
notes: "First, assess if this is a simple UI change (use simple_enhancement_sequence) or complex enhancement requiring full planning."
- agent: ux-expert
action: UX Audit
description: >-
Conduct comprehensive UX audit and competitive analysis
inputs:
- frontend-assessment
- user-feedback
outputs:
- ux-audit-report
- competitor-analysis
- accessibility-audit
prompts:
- "Let's audit the current user experience"
- "How do competitors handle similar flows?"
- step: ui_analysis
agent: analyst
action: analyze existing UI
notes: "Review existing frontend application, user feedback, analytics data, and identify improvement areas."
- id: enhancement-strategy
name: UI Enhancement Strategy
description: Define UI improvement strategy and goals
steps:
- agent: pm
action: UI Enhancement Planning
description: >-
Define enhancement goals, priorities, and success metrics
inputs:
- ux-audit-report
- usability-issues
outputs:
- ui-enhancement-strategy
- improvement-priorities
- success-metrics
prompts:
- "What are the priority UI improvements?"
- "Define success metrics for the redesign"
- agent: pm
creates: brownfield-prd.md
uses: brownfield-prd-tmpl
requires: existing_ui_analysis
notes: "Creates comprehensive brownfield PRD focused on UI enhancement with existing system analysis. SAVE OUTPUT: Copy final brownfield-prd.md to your project's docs/ folder."
- agent: ux-expert
action: Design Strategy
description: >-
Create design strategy and visual direction
inputs:
- ui-enhancement-strategy
- competitor-analysis
outputs:
- design-strategy
- visual-direction
- brand-evolution
prompts:
- "Define the new visual direction"
- "How should the brand evolve?"
- agent: ux-expert
creates: front-end-spec.md
uses: front-end-spec-tmpl
requires: brownfield-prd.md
notes: "Creates UI/UX specification for brownfield enhancement that integrates with existing design patterns. SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder."
- id: incremental-design
name: Incremental UI Design
description: Design improvements that can be rolled out incrementally
steps:
- agent: ux-expert
action: Progressive Design System
description: >-
Create new design system that can coexist with existing UI
inputs:
- design-strategy
- frontend-assessment
outputs:
- progressive-design-system
- component-migration-plan
- style-guide-evolution
prompts:
- "Design a system that can coexist with current UI"
- "Plan component-by-component migration"
- agent: ui-architect
creates: brownfield-architecture.md
uses: brownfield-architecture-tmpl
requires:
- brownfield-prd.md
- front-end-spec.md
notes: "Creates brownfield frontend architecture with component integration strategy and migration planning. SAVE OUTPUT: Copy final brownfield-architecture.md to your project's docs/ folder."
- agent: ui-architect
action: Frontend Migration Architecture
description: >-
Design technical approach for gradual frontend migration
inputs:
- progressive-design-system
- existing-frontend
outputs:
- migration-architecture
- component-strategy
- bundling-strategy
prompts:
- "Design incremental migration approach"
- "How to avoid breaking existing functionality?"
- agent: po
validates: all_artifacts
uses: brownfield-checklist
notes: "Validates all brownfield documents for UI integration safety and design consistency. May require updates to any document."
- id: user-validation
name: User Testing & Validation
description: Validate new designs with users
steps:
- agent: ux-expert
action: Prototype & Test
description: >-
Create prototypes and conduct user testing
inputs:
- progressive-design-system
- improvement-priorities
outputs:
- interactive-prototypes
- user-testing-results
- design-iterations
prompts:
- "Let's create testable prototypes"
- "Test with real users and iterate"
- agent: various
updates: any_flagged_documents
condition: po_checklist_issues
notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
- id: technical-planning
name: Implementation Planning
description: Plan technical implementation of UI changes
steps:
- agent: ui-architect
action: Technical Implementation Plan
description: >-
Create detailed technical plan for UI migration
inputs:
- migration-architecture
- design-iterations
outputs:
- implementation-roadmap
- risk-mitigation-plan
- rollback-strategy
prompts:
- "Create step-by-step implementation plan"
- "Plan for safe rollbacks if needed"
- workflow_end:
action: move_to_ide
notes: "All planning artifacts complete. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
- agent: qa
action: UI Testing Strategy
description: >-
Plan testing approach for UI changes
inputs:
- implementation-roadmap
- user-testing-results
outputs:
- ui-test-strategy
- visual-regression-tests
- cross-browser-testing
- accessibility-testing
prompts:
- "Plan comprehensive UI testing"
- "Ensure no regressions in existing flows"
# For Simple UI Enhancements (1-3 Stories, Following Existing Design)
simple_enhancement_sequence:
- step: enhancement_type
action: choose approach
notes: "Choose between creating single story (simple component change) or epic (1-3 related UI changes)."
- id: deployment-strategy
name: Gradual Rollout Planning
description: Plan safe deployment of UI changes
steps:
- agent: ui-architect
action: Feature Flag Strategy
description: >-
Design feature flagging for gradual UI rollout
inputs:
- implementation-roadmap
- risk-mitigation-plan
outputs:
- feature-flag-design
- a-b-testing-plan
- monitoring-strategy
prompts:
- "Design A/B testing for new UI components"
- "Plan feature flags for safe rollout"
- agent: pm|po|sm
creates: brownfield_epic OR brownfield_story
uses: brownfield-create-epic OR brownfield-create-story
notes: "Create focused UI enhancement with existing design system integration. Choose agent based on team preference and context."
transitions:
- from: ui-analysis
to: enhancement-strategy
condition: assessment complete
- from: enhancement-strategy
to: incremental-design
condition: strategy defined
- from: incremental-design
to: user-validation
condition: designs ready
- from: user-validation
to: technical-planning
condition: designs validated
- from: technical-planning
to: deployment-strategy
condition: implementation planned
- workflow_end:
action: move_to_ide
notes: "UI enhancement defined. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
special_considerations:
- name: User Adoption
description: Plan for user training and change management
- name: SEO Impact
description: Ensure URL structure and SEO aren't negatively affected
- name: Performance
description: Maintain or improve existing performance metrics
- name: Analytics
description: Preserve analytics tracking through UI changes
flow_diagram: |
```mermaid
graph TD
A[Start: UI Enhancement] --> B{Enhancement Complexity?}
B -->|Complex/Significant| C[analyst: analyze existing UI]
B -->|Simple| D{1 Story or 2-3 Stories?}
C --> E[pm: brownfield-prd.md]
E --> F[ux-expert: front-end-spec.md]
F --> G[ui-architect: brownfield-architecture.md]
G --> H[po: validate with brownfield-checklist]
H --> I{PO finds issues?}
I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K[Move to IDE Environment]
J --> H
D -->|1 Story| L[pm/po/sm: brownfield-create-story]
D -->|2-3 Stories| M[pm/po/sm: brownfield-create-epic]
L --> N[Move to IDE Environment]
M --> N
style K fill:#90EE90
style N fill:#90EE90
style E fill:#FFE4B5
style F fill:#FFE4B5
style G fill:#FFE4B5
style L fill:#FFB6C1
style M fill:#FFB6C1
```
decision_guidance:
use_complex_sequence_when:
- UI enhancement requires multiple coordinated stories (4+)
- Design system changes needed
- New component patterns required
- User research and testing needed
- Multiple team members will work on related changes
use_simple_sequence_when:
- Enhancement can be completed in 1-3 stories
- Follows existing design patterns exactly
- Component changes are isolated
- Risk to existing UI is low
- Change maintains current user experience
handoff_prompts:
analyst_to_pm: "UI analysis complete. Create comprehensive brownfield PRD with UI integration strategy."
pm_to_ux: "Brownfield PRD ready. Save it as docs/brownfield-prd.md, then create the UI/UX specification."
ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md, then create the frontend architecture."
architect_to_po: "Architecture complete. Save it as docs/brownfield-architecture.md. Please validate all artifacts for UI integration safety."
po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
simple_to_ide: "UI enhancement defined with existing design integration. Move to IDE environment to begin development."
complex_complete: "All brownfield planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."

125
agent-team-workflows/greenfield-fullstack.yml
View File

@@ -2,15 +2,18 @@ workflow:
id: greenfield-fullstack
name: Greenfield Full-Stack Application Development
description: >-
Agent workflow for building production-ready full-stack applications
from concept to development-ready artifacts.
Agent workflow for building full-stack applications from concept to development.
Supports both comprehensive planning for complex projects and rapid prototyping for simple ones.
type: greenfield
project_types:
- web-app
- saas
- enterprise-app
- prototype
- mvp
sequence:
# For Complex Projects (Production-Ready, Multiple Features)
complex_project_sequence:
- agent: analyst
creates: project-brief.md
optional_steps:
@@ -18,7 +21,7 @@ workflow:
- market_research_prompt
notes: "Can do brainstorming first, then optional deep research before creating project brief. SAVE OUTPUT: Copy final project-brief.md to your project's docs/ folder."
- agent: pm
- agent: pm
creates: prd.md
requires: project-brief.md
notes: "Creates PRD from project brief using prd-tmpl. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
@@ -38,7 +41,7 @@ workflow:
- agent: fullstack-architect
creates: fullstack-architecture.md
requires:
requires:
- prd.md
- front-end-spec.md
optional_steps:
@@ -75,47 +78,91 @@ workflow:
action: move_to_ide
notes: "All planning artifacts complete. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
# For Simple Projects (Prototypes, MVPs, Quick Experiments)
simple_project_sequence:
- step: project_scope
action: assess complexity
notes: "First, assess if this needs full planning (use complex_project_sequence) or can be a simple prototype/MVP."
- agent: analyst
creates: project-brief.md
optional_steps:
- brainstorming_session
notes: "Creates focused project brief for simple project. SAVE OUTPUT: Copy final project-brief.md to your project's docs/ folder."
- agent: pm
creates: simple_epic OR single_story
uses: create-epic OR create-story
requires: project-brief.md
notes: "Create simple epic or story instead of full PRD for rapid development. Choose based on scope."
- workflow_end:
action: move_to_ide
notes: "Simple project defined. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
flow_diagram: |
```mermaid
graph TD
A[Start] --> B[analyst: project-brief.md]
B --> C[pm: prd.md]
C --> D[ux-expert: front-end-spec.md]
D --> D2{Generate v0 prompt?}
D2 -->|Yes| D3[ux-expert: create v0 prompt]
D2 -->|No| E[fullstack-architect: fullstack-architecture.md]
D3 --> D4[User: generate UI in v0/Lovable]
D4 --> E
E --> F{Architecture suggests PRD changes?}
F -->|Yes| G[pm: update prd.md]
F -->|No| H[po: validate all artifacts]
G --> H
H --> I{PO finds issues?}
I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K{Generated UI?}
K -->|Yes| L[Guide project structure setup]
K -->|No| M[Guide development order]
L --> M
M --> N[Move to IDE Environment]
J --> H
A[Start: Greenfield Project] --> B{Project Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
B -.-> B1[Optional: brainstorming]
B -.-> B2[Optional: market research]
D -.-> D1[Optional: user research]
E -.-> E1[Optional: technical research]
C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?}
F2 -->|Yes| F3[ux-expert: create v0 prompt]
F2 -->|No| G[fullstack-architect: fullstack-architecture.md]
F3 --> F4[User: generate UI in v0/Lovable]
F4 --> G
G --> H{Architecture suggests PRD changes?}
H -->|Yes| I[pm: update prd.md]
H -->|No| J[po: validate all artifacts]
I --> J
J --> K{PO finds issues?}
K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment]
L --> J
style N fill:#90EE90
style D3 fill:#E6E6FA
style D4 fill:#E6E6FA
style L fill:#E6E6FA
style M fill:#E6E6FA
style B fill:#FFE4B5
D --> N[pm: simple epic or story]
N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style M fill:#90EE90
style O fill:#90EE90
style F3 fill:#E6E6FA
style F4 fill:#E6E6FA
style C fill:#FFE4B5
style D fill:#FFE4B5
style E fill:#FFE4B5
style F fill:#FFE4B5
style G fill:#FFE4B5
style D fill:#FFB6C1
style N fill:#FFB6C1
```
decision_guidance:
use_complex_sequence_when:
- Building production-ready applications
- Multiple team members will be involved
- Complex feature requirements (4+ stories)
- Need comprehensive documentation
- Long-term maintenance expected
- Enterprise or customer-facing applications
use_simple_sequence_when:
- Building prototypes or MVPs
- Solo developer or small team
- Simple requirements (1-3 stories)
- Quick experiments or proof-of-concepts
- Short-term or throwaway projects
- Learning or educational projects
handoff_prompts:
# Complex sequence prompts
analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD."
pm_to_ux: "PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification."
ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the fullstack architecture."
@@ -123,4 +170,8 @@ workflow:
architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/."
updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
workflow_complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
complex_complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
# Simple sequence prompts
simple_analyst_to_pm: "Focused project brief complete. Save it as docs/project-brief.md, then create simple epic or story for rapid development."
simple_complete: "Simple project defined. Move to IDE environment to begin development."

99
agent-team-workflows/greenfield-service.yml
View File

@@ -2,16 +2,19 @@ workflow:
id: greenfield-service
name: Greenfield Service/API Development
description: >-
Agent workflow for building REST APIs, GraphQL services, or microservices
without frontend requirements.
Agent workflow for building backend services from concept to development.
Supports both comprehensive planning for complex services and rapid prototyping for simple APIs.
type: greenfield
project_types:
- rest-api
- graphql-api
- microservice
- backend-service
- api-prototype
- simple-service
sequence:
# For Complex Services (Production APIs, Multiple Endpoints)
complex_service_sequence:
- agent: analyst
creates: project-brief.md
optional_steps:
@@ -51,36 +54,90 @@ workflow:
action: move_to_ide
notes: "All planning artifacts complete. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
# For Simple Services (Simple APIs, Single Purpose Services)
simple_service_sequence:
- step: service_scope
action: assess complexity
notes: "First, assess if this needs full planning (use complex_service_sequence) or can be a simple API/service."
- agent: analyst
creates: project-brief.md
optional_steps:
- brainstorming_session
notes: "Creates focused project brief for simple service. SAVE OUTPUT: Copy final project-brief.md to your project's docs/ folder."
- agent: pm
creates: simple_epic OR single_story
uses: create-epic OR create-story
requires: project-brief.md
notes: "Create simple epic or story for API endpoints instead of full PRD for rapid development."
- workflow_end:
action: move_to_ide
notes: "Simple service defined. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
flow_diagram: |
```mermaid
graph TD
A[Start] --> B[analyst: project-brief.md]
B --> C[pm: prd.md]
C --> D[architect: architecture.md]
D --> E{Architecture suggests PRD changes?}
E -->|Yes| F[pm: update prd.md]
E -->|No| G[po: validate all artifacts]
F --> G
G --> H{PO finds issues?}
H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment]
I --> G
A[Start: Service Development] --> B{Service Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
B -.-> B1[Optional: brainstorming]
B -.-> B2[Optional: market research]
D -.-> D1[Optional: technical research]
C --> E[pm: prd.md]
E --> F[architect: architecture.md]
F --> G{Architecture suggests PRD changes?}
G -->|Yes| H[pm: update prd.md]
G -->|No| I[po: validate all artifacts]
H --> I
I --> J{PO finds issues?}
J -->|Yes| K[Return to relevant agent for fixes]
J -->|No| L[Move to IDE Environment]
K --> I
style J fill:#90EE90
style B fill:#FFE4B5
D --> M[pm: simple epic or story]
M --> N[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style L fill:#90EE90
style N fill:#90EE90
style C fill:#FFE4B5
style D fill:#FFE4B5
style E fill:#FFE4B5
style F fill:#FFE4B5
style D fill:#FFB6C1
style M fill:#FFB6C1
```
decision_guidance:
use_complex_sequence_when:
- Building production APIs or microservices
- Multiple endpoints and complex business logic
- Need comprehensive documentation and testing
- Multiple team members will be involved
- Long-term maintenance expected
- Enterprise or external-facing APIs
use_simple_sequence_when:
- Building simple APIs or single-purpose services
- Few endpoints with straightforward logic
- Prototyping or proof-of-concept APIs
- Solo developer or small team
- Internal tools or utilities
- Learning or experimental projects
handoff_prompts:
# Complex sequence prompts
analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD."
pm_to_architect: "PRD is ready. Save it as docs/prd.md in your project, then create the service architecture."
architect_review: "Architecture complete. Save it as docs/architecture.md. Do you suggest any changes to the PRD stories or need new stories added?"
architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/."
updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
workflow_complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
complex_complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
# Simple sequence prompts
simple_analyst_to_pm: "Focused project brief complete. Save it as docs/project-brief.md, then create simple epic or story for API development."
simple_complete: "Simple service defined. Move to IDE environment to begin development."

117
agent-team-workflows/greenfield-ui.yml
View File

@@ -2,16 +2,19 @@ workflow:
id: greenfield-ui
name: Greenfield UI/Frontend Development
description: >-
Agent workflow for building frontend applications that consume existing APIs.
Perfect for SPAs, mobile apps, or micro-frontends.
Agent workflow for building frontend applications from concept to development.
Supports both comprehensive planning for complex UIs and rapid prototyping for simple interfaces.
type: greenfield
project_types:
- spa
- mobile-app
- micro-frontend
- static-site
- ui-prototype
- simple-interface
sequence:
# For Complex UIs (Production Apps, Multiple Views)
complex_ui_sequence:
- agent: analyst
creates: project-brief.md
optional_steps:
@@ -70,45 +73,91 @@ workflow:
action: move_to_ide
notes: "All planning artifacts complete. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
# For Simple UIs (Simple Interfaces, Few Components)
simple_ui_sequence:
- step: ui_scope
action: assess complexity
notes: "First, assess if this needs full planning (use complex_ui_sequence) or can be a simple interface."
- agent: analyst
creates: project-brief.md
optional_steps:
- brainstorming_session
notes: "Creates focused project brief for simple UI. SAVE OUTPUT: Copy final project-brief.md to your project's docs/ folder."
- agent: ux-expert
creates: simple_wireframes OR quick_spec
uses: create-epic OR create-story
requires: project-brief.md
notes: "Create simple wireframes and component list instead of full UI/UX spec for rapid development."
- workflow_end:
action: move_to_ide
notes: "Simple UI defined. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
flow_diagram: |
```mermaid
graph TD
A[Start] --> B[analyst: project-brief.md]
B --> C[pm: prd.md]
C --> D[ux-expert: front-end-spec.md]
D --> D2{Generate v0 prompt?}
D2 -->|Yes| D3[ux-expert: create v0 prompt]
D2 -->|No| E[ui-architect: front-end-architecture.md]
D3 --> D4[User: generate UI in v0/Lovable]
D4 --> E
E --> F{Architecture suggests PRD changes?}
F -->|Yes| G[pm: update prd.md]
F -->|No| H[po: validate all artifacts]
G --> H
H --> I{PO finds issues?}
I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K{Generated UI?}
K -->|Yes| L[Guide project structure setup]
K -->|No| M[Move to IDE Environment]
L --> M
J --> H
A[Start: UI Development] --> B{UI Complexity?}
B -->|Complex/Production| C[analyst: project-brief.md]
B -->|Simple/Prototype| D[analyst: focused project-brief.md]
B -.-> B1[Optional: brainstorming]
B -.-> B2[Optional: market research]
D -.-> D1[Optional: user research]
E -.-> E1[Optional: technical research]
C --> E[pm: prd.md]
E --> F[ux-expert: front-end-spec.md]
F --> F2{Generate v0 prompt?}
F2 -->|Yes| F3[ux-expert: create v0 prompt]
F2 -->|No| G[ui-architect: front-end-architecture.md]
F3 --> F4[User: generate UI in v0/Lovable]
F4 --> G
G --> H{Architecture suggests PRD changes?}
H -->|Yes| I[pm: update prd.md]
H -->|No| J[po: validate all artifacts]
I --> J
J --> K{PO finds issues?}
K -->|Yes| L[Return to relevant agent for fixes]
K -->|No| M[Move to IDE Environment]
L --> J
D --> N[ux-expert: simple wireframes]
N --> O[Move to IDE Environment]
C -.-> C1[Optional: brainstorming]
C -.-> C2[Optional: market research]
F -.-> F1[Optional: user research]
G -.-> G1[Optional: technical research]
D -.-> D1[Optional: brainstorming]
style M fill:#90EE90
style D3 fill:#E6E6FA
style D4 fill:#E6E6FA
style L fill:#E6E6FA
style B fill:#FFE4B5
style O fill:#90EE90
style F3 fill:#E6E6FA
style F4 fill:#E6E6FA
style C fill:#FFE4B5
style D fill:#FFE4B5
style E fill:#FFE4B5
style F fill:#FFE4B5
style G fill:#FFE4B5
style D fill:#FFB6C1
style N fill:#FFB6C1
```
decision_guidance:
use_complex_sequence_when:
- Building production frontend applications
- Multiple views/pages with complex interactions
- Need comprehensive UI/UX design and testing
- Multiple team members will be involved
- Long-term maintenance expected
- Customer-facing applications
use_simple_sequence_when:
- Building simple interfaces or prototypes
- Few views with straightforward interactions
- Internal tools or admin interfaces
- Solo developer or small team
- Quick experiments or proof-of-concepts
- Learning or educational projects
handoff_prompts:
# Complex sequence prompts
analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD."
pm_to_ux: "PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification."
ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the frontend architecture."
@@ -116,4 +165,8 @@ workflow:
architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/."
updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
workflow_complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
complex_complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
# Simple sequence prompts
simple_analyst_to_ux: "Focused project brief complete. Save it as docs/project-brief.md, then create simple wireframes for rapid development."
simple_complete: "Simple UI defined. Move to IDE environment to begin development."