requirements-trace

Verify requirement implementation and test coverage with bidirectional trace matrices.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jscott3201/ai-agent-skills --skill requirements-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements-trace
Source: https://github.com/jscott3201/ai-agent-skills/tree/main/skills/requirements-trace
Command: npx skills add https://github.com/jscott3201/ai-agent-skills --skill requirements-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that implemented code matches intended requirements and that each requirement has corresponding automated tests, preventing scope creep and unverified behavior before release.

Core Features & Use Cases

  • Bidirectional trace matrix: Maps requirements to implementation files/functions and to test cases to show coverage and gaps.
  • Gap triage workflow: Presents gaps one at a time with options to address, accept, or defer and records triage decisions.
  • Untraced code detection: Identifies code introduced without a traced requirement to catch scope creep or missing requirements.

Quick Start

Run a requirements trace on the latest feature plan and present each gap for triage.

Frequently Asked Questions about requirements-trace

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

FAQPage Schema
How do I map implemented code and tests to specific requirements for traceability?

Requirements traceability maps every requirement to corresponding implementation files, functions, and automated test cases to verify coverage and identify gaps. It searches codebases and test suites for numbered requirement mappings to build a bidirectional trace matrix.

What is the best way to identify untraced code introduced without a requirement?

Untraced code detection identifies code introduced without a mapped requirement to catch scope creep. It scans the codebase to flag functions or files lacking a traced requirement, ensuring all implementation aligns with intended feature plans.

How do I perform a gap analysis on test coverage for a feature plan?

Gap analysis on test coverage compares implemented code and test cases against feature plans to find partial or missing implementations. It presents gaps individually for triage, allowing you to address, accept, or defer each missing test or code segment.

Can I record triage decisions for missing requirements directly during the audit?

You can record triage decisions for missing requirements directly during the audit. The gap triage workflow presents gaps one at a time with options to address, accept, or defer, and records these decisions to SeleneDB when available.

Does requirements traceability work for post-implementation QA before a release?

Requirements traceability is specifically applicable to post-implementation QA of feature plans, design documents, and codebases. It audits traceability and verifies that implemented code matches intended requirements and has corresponding automated tests before release preparation.