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

docs(code-review): use variable reference for sprint-status path

This commit is contained in:
Alex Verkhovsky 2026-01-05 07:21:44 -08:00
parent 3fc411d9c9
commit 551a2ccb53
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/modules/bmm/workflows/4-implementation/code-review/steps/step-01-load-story.md
View File

@ -28,17 +28,14 @@ Ask user: "Which story would you like to review?"
**Try input as direct file path first:** **Try input as direct file path first:**
If input resolves to an existing file: If input resolves to an existing file:
- Verify it's in `sprint_status` with status `review` or `done` - Verify it's in {implementation_artifacts}/sprint-status.yaml with status `review` or `done`
- If verified → set `story_path` to that file path - If verified → set `story_path` to that file path
- If NOT verified → Warn user the file is not in sprint_status (or wrong status). Ask: "Continue anyway?" - If NOT verified → Warn user the file is not in {implementation_artifacts}/sprint-status.yaml (or wrong status). Ask: "Continue anyway?"
- If yes → set `story_path` - If yes → set `story_path`
- If no → return to user prompt (ask "Which story would you like to review?" again) - If no → return to user prompt (ask "Which story would you like to review?" again)
**Search sprint_status** (if input is not a direct file): **Search {implementation_artifacts}/sprint-status.yaml** (if input is not a direct file):
Search for stories with status `review` or `done`. Match by priority:
The `sprint_status` file (`{implementation_artifacts}/sprint-status.yaml`) is generated by the sprint-planning workflow and contains the development_status map with all epics and stories, along with their current status (backlog, ready-for-dev, in-progress, review, done).
Search this file for stories with status `review` or `done`. Match by priority:
1. Story number resembles input closely enough (e.g., "1-2" matches "1 2", "1.2", "one dash two", "one two"; "1-32" matches "one thirty two"). Do NOT match if numbers differ (e.g., "1-33" does not match "1-32") 1. Story number resembles input closely enough (e.g., "1-2" matches "1 2", "1.2", "one dash two", "one two"; "1-32" matches "one thirty two"). Do NOT match if numbers differ (e.g., "1-33" does not match "1-32")
2. Exact story name/key (e.g., "1-2-user-auth-api") 2. Exact story name/key (e.g., "1-2-user-auth-api")
3. Story name/title resembles input closely enough 3. Story name/title resembles input closely enough