bmm-opencode 1.4.3 → 1.6.0

package/_bmad/tea/workflows/testarch/test-design/test-design-template.md

@@ -0,0 +1,294 @@
+# Test Design: Epic {epic_num} - {epic_title}
+
+**Date:** {date}
+**Author:** {user_name}
+**Status:** Draft / Approved
+
+---
+
+## Executive Summary
+
+**Scope:** {design_level} test design for Epic {epic_num}
+
+**Risk Summary:**
+
+- Total risks identified: {total_risks}
+- High-priority risks (≥6): {high_priority_count}
+- Critical categories: {top_categories}
+
+**Coverage Summary:**
+
+- P0 scenarios: {p0_count} ({p0_hours} hours)
+- P1 scenarios: {p1_count} ({p1_hours} hours)
+- P2/P3 scenarios: {p2p3_count} ({p2p3_hours} hours)
+- **Total effort**: {total_hours} hours (~{total_days} days)
+
+---
+
+## Risk Assessment
+
+### High-Priority Risks (Score ≥6)
+
+| Risk ID | Category | Description   | Probability | Impact | Score | Mitigation   | Owner   | Timeline |
+| ------- | -------- | ------------- | ----------- | ------ | ----- | ------------ | ------- | -------- |
+| R-001   | SEC      | {description} | 2           | 3      | 6     | {mitigation} | {owner} | {date}   |
+| R-002   | PERF     | {description} | 3           | 2      | 6     | {mitigation} | {owner} | {date}   |
+
+### Medium-Priority Risks (Score 3-4)
+
+| Risk ID | Category | Description   | Probability | Impact | Score | Mitigation   | Owner   |
+| ------- | -------- | ------------- | ----------- | ------ | ----- | ------------ | ------- |
+| R-003   | TECH     | {description} | 2           | 2      | 4     | {mitigation} | {owner} |
+| R-004   | DATA     | {description} | 1           | 3      | 3     | {mitigation} | {owner} |
+
+### Low-Priority Risks (Score 1-2)
+
+| Risk ID | Category | Description   | Probability | Impact | Score | Action  |
+| ------- | -------- | ------------- | ----------- | ------ | ----- | ------- |
+| R-005   | OPS      | {description} | 1           | 2      | 2     | Monitor |
+| R-006   | BUS      | {description} | 1           | 1      | 1     | Monitor |
+
+### Risk Category Legend
+
+- **TECH**: Technical/Architecture (flaws, integration, scalability)
+- **SEC**: Security (access controls, auth, data exposure)
+- **PERF**: Performance (SLA violations, degradation, resource limits)
+- **DATA**: Data Integrity (loss, corruption, inconsistency)
+- **BUS**: Business Impact (UX harm, logic errors, revenue)
+- **OPS**: Operations (deployment, config, monitoring)
+
+---
+
+## Test Coverage Plan
+
+### P0 (Critical) - Run on every commit
+
+**Criteria**: Blocks core journey + High risk (≥6) + No workaround
+
+| Requirement   | Test Level | Risk Link | Test Count | Owner | Notes   |
+| ------------- | ---------- | --------- | ---------- | ----- | ------- |
+| {requirement} | E2E        | R-001     | 3          | QA    | {notes} |
+| {requirement} | API        | R-002     | 5          | QA    | {notes} |
+
+**Total P0**: {p0_count} tests, {p0_hours} hours
+
+### P1 (High) - Run on PR to main
+
+**Criteria**: Important features + Medium risk (3-4) + Common workflows
+
+| Requirement   | Test Level | Risk Link | Test Count | Owner | Notes   |
+| ------------- | ---------- | --------- | ---------- | ----- | ------- |
+| {requirement} | API        | R-003     | 4          | QA    | {notes} |
+| {requirement} | Component  | -         | 6          | DEV   | {notes} |
+
+**Total P1**: {p1_count} tests, {p1_hours} hours
+
+### P2 (Medium) - Run nightly/weekly
+
+**Criteria**: Secondary features + Low risk (1-2) + Edge cases
+
+| Requirement   | Test Level | Risk Link | Test Count | Owner | Notes   |
+| ------------- | ---------- | --------- | ---------- | ----- | ------- |
+| {requirement} | API        | R-004     | 8          | QA    | {notes} |
+| {requirement} | Unit       | -         | 15         | DEV   | {notes} |
+
+**Total P2**: {p2_count} tests, {p2_hours} hours
+
+### P3 (Low) - Run on-demand
+
+**Criteria**: Nice-to-have + Exploratory + Performance benchmarks
+
+| Requirement   | Test Level | Test Count | Owner | Notes   |
+| ------------- | ---------- | ---------- | ----- | ------- |
+| {requirement} | E2E        | 2          | QA    | {notes} |
+| {requirement} | Unit       | 8          | DEV   | {notes} |
+
+**Total P3**: {p3_count} tests, {p3_hours} hours
+
+---
+
+## Execution Order
+
+### Smoke Tests (<5 min)
+
+**Purpose**: Fast feedback, catch build-breaking issues
+
+- [ ] {scenario} (30s)
+- [ ] {scenario} (45s)
+- [ ] {scenario} (1min)
+
+**Total**: {smoke_count} scenarios
+
+### P0 Tests (<10 min)
+
+**Purpose**: Critical path validation
+
+- [ ] {scenario} (E2E)
+- [ ] {scenario} (API)
+- [ ] {scenario} (API)
+
+**Total**: {p0_count} scenarios
+
+### P1 Tests (<30 min)
+
+**Purpose**: Important feature coverage
+
+- [ ] {scenario} (API)
+- [ ] {scenario} (Component)
+
+**Total**: {p1_count} scenarios
+
+### P2/P3 Tests (<60 min)
+
+**Purpose**: Full regression coverage
+
+- [ ] {scenario} (Unit)
+- [ ] {scenario} (API)
+
+**Total**: {p2p3_count} scenarios
+
+---
+
+## Resource Estimates
+
+### Test Development Effort
+
+| Priority  | Count             | Hours/Test | Total Hours       | Notes                   |
+| --------- | ----------------- | ---------- | ----------------- | ----------------------- |
+| P0        | {p0_count}        | 2.0        | {p0_hours}        | Complex setup, security |
+| P1        | {p1_count}        | 1.0        | {p1_hours}        | Standard coverage       |
+| P2        | {p2_count}        | 0.5        | {p2_hours}        | Simple scenarios        |
+| P3        | {p3_count}        | 0.25       | {p3_hours}        | Exploratory             |
+| **Total** | **{total_count}** | **-**      | **{total_hours}** | **~{total_days} days**  |
+
+### Prerequisites
+
+**Test Data:**
+
+- {factory_name} factory (faker-based, auto-cleanup)
+- {fixture_name} fixture (setup/teardown)
+
+**Tooling:**
+
+- {tool} for {purpose}
+- {tool} for {purpose}
+
+**Environment:**
+
+- {env_requirement}
+- {env_requirement}
+
+---
+
+## Quality Gate Criteria
+
+### Pass/Fail Thresholds
+
+- **P0 pass rate**: 100% (no exceptions)
+- **P1 pass rate**: ≥95% (waivers required for failures)
+- **P2/P3 pass rate**: ≥90% (informational)
+- **High-risk mitigations**: 100% complete or approved waivers
+
+### Coverage Targets
+
+- **Critical paths**: ≥80%
+- **Security scenarios**: 100%
+- **Business logic**: ≥70%
+- **Edge cases**: ≥50%
+
+### Non-Negotiable Requirements
+
+- [ ] All P0 tests pass
+- [ ] No high-risk (≥6) items unmitigated
+- [ ] Security tests (SEC category) pass 100%
+- [ ] Performance targets met (PERF category)
+
+---
+
+## Mitigation Plans
+
+### R-001: {Risk Description} (Score: 6)
+
+**Mitigation Strategy:** {detailed_mitigation}
+**Owner:** {owner}
+**Timeline:** {date}
+**Status:** Planned / In Progress / Complete
+**Verification:** {how_to_verify}
+
+### R-002: {Risk Description} (Score: 6)
+
+**Mitigation Strategy:** {detailed_mitigation}
+**Owner:** {owner}
+**Timeline:** {date}
+**Status:** Planned / In Progress / Complete
+**Verification:** {how_to_verify}
+
+---
+
+## Assumptions and Dependencies
+
+### Assumptions
+
+1. {assumption}
+2. {assumption}
+3. {assumption}
+
+### Dependencies
+
+1. {dependency} - Required by {date}
+2. {dependency} - Required by {date}
+
+### Risks to Plan
+
+- **Risk**: {risk_to_plan}
+  - **Impact**: {impact}
+  - **Contingency**: {contingency}
+
+---
+
+---
+
+## Follow-on Workflows (Manual)
+
+- Run `*atdd` to generate failing P0 tests (separate workflow; not auto-run).
+- Run `*automate` for broader coverage once implementation exists.
+
+---
+
+## Approval
+
+**Test Design Approved By:**
+
+- [ ] Product Manager: {name} Date: {date}
+- [ ] Tech Lead: {name} Date: {date}
+- [ ] QA Lead: {name} Date: {date}
+
+**Comments:**
+
+---
+
+---
+
+---
+
+## Appendix
+
+### Knowledge Base References
+
+- `risk-governance.md` - Risk classification framework
+- `probability-impact.md` - Risk scoring methodology
+- `test-levels-framework.md` - Test level selection
+- `test-priorities-matrix.md` - P0-P3 prioritization
+
+### Related Documents
+
+- PRD: {prd_link}
+- Epic: {epic_link}
+- Architecture: {arch_link}
+- Tech Spec: {tech_spec_link}
+
+---
+
+**Generated by**: BMad TEA Agent - Test Architect Module
+**Workflow**: `_bmad/tea/testarch/test-design`
+**Version**: 4.0 (BMad v6)

package/_bmad/tea/workflows/testarch/test-design/validation-report-20260127-095021.md

@@ -0,0 +1,73 @@
+---
+validationDate: 2026-01-27
+workflowName: testarch-test-design
+workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/test-design
+validationStatus: COMPLETE
+completionDate: 2026-01-27 10:03:10
+---
+
+# Validation Report: testarch-test-design
+
+**Validation Started:** 2026-01-27 09:50:21
+**Validator:** BMAD Workflow Validation System (Codex)
+**Standards Version:** BMAD Workflow Standards
+
+## File Structure & Size
+
+- workflow.md present: YES
+- instructions.md present: YES
+- workflow.yaml present: YES
+- step files found: 8
+
+**Step File Sizes:**
+
+- steps-c/step-01-detect-mode.md: 93 lines [GOOD]
+- steps-c/step-02-load-context.md: 112 lines [GOOD]
+- steps-c/step-03-risk-and-testability.md: 76 lines [GOOD]
+- steps-c/step-04-coverage-plan.md: 88 lines [GOOD]
+- steps-c/step-05-generate-output.md: 85 lines [GOOD]
+- steps-e/step-01-assess.md: 51 lines [GOOD]
+- steps-e/step-02-apply-edit.md: 46 lines [GOOD]
+- steps-v/step-01-validate.md: 53 lines [GOOD]
+- workflow-plan.md present: YES
+
+## Frontmatter Validation
+
+- No frontmatter violations found
+
+## Critical Path Violations
+
+- No {project-root} hardcoded paths detected in body
+- No dead relative links detected
+
+## Menu Handling Validation
+
+- No menu structures detected (linear step flow) [N/A]
+
+## Step Type Validation
+
+- Last step steps-v/step-01-validate.md has no nextStepFile (final step OK)
+- Step type validation assumes linear sequence (no branching/menu). Workflow-plan.md present for reference. [INFO]
+
+## Output Format Validation
+
+- Templates present: test-design-architecture-template.md, test-design-qa-template.md, test-design-template.md
+- Steps with outputFile in frontmatter:
+  - steps-c/step-05-generate-output.md
+  - steps-v/step-01-validate.md
+
+## Validation Design Check
+
+- checklist.md present: YES
+- Validation steps folder (steps-v) present: YES
+
+## Instruction Style Check
+
+- All steps include STEP GOAL, MANDATORY EXECUTION RULES, EXECUTION PROTOCOLS, CONTEXT BOUNDARIES, and SUCCESS/FAILURE metrics
+
+## Summary
+
+- Validation completed: 2026-01-27 10:03:10
+- Critical issues: 0
+- Warnings: 0 (informational notes only)
+- Readiness: READY (manual review optional)

package/_bmad/tea/workflows/testarch/test-design/validation-report-20260127-102401.md

@@ -0,0 +1,116 @@
+---
+validationDate: 2026-01-27
+workflowName: testarch-test-design
+workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/test-design
+validationStatus: COMPLETE
+completionDate: 2026-01-27 10:24:01
+---
+
+# Validation Report: testarch-test-design
+
+**Validation Started:** 2026-01-27 10:24:01
+**Validator:** BMAD Workflow Validation System (Codex)
+**Standards Version:** BMAD Workflow Standards
+
+## File Structure & Size
+
+- workflow.md present: YES
+- instructions.md present: YES
+- workflow.yaml present: YES
+- step files found: 8
+
+**Step File Sizes:**
+
+- steps-c/step-01-detect-mode.md: 92 lines [GOOD]
+- steps-c/step-02-load-context.md: 111 lines [GOOD]
+- steps-c/step-03-risk-and-testability.md: 75 lines [GOOD]
+- steps-c/step-04-coverage-plan.md: 87 lines [GOOD]
+- steps-c/step-05-generate-output.md: 84 lines [GOOD]
+- steps-e/step-01-assess.md: 50 lines [GOOD]
+- steps-e/step-02-apply-edit.md: 45 lines [GOOD]
+- steps-v/step-01-validate.md: 52 lines [GOOD]
+- workflow-plan.md present: YES
+
+## Frontmatter Validation
+
+- No frontmatter violations found
+
+## Critical Path Violations
+
+### Config Variables (Exceptions)
+
+Standard BMAD config variables treated as valid exceptions: bmb_creations_output_folder, communication_language, document_output_language, output_folder, planning_artifacts, project-root, project_name, test_artifacts, user_name
+
+- No {project-root} hardcoded paths detected in body
+
+- No dead relative links detected
+
+- No module path assumptions detected
+
+**Status:** ✅ PASS - No critical violations
+
+## Menu Handling Validation
+
+- No menu structures detected (linear step flow) [N/A]
+
+## Step Type Validation
+
+- steps-c/step-01-detect-mode.md: Init [PASS]
+- steps-c/step-02-load-context.md: Middle [PASS]
+- steps-c/step-03-risk-and-testability.md: Middle [PASS]
+- steps-c/step-04-coverage-plan.md: Middle [PASS]
+- steps-c/step-05-generate-output.md: Final [PASS]
+- Step type validation assumes linear sequence (no branching/menu). Workflow-plan.md present for reference. [INFO]
+
+## Output Format Validation
+
+- Templates present: test-design-architecture-template.md, test-design-qa-template.md, test-design-template.md
+- Steps with outputFile in frontmatter:
+  - steps-c/step-05-generate-output.md
+  - steps-v/step-01-validate.md
+- checklist.md present: YES
+
+## Validation Design Check
+
+- Validation steps folder (steps-v) present: YES
+- Validation step(s) present: step-01-validate.md
+- Validation steps reference checklist data and auto-proceed
+
+## Instruction Style Check
+
+- Instruction style: Prescriptive (appropriate for TEA quality/compliance workflows)
+- Steps emphasize mandatory sequence, explicit success/failure metrics, and risk-based guidance
+
+## Collaborative Experience Check
+
+- Overall facilitation quality: GOOD
+- Steps use progressive prompts and clear role reinforcement; no laundry-list interrogation detected
+- Flow progression is clear and aligned to workflow goals
+
+## Subprocess Optimization Opportunities
+
+- No high-priority subprocess optimizations identified; workflow already uses step-file architecture
+- Pattern 1 (grep/regex): N/A for most steps
+- Pattern 2 (per-file analysis): already aligned to validation structure
+- Pattern 3 (data ops): minimal data file loads
+- Pattern 4 (parallel): optional for validation only
+
+## Cohesive Review
+
+- Overall assessment: GOOD
+- Flow is linear, goals are clear, and outputs map to TEA artifacts
+- Voice and tone consistent with Test Architect persona
+- Recommendation: READY (minor refinements optional)
+
+## Plan Quality Validation
+
+- Plan file present: workflow-plan.md
+- Planned steps found: 8 (all implemented)
+- Plan implementation status: Fully Implemented
+
+## Summary
+
+- Validation completed: 2026-01-27 10:24:01
+- Critical issues: 0
+- Warnings: 0 (informational notes only)
+- Readiness: READY (manual review optional)

package/_bmad/tea/workflows/testarch/test-design/workflow-plan.md

@@ -0,0 +1,22 @@
+    # Workflow Plan: testarch-test-design
+
+    ## Create Mode (steps-c)
+    - step-01-detect-mode.md
+
+- step-02-load-context.md
+- step-03-risk-and-testability.md
+- step-04-coverage-plan.md
+- step-05-generate-output.md
+
+  ## Validate Mode (steps-v)
+  - step-01-validate.md
+
+  ## Edit Mode (steps-e)
+  - step-01-assess.md
+  - step-02-apply-edit.md
+
+  ## Outputs
+  - {output_folder}/test-design-architecture.md (system-level)
+
+- {output_folder}/test-design-qa.md (system-level)
+- {output_folder}/test-design-epic-{epic_num}.md (epic-level)

package/_bmad/tea/workflows/testarch/test-design/workflow.md

@@ -0,0 +1,39 @@
+---
+name: testarch-test-design
+description: 'Epic-level test plan (Phase 4)'
+web_bundle: true
+---
+
+# Test Design and Risk Assessment
+
+**Goal:** Epic-level test plan (Phase 4)
+
+**Role:** You are the Master Test Architect.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This workflow uses **tri-modal step-file architecture**:
+
+- **Create mode (steps-c/)**: primary execution flow
+- **Validate mode (steps-v/)**: validation against checklist
+- **Edit mode (steps-e/)**: revise existing outputs
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Mode Determination
+
+"Welcome to the workflow. What would you like to do?"
+
+- **[C] Create** — Run the workflow
+- **[V] Validate** — Validate existing outputs
+- **[E] Edit** — Edit existing outputs
+
+### 2. Route to First Step
+
+- **If C:** Load `steps-c/step-01-detect-mode.md`
+- **If V:** Load `steps-v/step-01-validate.md`
+- **If E:** Load `steps-e/step-01-assess.md`

package/_bmad/tea/workflows/testarch/test-design/workflow.yaml

@@ -0,0 +1,69 @@
+# Test Architect workflow: test-design
+name: testarch-test-design
+description: "Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase."
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/_bmad/tea/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/_bmad/tea/workflows/testarch/test-design"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+# Note: Template selection is mode-based (see instructions.md Step 1.5):
+#   - System-level: test-design-architecture-template.md + test-design-qa-template.md
+#   - Epic-level: test-design-template.md (unchanged)
+template: "{installed_path}/test-design-template.md"
+
+# Variables and inputs
+variables:
+  design_level: "full" # full, targeted, minimal - scope of design effort
+  mode: "auto-detect" # auto-detect (default), system-level, epic-level
+
+# Output configuration
+# Note: Actual output file determined dynamically based on mode detection
+# Declared outputs for new workflow format
+outputs:
+  # System-Level Mode (Phase 3) - TWO documents
+  - id: test-design-architecture
+    description: "System-level test architecture: Architectural concerns, testability gaps, NFR requirements for Architecture/Dev teams"
+    path: "{output_folder}/test-design-architecture.md"
+    mode: system-level
+    audience: architecture
+
+  - id: test-design-qa
+    description: "System-level test design: Test execution recipe, coverage plan, Sprint 0 setup for QA team"
+    path: "{output_folder}/test-design-qa.md"
+    mode: system-level
+    audience: qa
+
+  # Epic-Level Mode (Phase 4) - ONE document (unchanged)
+  - id: epic-level
+    description: "Epic-level test plan (Phase 4)"
+    path: "{output_folder}/test-design-epic-{epic_num}.md"
+    mode: epic-level
+# Note: No default_output_file - mode detection determines which outputs to write
+
+# Required tools
+required_tools:
+  - read_file # Read PRD, epics, stories, architecture docs
+  - write_file # Create test design document
+  - list_files # Find related documentation
+  - search_repo # Search for existing tests and patterns
+
+tags:
+  - qa
+  - planning
+  - test-architect
+  - risk-assessment
+  - coverage
+
+execution_hints:
+  interactive: false # Minimize prompts
+  autonomous: true # Proceed without user input unless blocked
+  iterative: true