8.4 KiB
8.4 KiB
| 1 | module | phase | name | code | sequence | workflow-file | command | required | agent | options | description | output-location | outputs | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | wds | 0-wds-agents | Wake Saga | SAGA | 1 | _bmad/wds/agents/saga-analyst.agent.yaml | bmad-wds-saga | false | saga-analyst | Agent Activation | Agent launcher. Wakes Saga (Strategic Analyst) who handles Phases 1-2. Saga introduces herself scans attached repos for WDS projects checks phase completion status finds unfinished agent dialogs and offers contextually appropriate next steps. Use this to start Product Brief or Trigger Map work. | |||
| 3 | wds | 0-wds-agents | Wake Freya | FREYA | 2 | _bmad/wds/agents/freya-ux.agent.yaml | bmad-wds-freya | false | freya-ux | Agent Activation | Agent launcher. Wakes Freya (UX Designer) who handles Phases 3-4. Freya introduces herself scans repos checks prerequisites (Product Brief + Trigger Map) detects scenario and design status and offers appropriate next steps. Use this to start UX Scenarios or UX Design work. | |||
| 4 | wds | 0-wds-agents | Wake Idunn | IDUNN | 3 | _bmad/wds/agents/idunn-pm.agent.yaml | bmad-wds-idunn | false | idunn-pm | Agent Activation | Agent launcher. Wakes Idunn (Project Manager) who handles project oversight and Phase 5 (Design System). Idunn provides comprehensive status across ALL phases identifies unfinished work shows critical path and coordinates handoffs between agents. Use this for project overview or Design System work. | |||
| 5 | wds | 0-wds-pitch | Alignment & Signoff | AS | 10 | _bmad/wds/workflows/0-alignment-signoff/workflow.md | bmad-wds-alignment | false | saga-analyst | Create Mode | Optional. Secure stakeholder buy-in before the project starts. Create a pitch document service agreement and signoff. Use when working with clients or stakeholders who need to approve budget and scope. Skip if building your own product or working with a small trusted team. | design_artifacts/A-Product-Brief | pitch service-agreement signoff | |
| 6 | wds | 1-wds-strategy | Project Brief | PB | 10 | _bmad/wds/workflows/1-project-brief/workflow.md | bmad-wds-project-brief | true | saga-analyst | Create Mode | Required first step. Define the product vision positioning competitive analysis and success criteria. The Project Brief is your North Star — every design decision traces back to it. Saga guides you through the five questions that anchor the entire project. | design_artifacts/A-Product-Brief | project-brief.md | |
| 7 | wds | 1-wds-strategy | Trigger Mapping | TM | 20 | _bmad/wds/workflows/2-trigger-mapping/workflow.md | bmad-wds-trigger-mapping | true | saga-analyst | Create Mode | Required. Map business goals to user psychology through five workshops. Create personas with real driving forces and score every feature against them. This is the secret weapon of WDS — it replaces guesswork with traceable design decisions. | design_artifacts/B-Trigger-Map | trigger-map.md personas/ feature-impact-analysis.md | |
| 8 | wds | 1-wds-strategy | Platform Requirements | PR | 30 | _bmad/wds/workflows/1-project-brief/workflow.md | bmad-wds-platform-requirements | false | idunn-pm | Create Mode | Define the technical boundaries that inform design decisions. Platforms devices integrations constraints and risks. Know your boundaries before designing within them. Recommended for complex products. Can be skipped for simple landing pages. Sub-workflow 106 under Phase 1. | design_artifacts/A-Product-Brief | platform-requirements.md | |
| 9 | wds | 2-wds-design | Outline Scenarios | OS | 10 | _bmad/wds/workflows/3-scenarios/workflow.md | bmad-wds-outline-scenarios | true | freya-ux | Create Mode | Required. Define the user journeys you will design. Scenarios are journeys not pages — they start with a persona and a goal and end with an outcome. Each scenario connects to a driving force from the Trigger Map. This step shapes everything that follows. | design_artifacts/C-UX-Scenarios | scenario-overview.md | |
| 10 | wds | 2-wds-design | Conceptual Sketching | CS | 20 | _bmad/wds/workflows/4-ux-design/workflow.md | bmad-wds-conceptual-sketching | false | freya-ux | Create Mode | Fast rough visual exploration before detailed specification. Multiple entry points: provide a hand sketch share inspiration let the AI generate options or discuss with Freya. The goal is direction not perfection. Recommended for complex or unfamiliar flows. Can be skipped for straightforward scenarios. | design_artifacts/C-UX-Scenarios | sketches | |
| 11 | wds | 2-wds-design | Storyboarding | SB | 30 | _bmad/wds/workflows/4-ux-design/workflow.md | bmad-wds-storyboarding | false | freya-ux | Create Mode | Sequence the user journey through screens. Map entry points transitions success states and error paths as a visual narrative. Helps catch gaps before detailed specification. Recommended for multi-step flows. Can be skipped if the scenario is simple enough to specify directly. | design_artifacts/C-UX-Scenarios | storyboards | |
| 12 | wds | 2-wds-design | Conceptual Specifications | SP | 40 | _bmad/wds/workflows/4-ux-design/workflow.md | bmad-wds-conceptual-specs | true | freya-ux | Create Mode | Required. The core of WDS. Document every design decision — what why how and exact content for every element on every page. Nothing is left to interpretation. The specification IS the design. Pages sections widgets elements and all their states. A developer or AI agent can build directly from this without asking questions. | design_artifacts/C-UX-Scenarios | page-specs scenario-specs | |
| 13 | wds | 2-wds-design | Functional Components | FI | 50 | _bmad/wds/workflows/4-ux-design/workflow.md | bmad-wds-functional-components | false | freya-ux | Create Mode | Identify reusable patterns across your specifications. When the same component appears three or more times with consistent behavior extract it into a reusable definition. This grows your design system organically. Skip if using Design System Mode None. | design_artifacts/C-UX-Scenarios | component-candidates | |
| 14 | wds | 2-wds-design | Visual Design | VD | 60 | _bmad/wds/workflows/6-asset-generation/workflow.md | bmad-wds-visual-design | false | freya-ux | Create Mode | Transform specifications into visual prototypes. Generate styled HTML prototypes from specs then refine with Figma round-trips using code.to.design or AI image generation. This is where soul enters the product. A visual designer should set the visual language — the AI applies it consistently. | design_artifacts/C-UX-Scenarios | html-prototypes visual-designs | |
| 15 | wds | 2-wds-design | Design System | DS | 70 | _bmad/wds/workflows/7-design-system/workflow.md | bmad-wds-design-system | false | freya-ux | Create Mode | Manage your component library based on project mode: None Building Library or Existing. Components and design tokens grow organically from your design work. Each project builds on the last. Skip if using Design System Mode None. | design_artifacts/D-Design-System | components/ design-tokens.md | |
| 16 | wds | 2-wds-design | Design Delivery | DD | 80 | _bmad/wds/workflows/4-ux-design/workflow-handover.md | bmad-wds-design-delivery | true | freya-ux | Create Mode | Required. Validate specifications are complete and package them for development as DD yaml files. Freya runs a final audit checking every element every state and accessibility. The DD contract is what developers or the agentic development phase builds from. Nothing ships without this validation. | design_artifacts/E-PRD/Design-Deliveries | delivery-package acceptance-criteria | |
| 17 | wds | 3-wds-build | Agentic Development | AD | 10 | _bmad/wds/workflows/_agent-dialogs/workflow.md | bmad-wds-agentic-development | false | pm | Create Mode | Build iteratively using Agent Dialogs. Design one thing build it verify with Puppeteer in the browser iterate. Every decision is logged so you can restart conversations without losing context. The agent tests its own work against acceptance criteria while you handle qualitative judgment. | _progress/agent-dialogs | dialog-documents | |
| 18 | wds | 3-wds-build | Acceptance Testing | AT | 20 | _bmad/wds/workflows/5-agentic-development/workflow-acceptance-testing.md | bmad-wds-usability-testing | false | freya-ux | Create Mode | Test the product on real users using their own devices in their own environment. Plan the test scenario conduct sessions with silence and deflection then replay recordings with users for retrospective think-aloud. The Whiteport Rule: if it is not worth showing to 5 users and 1 domain expert it should not be built. | design_artifacts/F-Testing | test-results findings | |
| 19 | wds | 3-wds-build | Product Evolution | PE | 30 | _bmad/wds/workflows/8-product-evolution/workflow.md | bmad-wds-product-evolution | false | idunn-pm | Create Mode | Continuous improvement for living products. The full WDS process in miniature — receive feedback connect to Trigger Map update the spec first then project into code verify and document. Every change uses a Product Evolution Agent Dialog. Start here if you have an existing product you want to improve. | design_artifacts | updated-artifacts |