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

fix(quick-dev): scope editor open and summary to plan-code-review only 

One-shot mode displays the review order in conversation output and has
no spec file to open. Guard the code -r step and spec-specific summary
items behind plan-code-review.
This commit is contained in:
Alex Verkhovsky 2026-03-17 09:53:34 -06:00
parent 39359ddbcd
commit 653c3ae152
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/step-05-present.md
View File

@ -55,13 +55,12 @@ When there is only one concern, omit the bold label — just list the stops dire
1. **Plan-code-review:** Change `{spec_file}` status to `done` in the frontmatter. 1. **Plan-code-review:** Change `{spec_file}` status to `done` in the frontmatter.
2. If version control is available and the tree is dirty, create a local commit with a conventional message derived from the spec title (plan-code-review) or the intent (one-shot). 2. If version control is available and the tree is dirty, create a local commit with a conventional message derived from the spec title (plan-code-review) or the intent (one-shot).
3. Open the spec in the user's editor so they can click through the Suggested Review Order: 3. **Plan-code-review only:** Open the spec in the user's editor so they can click through the Suggested Review Order:
- Run `code -r "{spec_file}"` to open the spec in the current VS Code window (reuses the window where the project or worktree is open). Always double-quote the path to handle spaces and special characters. - Run `code -r "{spec_file}"` to open the spec in the current VS Code window (reuses the window where the project or worktree is open). Always double-quote the path to handle spaces and special characters.
- If `code` is not available (command fails), skip gracefully and tell the user the spec file path instead. - If `code` is not available (command fails), skip gracefully and tell the user the spec file path instead.
4. Display summary of your work to the user, including the commit hash if one was created. Include: 4. Display summary of your work to the user, including the commit hash if one was created. Include:
- A note that the spec is open in their editor (or the file path if it couldn't be opened). - **Plan-code-review:** A note that the spec is open in their editor (or the file path if it couldn't be opened). Mention that `{spec_file}` now contains a Suggested Review Order.
- **Navigation tip:** "Ctrl+click (Cmd+click on macOS) the links in the Suggested Review Order to jump to each stop." - **Navigation tip:** "Ctrl+click (Cmd+click on macOS) the links in the Suggested Review Order to jump to each stop."
- For plan-code-review, mention that `{spec_file}` now contains a Suggested Review Order.
- Offer to push and/or create a pull request. - Offer to push and/or create a pull request.
Workflow complete. Workflow complete.