How do I install the Requirements Traceability skill?

Run npx skillmds@latest add ashfordeou/requirements-traceability in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Requirements Traceability safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Requirements Traceability?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Requirements Traceability free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Requirements Traceability?

ashfordeOU (@ashfordeou) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Requirements Traceability by ashfordeou

Name: Requirements Traceability
Author: ashfordeOU

Requirements Traceability

Use when planning or auditing requirements traceability per ARP4754A: determine closure status across SRATS, high-level requirements (HLR), low-level requirements (LLR), code, and test levels, list traceability gaps for a level, flag derived requirements, and compute the verified-closure ratio of the trace matrix. Bidirectional closure (each level traces down and back up) and open verification items drive the closed/open verdict; all logic is deterministic, offline stdlib. Trigger: traceability, requirements, closure, SRATS, high-level requirements, low-level requirements, derived requirements, verification, trace matrix.

ashfordeOU 5f64bfe 3 files · 12.9 KB Updated Sep 17, 2026

File contents

ARP4754A Requirements Traceability (systems-engineering-safety/arp4754a/requirements-traceability)

Use when the task is requirements traceability per ARP4754A: determining closure across the SRATS-to-test chain, listing traceability gaps, flagging derived requirements, and measuring verified-closure of the trace matrix.

Domain quick reference

ARP4754A development assurance runs on traceability: system requirements (SRATS) trace to high-level requirements (HLR), HLR trace to low-level requirements (LLR), LLR trace to code and test.
Closure is bidirectional per level: every HLR has an incoming SRATS trace and an outgoing LLR trace; every LLR has an incoming HLR trace and an outgoing code or test trace.
A traced pair with verification still open is an open verification item and keeps the closure status open.
Derived requirements (requirements whose content is not directly traceable to a parent source) must be explicitly flagged.
Verified-closure ratio = verified traces / total traces (0..1).

Workflow

Collect the trace matrix as (from, to, verified) links.
Determine closure status and review the gap list.
Focus on one level (srats/hlr/llr/code/test) for triage.
Flag derived requirements explicitly.
Track the verified-closure ratio as evidence of closure progress.

Pitfalls

One-directional closure treated as closure (HLR down but no SRATS back-up).
Verification status ignored (open items left in a 'closed' claim).
Derived requirements unflagged and treated as top-level.
Ratio reported without the gap list (a high ratio can still hide missing coverage).

Behavior contract (gate 3)

The logic is exercised by the gate 3 contract test: scripts/test_requirements_traceability.py against scripts/requirements_traceability_logic.py (stdlib unittest, offline). Run: python3 scripts/test_requirements_traceability.py

Compliance

Standards referenced, not reproduced: ARP4754A / ARP4761A text is proprietary (SAE); summary-only per standards-map.yaml and brief 06.
Revision note: ARP4754B (2023) supersedes ARP4754A; this skill keys to ARP4754A as the certification-baseline revision (FAA AC 20-174 cites A); see standards-map.yaml arp4754a.revision_decision.
compliance: STANDARDS-REF, gated: false.

---name: requirements-traceabilitydescription: Use when planning or auditing requirements traceability per ARP4754A: determine closure status across SRATS, high-level requirements (HLR), low-level requirements (LLR), code, and test levels, list traceability gaps for a level, flag derived requirements, and compute the verified-closure ratio of the trace matrix. Bidirectional closure (each level traces down and back up) and open verification items drive the closed/open verdict; all logic is deterministic, offline stdlib. Trigger: traceability, requirements, closure, SRATS, high-level requirements, low-level requirements, derived requirements, verification, trace matrix.license: Apache-2.0---# ARP4754A Requirements Traceability (systems-engineering-safety/arp4754a/requirements-traceability)Use when the task is requirements traceability per ARP4754A:determining closure across the SRATS-to-test chain, listingtraceability gaps, flagging derived requirements, and measuringverified-closure of the trace matrix.## Domain quick reference- ARP4754A development assurance runs on traceability: system requirements (SRATS) trace to high-level requirements (HLR), HLR trace to low-level requirements (LLR), LLR trace to code and test.- Closure is bidirectional per level: every HLR has an incoming SRATS trace and an outgoing LLR trace; every LLR has an incoming HLR trace and an outgoing code or test trace.- A traced pair with verification still open is an open verification item and keeps the closure status open.- Derived requirements (requirements whose content is not directly traceable to a parent source) must be explicitly flagged.- Verified-closure ratio = verified traces / total traces (0..1).## Workflow1. Collect the trace matrix as (from, to, verified) links.2. Determine closure status and review the gap list.3. Focus on one level (srats/hlr/llr/code/test) for triage.4. Flag derived requirements explicitly.5. Track the verified-closure ratio as evidence of closure progress.## Pitfalls- One-directional closure treated as closure (HLR down but no SRATS back-up).- Verification status ignored (open items left in a 'closed' claim).- Derived requirements unflagged and treated as top-level.- Ratio reported without the gap list (a high ratio can still hide missing coverage).## Behavior contract (gate 3)The logic is exercised by the gate 3 contract test:scripts/test_requirements_traceability.py againstscripts/requirements_traceability_logic.py (stdlib unittest, offline).Run: python3 scripts/test_requirements_traceability.py## Compliance- Standards referenced, not reproduced: ARP4754A / ARP4761A text is proprietary (SAE); summary-only per standards-map.yaml and brief 06.- Revision note: ARP4754B (2023) supersedes ARP4754A; this skill keys to ARP4754A as the certification-baseline revision (FAA AC 20-174 cites A); see standards-map.yaml arp4754a.revision_decision.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions