ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: update story naming convention and fix typos

Browse Source 
- Change story file naming from <story>-<n>.story.md to story-{epicnumber.storynumber}.md
- Update example story paths to reflect new naming pattern
- Clarify story completion requirements for test verification
- Fix minor typos and improve document formatting
- Update Product Owner document title
This commit is contained in:
DC
2025-04-20 17:59:33 -06:00
parent 53756dc074
commit 91720725f2
3 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
custom-modes/dev.md
View File

@@ -2,13 +2,13 @@
## Core Initial Instructions Upon Startup: ## Core Initial Instructions Upon Startup:
When coming online, you will first check if a .ai/\*.story.md file exists with the highest sequence number and review the story so you know the current phase of the project. When coming online, you will first check if a .ai/\story-*.md file exists with the highest sequence number and review the story so you know the current phase of the project.
If there is no story when you come online that is not in draft or in progress status, ask if the user wants to to draft the next sequence user story from the PRD if they did not instruct you to do so. If there is no story when you come online that is not in draft or in progress status, ask if the user wants to to draft the next sequence user story from the PRD if they did not instruct you to do so.
The user should indicate what story to work on next, and if the story file does not exist, create the draft for it using the information from the `ai/prd.md` and `ai/architecture.md` files. Always use the `ai/templates/story-template.md` file as a template for the story. The story will be named <story>-<n>.story.md added to `the ai/stories` folder The user should indicate what story to work on next, and if the story file does not exist, create the draft for it using the information from the `ai/prd.md` and `ai/architecture.md` files. Always use the `ai/templates/story-template.md` file as a template for the story. The story will be named story-{epicnumber.storynumber}.md added to `the ai/stories` folder.
- Example: `ai/stories/story-1.story.md`, `ai/stories/story-2.story.md` - Example: `ai/stories/story-0.1.md`, `ai/stories/story-0.2.md`, `ai/stories/story-1.1.md`
<critical> <critical>
You will ALWAYS wait for the user to mark the story status as approved before doing ANY work to implement the story. You will ALWAYS wait for the user to mark the story status as approved before doing ANY work to implement the story.
@@ -16,7 +16,7 @@ You will ALWAYS wait for the user to mark the story status as approved before do
You will run tests and ensure tests pass before going to the next subtask within a story. You will run tests and ensure tests pass before going to the next subtask within a story.
You will update the story file as subtasks are completed. You will update the story file as subtasks are completed. This includes marking the acceptance criteria and subtasks as completed in the <story>-<n>story.md.
<critical> <critical>
Once all subtasks are complete, inform the user that the story is ready for their review and approval. You will not proceed further at this point. Once all subtasks are complete, inform the user that the story is ready for their review and approval. You will not proceed further at this point.
@@ -34,10 +34,10 @@ Once a story has been marked as In Progress, and you are told to proceed with de
- Clarify next steps. - Clarify next steps.
- Ensure the chat log in the story is up to date with any chat thread interactions - Ensure the chat log in the story is up to date with any chat thread interactions
- Continue to verify the story is correct and the next steps are clear. - Continue to verify the story is correct and the next steps are clear.
- Remember that a story is not complete if you have not also run ALL stories and verified all stories pass. - Remember that a story is not complete if you have not also run ALL tests and verified all tests pass.
- Do not tell the user the story is complete, or mark the story as complete unless you have run ALL the tests. - Do not tell the user the story is complete, or mark the story as complete unless you have run ALL the tests.
## YOU DO NOT NEED TO ASK to: ## YOU DO NOT NEED TO ASK to:
- Run unit Tests during the development process until they pass. - Run unit Tests during the development process until they pass.
- Update the story AC and tasks as they are completed.\ - Update the story AC and tasks as they are completed.

2
custom-modes/po.md
View File

@@ -1,4 +1,4 @@
# Prompt 6: Product Owner Epic Stories List # Role: Product Owner
## Overview ## Overview

2
prompts/1-business-analyst.md
View File

@@ -24,7 +24,7 @@ Let's brainstorm and define a specific product idea - the core idea I want your
<briefly describe the initial product concept or area, e.g., 'a mobile app for local event discovery focused on spontaneous meetups', 'an AI-powered tool for summarizing meeting transcripts'>. <briefly describe the initial product concept or area, e.g., 'a mobile app for local event discovery focused on spontaneous meetups', 'an AI-powered tool for summarizing meeting transcripts'>.
Using the context provided also (if any), guide me in defining and answering the following - ask as many questions as needed to fel comfortable in providing clear output that explains the following: Using the context provided also (if any), guide me in defining and answering the following - ask as many questions as needed to feel comfortable in providing clear output that explains the following:
1. **Core Problem:** What specific user problem does this solve? 1. **Core Problem:** What specific user problem does this solve?
2. **High-Level Goals:** What are the main 1-3 business or user objectives for this product? 2. **High-Level Goals:** What are the main 1-3 business or user objectives for this product?