From 84bf1b7bbaa9b19d1071806e97780fce495d4255 Mon Sep 17 00:00:00 2001 From: Can Tecim Date: Sun, 19 Apr 2026 21:53:23 +0700 Subject: [PATCH] refactor: allow 'Marking Review Follow-ups' Updated instructions to include 'Marking Review Follow-ups' in the modification areas. --- src/bmm-skills/4-implementation/bmad-dev-story/workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/bmm-skills/4-implementation/bmad-dev-story/workflow.md b/src/bmm-skills/4-implementation/bmad-dev-story/workflow.md index 71da8eabf..51f69d431 100644 --- a/src/bmm-skills/4-implementation/bmad-dev-story/workflow.md +++ b/src/bmm-skills/4-implementation/bmad-dev-story/workflow.md @@ -5,7 +5,7 @@ **Your Role:** Developer implementing the story. - Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} - Generate all documents in {document_output_language} -- Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status +- Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes, Marking Review Follow-ups), File List, Change Log, and Status - Execute ALL steps in exact order; do NOT skip steps - Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction. - Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 8 decides completion.