bmad-method 4.10.1 → 4.10.2
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/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,10 @@
|
|
|
1
|
+
## [4.10.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.1...v4.10.2) (2025-06-20)
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
### Bug Fixes
|
|
5
|
+
|
|
6
|
+
* file formatting ([c78a35f](https://github.com/bmadcode/BMAD-METHOD/commit/c78a35f547459b07a15d94c827ec05921cd21571))
|
|
7
|
+
|
|
1
8
|
## [4.10.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.0...v4.10.1) (2025-06-20)
|
|
2
9
|
|
|
3
10
|
|
|
@@ -57,12 +57,40 @@ To identify the next logical story based on project progress and epic definition
|
|
|
57
57
|
```
|
|
58
58
|
|
|
59
59
|
- Proceed only if user selects option 3 (Override) or if the last story was 'Done'.
|
|
60
|
-
- If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}*.md`) and parse it to find ALL stories in that epic.
|
|
61
|
-
-
|
|
60
|
+
- If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}*.md`) and parse it to find ALL stories in that epic. **ALWAYS select the next sequential story** (e.g., if last was 2.2, next MUST be 2.3).
|
|
61
|
+
- If the next sequential story has unmet prerequisites, present this to the user:
|
|
62
|
+
|
|
63
|
+
```plaintext
|
|
64
|
+
ALERT: Next story has unmet prerequisites:
|
|
65
|
+
Story: {epicNum}.{storyNum} - {Story Title}
|
|
66
|
+
Prerequisites not met: [list specific prerequisites]
|
|
67
|
+
|
|
68
|
+
Would you like to:
|
|
69
|
+
1. Create the story anyway (mark prerequisites as pending)
|
|
70
|
+
2. Skip to a different story (requires your specific instruction)
|
|
71
|
+
3. Cancel story creation
|
|
72
|
+
|
|
73
|
+
Please choose an option (1/2/3):
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
- If there are no more stories in the current epic (e.g., 2.9 was done and there is no 2.10):
|
|
77
|
+
|
|
78
|
+
```plaintext
|
|
79
|
+
Epic {epicNum} Complete: All stories in Epic {epicNum} have been completed.
|
|
80
|
+
|
|
81
|
+
Would you like to:
|
|
82
|
+
1. Begin Epic {epicNum + 1} with story {epicNum + 1}.1
|
|
83
|
+
2. Select a specific story to work on
|
|
84
|
+
3. Cancel story creation
|
|
85
|
+
|
|
86
|
+
Please choose an option (1/2/3):
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
- **CRITICAL**: NEVER automatically skip to another epic or non-sequential story. The user MUST explicitly instruct which story to create if skipping the sequential order.
|
|
62
90
|
|
|
63
91
|
- **If no story files exist in `docs/stories/`:**
|
|
64
|
-
- The next story is the first story
|
|
65
|
-
- If
|
|
92
|
+
- The next story is ALWAYS 1.1 (the first story of the first epic).
|
|
93
|
+
- If story 1.1 has unmet prerequisites, follow the same alert process as above.
|
|
66
94
|
- Announce the identified story to the user: "Identified next story for preparation: {epicNum}.{storyNum} - {Story Title}".
|
|
67
95
|
|
|
68
96
|
### 2. Gather Core Story Requirements (from Epic)
|
package/package.json
CHANGED