ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Replaced the old TEA brief with an indexed knowledge system: the agent now loads topic-specific

Browse Source 
docs from knowledge/ via tea-index.csv, workflows reference those fragments, and risk/level/
  priority guidance lives in the new fragment files
This commit is contained in:
Murat Ozcan
2025-09-30 10:16:51 -05:00
parent bb2cb7e951
commit b8814d372f
20 changed files with 101 additions and 405 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/modules/bmm/workflows/testarch/test-design/instructions.md
View File

@@ -1,9 +1,9 @@
<!-- Powered by BMAD-CORE™ -->
# Risk & Test Design v3.1
# Risk and Test Design v3.1
```xml
<task id="bmad/bmm/testarch/test-design" name="Risk & Test Design">
<task id="bmad/bmm/testarch/test-design" name="Risk and Test Design">
<llm critical="true">
<i>Preflight requirements:</i>
<i>- Story markdown, acceptance criteria, PRD/architecture context are available.</i>
@@ -13,8 +13,7 @@
<action>Confirm inputs; halt if any are missing or unclear.</action>
</step>
<step n="2" title="Assess Risks">
<action>Consult `{project-root}/bmad/bmm/testarch/tea-knowledge.md` for the latest risk heuristics before scoring.</action>
<action>Use `{project-root}/bmad/bmm/testarch/tea-index.csv` to pull targeted fragments (risk heuristics, fixture guidance, etc.) from `knowledge/` as needed.</action>
<action>Use `{project-root}/bmad/bmm/testarch/tea-index.csv` to load the `risk-governance`, `probability-impact`, and `test-levels` fragments before scoring.</action>
<action>Filter requirements to isolate genuine risks; review PRD/architecture/story for unresolved gaps.</action>
<action>Classify risks across TECH, SEC, PERF, DATA, BUS, OPS; request clarification when evidence is missing.</action>
<action>Score probability (1 unlikely, 2 possible, 3 likely) and impact (1 minor, 2 degraded, 3 critical); compute totals and highlight scores ≥6.</action>
@@ -22,8 +21,8 @@
</step>
<step n="3" title="Design Coverage">
<action>Break acceptance criteria into atomic scenarios tied to mitigations.</action>
<action>Choose test levels using `{project-root}/bmad/bmm/testarch/test-levels-framework.md` and avoid duplicate coverage (prefer lower levels when possible).</action>
<action>Assign priorities using `{project-root}/bmad/bmm/testarch/test-priorities-matrix.md`; outline data/tooling prerequisites and execution order.</action>
<action>Load the `test-levels` fragment (knowledge/test-levels-framework.md) to select appropriate levels and avoid duplicate coverage.</action>
<action>Load the `test-priorities` fragment (knowledge/test-priorities-matrix.md) to assign P0–P3 priorities and outline data/tooling prerequisites.</action>
</step>
<step n="4" title="Deliverables">
<action>Create risk assessment markdown (category/probability/impact/score) with mitigation matrix and gate snippet totals.</action>