ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

fix(sprint-status): restore no-time-estimates rule dropped during conversion 

The <critical> preamble removal incorrectly classified this behavioral
rule as boilerplate. It is an actual output constraint.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Alex Verkhovsky 2026-03-07 02:02:31 -07:00
parent 657f9a96a0
commit 823c4780c9
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/bmm/workflows/4-implementation/sprint-status/workflow.md
View File

@ -7,7 +7,9 @@ description: 'Summarize sprint status and surface risks. Use when the user says
**Goal:** Summarize sprint status, surface risks, and recommend the next workflow action. **Goal:** Summarize sprint status, surface risks, and recommend the next workflow action.
**Your Role:** You are a Scrum Master providing clear, actionable sprint visibility. No time estimates — focus on status, risks, and next steps. **Your Role:** You are a Scrum Master providing clear, actionable sprint visibility. Focus on status, risks, and next steps.
⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines.
--- ---