bmad-method 4.27.5 → 5.0.0

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

@@ -1,187 +0,0 @@
-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
-
-  sequence:
-    - step: service_analysis
-      agent: architect
-      action: analyze existing project and use task document-project
-      creates: multiple documents per the document-project template
-      notes: "Review existing service documentation, codebase, performance metrics, and identify integration dependencies."
-
-    - agent: pm
-      creates: prd.md
-      uses: brownfield-prd-tmpl
-      requires: existing_service_analysis
-      notes: "Creates comprehensive PRD focused on service enhancement with existing system analysis. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
-
-    - agent: architect
-      creates: architecture.md
-      uses: brownfield-architecture-tmpl
-      requires: prd.md
-      notes: "Creates architecture with service integration strategy and API evolution planning. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
-
-    - agent: po
-      validates: all_artifacts
-      uses: po-master-checklist
-      notes: "Validates all 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."
-
-    - agent: po
-      action: shard_documents
-      creates: sharded_docs
-      requires: all_artifacts_in_project
-      notes: |
-        Shard documents for IDE development:
-        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-        - Creates docs/prd/ and docs/architecture/ folders with sharded content
-
-    - agent: sm
-      action: create_story
-      creates: story.md
-      requires: sharded_docs
-      repeats: for_each_epic
-      notes: |
-        Story creation cycle:
-        - SM Agent (New Chat): @sm → *create
-        - Creates next story from sharded docs
-        - Story starts in "Draft" status
-
-    - agent: analyst/pm
-      action: review_draft_story
-      updates: story.md
-      requires: story.md
-      optional: true
-      condition: user_wants_story_review
-      notes: |
-        OPTIONAL: Review and approve draft story
-        - NOTE: story-review task coming soon
-        - Review story completeness and alignment
-        - Update story status: Draft → Approved
-
-    - agent: dev
-      action: implement_story
-      creates: implementation_files
-      requires: story.md
-      notes: |
-        Dev Agent (New Chat): @dev
-        - Implements approved story
-        - Updates File List with all changes
-        - Marks story as "Review" when complete
-
-    - agent: qa
-      action: review_implementation
-      updates: implementation_files
-      requires: implementation_files
-      optional: true
-      notes: |
-        OPTIONAL: QA Agent (New Chat): @qa → review-story
-        - Senior dev review with refactoring ability
-        - Fixes small issues directly
-        - Leaves checklist for remaining items
-        - Updates story status (Review → Done or stays Review)
-
-    - agent: dev
-      action: address_qa_feedback
-      updates: implementation_files
-      condition: qa_left_unchecked_items
-      notes: |
-        If QA left unchecked items:
-        - Dev Agent (New Chat): Address remaining items
-        - Return to QA for final approval
-
-    - repeat_development_cycle:
-      action: continue_for_all_stories
-      notes: |
-        Repeat story cycle (SM → Dev → QA) for all epic stories
-        Continue until all stories in PRD are complete
-
-    - agent: po
-      action: epic_retrospective
-      creates: epic-retrospective.md
-      condition: epic_complete
-      optional: true
-      notes: |
-        OPTIONAL: After epic completion
-        - NOTE: epic-retrospective task coming soon
-        - Validate epic was completed correctly
-        - Document learnings and improvements
-
-    - workflow_end:
-      action: project_complete
-      notes: |
-        All stories implemented and reviewed!
-        Project development phase complete.
-        
-        Reference: data#bmad-kb:IDE Development Workflow
-
-  flow_diagram: |
-    ```mermaid
-    graph TD
-        A[Start: Service Enhancement] --> B[analyst: analyze existing service]
-        B --> C[pm: prd.md]
-        C --> D[architect: architecture.md]
-        D --> E[po: validate with po-master-checklist]
-        E --> F{PO finds issues?}
-        F -->|Yes| G[Return to relevant agent for fixes]
-        F -->|No| H[po: shard documents]
-        G --> E
-        
-        H --> I[sm: create story]
-        I --> J{Review draft story?}
-        J -->|Yes| K[analyst/pm: review & approve story]
-        J -->|No| L[dev: implement story]
-        K --> L
-        L --> M{QA review?}
-        M -->|Yes| N[qa: review implementation]
-        M -->|No| O{More stories?}
-        N --> P{QA found issues?}
-        P -->|Yes| Q[dev: address QA feedback]
-        P -->|No| O
-        Q --> N
-        O -->|Yes| I
-        O -->|No| R{Epic retrospective?}
-        R -->|Yes| S[po: epic retrospective]
-        R -->|No| T[Project Complete]
-        S --> T
-
-        style T fill:#90EE90
-        style H fill:#ADD8E6
-        style I fill:#ADD8E6
-        style L fill:#ADD8E6
-        style C fill:#FFE4B5
-        style D fill:#FFE4B5
-        style K fill:#F0E68C
-        style N fill:#F0E68C
-        style S fill:#F0E68C
-    ```
-
-  decision_guidance:
-    when_to_use:
-      - Service enhancement requires coordinated stories
-      - API versioning or breaking changes needed
-      - Database schema changes required
-      - Performance or scalability improvements needed
-      - Multiple integration points affected
-
-  handoff_prompts:
-    analyst_to_pm: "Service analysis complete. Create comprehensive PRD with service integration strategy."
-    pm_to_architect: "PRD ready. Save it as docs/prd.md, then create the service architecture."
-    architect_to_po: "Architecture complete. Save it as docs/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."
-    complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."

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

@@ -1,197 +0,0 @@
-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
-
-  sequence:
-    - step: ui_analysis
-      agent: architect
-      action: analyze existing project and use task document-project
-      creates: multiple documents per the document-project template
-      notes: "Review existing frontend application, user feedback, analytics data, and identify improvement areas."
-
-    - agent: pm
-      creates: prd.md
-      uses: brownfield-prd-tmpl
-      requires: existing_ui_analysis
-      notes: "Creates comprehensive PRD focused on UI enhancement with existing system analysis. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
-
-    - agent: ux-expert
-      creates: front-end-spec.md
-      uses: front-end-spec-tmpl
-      requires: prd.md
-      notes: "Creates UI/UX specification that integrates with existing design patterns. SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder."
-
-    - agent: architect
-      creates: architecture.md
-      uses: brownfield-architecture-tmpl
-      requires:
-        - prd.md
-        - front-end-spec.md
-      notes: "Creates frontend architecture with component integration strategy and migration planning. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
-
-    - agent: po
-      validates: all_artifacts
-      uses: po-master-checklist
-      notes: "Validates all 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."
-
-    - agent: po
-      action: shard_documents
-      creates: sharded_docs
-      requires: all_artifacts_in_project
-      notes: |
-        Shard documents for IDE development:
-        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-        - Creates docs/prd/ and docs/architecture/ folders with sharded content
-
-    - agent: sm
-      action: create_story
-      creates: story.md
-      requires: sharded_docs
-      repeats: for_each_epic
-      notes: |
-        Story creation cycle:
-        - SM Agent (New Chat): @sm → *create
-        - Creates next story from sharded docs
-        - Story starts in "Draft" status
-
-    - agent: analyst/pm
-      action: review_draft_story
-      updates: story.md
-      requires: story.md
-      optional: true
-      condition: user_wants_story_review
-      notes: |
-        OPTIONAL: Review and approve draft story
-        - NOTE: story-review task coming soon
-        - Review story completeness and alignment
-        - Update story status: Draft → Approved
-
-    - agent: dev
-      action: implement_story
-      creates: implementation_files
-      requires: story.md
-      notes: |
-        Dev Agent (New Chat): @dev
-        - Implements approved story
-        - Updates File List with all changes
-        - Marks story as "Review" when complete
-
-    - agent: qa
-      action: review_implementation
-      updates: implementation_files
-      requires: implementation_files
-      optional: true
-      notes: |
-        OPTIONAL: QA Agent (New Chat): @qa → review-story
-        - Senior dev review with refactoring ability
-        - Fixes small issues directly
-        - Leaves checklist for remaining items
-        - Updates story status (Review → Done or stays Review)
-
-    - agent: dev
-      action: address_qa_feedback
-      updates: implementation_files
-      condition: qa_left_unchecked_items
-      notes: |
-        If QA left unchecked items:
-        - Dev Agent (New Chat): Address remaining items
-        - Return to QA for final approval
-
-    - repeat_development_cycle:
-      action: continue_for_all_stories
-      notes: |
-        Repeat story cycle (SM → Dev → QA) for all epic stories
-        Continue until all stories in PRD are complete
-
-    - agent: po
-      action: epic_retrospective
-      creates: epic-retrospective.md
-      condition: epic_complete
-      optional: true
-      notes: |
-        OPTIONAL: After epic completion
-        - NOTE: epic-retrospective task coming soon
-        - Validate epic was completed correctly
-        - Document learnings and improvements
-
-    - workflow_end:
-      action: project_complete
-      notes: |
-        All stories implemented and reviewed!
-        Project development phase complete.
-        
-        Reference: data#bmad-kb:IDE Development Workflow
-
-  flow_diagram: |
-    ```mermaid
-    graph TD
-        A[Start: UI Enhancement] --> B[analyst: analyze existing UI]
-        B --> C[pm: prd.md]
-        C --> D[ux-expert: front-end-spec.md]
-        D --> E[architect: architecture.md]
-        E --> F[po: validate with po-master-checklist]
-        F --> G{PO finds issues?}
-        G -->|Yes| H[Return to relevant agent for fixes]
-        G -->|No| I[po: shard documents]
-        H --> F
-        
-        I --> J[sm: create story]
-        J --> K{Review draft story?}
-        K -->|Yes| L[analyst/pm: review & approve story]
-        K -->|No| M[dev: implement story]
-        L --> M
-        M --> N{QA review?}
-        N -->|Yes| O[qa: review implementation]
-        N -->|No| P{More stories?}
-        O --> Q{QA found issues?}
-        Q -->|Yes| R[dev: address QA feedback]
-        Q -->|No| P
-        R --> O
-        P -->|Yes| J
-        P -->|No| S{Epic retrospective?}
-        S -->|Yes| T[po: epic retrospective]
-        S -->|No| U[Project Complete]
-        T --> U
-
-        style U fill:#90EE90
-        style I fill:#ADD8E6
-        style J fill:#ADD8E6
-        style M fill:#ADD8E6
-        style C fill:#FFE4B5
-        style D fill:#FFE4B5
-        style E fill:#FFE4B5
-        style L fill:#F0E68C
-        style O fill:#F0E68C
-        style T fill:#F0E68C
-    ```
-
-  decision_guidance:
-    when_to_use:
-      - UI enhancement requires coordinated stories
-      - Design system changes needed
-      - New component patterns required
-      - User research and testing needed
-      - Multiple team members will work on related changes
-
-  handoff_prompts:
-    analyst_to_pm: "UI analysis complete. Create comprehensive PRD with UI integration strategy."
-    pm_to_ux: "PRD ready. Save it as docs/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/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."
-    complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."

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

@@ -1,206 +0,0 @@
-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
-
-  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."
-
-    - agent: po
-      action: shard_documents
-      creates: sharded_docs
-      requires: all_artifacts_in_project
-      notes: |
-        Shard documents for IDE development:
-        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-        - Creates docs/prd/ and docs/architecture/ folders with sharded content
-
-    - agent: sm
-      action: create_story
-      creates: story.md
-      requires: sharded_docs
-      repeats: for_each_epic
-      notes: |
-        Story creation cycle:
-        - SM Agent (New Chat): @sm → *create
-        - Creates next story from sharded docs
-        - Story starts in "Draft" status
-
-    - agent: analyst/pm
-      action: review_draft_story
-      updates: story.md
-      requires: story.md
-      optional: true
-      condition: user_wants_story_review
-      notes: |
-        OPTIONAL: Review and approve draft story
-        - NOTE: story-review task coming soon
-        - Review story completeness and alignment
-        - Update story status: Draft → Approved
-
-    - agent: dev
-      action: implement_story
-      creates: implementation_files
-      requires: story.md
-      notes: |
-        Dev Agent (New Chat): @dev
-        - Implements approved story
-        - Updates File List with all changes
-        - Marks story as "Review" when complete
-
-    - agent: qa
-      action: review_implementation
-      updates: implementation_files
-      requires: implementation_files
-      optional: true
-      notes: |
-        OPTIONAL: QA Agent (New Chat): @qa → review-story
-        - Senior dev review with refactoring ability
-        - Fixes small issues directly
-        - Leaves checklist for remaining items
-        - Updates story status (Review → Done or stays Review)
-
-    - agent: dev
-      action: address_qa_feedback
-      updates: implementation_files
-      condition: qa_left_unchecked_items
-      notes: |
-        If QA left unchecked items:
-        - Dev Agent (New Chat): Address remaining items
-        - Return to QA for final approval
-
-    - repeat_development_cycle:
-      action: continue_for_all_stories
-      notes: |
-        Repeat story cycle (SM → Dev → QA) for all epic stories
-        Continue until all stories in PRD are complete
-
-    - agent: po
-      action: epic_retrospective
-      creates: epic-retrospective.md
-      condition: epic_complete
-      optional: true
-      notes: |
-        OPTIONAL: After epic completion
-        - NOTE: epic-retrospective task coming soon
-        - Validate epic was completed correctly
-        - Document learnings and improvements
-
-    - workflow_end:
-      action: project_complete
-      notes: |
-        All stories implemented and reviewed!
-        Service development phase complete.
-        
-        Reference: {root}/data/bmad-kb.md#IDE Development Workflow
-
-  flow_diagram: |
-    ```mermaid
-    graph TD
-        A[Start: Service Development] --> 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[po: shard documents]
-        I --> G
-        
-        J --> K[sm: create story]
-        K --> L{Review draft story?}
-        L -->|Yes| M[analyst/pm: review & approve story]
-        L -->|No| N[dev: implement story]
-        M --> N
-        N --> O{QA review?}
-        O -->|Yes| P[qa: review implementation]
-        O -->|No| Q{More stories?}
-        P --> R{QA found issues?}
-        R -->|Yes| S[dev: address QA feedback]
-        R -->|No| Q
-        S --> P
-        Q -->|Yes| K
-        Q -->|No| T{Epic retrospective?}
-        T -->|Yes| U[po: epic retrospective]
-        T -->|No| V[Project Complete]
-        U --> V
-
-        B -.-> B1[Optional: brainstorming]
-        B -.-> B2[Optional: market research]
-        D -.-> D1[Optional: technical research]
-
-        style V fill:#90EE90
-        style J fill:#ADD8E6
-        style K fill:#ADD8E6
-        style N fill:#ADD8E6
-        style B fill:#FFE4B5
-        style C fill:#FFE4B5
-        style D fill:#FFE4B5
-        style M fill:#F0E68C
-        style P fill:#F0E68C
-        style U fill:#F0E68C
-    ```
-
-  decision_guidance:
-    when_to_use:
-      - 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
-
-  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."
-    complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."