traceability

Generate a bi-directional traceability matrix linking acceptance criteria to code, tests, and reviews.

3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill traceability-artemiopadilla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traceability
Source: https://github.com/ArtemioPadilla/agent-triforce/tree/main/.claude/skills/traceability
Command: npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill traceability-artemiopadilla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a bi-directional traceability matrix that links acceptance criteria from specs to implementation files, test cases, and review findings, enabling IEEE 830-style audits and auditable product verification.

Core Features & Use Cases

  • Extract acceptance criteria from feature specs and assign stable IDs (AC-{NNN}).
  • Map each criterion to corresponding code in src/, tests in tests/, and findings in docs/reviews/.
  • Generate a publishable matrix at docs/traceability/{feature-name}-matrix.md and provide coverage status.

Quick Start

Run the traceability workflow on your feature spec to produce the matrix at docs/traceability/{feature-name}-matrix.md.

Frequently Asked Questions about traceability

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

FAQPage Schema
How do I create a traceability matrix for acceptance criteria?

A traceability matrix is generated by scanning src/, tests/, and docs/reviews to map spec acceptance criteria to source code and test cases. The workflow extracts criteria, assigns stable IDs, and outputs a bi-directional matrix at docs/traceability/{feature-name}-matrix.md.

What is IEEE 830 style traceability for feature specs?

IEEE 830 traceability provides bi-directional mapping between feature specs, implementation files, and test cases to enable auditable product verification. This approach extracts acceptance criteria from docs/specs, assigns them stable IDs, and links them directly to code and test artifacts.

How do I map test cases to spec requirements automatically?

Mapping test cases to requirements is done by scanning the tests/ and src/ directories against feature specs in docs/specs. The process extracts acceptance criteria, assigns stable AC-{NNN} identifiers, and links each criterion to corresponding test files and review findings.

Can I generate a bi-directional spec-to-code matrix without external dependencies?

Generating a bi-directional spec-to-code matrix requires no external dependencies. The workflow scans local src/, tests/, and docs/reviews directories to link acceptance criteria to implementation files and test cases, producing a publishable matrix file with coverage status.

Where should I store feature specs for traceability matrix generation?

Feature specs should be stored in the docs/specs directory to enable traceability matrix generation. The workflow scans this location to extract acceptance criteria and maps them to source code, tests, and review findings, outputting the matrix to docs/traceability/{feature-name}-matrix.md.

What is the best way to audit test coverage against feature requirements?

Auditing test coverage against requirements is achieved by generating a traceability matrix that links acceptance criteria to test cases and review findings. This provides a coverage status report by scanning src/, tests/, and docs/reviews to ensure every spec criterion is verified.