From 978a93ed331757ab341dd4a1330d58aedb2b9254 Mon Sep 17 00:00:00 2001 From: murat Date: Thu, 11 Dec 2025 09:34:22 -0600 Subject: [PATCH 1/5] docs: test arch ADR usage update --- package-lock.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package-lock.json b/package-lock.json index 6af9597d..e14a1431 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "bmad-method", - "version": "6.0.0-alpha.15", + "version": "6.0.0-alpha.16", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "bmad-method", - "version": "6.0.0-alpha.15", + "version": "6.0.0-alpha.16", "license": "MIT", "dependencies": { "@kayvan/markdown-tree-parser": "^1.6.1", From 6d5a1084ebf8fa42e78a53824e2ea5aa2be6943e Mon Sep 17 00:00:00 2001 From: murat Date: Thu, 11 Dec 2025 09:43:25 -0600 Subject: [PATCH 2/5] docs: test arch ADR usage update 2 --- src/modules/bmm/docs/test-architecture.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/src/modules/bmm/docs/test-architecture.md b/src/modules/bmm/docs/test-architecture.md index 76b75bf3..52527931 100644 --- a/src/modules/bmm/docs/test-architecture.md +++ b/src/modules/bmm/docs/test-architecture.md @@ -26,14 +26,17 @@ graph TB subgraph Phase3["Phase 3: SOLUTIONING"] Architecture["Architect: *architecture"] EpicsStories["PM/Architect: *create-epics-and-stories"] + TestDesignSys["TEA: *test-design (system-level)"] Framework["TEA: *framework"] CI["TEA: *ci"] GateCheck["Architect: *implementation-readiness"] Architecture --> EpicsStories + Architecture --> TestDesignSys + TestDesignSys --> Framework EpicsStories --> Framework Framework --> CI CI --> GateCheck - Phase3Note["Epics created AFTER architecture,
then test infrastructure setup"] + Phase3Note["Epics created AFTER architecture,
then system-level test design and test infra setup"] EpicsStories -.-> Phase3Note end @@ -96,9 +99,12 @@ graph TB - **Phase 3** (Track-dependent): Solutioning (`*architecture` → `*create-epics-and-stories` → TEA: `*framework`, `*ci` → `*implementation-readiness`) - **Phase 4** (Required): Implementation (`*sprint-planning` → per-epic: `*test-design` → per-story: dev workflows) -**TEA workflows:** `*framework` and `*ci` run once in Phase 3 after architecture. `*test-design` runs per-epic in Phase 4. Output: `test-design-epic-N.md`. +**TEA workflows:** `*framework` and `*ci` run once in Phase 3 after architecture. `*test-design` is **dual-mode**: -Quick Flow track skips Phase 1 and 3. BMad Method and Enterprise use all phases based on project needs. +- **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. ### Why TEA is Different from Other BMM Agents 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 3/5] 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 From 6e9fe6c9a2eebc934f69cedaaa90b7bcba241cdb Mon Sep 17 00:00:00 2001 From: murat Date: Thu, 11 Dec 2025 11:35:26 -0600 Subject: [PATCH 4/5] fix: addressed review comment --- .../bmm/workflows/testarch/test-design/workflow.yaml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/modules/bmm/workflows/testarch/test-design/workflow.yaml b/src/modules/bmm/workflows/testarch/test-design/workflow.yaml index 9a1042c1..176230e0 100644 --- a/src/modules/bmm/workflows/testarch/test-design/workflow.yaml +++ b/src/modules/bmm/workflows/testarch/test-design/workflow.yaml @@ -24,8 +24,14 @@ variables: # Output configuration # Note: Actual output file determined dynamically based on mode detection -# - System-Level (Phase 3): {output_folder}/test-design-system.md -# - Epic-Level (Phase 4): {output_folder}/test-design-epic-{epic_num}.md +# Declared outputs for new workflow format +outputs: + - id: system-level + description: "System-level testability review (Phase 3)" + path: "{output_folder}/test-design-system.md" + - id: epic-level + description: "Epic-level test plan (Phase 4)" + path: "{output_folder}/test-design-epic-{epic_num}.md" default_output_file: "{output_folder}/test-design-epic-{epic_num}.md" # Required tools From b4d7e1adef40d1e80248640c09c35735cb02d183 Mon Sep 17 00:00:00 2001 From: murat Date: Thu, 11 Dec 2025 13:13:44 -0600 Subject: [PATCH 5/5] docs: addressed further PR comments --- src/modules/bmm/docs/test-architecture.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/modules/bmm/docs/test-architecture.md b/src/modules/bmm/docs/test-architecture.md index 5637f0b5..49fdba5f 100644 --- a/src/modules/bmm/docs/test-architecture.md +++ b/src/modules/bmm/docs/test-architecture.md @@ -36,7 +36,7 @@ graph TB EpicsStories --> Framework Framework --> CI CI --> GateCheck - Phase3Note["Epics created AFTER architecture,
then system-level test design and test infra setup"] + Phase3Note["Epics created AFTER architecture,
then system-level test design and test infrastructure setup"] EpicsStories -.-> Phase3Note end @@ -96,12 +96,12 @@ graph TB - **Documentation** (Optional for brownfield): Prerequisite using `*document-project` - **Phase 1** (Optional): Discovery/Analysis (`*brainstorm`, `*research`, `*product-brief`) - **Phase 2** (Required): Planning (`*prd` creates PRD with FRs/NFRs) -- **Phase 3** (Track-dependent): Solutioning (`*architecture` → `*create-epics-and-stories` → TEA: `*framework`, `*ci` → `*implementation-readiness`) +- **Phase 3** (Track-dependent): Solutioning (`*architecture` → `*test-design` (system-level) → `*create-epics-and-stories` → TEA: `*framework`, `*ci` → `*implementation-readiness`) - **Phase 4** (Required): Implementation (`*sprint-planning` → per-epic: `*test-design` → per-story: dev workflows) **TEA workflows:** `*framework` and `*ci` run once in Phase 3 after architecture. `*test-design` is **dual-mode**: -- **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. +- **System-level (Phase 3):** Run immediately after architecture/ADR drafting to produce `test-design-system.md` (testability review, ADR → test mapping, Architecturally Significant Requirements (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 Phases 1 and 3.