bmm-opencode 1.5.0 → 1.6.0

package/_bmad/tea/workflows/testarch/test-design/steps-c/step-02-load-context.md

@@ -0,0 +1,127 @@
+---
+name: 'step-02-load-context'
+description: 'Load documents, configuration, and knowledge fragments for the chosen mode'
+nextStepFile: './step-03-risk-and-testability.md'
+knowledgeIndex: '{project-root}/_bmad/tea/testarch/tea-index.csv'
+---
+
+# Step 2: Load Context & Knowledge Base
+
+## STEP GOAL
+
+Load the required documents, config flags, and knowledge fragments needed to produce accurate test design outputs.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- 🎯 Only load artifacts required for the selected mode
+
+---
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Record outputs before proceeding
+- 📖 Load the next step only when instructed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: config, loaded artifacts, and knowledge fragments
+- Focus: this step's goal only
+- Limits: do not execute future steps
+- Dependencies: prior steps' outputs (if any)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+## 1. Load Configuration
+
+From `{config_source}`:
+
+- Read `tea_use_playwright_utils`
+- Note `output_folder`
+
+---
+
+## 2. Load Project Artifacts (Mode-Specific)
+
+### System-Level Mode (Phase 3)
+
+Load:
+
+- PRD (FRs + NFRs)
+- ADRs or architecture decisions
+- Architecture / tech-spec document
+- Epics (for scope)
+
+Extract:
+
+- Tech stack & dependencies
+- Integration points
+- NFRs (performance, security, reliability, compliance)
+
+### Epic-Level Mode (Phase 4)
+
+Load:
+
+- Epic and story docs with acceptance criteria
+- PRD (if available)
+- Architecture / tech-spec (if available)
+- Prior system-level test-design outputs (if available)
+
+Extract:
+
+- Testable requirements
+- Integration points
+- Known coverage gaps
+
+---
+
+## 3. Analyze Existing Test Coverage (Epic-Level)
+
+If epic-level:
+
+- Scan the repository for existing tests (search for `tests/`, `spec`, `e2e`, `api` folders)
+- Identify coverage gaps and flaky areas
+- Note existing fixture and test patterns
+
+---
+
+## 4. Load Knowledge Base Fragments
+
+Use `{knowledgeIndex}` to select and load only relevant fragments.
+
+### System-Level Mode (Required)
+
+- `adr-quality-readiness-checklist.md`
+- `test-levels-framework.md`
+- `risk-governance.md`
+- `test-quality.md`
+
+### Epic-Level Mode (Required)
+
+- `risk-governance.md`
+- `probability-impact.md`
+- `test-levels-framework.md`
+- `test-priorities-matrix.md`
+
+---
+
+## 5. Confirm Loaded Inputs
+
+Summarize what was loaded and confirm with the user if anything is missing.
+
+Load next step: `{nextStepFile}`
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Step completed in full with required outputs
+
+### ❌ SYSTEM FAILURE:
+
+- Skipped sequence steps or missing outputs
+  **Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/tea/workflows/testarch/test-design/steps-c/step-03-risk-and-testability.md

@@ -0,0 +1,85 @@
+---
+name: 'step-03-risk-and-testability'
+description: 'Perform testability review (system-level) and risk assessment'
+nextStepFile: './step-04-coverage-plan.md'
+---
+
+# Step 3: Testability & Risk Assessment
+
+## STEP GOAL
+
+Produce a defensible testability review (system-level) and a risk assessment matrix (all modes).
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- 🎯 Base conclusions on evidence from loaded artifacts
+
+---
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Record outputs before proceeding
+- 📖 Load the next step only when instructed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: config, loaded artifacts, and knowledge fragments
+- Focus: this step's goal only
+- Limits: do not execute future steps
+- Dependencies: prior steps' outputs (if any)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+## 1. System-Level Mode: Testability Review
+
+If **system-level**, evaluate architecture for:
+
+- **Controllability** (state seeding, mockability, fault injection)
+- **Observability** (logs, metrics, traces, deterministic assertions)
+- **Reliability** (isolation, reproducibility, parallel safety)
+
+**Structure output as:**
+
+1. **🚨 Testability Concerns** (actionable issues first)
+2. **✅ Testability Assessment Summary** (what is already strong)
+
+Also identify **ASRs** (Architecturally Significant Requirements):
+
+- Mark each as **ACTIONABLE** or **FYI**
+
+---
+
+## 2. All Modes: Risk Assessment
+
+Using `risk-governance.md` and `probability-impact.md` (if loaded):
+
+- Identify real risks (not just features)
+- Classify by category: TECH / SEC / PERF / DATA / BUS / OPS
+- Score Probability (1–3) and Impact (1–3)
+- Calculate Risk Score (P × I)
+- Flag high risks (score ≥ 6)
+- Define mitigation, owner, and timeline
+
+---
+
+## 3. Summarize Risk Findings
+
+Summarize the highest risks and their mitigation priorities.
+
+Load next step: `{nextStepFile}`
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Step completed in full with required outputs
+
+### ❌ SYSTEM FAILURE:
+
+- Skipped sequence steps or missing outputs
+  **Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/tea/workflows/testarch/test-design/steps-c/step-04-coverage-plan.md

@@ -0,0 +1,98 @@
+---
+name: 'step-04-coverage-plan'
+description: 'Design test coverage, priorities, execution strategy, and estimates'
+nextStepFile: './step-05-generate-output.md'
+---
+
+# Step 4: Coverage Plan & Execution Strategy
+
+## STEP GOAL
+
+Create the test coverage matrix, prioritize scenarios, and define execution strategy, resource estimates, and quality gates.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- 🚫 Avoid redundant coverage across test levels
+
+---
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Record outputs before proceeding
+- 📖 Load the next step only when instructed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: config, loaded artifacts, and knowledge fragments
+- Focus: this step's goal only
+- Limits: do not execute future steps
+- Dependencies: prior steps' outputs (if any)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+## 1. Coverage Matrix
+
+For each requirement or risk-driven scenario:
+
+- Decompose into atomic test scenarios
+- Select **test level** (E2E / API / Component / Unit) using `test-levels-framework.md`
+- Ensure no duplicate coverage across levels
+- Assign priorities (P0–P3) using `test-priorities-matrix.md`
+
+**Priority rules:**
+
+- P0: Blocks core functionality + high risk + no workaround
+- P1: Critical paths + medium/high risk
+- P2: Secondary flows + low/medium risk
+- P3: Nice-to-have, exploratory, benchmarks
+
+---
+
+## 2. Execution Strategy (Keep Simple)
+
+Use a **PR / Nightly / Weekly** model:
+
+- **PR**: All functional tests if <15 minutes
+- **Nightly/Weekly**: Long-running or expensive suites (perf, chaos, large datasets)
+- Avoid re-listing all tests (refer to coverage plan)
+
+---
+
+## 3. Resource Estimates (Ranges Only)
+
+Provide intervals (no false precision):
+
+- P0: e.g., "~25–40 hours"
+- P1: e.g., "~20–35 hours"
+- P2: e.g., "~10–30 hours"
+- P3: e.g., "~2–5 hours"
+- Total and timeline as ranges
+
+---
+
+## 4. Quality Gates
+
+Define thresholds:
+
+- P0 pass rate = 100%
+- P1 pass rate ≥ 95%
+- High-risk mitigations complete before release
+- Coverage target ≥ 80% (adjust if justified)
+
+Load next step: `{nextStepFile}`
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Step completed in full with required outputs
+
+### ❌ SYSTEM FAILURE:
+
+- Skipped sequence steps or missing outputs
+  **Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/tea/workflows/testarch/test-design/steps-c/step-05-generate-output.md

@@ -0,0 +1,97 @@
+---
+name: 'step-05-generate-output'
+description: 'Generate output documents and validate against checklist'
+outputFile: '{output_folder}/test-design-epic-{epic_num}.md'
+---
+
+# Step 5: Generate Outputs & Validate
+
+## STEP GOAL
+
+Write the final test-design document(s) using the correct template(s), then validate against the checklist.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- ✅ Use the provided templates and output paths
+
+---
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Record outputs before proceeding
+- 📖 Load the next step only when instructed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: config, loaded artifacts, and knowledge fragments
+- Focus: this step's goal only
+- Limits: do not execute future steps
+- Dependencies: prior steps' outputs (if any)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+## 1. Select Output Template(s)
+
+### System-Level Mode (Phase 3)
+
+Generate **two** documents:
+
+- `{output_folder}/test-design-architecture.md` using `test-design-architecture-template.md`
+- `{output_folder}/test-design-qa.md` using `test-design-qa-template.md`
+
+### Epic-Level Mode (Phase 4)
+
+Generate **one** document:
+
+- `{outputFile}` using `test-design-template.md`
+- If `epic_num` is unclear, ask the user
+
+---
+
+## 2. Populate Templates
+
+Ensure the outputs include:
+
+- Risk assessment matrix
+- Coverage matrix and priorities
+- Execution strategy
+- Resource estimates (ranges)
+- Quality gate criteria
+- Any mode-specific sections required by the template
+
+---
+
+## 3. Validation
+
+Validate the output(s) against:
+
+- `checklist.md` in this workflow folder
+
+If any checklist criteria are missing, fix before completion.
+
+---
+
+## 4. Completion Report
+
+Summarize:
+
+- Mode used
+- Output file paths
+- Key risks and gate thresholds
+- Any open assumptions
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Step completed in full with required outputs
+
+### ❌ SYSTEM FAILURE:
+
+- Skipped sequence steps or missing outputs
+  **Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/tea/workflows/testarch/test-design/steps-e/step-01-assess.md

@@ -0,0 +1,65 @@
+---
+name: 'step-01-assess'
+description: 'Load an existing output for editing'
+nextStepFile: './step-02-apply-edit.md'
+---
+
+# Step 1: Assess Edit Target
+
+## STEP GOAL:
+
+Identify which output should be edited and load it.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the Master Test Architect
+
+### Step-Specific Rules:
+
+- 🎯 Ask the user which output file to edit
+- 🚫 Do not edit until target is confirmed
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+
+## CONTEXT BOUNDARIES:
+
+- Available context: existing outputs
+- Focus: select edit target
+- Limits: no edits yet
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly.
+
+### 1. Identify Target
+
+Ask the user to provide the output file path or select from known outputs.
+
+### 2. Load Target
+
+Read the provided output file in full.
+
+### 3. Confirm
+
+Confirm the target and proceed to edit.
+
+Load next step: `{nextStepFile}`
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Target identified and loaded
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding without a confirmed target

package/_bmad/tea/workflows/testarch/test-design/steps-e/step-02-apply-edit.md

@@ -0,0 +1,60 @@
+---
+name: 'step-02-apply-edit'
+description: 'Apply edits to the selected output'
+---
+
+# Step 2: Apply Edits
+
+## STEP GOAL:
+
+Apply the requested edits to the selected output and confirm changes.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the Master Test Architect
+
+### Step-Specific Rules:
+
+- 🎯 Only apply edits explicitly requested by the user
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+
+## CONTEXT BOUNDARIES:
+
+- Available context: selected output and user changes
+- Focus: apply edits only
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly.
+
+### 1. Confirm Requested Changes
+
+Restate what will be changed and confirm.
+
+### 2. Apply Changes
+
+Update the output file accordingly.
+
+### 3. Report
+
+Summarize the edits applied.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Changes applied and confirmed
+
+### ❌ SYSTEM FAILURE:
+
+- Unconfirmed edits or missing update

package/_bmad/tea/workflows/testarch/test-design/steps-v/step-01-validate.md

@@ -0,0 +1,67 @@
+---
+name: 'step-01-validate'
+description: 'Validate workflow outputs against checklist'
+outputFile: '{output_folder}/test-design-validation-report.md'
+validationChecklist: '../checklist.md'
+---
+
+# Step 1: Validate Outputs
+
+## STEP GOAL:
+
+Validate outputs using the workflow checklist and record findings.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the Master Test Architect
+
+### Step-Specific Rules:
+
+- 🎯 Validate against `{validationChecklist}`
+- 🚫 Do not skip checks
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Write findings to `{outputFile}`
+
+## CONTEXT BOUNDARIES:
+
+- Available context: workflow outputs and checklist
+- Focus: validation only
+- Limits: do not modify outputs in this step
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly.
+
+### 1. Load Checklist
+
+Read `{validationChecklist}` and list all criteria.
+
+### 2. Validate Outputs
+
+Evaluate outputs against each checklist item.
+
+### 3. Write Report
+
+Write a validation report to `{outputFile}` with PASS/WARN/FAIL per section.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Validation report written
+- All checklist items evaluated
+
+### ❌ SYSTEM FAILURE:
+
+- Skipped checklist items
+- No report produced