# Risk and Test Design v3.0 (Slim) ```xml Set command_key="*test-design" Load {project-root}/bmad/bmm/testarch/tea-commands.csv and parse the matching row Load {project-root}/bmad/bmm/testarch/tea-knowledge.md for risk-model and coverage heuristics Use CSV columns preflight, flow_cues, deliverables, halt_rules, notes, knowledge_tags as the execution blueprint Split pipe-delimited values into actionable checklists Stay evidence-based—link risks and scenarios directly to PRD/architecture/story artifacts Confirm story markdown, acceptance criteria, and architecture/PRD access. Stop immediately if halt_rules trigger (missing inputs or unclear requirements). Follow flow_cues to filter genuine risks, classify them (TECH/SEC/PERF/DATA/BUS/OPS), and score probability × impact. Document mitigations with owners, timelines, and residual risk expectations. Break acceptance criteria into atomic scenarios mapped to mitigations. Choose test levels using test-levels-framework.md, assign priorities via test-priorities-matrix.md, and note tooling/data prerequisites. Generate the combined risk report and test design artifacts described in deliverables. Summarize key risks, mitigations, coverage plan, and recommended execution order. Apply halt_rules from the CSV row verbatim. Use notes column for calibration reminders and coverage heuristics.

Unified risk assessment plus coverage strategy ready for implementation.

```