skills.rest
taptap
taptapOFFICIAL
Explore all skills by this author →
Website𝕏@taptapGitHub

requirement-traceability

Maps requirements to code changes and generates traceability, coverage, and risk reports.

Updated Aug 27, 2026
Search Tags:#requirements#traceability#pr#api-contract#diff-analysis#smoke-test#mr
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill requirement-traceability-taptap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirement-traceability
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/test/skills/requirement-traceability
Command: npx skills add https://github.com/taptap/agents-plugins --skill requirement-traceability-taptap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill determines whether code changes (MR/PR diffs, local git diffs, or pasted diff text) correctly implement stated requirements and highlights coverage gaps, untraced changes, and integration risks so teams can confidently verify feature completeness before merge.

Core Features & Use Cases

  • Dual-channel traceability: Performs forward (requirements→code) and reverse (code→requirements) tracing and cross-validates results to produce robust mapping.
  • Conditional checks: Includes API contract comparisons and optional UI fidelity checks when design links or OpenAPI specs are provided.
  • Smoke-test mode: Extracts defects from verification failures and coverage gaps and enforces P0 gating for quick release decisions.

Quick Start

Use the requirement-traceability skill with the MR/PR links or diff input and an optional requirement document to generate traceability_matrix.json and traceability_coverage_report.json.

Frequently Asked Questions about requirement-traceability

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

FAQPage Schema
How do I trace requirements to code changes in a merge request?▼

Requirement traceability maps MR/PR diffs to stated requirements through forward and reverse tracing to identify coverage gaps and untraced code modifications before merging.

What is reverse traceability for code modifications?▼

Reverse traceability for code modifications is the process of mapping existing diff changes back to their originating requirements to ensure no untraced edits or undocumented features are introduced into the codebase.

Can I validate API contract changes against requirements from a git diff?▼

Yes, you can validate API contract changes from a git diff by providing OpenAPI specs to cross-check feature completeness and ensure modified code correctly implements the stated API requirements.

How do I generate a traceability matrix for untraced code modifications?▼

Generate a traceability matrix by processing local git diff files or pasted diff text against requirement documents to output a traceability_matrix.json file mapping code changes to specific requirements.

Does smoke testing extract defects from requirement coverage gaps?▼

Yes, smoke-test mode extracts defects from verification failures and coverage gaps while enforcing P0 gating to provide quick release decisions based on critical feature completeness.

Related Skills

Explore More Software Engineering Skills→
stravineststravinest

QA Workflow Skill

Automate end-to-end browser QA testing with Playwright and ArangoDB checks.

Community
Advanced
SandAI-orgSandAI-org
325

code-review

Inspect ahead-of-base diffs and generate structured P0-P4 markdown review reports.

Official
Intermediate
akirschke15-cmdakirschke15-cmd

verification-loop

Run a deterministic verification pipeline for TypeScript, Python, Go, and Rust changes.

Community
Advanced
ref-docsref-docs

traceability-auditor

Validate end-to-end traceability across requirements, design, tasks, code, and tests.

Official
Advanced