opensource/BMAD-METHOD
3
0
Fork 0
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-08-29 03:44:18 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(build): restore main Checkpoint 1 choices

Browse Source 
Drop the letter-coded continue/stop/edit menu and keep the wording already on main.
This commit is contained in:
Alex Verkhovsky
2026-08-27 15:45:51 -06:00
parent cac6830640
commit 993aeda192
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/bmm-skills/ship/bmad-build/step-02-plan.md
+3 -3
View File
@@ -54,9 +54,9 @@ Before approving, you can open the spec file in an editor or ask me questions an
HALT and give the user a choice:
- **[C] Approve & continue** — approve the spec and implement it in this session, directly from the spec: proceed to step-03 and take its no-subagent path (do not dispatch an implementation subagent), then step-04 as usual.
- **[S] Approve & stop** — approve the spec, leave it `ready-for-dev`, and stop; a later `bmad-build` resume dispatches implementation via step-03 normally.
- **[E] Edit** — apply the user's requested changes to the spec, then return to this checkpoint.
- **Approve and continue** — approve the spec and proceed to implementation in this session.
- **Approve and stop** — approve the spec, leave it `ready-for-dev`, and stop so a fresh `bmad-build` session can resume at implementation.
- **Review spec** — review the spec, use a subagent if available, and discuss the findings and revisions with the user until the user is ready to approve, then either stop or continue.
Before acting on approval, re-read `{spec_file}` from disk. If it is missing, HALT without recreating it, changing status, or proceeding. If it changed, acknowledge the external edits and continue with the updated version. Set status `ready-for-dev`; everything inside `<frozen-after-approval>` is then locked and only the human can change it.