bmad-method 4.27.6 → 5.0.0

package/.bmad-core/workflows/brownfield-fullstack.yml

@@ -0,0 +1,116 @@
+workflow:
+  id: brownfield-fullstack
+  name: Brownfield Full-Stack Enhancement
+  description: >-
+    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
+    - integration-enhancement
+
+  # 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."
+
+    - 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."
+
+    - 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: 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."
+
+    - agent: po
+      validates: all_artifacts
+      uses: po-master-checklist
+      notes: "Validates all brownfield documents for integration safety 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"
+
+  # 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)."
+
+    - 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."
+
+    - 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"
+
+  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[architect: brownfield-architecture.md]
+        F --> G[po: validate with po-master-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."

package/.bmad-core/workflows/brownfield-service.yml

@@ -0,0 +1,117 @@
+workflow:
+  id: brownfield-service
+  name: Brownfield Service/API Enhancement
+  description: >-
+    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
+    - integration-enhancement
+
+  # 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."
+
+    - step: service_analysis
+      agent: analyst
+      action: analyze existing service
+      notes: "Review existing service documentation, codebase, performance metrics, and identify integration dependencies."
+
+    - 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: 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."
+
+    - agent: po
+      validates: all_artifacts
+      uses: po-master-checklist
+      notes: "Validates all brownfield documents for service integration safety and API compatibility. 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"
+
+  # 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)."
+
+    - 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."
+
+    - 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"
+
+  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 po-master-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:
+      - 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
+
+    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."

package/.bmad-core/workflows/brownfield-ui.yml

@@ -0,0 +1,127 @@
+workflow:
+  id: brownfield-ui
+  name: Brownfield UI/Frontend Enhancement
+  description: >-
+    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-enhancement
+
+  # 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."
+
+    - step: ui_analysis
+      agent: analyst
+      action: analyze existing UI
+      notes: "Review existing frontend application, user feedback, analytics data, and identify improvement areas."
+
+    - 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
+      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."
+
+    - agent: 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: po
+      validates: all_artifacts
+      uses: po-master-checklist
+      notes: "Validates all brownfield documents for UI integration safety and design consistency. 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"
+
+  # 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)."
+
+    - 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."
+
+    - 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"
+
+  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[architect: brownfield-architecture.md]
+        G --> H[po: validate with po-master-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."

package/.bmad-core/workflows/greenfield-fullstack.yml

@@ -0,0 +1,177 @@
+workflow:
+  id: greenfield-fullstack
+  name: Greenfield Full-Stack Application Development
+  description: >-
+    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
+
+  # For Complex Projects (Production-Ready, Multiple Features)
+  complex_project_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: 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"
+
+  # 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-project-prd.md
+      uses: create doc simple-project-prd OR create-epic OR create-story
+      requires: project-brief.md
+      notes: "Create simple prd, 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: Greenfield Project] --> B{Project Complexity?}
+        B -->|Complex/Production| C[analyst: project-brief.md]
+        B -->|Simple/Prototype| D[analyst: focused project-brief.md]
+
+        C --> E[pm: prd.md]
+        E --> F[ux-expert: front-end-spec.md]
+        F --> F2{Generate v0 prompt?}
+        F2 -->|Yes| F3[ux-expert: create v0 prompt]
+        F2 -->|No| G[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
+
+        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 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."
+    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."
+    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."

package/.bmad-core/workflows/greenfield-service.yml

@@ -0,0 +1,143 @@
+workflow:
+  id: greenfield-service
+  name: Greenfield Service/API Development
+  description: >-
+    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
+
+  # For Complex Services (Production APIs, Multiple Endpoints)
+  complex_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"
+
+  # 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: Service Development] --> B{Service Complexity?}
+        B -->|Complex/Production| C[analyst: project-brief.md]
+        B -->|Simple/Prototype| D[analyst: focused project-brief.md]
+
+        C --> E[pm: prd.md]
+        E --> F[architect: architecture.md]
+        F --> G{Architecture suggests PRD changes?}
+        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
+
+        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 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."
+    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."