bmad-testarch-trace

Generate a requirements-to-tests traceability matrix with coverage gap analysis.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-testarch-trace-rinzler78
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-testarch-trace
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-testarch-trace
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-testarch-trace-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the manual effort of tracing requirements to tests and judging whether a release is ready, helping teams quickly see what is covered, what is missing, and what blocks deployment.

Core Features & Use Cases

  • Requirements Traceability: Builds a matrix that links acceptance criteria to E2E, API, component, and unit tests.
  • Coverage Gap Analysis: Detects missing coverage, partial coverage, duplicate validation, and common blind spots such as endpoint, auth, and error-path gaps.
  • Quality Gate Decision: Applies deterministic release rules to produce a PASS, CONCERNS, FAIL, or WAIVED outcome based on evidence.
  • Use Case: A test architect can run this Skill before a merge or release to produce an auditable coverage report and a clear deployment recommendation.

Quick Start

Ask the Skill to analyze the project’s requirements and tests, then generate a traceability matrix and release 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 generate a traceability matrix for release readiness?▼

Test coverage gap analysis detects missing, partial, and duplicate validation across requirements. It identifies common blind spots such as endpoint, authentication, and error-path gaps to prevent untested logic from reaching production.

How does a quality gate decision determine PASS or FAIL for a deployment?▼

Coverage gap analysis detects missing, partial, and duplicate validation across requirements. It identifies common blind spots such as endpoint, authentication, and error-path gaps to prevent untested logic from reaching production.

Can I check test coverage gaps for hotfixes and epics without manual tracing?▼

Coverage gap analysis detects missing, partial, and duplicate validation across requirements. It identifies common blind spots such as endpoint, authentication, and error-path gaps to prevent untested logic from reaching production.

What is requirements traceability in test architecture reviews?▼

Coverage gap analysis detects missing, partial, and duplicate validation across requirements. It identifies common blind spots such as endpoint, authentication, and error-path gaps to prevent untested logic from reaching production.

What's the best way to expose missing test coverage before a merge?▼

Coverage gap analysis detects missing, partial, and duplicate validation across requirements. It identifies common blind spots such as endpoint, authentication, and error-path gaps to prevent untested logic from reaching production.

When should I use a WAIVED status in a release readiness decision?▼

Coverage gap analysis detects missing, partial, and duplicate validation across requirements. It identifies common blind spots such as endpoint, authentication, and error-path gaps to prevent untested logic from reaching production.