mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
Align UX design workflow references (#935)
Co-authored-by: Brian <bmadcode@gmail.com>
This commit is contained in:
@@ -321,7 +321,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
||||
**Workflows:**
|
||||
|
||||
- `workflow-status` - Check what to do next
|
||||
- `create-design` - Conduct design thinking workshop to define UX specification with:
|
||||
- `create-ux-design` - Conduct design thinking workshop to define UX specification with:
|
||||
- Visual exploration and generation
|
||||
- Collaborative decision-making
|
||||
- AI-assisted design tools (v0, Lovable)
|
||||
@@ -944,7 +944,7 @@ Quick reference for agent selection:
|
||||
| ----------------------- | ---- | ------------------ | --------------------------------------------- | ------------------------------------- |
|
||||
| **Analyst** | 📊 | 1 (Analysis) | brainstorm, brief, research, document-project | Discovery, requirements, brownfield |
|
||||
| **PM** | 📋 | 2 (Planning) | prd, tech-spec, epics-stories | Planning, requirements docs |
|
||||
| **UX Designer** | 🎨 | 2 (Planning) | create-design, validate-design | UX-heavy projects, design |
|
||||
| **UX Designer** | 🎨 | 2 (Planning) | create-ux-design, validate-design | UX-heavy projects, design |
|
||||
| **Architect** | 🏗️ | 3 (Solutioning) | architecture, implementation-readiness | Technical design, architecture |
|
||||
| **SM** | 🏃 | 4 (Implementation) | sprint-planning, create-story, story-context | Story management, sprint coordination |
|
||||
| **DEV** | 💻 | 4 (Implementation) | develop-story, code-review, story-done | Implementation, coding |
|
||||
|
||||
@@ -240,7 +240,7 @@ Continuous deployment to production
|
||||
**UX Designer Workflow:**
|
||||
|
||||
```bash
|
||||
bmad ux *create-design
|
||||
bmad ux *create-ux-design
|
||||
```
|
||||
|
||||
**BMad produces:**
|
||||
|
||||
@@ -295,7 +295,7 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
|
||||
| Workflow Stage | Test Architect | Dev / Team | Outputs |
|
||||
| -------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
|
||||
| **Phase 1**: Discovery | - | Analyst ➕ `*research`, `*product-brief` | Domain research, compliance analysis, product brief |
|
||||
| **Phase 2**: Planning | Run ➕ `*nfr-assess` | PM `*prd` (creates PRD with FRs/NFRs), UX `*create-design` | Enterprise PRD with FRs/NFRs, UX design, ➕ NFR documentation |
|
||||
| **Phase 2**: Planning | Run ➕ `*nfr-assess` | PM `*prd` (creates PRD with FRs/NFRs), UX `*create-ux-design` | Enterprise PRD with FRs/NFRs, UX design, ➕ NFR documentation |
|
||||
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture and epic creation | Architect `*architecture`, `*create-epics-and-stories`, `*implementation-readiness` | Architecture, epics/stories, test framework, CI pipeline |
|
||||
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint plan with all epics |
|
||||
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic 🔄 (compliance focus) | Review epic scope and compliance requirements | `test-design-epic-N.md` with security/performance/compliance focus |
|
||||
|
||||
Reference in New Issue
Block a user