From d2d9010a8e494099b84b2cdeab1902397a12df87 Mon Sep 17 00:00:00 2001
From: Murat K Ozcan <34237651+muratkeremozcan@users.noreply.github.com>
Date: Thu, 11 Dec 2025 10:15:23 -0600
Subject: [PATCH] Update src/modules/bmm/docs/test-architecture.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---
 src/modules/bmm/docs/test-architecture.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/modules/bmm/docs/test-architecture.md b/src/modules/bmm/docs/test-architecture.md
index 52527931..5637f0b5 100644
--- a/src/modules/bmm/docs/test-architecture.md
+++ b/src/modules/bmm/docs/test-architecture.md
@@ -104,7 +104,9 @@ graph TB
 - **System-level (Phase 3):** Run immediately after architecture/ADR drafting to produce `test-design-system.md` (testability review, ADR → test mapping, ASRs, environment needs). Feeds the implementation-readiness gate.
 - **Epic-level (Phase 4):** Run per-epic to produce `test-design-epic-N.md` (risk, priorities, coverage plan).
 
-Quick Flow track skips Phase 1 and 3. BMad Method and Enterprise use all phases based on project needs. When an ADR/architecture draft is produced, run `*test-design` in **system-level** mode before the implementation-readiness gate so the ADR has an attached testability review and ADR → test mapping; keep it updated if ADRs change.
+Quick Flow track skips Phases 1 and 3.
+BMad Method and Enterprise use all phases based on project needs.
+When an ADR or architecture draft is produced, run `*test-design` in **system-level** mode before the implementation-readiness gate. This ensures the ADR has an attached testability review and ADR → test mapping. Keep the test-design updated if ADRs change.
 
 ### Why TEA is Different from Other BMM Agents