traceability

Generate a traceability matrix linking requirements to downstream artifacts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/turbobeest/dev-system --skill traceability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traceability
Source: https://github.com/turbobeest/dev-system/tree/main/skills/traceability
Command: npx skills add https://github.com/turbobeest/dev-system --skill traceability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manage requirement traceability, generate matrices, identify orphans, and validate trace links across the project artifacts.

Core Features & Use Cases

  • Trace generation: Build forward and backward trace matrices.
  • Coverage analytics: Measure trace coverage and identify gaps.
  • Orphan detection: Find artifacts lacking proper traces for remediation.

Quick Start

Use /trace to view the dashboard, then commands like /trace generate or /trace orphans to manage traces.

Frequently Asked Questions about traceability

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

FAQPage Schema
How do I build a traceability matrix linking requirements to code and tests?

Traceability matrices link requirements across PRDs, user stories, tasks, specifications, and tests to track coverage end-to-end. Use /trace generate to scan your project artifacts—REQ IDs in PRDs, @traces in test files, @implements in source code—and output a machine-readable matrix at .claude/traceability/matrix.json with forward and backward coverage metrics.

Can I identify orphaned requirements and artifacts with incomplete traces?

Orphan detection finds requirements lacking proper downstream traces and artifacts without upstream requirements. Run /trace orphans to automatically detect gaps, then use impact analysis to remediate unmapped PRD items, user stories, or code sections before they create compliance or testing risks.

What's the best way to measure coverage across requirements, specifications, and tests?

Coverage analytics quantify how completely your requirements trace through implementation and testing. The matrix outputs coverage percentages and identifies gaps, enabling you to validate that every PRD requirement has corresponding tasks, specifications, and test coverage before deployment.

When do I need a traceability matrix for software projects?

Traceability matrices become critical when managing PRDs, user stories, and test suites—projects needing proof that all requirements are implemented and tested. Use this Skill to automate compliance reporting, impact analysis, and validation of trace links across distributed project artifacts.

Does this work with projects using different task and specification formats?

Yes. The Skill scans .taskmaster/tasks/tasks.json for tasks, openspec/changes/*.md for specifications, and tests/**/*.{ts,js,py} for @traces annotations. It adapts to multi-language codebases and supports forward/backward tracing across heterogeneous artifact formats.

What happens if traces are incomplete or conflicting across my project?

Incomplete traces surface as coverage gaps and orphans in the generated matrix. The Skill validates all trace links and highlights artifacts missing REQ IDs or @implements annotations, enabling targeted remediation before they compound into downstream defects or compliance failures.