Implements requirements #1 and #2: stronger enforcement + progress tracking
REQUIREMENT #1: Stronger Enforcement
- dev-story Step 8 now MANDATES sprint-status.yaml update after EVERY task
- Previously: Updated only at story start (step 4) and end (step 9)
- Now: Updated after EACH task completion with CRITICAL + HALT enforcement
- Validation: Re-reads file to verify update persisted, HALTs on failure
REQUIREMENT #2: Progress Tracking
- Extended sprint-status.yaml format with inline progress comments
- Format: "story-key: in-progress # X/Y tasks (Z%)"
- Real-time visibility into story progress without opening story files
- Automatically updated by dev-story and batch-super-dev reconciliation
Progress Comment Format:
- in-progress: "# 3/10 tasks (30%)"
- review: "# 10/10 tasks (100%) - awaiting review"
- done: "# ✅ COMPLETED: Brief summary"
Benefits:
- Sprint-status.yaml becomes a real-time progress dashboard
- No need to open individual story files to check progress
- Immediate visibility when stories stall (same % for days)
- Enables better sprint planning and resource allocation
Files Modified:
- dev-story/instructions.xml (BMM + BMGD): Added mandatory task-level updates
- sprint-status/instructions.md (BMM + BMGD): Added progress parsing/display
- batch-super-dev/step-4.5-reconcile-story-status.md: Added progress to reconciliation
- docs/HOW-TO-VALIDATE-SPRINT-STATUS.md: Documented new format and enforcement
Breaking Change: None (backward compatible with old format)
- Old entries without progress comments still work
- New entries automatically add progress
- Gradual migration as stories are worked
* fix(bmm): sprint-status workflow improvements
- Remove dead by_epic template block and context_status variable (#1116, #1117)
- Define "first" story ordering as epic number then story number (#1119)
- Clarify retrospective check: "any retrospective status == optional" (#1120)
- Strengthen validate mode: check required metadata fields and valid statuses (#1121)
- Expand risk detection: stale file, orphaned stories, empty epics (#1122)
- Fix retrospective valid status: use "done" instead of "completed" for consistency
Fixes#1116, fixes#1117, fixes#1119, fixes#1120, fixes#1121, fixes#1122🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix(bmm): address CodeRabbit review feedback
- Improve retrospective status descriptions for clarity
- Fix empty epic detection to only warn on in-progress epics
- Add 'generated' to required metadata field validation
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Brian <bmadcode@gmail.com>
* fix(bmm): improve sprint-status validation and epic status handling
- Add status validation with interactive correction for unknown values
- Update epic statuses to match state machine: backlog, in-progress, done
- Map legacy "contexted" status to "in-progress" explicitly
- Add retrospective status counting (optional, completed)
- Rewrite risk detection rules for LLM clarity
- Fix warnings vs risks naming inconsistency in data mode
Closes#1106Closes#1118🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* style: fix prettier formatting in sprint-status instructions
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
The `drafted` story state is no longer used since create-story now sets
status directly to `ready-for-dev`. This PR removes all references to
this legacy state from BMM documentation and workflow files.
Changes:
- Remove `drafted` from story status definitions and state machine docs
- Remove dead story-context file detection (story-context files no longer exist)
- Replace "draft" verb with "create" in story-related messaging
- Add legacy `drafted` → `ready-for-dev` migration in sprint-status
- Clarify that validate-create-story is optional and doesn't change status
- Document story handoff sequence: create-story → (optional) validate → dev-story
Story lifecycle is now: backlog → ready-for-dev → in-progress → review → done
Closes#1089🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Removes references to epic-tech-context, story-context, story-done,
and story-ready workflows that were deleted in the Phase 4 transformation.
Also renames mislabeled excalidraw element IDs from proc-story-done
to proc-code-review to match the actual displayed text.
Fixes#1088
* 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>
Jonah Schulte
Brian Madison
Alex Verkhovsky
Dicky Moore