From c78a35f547459b07a15d94c827ec05921cd21571 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Thu, 19 Jun 2025 22:47:57 -0500 Subject: [PATCH] fix: file formatting --- bmad-core/tasks/create-next-story.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/bmad-core/tasks/create-next-story.md b/bmad-core/tasks/create-next-story.md index 0d936a81..ed4fe3a6 100644 --- a/bmad-core/tasks/create-next-story.md +++ b/bmad-core/tasks/create-next-story.md @@ -59,7 +59,7 @@ To identify the next logical story based on project progress and epic definition - Proceed only if user selects option 3 (Override) or if the last story was 'Done'. - If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}*.md`) and parse it to find ALL stories in that epic. **ALWAYS select the next sequential story** (e.g., if last was 2.2, next MUST be 2.3). - If the next sequential story has unmet prerequisites, present this to the user: - + ```plaintext ALERT: Next story has unmet prerequisites: Story: {epicNum}.{storyNum} - {Story Title} @@ -72,9 +72,9 @@ To identify the next logical story based on project progress and epic definition Please choose an option (1/2/3): ``` - + - If there are no more stories in the current epic (e.g., 2.9 was done and there is no 2.10): - + ```plaintext Epic {epicNum} Complete: All stories in Epic {epicNum} have been completed. @@ -85,7 +85,7 @@ To identify the next logical story based on project progress and epic definition Please choose an option (1/2/3): ``` - + - **CRITICAL**: NEVER automatically skip to another epic or non-sequential story. The user MUST explicitly instruct which story to create if skipping the sequential order. - **If no story files exist in `docs/stories/`:**