@stefanoginella/auto-bmad 0.1.25 → 0.1.26
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/README.md +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# 🤖 Auto BMAD
|
|
2
2
|
|
|
3
|
-
[](https://docs.anthropic.com/en/docs/claude-code) [](https://www.npmjs.com/package/@stefanoginella/auto-bmad) [](LICENSE.md) [](https://docs.anthropic.com/en/docs/claude-code) [](https://github.com/bmad-code-org/BMAD-METHOD)
|
|
4
4
|
|
|
5
5
|
Automated (and very opinionated) BMAD pipeline orchestration for Claude Code.
|
|
6
6
|
|
|
@@ -14,7 +14,7 @@ Four sequential pipeline commands that drive the BMAD software development lifec
|
|
|
14
14
|
|---------|-------|-------------|
|
|
15
15
|
| `/auto-bmad-plan` | 11 | Pre-implementation pipeline: product brief, PRD, validate, UX, architecture, test framework, test design, epics, readiness, project context, sprint planning |
|
|
16
16
|
| `/auto-bmad-epic-start` | 1 | Start a new epic: epic-level test design |
|
|
17
|
-
| `/auto-bmad-story` |
|
|
17
|
+
| `/auto-bmad-story` | 13 | Develop a story: create, validate, adversarial review, ATDD, develop, edge-case hunt, 3x code review, NFR, trace, automate, test review |
|
|
18
18
|
| `/auto-bmad-epic-end` | 3 | Close an epic: trace, retrospective, project context refresh |
|
|
19
19
|
|
|
20
20
|
## 🗂 Artifacts
|
|
@@ -36,7 +36,7 @@ This is what a complete workflow using the pipelines might look like. If you alr
|
|
|
36
36
|
2. **Run `/auto-bmad-plan`** to kick off the initial planning pipeline for a new project or major initiative. This sets up the overall architecture, test framework, CI configuration, and initial epics and stories.
|
|
37
37
|
3. **Review the PRD, Architecture, UX design, Epics, and Test Plan** generated by the plan pipeline. Make sure they look good and adjust if necessary before moving on to implementation. You might want to go through a few iterations of `/bmad-party-mode` to refine the output, since it sets the foundation for the next steps.
|
|
38
38
|
4. **For each new epic**, run `/auto-bmad-epic-start` to establish a baseline and plan the story order based on the epic's goals and dependencies.
|
|
39
|
-
5. **For each story within an epic**, run `/auto-bmad-story` to develop the story from creation through delivery, including validation, ATDD, development,
|
|
39
|
+
5. **For each story within an epic**, run `/auto-bmad-story` to develop the story from creation through delivery, including validation, adversarial review, ATDD, development, edge-case hunt, code review, NFR, traceability, test automation, and test review.
|
|
40
40
|
6. **After each story**, review the report generated by the story pipeline and any other BMAD artifacts, perform some manual testing, and correct course if necessary.
|
|
41
41
|
7. **At the end of an epic**, run `/auto-bmad-epic-end` to close the epic, aggregate data, perform a traceability gate, conduct a retrospective, and preview the next epic.
|
|
42
42
|
8. **Review the outputs of each pipeline run**, check the generated artifacts, and make adjustments as needed. The pipelines are opinionated and automated, but they still require human judgment and iteration. Use `/bmad-bmm-correct-course` when big changes are needed.
|