bmad-testarch-trace

Generate traceability matrices and deterministic gate decisions from coverage data.

1|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-testarch-trace-mazenmrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-trace
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-testarch-trace
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-testarch-trace-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Traceability & Gate Decision Skill automates the creation of a comprehensive traceability matrix from coverage data, aligns requirements to tests, and produces a deterministic gate decision to support release readiness.

Core Features & Use Cases

  • Build and analyze traceability matrices linking requirements to tests and identify coverage gaps.
  • Generate actionable, machine-readable artifacts such as e2e-trace-summary.json and gate-decision.json.
  • Produce prioritized recommendations and deterministic gate decisions for stories, epics, or releases.

Quick Start

Run the bmad-testarch-trace workflow to produce the traceability matrix and gate decision from your current project state.

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 from requirements and tests?

A traceability matrix links requirements and user journeys to tests to identify coverage gaps. This Skill automates that mapping to produce a deterministic gate decision and machine-readable artifacts like e2e-trace-summary.json for release readiness.

What is a deterministic gate decision in test architecture and coverage analysis?

A deterministic gate decision applies formal gate rules to coverage data to evaluate release readiness for stories, epics, or releases. It enforces strict criteria and provides actionable recommendations to resolve coverage gaps.

Can I use machine-readable artifacts from gap-analysis for CI pipelines and audits?

Yes, the coverage gap-analysis produces machine-readable artifacts like e2e-trace-summary.json and gate-decision.json. These outputs are designed for CI pipelines and audits to enforce deterministic gate rules.

How do I identify coverage gaps between user journeys and my test suite?

Map user journeys and requirements to existing tests within a traceability matrix to identify coverage gaps. The Skill applies formal or synthetic coverage sources to highlight missing links and provide prioritized recommendations.

Does test architecture traceability require formal coverage sources or can I use synthetic ones?

Test architecture traceability supports both formal and synthetic coverage sources. The Skill applies either source to generate the traceability matrix and enforce deterministic gate rules for release readiness.

When do I need a traceability matrix for gate decisions instead of manual test reviews?

You need a traceability matrix for gate decisions when releasing stories, epics, or features where manual reviews are insufficient. It enforces deterministic gate rules and produces audit-ready artifacts for CI pipelines.