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

brownfield experimental docs added to templates

Browse Source
This commit is contained in:
Brian Madison
2025-06-08 19:22:57 -05:00
parent f1fa6256f0
commit 460c47f5c8
34 changed files with 1872 additions and 1848 deletions
Download Patch File Download Diff File Expand all files Collapse all files

188
agent-team-workflows/api-only.yml
View File

@@ -1,188 +0,0 @@
workflow:
id: api-only
name: API-First Development
description: >-
Workflow for building REST APIs, GraphQL services, or microservices
without frontend components.
type: greenfield
project_types:
- rest-api
- graphql-api
- microservice
- backend-service
stages:
- id: api-discovery
name: API Requirements Discovery
description: Understand API consumers and requirements
steps:
- agent: analyst
action: API Requirements Analysis
description: >-
Analyze API consumers, use cases, and integration requirements
outputs:
- api-requirements
- consumer-analysis
prompts:
- "Who will consume this API? Internal services, mobile apps, third parties?"
- "What are the main operations and data flows?"
- id: api-design
name: API Product Design
description: Design API as a product
steps:
- agent: pm
action: API Product Strategy
description: >-
Define API product strategy, versioning, and roadmap
inputs:
- api-requirements
outputs:
- api-product-spec
- api-roadmap
prompts:
- "What's the API versioning strategy?"
- "How will the API evolve over time?"
- agent: architect
action: API Architecture Design
description: >-
Design RESTful resources, GraphQL schema, or service contracts
inputs:
- api-product-spec
outputs:
- api-design-doc
- openapi-spec
- data-contracts
prompts:
- "Let's design the API endpoints and data models"
- "Define authentication and authorization strategy"
- id: technical-design
name: Technical Architecture
description: Design backend architecture and infrastructure
steps:
- agent: architect
action: Backend Architecture
description: >-
Design service architecture, database, and integrations
inputs:
- api-design-doc
outputs:
- backend-architecture
- database-design
- integration-architecture
prompts:
- "Design the service layer architecture"
- "What databases and caching strategies?"
- agent: devops
action: API Infrastructure
description: >-
Design API gateway, rate limiting, monitoring, and deployment
inputs:
- backend-architecture
outputs:
- api-infrastructure
- monitoring-strategy
- deployment-plan
prompts:
- "Design API gateway and rate limiting"
- "Define monitoring and alerting strategy"
- id: validation
name: API Design Validation
description: Validate API design and documentation
steps:
- agent: po
action: API Design Review
description: >-
Review API design for completeness and usability
inputs:
- api-design-doc
- openapi-spec
outputs:
- api-validation-report
- api-documentation
prompts:
- "Review API design for developer experience"
- "Is the API documentation complete?"
- id: development-planning
name: Implementation Planning
description: Plan API implementation sprints
steps:
- agent: sm
action: API Development Stories
description: >-
Create stories for endpoints, middleware, and infrastructure
inputs:
- api-design-doc
- backend-architecture
outputs:
- api-stories
- implementation-plan
prompts:
- "Break down API into implementation stories"
- "Prioritize endpoints for phased delivery"
- agent: qa
action: API Test Planning
description: >-
Create API testing strategy and automation plan
inputs:
- openapi-spec
- api-stories
outputs:
- api-test-strategy
- contract-tests
- performance-tests
prompts:
- "Design API contract testing approach"
- "Plan load testing and performance benchmarks"
- id: developer-experience
name: Developer Experience
description: Prepare API for developers
steps:
- agent: dev
action: SDK & Documentation Planning
description: >-
Plan SDK development and interactive documentation
inputs:
- openapi-spec
- api-documentation
outputs:
- sdk-requirements
- doc-portal-plan
prompts:
- "Which language SDKs are needed?"
- "Plan interactive API documentation"
transitions:
- from: api-discovery
to: api-design
condition: requirements analyzed
- from: api-design
to: technical-design
condition: api spec completed
- from: technical-design
to: validation
condition: architecture completed
- from: validation
to: development-planning
condition: design approved
- from: development-planning
to: developer-experience
condition: stories created
artifacts:
openapi-spec:
format: openapi-3.0
description: Complete API specification
api-design-doc:
template: api-design-tmpl
description: API design decisions and patterns
contract-tests:
format: postman-collection
description: API contract test suite

229
agent-team-workflows/backend-service.yml
View File

@@ -1,229 +0,0 @@
workflow:
id: backend-service
name: Backend Service Development
description: >-
Workflow for building microservices, backend APIs, or data processing services
with focus on scalability, reliability, and maintainability.
type: greenfield
project_types:
- microservice
- data-pipeline
- background-worker
- event-processor
stages:
- id: service-discovery
name: Service Requirements
description: Define service boundaries and responsibilities
steps:
- agent: analyst
action: Service Analysis
description: >-
Analyze service requirements, boundaries, and integrations
outputs:
- service-brief
- integration-requirements
- data-flow-analysis
prompts:
- "What is this service's primary responsibility?"
- "What other services will it interact with?"
- "What are the data input/output requirements?"
- id: service-design
name: Service Design
description: Design service architecture and contracts
steps:
- agent: architect
action: Service Architecture
description: >-
Design service internals, API contracts, and data models
inputs:
- service-brief
- integration-requirements
outputs:
- service-architecture
- api-contracts
- event-schemas
- data-models
prompts:
- "Design the service architecture pattern"
- "Define API contracts and event schemas"
- "Choose appropriate data storage solutions"
- agent: architect
action: Integration Design
description: >-
Design service mesh, messaging, and integration patterns
inputs:
- service-architecture
- integration-requirements
outputs:
- integration-architecture
- messaging-patterns
- service-mesh-config
prompts:
- "Design inter-service communication"
- "Choose messaging patterns (sync/async)"
- "Define service discovery approach"
- id: reliability-design
name: Reliability & Performance
description: Design for production reliability
steps:
- agent: devops
action: Production Architecture
description: >-
Design deployment, scaling, and reliability features
inputs:
- service-architecture
outputs:
- deployment-architecture
- scaling-strategy
- reliability-patterns
- observability-design
prompts:
- "Design auto-scaling and load balancing"
- "Plan fault tolerance and circuit breakers"
- "Design comprehensive observability"
- agent: architect
action: Performance Design
description: >-
Design caching, optimization, and performance strategies
inputs:
- service-architecture
- data-flow-analysis
outputs:
- performance-architecture
- caching-strategy
- query-optimization
prompts:
- "Identify performance bottlenecks"
- "Design caching layers"
- "Optimize data access patterns"
- id: security-design
name: Security Architecture
description: Design security controls and compliance
steps:
- agent: architect
action: Security Design
description: >-
Design authentication, authorization, and data security
inputs:
- service-architecture
- api-contracts
outputs:
- security-architecture
- auth-design
- encryption-strategy
- compliance-controls
prompts:
- "Design authentication and authorization"
- "Plan data encryption at rest and in transit"
- "Address compliance requirements"
- id: validation
name: Architecture Validation
description: Validate complete service design
steps:
- agent: po
action: Service Design Review
description: >-
Review service design for completeness and alignment
inputs:
- service-architecture
- integration-architecture
- security-architecture
outputs:
- design-approval
- risk-assessment
prompts:
- "Review service boundaries and responsibilities"
- "Validate non-functional requirements"
- id: implementation-planning
name: Implementation Planning
description: Plan service implementation
steps:
- agent: sm
action: Service Implementation Stories
description: >-
Create implementation stories with clear boundaries
inputs:
- service-architecture
- api-contracts
outputs:
- implementation-stories
- api-development-plan
- integration-test-plan
prompts:
- "Break down into implementation stories"
- "Define story dependencies"
- "Plan incremental delivery"
- agent: qa
action: Service Testing Strategy
description: >-
Design testing strategy for distributed systems
inputs:
- service-architecture
- integration-architecture
outputs:
- test-strategy
- contract-testing-plan
- chaos-testing-plan
- performance-test-plan
prompts:
- "Design contract testing approach"
- "Plan chaos engineering tests"
- "Define performance benchmarks"
- id: operational-readiness
name: Operational Readiness
description: Prepare for production deployment
steps:
- agent: devops
action: Production Readiness
description: >-
Create runbooks, monitoring, and deployment procedures
inputs:
- deployment-architecture
- observability-design
outputs:
- runbooks
- monitoring-dashboards
- alert-rules
- deployment-procedures
prompts:
- "Create operational runbooks"
- "Design monitoring dashboards"
- "Define SLIs and SLOs"
transitions:
- from: service-discovery
to: service-design
condition: requirements defined
- from: service-design
to: reliability-design
condition: architecture completed
- from: reliability-design
to: security-design
condition: reliability planned
- from: security-design
to: validation
condition: security designed
- from: validation
to: implementation-planning
condition: design approved
- from: implementation-planning
to: operational-readiness
condition: stories created
key_artifacts:
- Service architecture document
- API contracts and schemas
- Integration architecture
- Security controls
- Operational runbooks
- Test strategies

8
agent-team-workflows/brownfield-enhancement.yml → agent-team-workflows/brownfield-fullstack.yml
View File

@@ -1,6 +1,6 @@
workflow:
id: brownfield-enhancement
name: Brownfield Enhancement
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.
@@ -33,7 +33,7 @@ workflow:
- "Share any existing documentation or system diagrams"
- "You can also share the codebase if you have access to it"
- agent: dev
- agent: fullstack-architect
action: Code Analysis
description: >-
Deep dive into codebase quality and structure
@@ -66,7 +66,7 @@ workflow:
- "What specific enhancements are we targeting?"
- "Define success metrics for these improvements"
- agent: architect
- agent: fullstack-architect
action: Integration Architecture
description: >-
Design how new features integrate with existing system

253
agent-team-workflows/brownfield-service.yml Normal file
View File

@@ -0,0 +1,253 @@
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.
type: brownfield
project_types:
- service-modernization
- api-enhancement
- microservice-extraction
- performance-optimization
- technical-debt-reduction
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"
- 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"
- 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: 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"
- 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: 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"
- 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"
- 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"
- 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"
- 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"
- 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"
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
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

217
agent-team-workflows/brownfield-ui.yml Normal file
View File

@@ -0,0 +1,217 @@
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.
type: brownfield
project_types:
- ui-modernization
- framework-migration
- design-refresh
- frontend-refactoring
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"
- 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?"
- 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: 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?"
- 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
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?"
- 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"
- 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"
- 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"
- 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"
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
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

219
agent-team-workflows/frontend-only.yml
View File

@@ -1,219 +0,0 @@
workflow:
id: frontend-only
name: Frontend Application Development
description: >-
Workflow for building frontend applications that consume existing APIs.
Perfect for SPAs, mobile apps, or micro-frontends.
type: greenfield
project_types:
- spa
- mobile-app
- micro-frontend
- static-site
stages:
- id: frontend-discovery
name: Frontend Requirements
description: Understand user needs and API constraints
steps:
- agent: analyst
action: Frontend Analysis
description: >-
Analyze user needs, existing APIs, and frontend requirements
inputs:
- api-documentation
- user-requirements
outputs:
- frontend-brief
- api-integration-plan
prompts:
- "What APIs will the frontend consume?"
- "What are the key user interactions?"
- id: ux-design
name: User Experience Design
description: Design complete user experience
steps:
- agent: ux-expert
action: Complete UX Process
description: >-
User research, personas, flows, wireframes, and prototypes
inputs:
- frontend-brief
outputs:
- user-research
- personas
- user-flows
- wireframes
- interactive-prototype
prompts:
- "Let's understand your users deeply"
- "Design the complete user journey"
- agent: ux-expert
action: Visual Design
description: >-
Create visual designs and style guide
inputs:
- wireframes
- brand-guidelines
outputs:
- visual-designs
- style-guide
- design-tokens
prompts:
- "Create the visual language"
- "Define colors, typography, and spacing"
- id: frontend-architecture
name: Frontend Technical Design
description: Design frontend architecture and components
steps:
- agent: ui-architect
action: Frontend Architecture
description: >-
Design component architecture, state management, and routing
inputs:
- interactive-prototype
- api-integration-plan
outputs:
- frontend-architecture
- component-hierarchy
- state-management-design
- routing-design
prompts:
- "Design the frontend architecture"
- "Choose framework and design patterns"
- agent: ui-architect
action: Component Design System
description: >-
Create detailed component specifications and AI generation prompts
inputs:
- visual-designs
- design-tokens
outputs:
- component-library-spec
- ai-generation-prompts
- accessibility-guidelines
prompts:
- "Design reusable component system"
- "Create prompts for AI UI generation"
- id: api-integration
name: API Integration Planning
description: Plan API integration and data flow
steps:
- agent: fullstack-architect
action: Integration Architecture
description: >-
Design API integration, data fetching, and caching strategies
inputs:
- api-documentation
- frontend-architecture
outputs:
- integration-patterns
- data-flow-design
- error-handling-strategy
- caching-strategy
prompts:
- "Design efficient API integration"
- "Plan offline capabilities if needed"
- id: performance-planning
name: Performance & Optimization
description: Plan for optimal performance
steps:
- agent: ui-architect
action: Performance Strategy
description: >-
Design performance optimization and PWA features
inputs:
- frontend-architecture
outputs:
- performance-budget
- optimization-strategy
- pwa-features
prompts:
- "Set performance budgets"
- "Plan lazy loading and code splitting"
- id: validation
name: Design Validation
description: Validate all frontend designs
steps:
- agent: po
action: Frontend Validation
description: >-
Validate UX, technical design, and accessibility
inputs:
- visual-designs
- frontend-architecture
- component-library-spec
outputs:
- design-approval
- accessibility-review
prompts:
- "Review all designs for consistency"
- "Validate accessibility compliance"
- id: development-planning
name: Frontend Development Planning
description: Plan implementation sprints
steps:
- agent: sm
action: Frontend Stories
description: >-
Create component and feature stories
inputs:
- component-library-spec
- frontend-architecture
outputs:
- component-stories
- feature-stories
- sprint-plan
prompts:
- "Break down into component stories"
- "Plan progressive enhancement"
- agent: qa
action: Frontend Testing Strategy
description: >-
Plan unit, integration, and E2E testing
inputs:
- component-stories
- user-flows
outputs:
- test-strategy
- e2e-test-scenarios
- visual-regression-tests
prompts:
- "Design component testing approach"
- "Plan E2E test scenarios"
transitions:
- from: frontend-discovery
to: ux-design
condition: requirements understood
- from: ux-design
to: frontend-architecture
condition: designs completed
- from: frontend-architecture
to: api-integration
condition: architecture defined
- from: api-integration
to: performance-planning
condition: integration planned
- from: performance-planning
to: validation
condition: optimization planned
- from: validation
to: development-planning
condition: designs approved
deliverables:
- Interactive prototype
- Component library specification
- AI UI generation prompts
- Frontend architecture document
- Performance optimization plan

227
agent-team-workflows/fullstack-app.yml
View File

@@ -1,227 +0,0 @@
workflow:
id: fullstack-app
name: Full-Stack Application Development
description: >-
Comprehensive workflow for building production-ready full-stack applications
with emphasis on UI/UX and scalable architecture.
type: greenfield
project_types:
- web-app
- saas
- enterprise-app
stages:
- id: discovery
name: Discovery & Analysis
description: Deep dive into requirements and market analysis
steps:
- agent: analyst
action: Market & Requirements Analysis
description: >-
Analyze market, competitors, and gather detailed requirements
outputs:
- project-brief
- market-analysis
prompts:
- "Let's analyze the market landscape for your application"
- "What are your competitive advantages?"
- id: product-design
name: Product Design
description: Create comprehensive product specifications
steps:
- agent: pm
action: Create Detailed PRD
description: >-
Create comprehensive PRD with user stories and success metrics
inputs:
- project-brief
- market-analysis
outputs:
- prd
- success-metrics
prompts:
- "Let's define detailed features and user stories"
- "What metrics will measure success?"
- agent: ux-expert
action: Complete UX Design
description: >-
Create user research, personas, flows, and detailed wireframes
inputs:
- prd
outputs:
- user-personas
- user-flows
- wireframes
- ui-specifications
prompts:
- "Let's create detailed user personas"
- "Time to design the complete user experience"
- id: ui-development
name: UI Design & Prototyping
description: Create high-fidelity designs and interactive prototypes
steps:
- agent: ui-architect
action: UI Architecture & Design System
description: >-
Create design system, component library specs, and UI architecture
inputs:
- wireframes
- ui-specifications
outputs:
- design-system
- component-specs
- ui-architecture
prompts:
- "Let's create a scalable design system"
- "Define reusable component architecture"
- agent: ux-expert
action: Generate UI Components
description: >-
Create AI prompts and generate actual UI components
inputs:
- design-system
- component-specs
outputs:
- ui-generation-prompts
- generated-components
prompts:
- "Let's create prompts for AI UI generation"
- "Generate the core UI components"
- id: technical-architecture
name: System Architecture
description: Design complete technical architecture
steps:
- agent: fullstack-architect
action: System Architecture Design
description: >-
Design complete system including microservices, APIs, and infrastructure
inputs:
- prd
- ui-architecture
outputs:
- system-architecture
- api-specifications
- data-models
prompts:
- "Design the complete system architecture"
- "Define API contracts and data models"
- agent: architect
action: Backend Architecture
description: >-
Detail backend services, integrations, and technical specifications
inputs:
- system-architecture
- api-specifications
outputs:
- backend-architecture
- integration-specs
prompts:
- "Detail the backend service architecture"
- "Define third-party integrations"
- agent: devops
action: Infrastructure Design
description: >-
Design cloud infrastructure, CI/CD, and deployment architecture
inputs:
- system-architecture
outputs:
- infrastructure-design
- deployment-architecture
- ci-cd-pipeline
prompts:
- "Design the cloud infrastructure"
- "Create CI/CD pipeline specifications"
- id: validation
name: Comprehensive Validation
description: Validate all artifacts and ensure alignment
steps:
- agent: po
action: Full Artifact Validation
description: >-
Validate all documents, ensure alignment, and approve for development
inputs:
- prd
- system-architecture
- ui-architecture
- infrastructure-design
outputs:
- validation-report
- approved-artifacts
prompts:
- "Complete validation of all artifacts"
- "Any final adjustments needed?"
- id: development-planning
name: Sprint Planning
description: Create detailed development plan and stories
steps:
- agent: sm
action: Create Sprint Plan
description: >-
Create epics, user stories, and detailed sprint plan
inputs:
- approved-artifacts
outputs:
- epics
- user-stories
- sprint-plan
- definition-of-done
prompts:
- "Let's break this into epics and stories"
- "Create the sprint roadmap"
- id: quality-planning
name: Quality Assurance Planning
description: Define testing strategy and quality metrics
steps:
- agent: qa
action: Test Strategy & Planning
description: >-
Create comprehensive test strategy and automation plan
inputs:
- prd
- system-architecture
- user-stories
outputs:
- test-strategy
- test-cases
- automation-plan
prompts:
- "Define the testing strategy"
- "Plan test automation approach"
transitions:
- from: discovery
to: product-design
condition: project-brief completed
- from: product-design
to: ui-development
condition: prd and wireframes completed
- from: ui-development
to: technical-architecture
condition: ui components designed
- from: technical-architecture
to: validation
condition: all architecture completed
- from: validation
to: development-planning
condition: artifacts approved
- from: development-planning
to: quality-planning
condition: stories created
checkpoints:
- after: product-design
review: Stakeholder review of PRD and UX
- after: technical-architecture
review: Architecture review board
- after: validation
review: Final go/no-go decision

126
agent-team-workflows/greenfield-fullstack.yml Normal file
View File

@@ -0,0 +1,126 @@
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.
type: greenfield
project_types:
- web-app
- saas
- enterprise-app
sequence:
- agent: analyst
creates: project-brief.md
optional_steps:
- brainstorming_session
- 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
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."
- agent: ux-expert
creates: front-end-spec.md
requires: prd.md
optional_steps:
- user_research_prompt
notes: "Creates UI/UX specification using front-end-spec-tmpl. SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder."
- agent: ux-expert
creates: v0_prompt (optional)
requires: front-end-spec.md
condition: user_wants_ai_generation
notes: "OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure."
- agent: fullstack-architect
creates: fullstack-architecture.md
requires:
- prd.md
- front-end-spec.md
optional_steps:
- technical_research_prompt
- review_generated_ui_structure
notes: "Creates comprehensive architecture using fullstack-architecture-tmpl. If user generated UI with v0/Lovable, can incorporate the project structure into architecture. May suggest changes to PRD stories or new stories. SAVE OUTPUT: Copy final fullstack-architecture.md to your project's docs/ folder."
- agent: pm
updates: prd.md (if needed)
requires: fullstack-architecture.md
condition: architecture_suggests_prd_changes
notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder."
- agent: po
validates: all_artifacts
uses: po-master-checklist
notes: "Validates all documents for consistency and completeness. May require updates to any document."
- 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."
- project_setup_guidance:
action: guide_project_structure
condition: user_has_generated_ui
notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance."
- development_order_guidance:
action: guide_development_sequence
notes: "Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order."
- 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"
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
B -.-> B1[Optional: brainstorming]
B -.-> B2[Optional: market research]
D -.-> D1[Optional: user research]
E -.-> E1[Optional: technical research]
style N fill:#90EE90
style D3 fill:#E6E6FA
style D4 fill:#E6E6FA
style L fill:#E6E6FA
style M fill:#E6E6FA
style B fill:#FFE4B5
style C fill:#FFE4B5
style D fill:#FFE4B5
style E fill:#FFE4B5
```
handoff_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."
architect_review: "Architecture complete. Save it as docs/fullstack-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."

179
agent-team-workflows/greenfield-mvp.yml
View File

@@ -1,179 +0,0 @@
workflow:
id: greenfield-mvp
name: Greenfield MVP Development
description: >-
Complete workflow for building a new MVP from scratch. Takes you from initial
idea through planning, architecture, and development setup.
type: greenfield
project_types:
- web-app
- mobile-app
- full-stack
- app with microservice rest api
stages:
- id: discovery
name: Discovery & Requirements
description: Understand the problem space and gather requirements
steps:
- agent: analyst
action: Create Project Brief
description: >-
Brainstorm and document the project vision, goals, and high-level requirements
outputs:
- project-brief
prompts:
- "Let's explore your project idea. What problem are you trying to solve?"
- "Who are your target users and what are their main pain points?"
- id: planning
name: Product Planning
description: Define the product and create detailed requirements
steps:
- agent: pm
action: Create PRD
description: >-
Transform the project brief into a comprehensive Product Requirements Document
inputs:
- project-brief
outputs:
- prd
prompts:
- "Based on the project brief, let's define the MVP features"
- "What are the must-have features vs nice-to-have for launch?"
- agent: ux-expert
action: Design UX Strategy
description: >-
Create user flows, wireframes, and UI specifications
inputs:
- prd
outputs:
- ux-strategy
- ui-specifications
prompts:
- "Let's map out the user journey for the core features"
- "What UI patterns best serve your users' needs?"
- id: architecture
name: Technical Architecture
description: Design the system architecture and technical approach
steps:
- agent: fullstack-architect
action: Create Architecture Document
description: >-
Design comprehensive system architecture covering all layers
inputs:
- prd
- ui-specifications
outputs:
- architecture-doc
prompts:
- "Let's design a scalable architecture for your MVP"
- "What are your performance and scaling requirements?"
- agent: ui-architect
action: Create Frontend Architecture
description: >-
Detail the frontend architecture and component design
inputs:
- architecture-doc
- ui-specifications
outputs:
- frontend-architecture
- ui-prompt-specs
prompts:
- "Let's define the frontend stack and component architecture"
- "Should we generate UI components with AI assistance?"
- id: validation
name: Validation & Refinement
description: Review and validate all planning artifacts
steps:
- agent: po
action: Validate Artifacts
description: >-
Review all documents for consistency and completeness
inputs:
- project-brief
- prd
- architecture-doc
- frontend-architecture
outputs:
- validation-report
- change-requests
prompts:
- "Let's review all artifacts for consistency"
- "Are there any gaps or conflicts to address?"
- id: development-planning
name: Development Planning
description: Create actionable development stories
steps:
- agent: sm
action: Create User Stories
description: >-
Break down requirements into sprint-ready user stories
inputs:
- prd
- architecture-doc
- validation-report
outputs:
- user-stories
- sprint-plan
prompts:
- "Let's create the first sprint's user stories"
- "How should we prioritize the backlog?"
- id: development-handoff
name: Development Handoff
description: Transition to implementation phase
steps:
- agent: dev
action: Development Setup
description: >-
Review all artifacts and set up development environment
inputs:
- architecture-doc
- frontend-architecture
- user-stories
outputs:
- dev-environment
- implementation-plan
prompts:
- "Let's set up the development environment"
- "Ready to start implementing the first story?"
transitions:
- from: discovery
to: planning
condition: project-brief completed
- from: planning
to: architecture
condition: prd and ui-specifications completed
- from: architecture
to: validation
condition: all architecture docs completed
- from: validation
to: development-planning
condition: validation passed
- from: development-planning
to: development-handoff
condition: stories created
artifacts:
project-brief:
template: project-brief-tmpl
description: High-level project vision and goals
prd:
template: prd-tmpl
description: Detailed product requirements
architecture-doc:
template: fullstack-architecture-tmpl
description: Complete system architecture
frontend-architecture:
template: front-end-architecture-tmpl
description: Frontend-specific architecture
user-stories:
template: story-tmpl
description: Development-ready user stories

86
agent-team-workflows/greenfield-service.yml Normal file
View File

@@ -0,0 +1,86 @@
workflow:
id: greenfield-service
name: Greenfield Service/API Development
description: >-
Agent workflow for building REST APIs, GraphQL services, or microservices
without frontend requirements.
type: greenfield
project_types:
- rest-api
- graphql-api
- microservice
- backend-service
sequence:
- agent: analyst
creates: project-brief.md
optional_steps:
- brainstorming_session
- 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
creates: prd.md
requires: project-brief.md
notes: "Creates PRD from project brief using prd-tmpl, focused on API/service requirements. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
- agent: architect
creates: architecture.md
requires: prd.md
optional_steps:
- technical_research_prompt
notes: "Creates backend/service architecture using architecture-tmpl. May suggest changes to PRD stories or new stories. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
- agent: pm
updates: prd.md (if needed)
requires: architecture.md
condition: architecture_suggests_prd_changes
notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder."
- agent: po
validates: all_artifacts
uses: po-master-checklist
notes: "Validates all documents for consistency and completeness. May require updates to any document."
- 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."
- 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"
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
B -.-> B1[Optional: brainstorming]
B -.-> B2[Optional: market research]
D -.-> D1[Optional: technical research]
style J fill:#90EE90
style B fill:#FFE4B5
style C fill:#FFE4B5
style D fill:#FFE4B5
```
handoff_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."

119
agent-team-workflows/greenfield-ui.yml Normal file
View File

@@ -0,0 +1,119 @@
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.
type: greenfield
project_types:
- spa
- mobile-app
- micro-frontend
- static-site
sequence:
- agent: analyst
creates: project-brief.md
optional_steps:
- brainstorming_session
- 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
creates: prd.md
requires: project-brief.md
notes: "Creates PRD from project brief using prd-tmpl, focused on UI/frontend requirements. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
- agent: ux-expert
creates: front-end-spec.md
requires: prd.md
optional_steps:
- user_research_prompt
notes: "Creates UI/UX specification using front-end-spec-tmpl. SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder."
- agent: ux-expert
creates: v0_prompt (optional)
requires: front-end-spec.md
condition: user_wants_ai_generation
notes: "OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure."
- agent: ui-architect
creates: front-end-architecture.md
requires: front-end-spec.md
optional_steps:
- technical_research_prompt
- review_generated_ui_structure
notes: "Creates frontend architecture using front-end-architecture-tmpl. If user generated UI with v0/Lovable, can incorporate the project structure into architecture. May suggest changes to PRD stories or new stories. SAVE OUTPUT: Copy final front-end-architecture.md to your project's docs/ folder."
- agent: pm
updates: prd.md (if needed)
requires: front-end-architecture.md
condition: architecture_suggests_prd_changes
notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder."
- agent: po
validates: all_artifacts
uses: po-master-checklist
notes: "Validates all documents for consistency and completeness. May require updates to any document."
- 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."
- project_setup_guidance:
action: guide_project_structure
condition: user_has_generated_ui
notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance."
- 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"
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
B -.-> B1[Optional: brainstorming]
B -.-> B2[Optional: market research]
D -.-> D1[Optional: user research]
E -.-> E1[Optional: technical research]
style M fill:#90EE90
style D3 fill:#E6E6FA
style D4 fill:#E6E6FA
style L fill:#E6E6FA
style B fill:#FFE4B5
style C fill:#FFE4B5
style D fill:#FFE4B5
style E fill:#FFE4B5
```
handoff_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."
architect_review: "Frontend architecture complete. Save it as docs/front-end-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."