--- ---
Choose a track above to see the recommended 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.
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.