diff --git a/website/src/components/WorkflowGuide.astro b/website/src/components/WorkflowGuide.astro index b3500858..d9dc7e19 100644 --- a/website/src/components/WorkflowGuide.astro +++ b/website/src/components/WorkflowGuide.astro @@ -2,188 +2,160 @@ ---
/bmad-help
+ Run this anytime to see what to do next — or ask it a question like "what should I do to build a web app?"
+ Loading agents is optional. If your IDE supports slash commands, you can run workflows directly.
+Choose a track above to see the recommended workflow.
+Select a track above to see the workflow.
- -Explore and validate your idea before committing to a plan. Use these workflows when starting fresh or when requirements are unclear.
-brainstorm-project
- A guided ideation session that takes your project idea and uses 60+ techniques to create brainstorm notes.
-research
- Conducts market, technical, or competitive research on your questions and produces a structured research document.
-product-brief
+ Combines your brainstorm and research notes into a strategic foundation document — product-brief.md — covering problem statement, target users, and MVP scope.
-/brainstorm-project
+ Analyst
+
+ Guided ideation using 60+ techniques to explore your project idea and create brainstorm notes.
+/research
+ Analyst
+
+ Market, technical, or competitive research producing a structured research document.
+/product-brief
+ Analyst
+
+ Combines brainstorm and research into a foundation document covering problem, users, and MVP scope.
+/quick-spec
+ Barry
+
+ Analyzes your codebase, auto-detects stack, and produces tech-spec.md with implementation-ready story files.
+/create-prd
+ PM
+
+ Creates PRD.md with user personas, requirements, success metrics, and risks.
+/create-ux-design
+ UX Designer
+
+ Creates ux-design.md with user journeys, wireframes, and a design system.
+/create-architecture
+ Architect
+
+ Designs system architecture with ADRs covering data, API, security, and deployment decisions.
+/create-epics-and-stories
+ PM
+
+ Breaks PRD and architecture into epic files with prioritized, technically-informed stories.
+/implementation-readiness
+ Architect
+
+ Validates cohesion across all planning documents to confirm you're ready to build.
+/sprint-planning
+ SM
+
+ Initializes sprint-status.yaml to track all stories through development. Run once.
+/create-story
+ SM
+
+ Prepares a story file with full context and acceptance criteria from the epic.
+/dev-story
+ DEV
+
+ Implements production code and tests following architecture patterns.
+/code-review
+ DEV
+
+ Reviews code for quality, architecture alignment, tests, and security.
Define what to build and why. Your track determines the planning workflow — Quick Flow uses a streamlined tech-spec, while BMad Method and Enterprise create a full PRD.
-quick-spec
- Analyzes your project context and codebase, auto-detects your stack, and produces tech-spec.md with implementation-ready story files in one step.
-create-prd
- Uses your product brief (if available) to create PRD.md with user personas, requirements, success metrics, and risks.
-create-ux-design
-
- Uses your PRD or tech-spec to create ux-design.md with user journeys, wireframes, and a design system.
-Make technical decisions explicit, then break work into epics and stories informed by those decisions. Architecture must come before story creation.
-create-architecture
- Uses your PRD to design the system architecture, producing architecture.md with ADRs covering data, API, security, and deployment decisions.
-create-epics-and-stories
- Combines your PRD and architecture to break work into epic files with prioritized, technically-informed stories.
-implementation-readiness
-
- Reviews all Phase 2-3 outputs to validate cohesion and produces a gate check report confirming you're ready to build.
-Build one story at a time through a repeating cycle. Complete each story's full lifecycle (dev + review) before starting the next. Use a fresh chat for each workflow run.
-sprint-planning
- Uses your epic files to initialize sprint-status.yaml, which tracks all stories through development. Run once before starting.
-create-story
- Uses the epic and sprint-status to prepare a story-[slug].md file with full context and acceptance criteria, ready for development.
-dev-story
- Uses the story file and architecture to implement production code and tests following established patterns.
-code-review
- Reviews your implemented code for quality, architecture alignment, tests, and security, producing a review report.
-epic-retrospective
- Reviews the completed epic to capture team learnings and create retrospective notes for improving the next epic.
-/epic-retrospective
+ SM
+
+ Captures learnings from a completed epic to improve the next one.