4eb889642d
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 |
||
|---|---|---|
| .. | ||
| instructions.md | ||
| workflow.yaml | ||