bmad-method 6.9.1-next.4 → 6.9.1-next.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/bmm-skills/4-implementation/bmad-dev-auto/step-01-clarify-and-route.md +1 -1
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/package.json",
3
3
  "name": "bmad-method",
4
- "version": "6.9.1-next.4",
4
+ "version": "6.9.1-next.5",
5
5
  "description": "Breakthrough Method of Agile AI-driven Development",
6
6
  "keywords": [
7
7
  "agile",
package/src/bmm-skills/4-implementation/bmad-dev-auto/step-01-clarify-and-route.md CHANGED
@@ -20,7 +20,7 @@ If the invocation prompt explicitly points to an existing spec file with recogni
20
20
  - `ready-for-dev` or `in-progress` → `./step-03-implement.md`
21
21
  - `in-review` → `./step-04-review.md`
22
22
  - `blocked` → HALT with status `blocked` and blocking condition `blocked spec supplied`.
23
- - `done` → ingest as context and proceed to INSTRUCTIONS — do not resume.
23
+ - `done` → set `review_loop_iteration` to `0` in the frontmatter, then **EARLY EXIT** to `./step-04-review.md` for a fresh review pass. (A `done` spec is a completed run, so this starts a follow-up review, not a resumption.)
24
24
 
25
25
  Otherwise, treat the invocation prompt as starting intent. This may be a story ID, ticket ID, file path, short description, or longer free-form intent. Do not infer workflow state from non-spec files.
26
26
  If the invocation prompt does not contain enough intent to identify what to implement, HALT with status `blocked` and blocking condition `unclear intent`.