bmad-testarch-trace

Map requirements to tests and emit a machine-readable e2e-trace summary with gate decision.

Updated Dec 23, 2025

Search Tags:#automation #quality #traceability #gate #gaps #test-coverage #matrix

Ready to run

npx skills add https://github.com/joekhosbayar/go-mighty --skill bmad-testarch-trace-joekhosbayar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-testarch-trace
Source: https://github.com/joekhosbayar/go-mighty/tree/main/.gemini/skills/bmad-testarch-trace
Command: npx skills add https://github.com/joekhosbayar/go-mighty --skill bmad-testarch-trace-joekhosbayar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The BMAD test-architecture traceability skill automates mapping requirements to tests, identifies coverage gaps, and decides gate readiness for releases.

Core Features & Use Cases

Generates a complete traceability matrix from resolved coverage data.
Performs gap analysis and produces actionable recommendations.
Emits a machine-readable summary and a gate decision when eligible.

Quick Start

Provide a target for the traceability workflow and run the BMAD traceability process to obtain the matrix and gate decision.

Frequently Asked Questions about bmad-testarch-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate building a traceability matrix from requirements to tests?▼

Automating a traceability matrix involves mapping each requirement to its corresponding tests to identify coverage gaps. This process generates a machine-readable summary and a gate decision to streamline deployment planning.

What is a gate decision in test coverage analysis?▼

A gate decision in test coverage analysis evaluates the traceability matrix to determine release readiness. It documents provenance, highlights coverage gaps, and provides remediation recommendations for deployment planning.

How do I identify test coverage gaps before a release?▼

Identifying test coverage gaps requires mapping resolved coverage data to build a complete traceability matrix. This analysis exposes unmapped requirements and generates actionable remediation recommendations for deployment planning.

Can I use automation to document provenance for e2e test summaries?▼

Automation can document provenance by emitting a machine-readable e2e-trace summary based on the traceability matrix. This summary captures the complete mapping between requirements and tests alongside coverage gap details.

What is the best way to generate remediation recommendations for deployment planning?▼

Generating remediation recommendations requires performing gap analysis on a traceability matrix built from resolved coverage data. This yields actionable steps to resolve missing test coverage before emitting a final gate decision.

Does gate readiness automation work without external dependencies?▼

Gate readiness automation operates independently without external dependencies, identifying coverage gaps and emitting a machine-readable e2e-trace summary with a gate decision based solely on the provided target data.