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

feat: workflow plans introduced, preliminary feature under review

Browse Source
This commit is contained in:
Brian Madison
2025-07-01 22:46:59 -05:00
parent 3e2e43dd88
commit 731589aa28
31 changed files with 4704 additions and 32755 deletions
Download Patch File Download Diff File Expand all files Collapse all files

295
bmad-core/workflows/brownfield-fullstack.yml
View File

@@ -12,23 +12,76 @@ workflow:
- integration-enhancement
sequence:
- step: enhancement_classification
agent: analyst
action: classify enhancement scope
notes: |
Determine enhancement complexity to route to appropriate path:
- Single story (< 4 hours) → Use brownfield-create-story task
- Small feature (1-3 stories) → Use brownfield-create-epic task
- Major enhancement (multiple epics) → Continue with full workflow
Ask user: "Can you describe the enhancement scope? Is this a small fix, a feature addition, or a major enhancement requiring architectural changes?"
- step: routing_decision
condition: based_on_classification
routes:
single_story:
agent: pm
uses: brownfield-create-story
notes: "Create single story for immediate implementation. Exit workflow after story creation."
small_feature:
agent: pm
uses: brownfield-create-epic
notes: "Create focused epic with 1-3 stories. Exit workflow after epic creation."
major_enhancement:
continue: to_next_step
notes: "Continue with comprehensive planning workflow below."
- step: documentation_check
agent: analyst
action: check existing documentation
condition: major_enhancement_path
notes: |
Check if adequate project documentation exists:
- Look for existing architecture docs, API specs, coding standards
- Assess if documentation is current and comprehensive
- If adequate: Skip document-project, proceed to PRD
- If inadequate: Run document-project first
- step: project_analysis
agent: architect
action: analyze existing project and use task document-project
creates: multiple documents per the document-project template
notes: "Review existing documentation, codebase structure, and identify integration points. Document current system understanding before proceeding."
creates: brownfield-architecture.md (or multiple documents)
condition: documentation_inadequate
notes: "Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation."
- agent: pm
creates: prd.md
uses: brownfield-prd-tmpl
requires: existing_project_analysis
notes: "Creates comprehensive PRD with existing system analysis and enhancement planning. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
requires: existing_documentation_or_analysis
notes: |
Creates PRD for major enhancement. If document-project was run, reference its output to avoid re-analysis.
If skipped, use existing project documentation.
SAVE OUTPUT: Copy final prd.md to your project's docs/ folder.
- step: architecture_decision
agent: pm/architect
action: determine if architecture document needed
condition: after_prd_creation
notes: |
Review PRD to determine if architectural planning is needed:
- New architectural patterns → Create architecture doc
- New libraries/frameworks → Create architecture doc
- Platform/infrastructure changes → Create architecture doc
- Following existing patterns → Skip to story creation
- agent: architect
creates: architecture.md
uses: brownfield-architecture-tmpl
requires: prd.md
notes: "Creates architecture with integration strategy and existing system constraints. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
condition: architecture_changes_needed
notes: "Creates architecture ONLY for significant architectural changes. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
- agent: po
validates: all_artifacts
@@ -40,60 +93,162 @@ workflow:
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
- agent: po
action: shard_documents
creates: sharded_docs
requires: all_artifacts_in_project
notes: |
Planning phase complete! Now transition to IDE Development:
1. ENSURE DOCUMENTS ARE IN PROJECT:
- Copy final prd.md to project's docs/prd.md
- Copy final architecture.md to project's docs/architecture.md
- All documents must be in the project before proceeding
2. SHARD DOCUMENTS (in IDE):
- 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
- This creates docs/prd/ and docs/architecture/ folders with sharded content
3. START DEVELOPMENT CYCLE:
a. SM Agent (New Chat): @sm → *create
- Creates next story from sharded docs
- Review and approve story (Draft → Approved)
b. Dev Agent (New Chat): @dev
- Implements approved story
- Updates File List with all changes
- Marks story as "Review" when complete
c. 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)
d. If QA left unchecked items:
- Dev Agent (New Chat): Address remaining items
- Return to QA for final approval
4. REPEAT: Continue cycle for all epic stories
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_or_brownfield_docs
repeats: for_each_epic_or_enhancement
notes: |
Story creation cycle:
- For sharded PRD: @sm → *create (uses create-next-story)
- For brownfield docs: @sm → use create-brownfield-story task
- Creates story from available documentation
- Story starts in "Draft" status
- May require additional context gathering for brownfield
- 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: Brownfield Enhancement] --> B[analyst: analyze existing project]
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[Move to IDE Environment]
G --> E
A[Start: Brownfield Enhancement] --> B[analyst: classify enhancement scope]
B --> C{Enhancement Size?}
C -->|Single Story| D[pm: brownfield-create-story]
C -->|1-3 Stories| E[pm: brownfield-create-epic]
C -->|Major Enhancement| F[analyst: check documentation]
D --> END1[To Dev Implementation]
E --> END2[To Story Creation]
F --> G{Docs Adequate?}
G -->|No| H[architect: document-project]
G -->|Yes| I[pm: brownfield PRD]
H --> I
I --> J{Architecture Needed?}
J -->|Yes| K[architect: architecture.md]
J -->|No| L[po: validate artifacts]
K --> L
L --> M{PO finds issues?}
M -->|Yes| N[Fix issues]
M -->|No| O[po: shard documents]
N --> L
O --> P[sm: create story]
P --> Q{Story Type?}
Q -->|Sharded PRD| R[create-next-story]
Q -->|Brownfield Docs| S[create-brownfield-story]
R --> T{Review draft?}
S --> T
T -->|Yes| U[review & approve]
T -->|No| V[dev: implement]
U --> V
V --> W{QA review?}
W -->|Yes| X[qa: review]
W -->|No| Y{More stories?}
X --> Z{Issues?}
Z -->|Yes| AA[dev: fix]
Z -->|No| Y
AA --> X
Y -->|Yes| P
Y -->|No| AB{Retrospective?}
AB -->|Yes| AC[po: retrospective]
AB -->|No| AD[Complete]
AC --> AD
style H fill:#90EE90
style C fill:#FFE4B5
style D fill:#FFE4B5
style AD fill:#90EE90
style END1 fill:#90EE90
style END2 fill:#90EE90
style D fill:#87CEEB
style E fill:#87CEEB
style I fill:#FFE4B5
style K fill:#FFE4B5
style O fill:#ADD8E6
style P fill:#ADD8E6
style V fill:#ADD8E6
style U fill:#F0E68C
style X fill:#F0E68C
style AC fill:#F0E68C
```
decision_guidance:
@@ -105,8 +260,38 @@ workflow:
- Multiple team members will work on related changes
handoff_prompts:
analyst_to_pm: "Existing project analysis complete. Create comprehensive PRD with integration strategy."
pm_to_architect: "PRD ready. Save it as docs/prd.md, then create the integration architecture."
classification_complete: |
Enhancement classified as: {{enhancement_type}}
{{if single_story}}: Proceeding with brownfield-create-story task for immediate implementation.
{{if small_feature}}: Creating focused epic with brownfield-create-epic task.
{{if major_enhancement}}: Continuing with comprehensive planning workflow.
documentation_assessment: |
Documentation assessment complete:
{{if adequate}}: Existing documentation is sufficient. Proceeding directly to PRD creation.
{{if inadequate}}: Running document-project to capture current system state before PRD.
document_project_to_pm: |
Project analysis complete. Key findings documented in:
- {{document_list}}
Use these findings to inform PRD creation and avoid re-analyzing the same aspects.
pm_to_architect_decision: |
PRD complete and saved as docs/prd.md.
Architectural changes identified: {{yes/no}}
{{if yes}}: Proceeding to create architecture document for: {{specific_changes}}
{{if no}}: No architectural changes needed. Proceeding to validation.
architect_to_po: "Architecture complete. Save it as docs/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."
complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
po_to_sm: |
All artifacts validated.
Documentation type available: {{sharded_prd / brownfield_docs}}
{{if sharded}}: Use standard create-next-story task.
{{if brownfield}}: Use create-brownfield-story task to handle varied documentation formats.
sm_story_creation: |
Creating story from {{documentation_type}}.
{{if missing_context}}: May need to gather additional context from user during story creation.
complete: "All planning artifacts validated and development can begin. Stories will be created based on available documentation format."

148
bmad-core/workflows/brownfield-service.yml
View File

@@ -41,42 +41,92 @@ workflow:
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
- agent: po
action: shard_documents
creates: sharded_docs
requires: all_artifacts_in_project
notes: |
Planning phase complete! Now transition to IDE Development:
1. ENSURE DOCUMENTS ARE IN PROJECT:
- Copy final prd.md to project's docs/prd.md
- Copy final architecture.md to project's docs/architecture.md
- All documents must be in the project before proceeding
2. SHARD DOCUMENTS (in IDE):
- 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
- This creates docs/prd/ and docs/architecture/ folders with sharded content
3. START DEVELOPMENT CYCLE:
a. SM Agent (New Chat): @sm → *create
- Creates next story from sharded docs
- Review and approve story (Draft → Approved)
b. Dev Agent (New Chat): @dev
- Implements approved story
- Updates File List with all changes
- Marks story as "Review" when complete
c. 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)
d. If QA left unchecked items:
- Dev Agent (New Chat): Address remaining items
- Return to QA for final approval
4. REPEAT: Continue cycle for all epic stories
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
@@ -89,12 +139,36 @@ workflow:
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[Move to IDE Environment]
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 H fill:#90EE90
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:

148
bmad-core/workflows/brownfield-ui.yml
View File

@@ -48,42 +48,92 @@ workflow:
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
- agent: po
action: shard_documents
creates: sharded_docs
requires: all_artifacts_in_project
notes: |
Planning phase complete! Now transition to IDE Development:
1. ENSURE DOCUMENTS ARE IN PROJECT:
- Copy final prd.md to project's docs/prd.md
- Copy final architecture.md to project's docs/architecture.md
- All documents must be in the project before proceeding
2. SHARD DOCUMENTS (in IDE):
- 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
- This creates docs/prd/ and docs/architecture/ folders with sharded content
3. START DEVELOPMENT CYCLE:
a. SM Agent (New Chat): @sm → *create
- Creates next story from sharded docs
- Review and approve story (Draft → Approved)
b. Dev Agent (New Chat): @dev
- Implements approved story
- Updates File List with all changes
- Marks story as "Review" when complete
c. 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)
d. If QA left unchecked items:
- Dev Agent (New Chat): Address remaining items
- Return to QA for final approval
4. REPEAT: Continue cycle for all epic stories
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
@@ -97,13 +147,37 @@ workflow:
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[Move to IDE Environment]
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 I fill:#90EE90
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:

148
bmad-core/workflows/greenfield-fullstack.yml
View File

@@ -73,42 +73,92 @@ workflow:
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
- agent: po
action: shard_documents
creates: sharded_docs
requires: all_artifacts_in_project
notes: |
Planning phase complete! Now transition to IDE Development:
1. ENSURE DOCUMENTS ARE IN PROJECT:
- Copy final prd.md to project's docs/prd.md
- Copy final architecture.md to project's docs/architecture.md
- All documents must be in the project before proceeding
2. SHARD DOCUMENTS (in IDE):
- 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
- This creates docs/prd/ and docs/architecture/ folders with sharded content
3. START DEVELOPMENT CYCLE:
a. SM Agent (New Chat): @sm → *create
- Creates next story from sharded docs
- Review and approve story (Draft → Approved)
b. Dev Agent (New Chat): @dev
- Implements approved story
- Updates File List with all changes
- Marks story as "Review" when complete
c. 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)
d. If QA left unchecked items:
- Dev Agent (New Chat): Address remaining items
- Return to QA for final approval
4. REPEAT: Continue cycle for all epic stories
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
@@ -129,21 +179,45 @@ workflow:
G --> H
H --> I{PO finds issues?}
I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K[Move to IDE Environment]
I -->|No| K[po: shard documents]
J --> H
K --> L[sm: create story]
L --> M{Review draft story?}
M -->|Yes| N[analyst/pm: review & approve story]
M -->|No| O[dev: implement story]
N --> O
O --> P{QA review?}
P -->|Yes| Q[qa: review implementation]
P -->|No| R{More stories?}
Q --> S{QA found issues?}
S -->|Yes| T[dev: address QA feedback]
S -->|No| R
T --> Q
R -->|Yes| L
R -->|No| U{Epic retrospective?}
U -->|Yes| V[po: epic retrospective]
U -->|No| W[Project Complete]
V --> W
B -.-> B1[Optional: brainstorming]
B -.-> B2[Optional: market research]
D -.-> D1[Optional: user research]
E -.-> E1[Optional: technical research]
style K fill:#90EE90
style W fill:#90EE90
style K fill:#ADD8E6
style L fill:#ADD8E6
style O fill:#ADD8E6
style D3 fill:#E6E6FA
style D4 fill:#E6E6FA
style B fill:#FFE4B5
style C fill:#FFE4B5
style D fill:#FFE4B5
style E fill:#FFE4B5
style N fill:#F0E68C
style Q fill:#F0E68C
style V fill:#F0E68C
```
decision_guidance:

148
bmad-core/workflows/greenfield-service.yml
View File

@@ -49,42 +49,92 @@ workflow:
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
- agent: po
action: shard_documents
creates: sharded_docs
requires: all_artifacts_in_project
notes: |
Planning phase complete! Now transition to IDE Development:
1. ENSURE DOCUMENTS ARE IN PROJECT:
- Copy final prd.md to project's docs/prd.md
- Copy final architecture.md to project's docs/architecture.md
- All documents must be in the project before proceeding
2. SHARD DOCUMENTS (in IDE):
- 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
- This creates docs/prd/ and docs/architecture/ folders with sharded content
3. START DEVELOPMENT CYCLE:
a. SM Agent (New Chat): @sm → *create
- Creates next story from sharded docs
- Review and approve story (Draft → Approved)
b. Dev Agent (New Chat): @dev
- Implements approved story
- Updates File List with all changes
- Marks story as "Review" when complete
c. 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)
d. If QA left unchecked items:
- Dev Agent (New Chat): Address remaining items
- Return to QA for final approval
4. REPEAT: Continue cycle for all epic stories
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: data#bmad-kb:IDE Development Workflow
@@ -100,17 +150,41 @@ workflow:
F --> G
G --> H{PO finds issues?}
H -->|Yes| I[Return to relevant agent for fixes]
H -->|No| J[Move to IDE Environment]
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 J fill:#90EE90
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:

148
bmad-core/workflows/greenfield-ui.yml
View File

@@ -68,42 +68,92 @@ workflow:
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
- agent: po
action: shard_documents
creates: sharded_docs
requires: all_artifacts_in_project
notes: |
Planning phase complete! Now transition to IDE Development:
1. ENSURE DOCUMENTS ARE IN PROJECT:
- Copy final prd.md to project's docs/prd.md
- Copy final architecture.md to project's docs/architecture.md
- All documents must be in the project before proceeding
2. SHARD DOCUMENTS (in IDE):
- 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
- This creates docs/prd/ and docs/architecture/ folders with sharded content
3. START DEVELOPMENT CYCLE:
a. SM Agent (New Chat): @sm → *create
- Creates next story from sharded docs
- Review and approve story (Draft → Approved)
b. Dev Agent (New Chat): @dev
- Implements approved story
- Updates File List with all changes
- Marks story as "Review" when complete
c. 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)
d. If QA left unchecked items:
- Dev Agent (New Chat): Address remaining items
- Return to QA for final approval
4. REPEAT: Continue cycle for all epic stories
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
@@ -124,21 +174,45 @@ workflow:
G --> H
H --> I{PO finds issues?}
I -->|Yes| J[Return to relevant agent for fixes]
I -->|No| K[Move to IDE Environment]
I -->|No| K[po: shard documents]
J --> H
K --> L[sm: create story]
L --> M{Review draft story?}
M -->|Yes| N[analyst/pm: review & approve story]
M -->|No| O[dev: implement story]
N --> O
O --> P{QA review?}
P -->|Yes| Q[qa: review implementation]
P -->|No| R{More stories?}
Q --> S{QA found issues?}
S -->|Yes| T[dev: address QA feedback]
S -->|No| R
T --> Q
R -->|Yes| L
R -->|No| U{Epic retrospective?}
U -->|Yes| V[po: epic retrospective]
U -->|No| W[Project Complete]
V --> W
B -.-> B1[Optional: brainstorming]
B -.-> B2[Optional: market research]
D -.-> D1[Optional: user research]
E -.-> E1[Optional: technical research]
style K fill:#90EE90
style W fill:#90EE90
style K fill:#ADD8E6
style L fill:#ADD8E6
style O fill:#ADD8E6
style D3 fill:#E6E6FA
style D4 fill:#E6E6FA
style B fill:#FFE4B5
style C fill:#FFE4B5
style D fill:#FFE4B5
style E fill:#FFE4B5
style N fill:#F0E68C
style Q fill:#F0E68C
style V fill:#F0E68C
```
decision_guidance: