mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
Feat/sprint status command (#1012)
* feat: add sprint-status command * minor changes to reduce the change radius --------- Co-authored-by: mq-bot <mq-bot@local> Co-authored-by: Brian <bmadcode@gmail.com>
This commit is contained in:
@@ -108,7 +108,8 @@ Stories move through these states in the sprint status file:
|
||||
|
||||
**As Needed:**
|
||||
|
||||
- Run `workflow-status` anytime to check progress
|
||||
- Run `sprint-status` anytime in Phase 4 to inspect sprint-status.yaml and get the next implementation command
|
||||
- Run `workflow-status` for cross-phase routing and project-level paths
|
||||
- Run `correct-course` if significant changes needed
|
||||
|
||||
---
|
||||
@@ -155,7 +156,7 @@ PRD (PM) → Architecture (Architect)
|
||||
## Troubleshooting
|
||||
|
||||
**Q: Which workflow should I run next?**
|
||||
A: Run `workflow-status` - it reads the sprint status file and tells you exactly what to do.
|
||||
A: Run `workflow-status` - it reads the sprint status file and tells you exactly what to do. During implementation (Phase 4) run `sprint-status` (fast check against sprint-status.yaml).
|
||||
|
||||
**Q: Story needs significant changes mid-implementation?**
|
||||
A: Run `correct-course` to analyze impact and route appropriately.
|
||||
|
||||
Reference in New Issue
Block a user