3af3d33d4a
This release introduces significant enhancements across multiple areas: QA Agent Transformation: - Transform QA agent into senior developer role with active code refactoring abilities - Add review-story task enabling QA to review, refactor, and improve code directly - Integrate QA review step into standard development workflow (SM → Dev → QA) - QA can fix small issues directly and leave checklist for remaining items - Updated dev agent to maintain File List for QA review focus Knowledge Base Improvements: - Add extensive brownfield development documentation and best practices - Clarify Web UI vs IDE usage with cost optimization strategies - Document PRD-first approach for large codebases/monorepos - Add comprehensive expansion packs explanation - Update IDE workflow to include QA review step - Clarify agent usage (bmad-master vs specialized agents) Brownfield Enhancements: - Create comprehensive Working in the Brownfield guide - Add document-project task to analyst agent capabilities - Implement PRD-first workflow option for focused documentation - Transform document-project to create practical brownfield architecture docs - Document technical debt, workarounds, and real-world constraints - Reference actual files instead of duplicating content - Add impact analysis when PRD is provided Documentation Task Improvements: - Simplify to always create ONE unified architecture document - Add deep codebase analysis phase with targeted questions - Focus on documenting reality including technical debt - Include Quick Reference section with key file paths - Add practical sections: useful commands, debugging tips, known issues Workflow Updates: - Update all 6 workflow files with detailed IDE transition instructions - Add clear SM → Dev → QA → Dev cycle explanation - Emphasize Gemini Web for brownfield analysis (1M+ context advantage) - Support both PRD-first and document-first approaches This release significantly improves the brownfield development experience and introduces a powerful shift-left QA approach with senior developer mentoring.
162 lines
7.1 KiB
YAML
162 lines
7.1 KiB
YAML
workflow:
|
|
id: greenfield-ui
|
|
name: Greenfield UI/Frontend Development
|
|
description: >-
|
|
Agent workflow for building frontend applications from concept to development.
|
|
Supports both comprehensive planning for complex UIs and rapid prototyping for simple interfaces.
|
|
type: greenfield
|
|
project_types:
|
|
- spa
|
|
- mobile-app
|
|
- micro-frontend
|
|
- static-site
|
|
- ui-prototype
|
|
- simple-interface
|
|
|
|
sequence:
|
|
- 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: 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: |
|
|
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
|
|
|
|
Reference: data#bmad-kb:IDE Development Workflow
|
|
|
|
flow_diagram: |
|
|
```mermaid
|
|
graph TD
|
|
A[Start: UI Development] --> 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[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[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 K fill:#90EE90
|
|
style D3 fill:#E6E6FA
|
|
style D4 fill:#E6E6FA
|
|
style B fill:#FFE4B5
|
|
style C fill:#FFE4B5
|
|
style D fill:#FFE4B5
|
|
style E fill:#FFE4B5
|
|
```
|
|
|
|
decision_guidance:
|
|
when_to_use:
|
|
- Building production frontend applications
|
|
- Multiple views/pages with complex interactions
|
|
- Need comprehensive UI/UX design and testing
|
|
- Multiple team members will be involved
|
|
- Long-term maintenance expected
|
|
- Customer-facing applications
|
|
|
|
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."
|
|
complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
|