trace-requirements

Generate bidirectional traceability matrices linking acceptance criteria to implementations and tests.

1|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill trace-requirements-acidicsoil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace-requirements
Source: https://github.com/AcidicSoil/lms-llmsTxt/tree/main/.claude/skills/trace-requirements
Command: npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill trace-requirements-acidicsoil

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Traceability across requirements, implementation, and tests is often manual, fragmented, and hard to audit. This skill automates the creation of a bidirectional traceability matrix that links ACs to concrete implementation evidence and tests, enabling reliable gap analysis and audit-ready reporting.

Core Features & Use Cases

  • Forward traceability: AC → Implementation evidence (files, lines, functions)
  • Backward traceability: Tests → AC mapping and coverage
  • Gap detection and severity assessment compatible with risk design
  • Audit-ready reports and traceability score calculations
  • Uses risk-profile and test-design inputs for richer context and prioritization
  • Useful for pre-release quality gates and compliance audits

Quick Start

Load a task specification, related assessments, and codebase data, then run forward and backward traceability to generate a comprehensive report.

Frequently Asked Questions about trace-requirements

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

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

To generate a bidirectional traceability matrix, load your task specification, codebase data, and test suites; the skill automatically links acceptance criteria to implementation evidence and tests to produce audit-ready documentation.

What is forward and backward traceability in software testing?

Forward traceability maps acceptance criteria to implementation evidence like files and functions, while backward traceability maps tests back to acceptance criteria to ensure full coverage and identify untested requirements.

How do I perform gap analysis on test designs and risk profiles?

Gap analysis assesses missing links between acceptance criteria, implementations, and tests by applying risk profiles and test designs to compute severity and provide a traceability score for quality-gate recommendations.

Can I use this for pre-release quality gates and compliance audits?

Yes, you can use the generated traceability score and gap severity assessments as pre-release quality gates and to produce audit-ready reports for compliance verification.

Do I need defined acceptance criteria and source code to run traceability analysis?

Yes, you need defined acceptance criteria, source code, test suites, risk profiles, and test designs as inputs to accurately compute forward and backward traceability and identify coverage gaps.

What is the best way to prepare for an audit using a traceability matrix?

The best way to prepare for an audit is to run automated bidirectional traceability across your codebase and tests, generating a comprehensive report that links evidence to acceptance criteria with severity-assessed gaps.