bmad-method 6.2.1-next.31 → 6.2.1-next.32
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.
package/package.json
CHANGED
|
@@ -15,13 +15,27 @@ spec_file: '' # set at runtime for plan-code-review before leaving this step
|
|
|
15
15
|
- The user chose this workflow on purpose. Later steps (e.g. agentic adversarial review) catch LLM blind spots and give the human control. Do not skip them.
|
|
16
16
|
- **EARLY EXIT** means: stop this step immediately — do not read or execute anything further here. Read and fully follow the target file instead. Return here ONLY if a later step explicitly says to loop back.
|
|
17
17
|
|
|
18
|
-
##
|
|
18
|
+
## Intent check (do this first)
|
|
19
19
|
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
-
|
|
20
|
+
Before listing artifacts or prompting the user, check whether you already know the intent. Check in this order — skip the remaining checks as soon as the intent is clear:
|
|
21
|
+
|
|
22
|
+
1. Explicit argument
|
|
23
|
+
Did the user pass a specific file path, spec name, or clear instruction this message?
|
|
24
|
+
- If it points to a file that matches the tech-spec template (has `status` frontmatter with a recognized value: ready-for-dev, in-progress, or in-review) → set `spec_file` and **EARLY EXIT** to the appropriate step (step-03 for ready/in-progress, step-04 for review).
|
|
25
|
+
- Anything else (intent files, external docs, plans, descriptions) → ingest it as starting intent and proceed to INSTRUCTIONS. Do not attempt to infer a workflow state from it.
|
|
26
|
+
|
|
27
|
+
2. Recent conversation
|
|
28
|
+
Do the last few human messages clearly show what the user intends to work on?
|
|
29
|
+
Use the same routing as above.
|
|
30
|
+
|
|
31
|
+
3. Otherwise — scan artifacts and ask
|
|
32
|
+
- `{wipFile}` exists? → Offer resume or archive.
|
|
33
|
+
- Active specs (`ready-for-dev`, `in-progress`, `in-review`) in `{implementation_artifacts}`? → List them and HALT. Ask user which to resume (or `[N]` for new).
|
|
34
|
+
- If `ready-for-dev` or `in-progress` selected: Set `spec_file`. **EARLY EXIT** → `./step-03-implement.md`
|
|
35
|
+
- If `in-review` selected: Set `spec_file`. **EARLY EXIT** → `./step-04-review.md`
|
|
36
|
+
- Unformatted spec or intent file lacking `status` frontmatter? → Suggest treating its contents as the starting intent. Do NOT attempt to infer a state and resume it.
|
|
37
|
+
|
|
38
|
+
Never ask extra questions if you already understand what the user intends.
|
|
25
39
|
|
|
26
40
|
## INSTRUCTIONS
|
|
27
41
|
|