From 823c4780c9a7e028af3bb492e2e90649eafc5aa3 Mon Sep 17 00:00:00 2001 From: Alex Verkhovsky Date: Sat, 7 Mar 2026 02:02:31 -0700 Subject: [PATCH] fix(sprint-status): restore no-time-estimates rule dropped during conversion The preamble removal incorrectly classified this behavioral rule as boilerplate. It is an actual output constraint. Co-Authored-By: Claude Opus 4.6 --- src/bmm/workflows/4-implementation/sprint-status/workflow.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/bmm/workflows/4-implementation/sprint-status/workflow.md b/src/bmm/workflows/4-implementation/sprint-status/workflow.md index aeed0ab23..859faec3e 100644 --- a/src/bmm/workflows/4-implementation/sprint-status/workflow.md +++ b/src/bmm/workflows/4-implementation/sprint-status/workflow.md @@ -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. -**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. ---