Compare commits

..

No commits in common. "b4d7e1adef40d1e80248640c09c35735cb02d183" and "d2d9010a8e494099b84b2cdeab1902397a12df87" have entirely different histories.

2 changed files with 5 additions and 11 deletions

View File

@ -36,7 +36,7 @@ graph TB
EpicsStories --> Framework EpicsStories --> Framework
Framework --> CI Framework --> CI
CI --> GateCheck CI --> GateCheck
Phase3Note["<b>Epics created AFTER architecture,</b><br/><b>then system-level test design and test infrastructure setup</b>"] Phase3Note["<b>Epics created AFTER architecture,</b><br/><b>then system-level test design and test infra setup</b>"]
EpicsStories -.-> Phase3Note EpicsStories -.-> Phase3Note
end end
@ -96,12 +96,12 @@ graph TB
- **Documentation** (Optional for brownfield): Prerequisite using `*document-project` - **Documentation** (Optional for brownfield): Prerequisite using `*document-project`
- **Phase 1** (Optional): Discovery/Analysis (`*brainstorm`, `*research`, `*product-brief`) - **Phase 1** (Optional): Discovery/Analysis (`*brainstorm`, `*research`, `*product-brief`)
- **Phase 2** (Required): Planning (`*prd` creates PRD with FRs/NFRs) - **Phase 2** (Required): Planning (`*prd` creates PRD with FRs/NFRs)
- **Phase 3** (Track-dependent): Solutioning (`*architecture` → `*test-design` (system-level) → `*create-epics-and-stories` → TEA: `*framework`, `*ci``*implementation-readiness`) - **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) - **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**: **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, Architecturally Significant Requirements (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, 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). - **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. Quick Flow track skips Phases 1 and 3.

View File

@ -24,14 +24,8 @@ variables:
# Output configuration # Output configuration
# Note: Actual output file determined dynamically based on mode detection # Note: Actual output file determined dynamically based on mode detection
# Declared outputs for new workflow format # - System-Level (Phase 3): {output_folder}/test-design-system.md
outputs: # - Epic-Level (Phase 4): {output_folder}/test-design-epic-{epic_num}.md
- 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" default_output_file: "{output_folder}/test-design-epic-{epic_num}.md"
# Required tools # Required tools