mirror of
https://github.com/bmad-code-org/BMAD-METHOD.git
synced 2026-01-30 04:32:02 +00:00
91f6c41be1
* docs: radical reduction of documentation scope for v6 beta Archive and basement unreviewed content to ship a focused, minimal doc set. Changes: - Archive stale how-to workflow guides (will rewrite for v6) - Archive outdated explanation and reference content - Move unreviewed content to basement for later review - Reorganize TEA docs into dedicated /tea/ section - Add workflow-map visual reference page - Simplify getting-started tutorial and sidebar navigation - Add explanation pages: brainstorming, adversarial-review, party-mode, quick-flow, advanced-elicitation - Fix base URL handling for subdirectory deployments (GitHub Pages forks) The goal is a minimal, accurate doc set for beta rather than comprehensive but potentially misleading content. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * refactor: restructure BMM and agents documentation by consolidating and flattening index files. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2.5 KiB
2.5 KiB
title, description
| title | description |
|---|---|
| How to Create a Story | How to create implementation-ready stories from epic backlog |
Use the create-story workflow to prepare the next story from the epic backlog for implementation.
When to Use This
- Before implementing each story
- When moving to the next story in an epic
- After sprint-planning has been run
:::note[Prerequisites]
- BMad Method installed
- SM (Scrum Master) agent available
- Sprint-status.yaml created by sprint-planning
- Architecture and PRD available for context :::
Steps
1. Load the SM Agent
Start a fresh chat and load the SM (Scrum Master) agent.
2. Run the Workflow
*create-story
3. Specify the Story
The agent will:
- Read the sprint-status.yaml
- Identify the next story to work on
- Or let you specify a particular story
4. Review the Story File
The agent creates a comprehensive story file ready for development.
What You Get
A story-[slug].md file containing:
- Story objective and scope
- Acceptance criteria (specific, testable)
- Technical implementation notes
- References to architecture decisions
- Dependencies on other stories
- Definition of Done
Story Content Sources
The create-story workflow pulls from:
- PRD — Requirements and acceptance criteria
- Architecture — Technical approach and ADRs
- Epic file — Story context and dependencies
- Existing code — Patterns to follow (brownfield)
Example Output
## Objective
Implement email verification flow for new user registrations.
## Acceptance Criteria
- [ ] User receives verification email within 30 seconds
- [ ] Email contains unique verification link
- [ ] Link expires after 24 hours
- [ ] User can request new verification email
## Technical Notes
- Use SendGrid API per ADR-003
- Store verification tokens in Redis per architecture
- Follow existing email template patterns in /templates
## Dependencies
- Story 1.1 (User Registration) - DONE
## Definition of Done
- All acceptance criteria pass
- Tests written and passing
- Code review approved
Tips
- Complete one story before creating the next — Focus on finishing
- Ensure dependencies are DONE — Don't start blocked stories
- Review technical notes — Align with architecture
- Use the story file as context — Pass to dev-story workflow
Next Steps
After creating a story:
- Implement Story — Run dev-story with the DEV agent
- Code Review — Run code-review after implementation