Compare commits

...

4 Commits

Author SHA1 Message Date
Michael Pursifull e22f4e1fa1
Merge 0c34e62530 into dd8c54cc9f 2026-01-29 00:03:17 +08:00
Michael Pursifull 0c34e62530
Merge branch 'main' into fix/embedded-src-bmm-paths 2026-01-28 00:53:16 -06:00
Michael Pursifull ab9d13497e
Merge branch 'main' into fix/embedded-src-bmm-paths 2026-01-28 00:03:17 -06:00
Michael Pursifull f26e1aa38b
fix: correct embedded file paths to use _bmad/bmm instead of src/bmm
Paths in workflow step files reference `{project-root}/src/bmm/...` which
works in the source repository but breaks when installed to a project
(where the path should be `{project-root}/_bmad/bmm/...`).

Files fixed:
- PRD workflow steps (step-e-01, step-e-01b, step-e-02, step-e-03)
- Test design workflow (tea-index.csv references)

Fixes #1436
2026-01-27 23:57:51 -06:00
1 changed files with 2 additions and 2 deletions

View File

@ -105,7 +105,7 @@ TEA test-design workflow supports TWO modes, detected automatically:
3. **Load Knowledge Base Fragments (System-Level)**
**Critical:** Consult `src/bmm/testarch/tea-index.csv` to load:
**Critical:** Consult `{project-root}/_bmad/bmm/testarch/tea-index.csv` to load:
- `adr-quality-readiness-checklist.md` - 8-category 29-criteria NFR framework (testability, security, scalability, DR, QoS, deployability, etc.)
- `test-levels-framework.md` - Test levels strategy guidance
- `risk-governance.md` - Testability risk identification
@ -139,7 +139,7 @@ TEA test-design workflow supports TWO modes, detected automatically:
4. **Load Knowledge Base Fragments (Epic-Level)**
**Critical:** Consult `src/bmm/testarch/tea-index.csv` to load:
**Critical:** Consult `{project-root}/_bmad/bmm/testarch/tea-index.csv` to load:
- `risk-governance.md` - Risk classification framework (6 categories: TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, owner tracking (625 lines, 4 examples)
- `probability-impact.md` - Risk scoring methodology (probability × impact matrix, automated classification, dynamic re-assessment, gate integration, 604 lines, 4 examples)
- `test-levels-framework.md` - Test level selection guidance (E2E vs API vs Component vs Unit with decision matrix, characteristics, when to use each, 467 lines, 4 examples)