requirement-traceability-analysis skillA
requirement-traceability-analysis is agent-read markdown (skill) from naodeng/awesome-qa-skills: Use this skill when requirements, acceptance criteria, design, code, tests, defects, or evidence must be mapped bidirectionally and coverage gaps made explicit; triggers include requirement traceability, traceability analysis, and traceability matrix..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Requirement Traceability Analysis Build a bidirectional, auditable mapping from requirements or controls to acceptance criteria, design, code, tests, defects, and validation evidence. Keep relationship types separate from coverage statuses; never turn names, static presence, or report wording into execution results. ## When to Use - You need to check whether requirements have acceptance, design, implementation, test, and defect coverage. - You need to find orphan requirements, orphan tests, broken links, stale artifacts, or missing evidence. - You need an auditable traceability matrix for release, change review, compliance, or risk governance. Do not use it only to write test cases, execute tests, or decide business priority; this Skill analyzes the mappings and evidence supplied by the user. ## Output Format Options - Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields. - Do not present a structured format or static inventory as execution, pass, approval, or release evidence. ## How to Use …
Read the whole file at its exact version.
How to install
mdr add naodeng/awesome-qa-skills/requirement-traceability-analysis@git:20260914.45aa88fmdr add naodeng/awesome-qa-skills/requirement-traceability-analysis@sha256:360a84756afe63bePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_443alsczb573c76z)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.45aa88f latest | 2026-09-14 | 45aa88f | 5,993 B | A | view · diff |
| git:20260914.72ab38e | 2026-09-14 | 72ab38e | 5,090 B | A | view · diff |
| git:20260914.ba5cf40 | 2026-09-14 | ba5cf40 | 4,939 B | A | view · diff |
| git:20260914.2a838ba | 2026-09-14 | 2a838ba | 3,785 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5993 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
naodeng/awesome-qa-skills · 230 stars · license NOASSERTION · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_443alsczb573c76z GET https://markdownregistry.com/api/v1/resolve?ref=naodeng/awesome-qa-skills/requirement-traceability-analysis GET https://markdownregistry.com/api/v1/blob/360a84756afe63bec35c41cc81a1204630f4a0541c4425bc2341405a7de2ce78
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.