mcpbeat

Traceability Audit

hoangnguyen0403/traceability-audit

Map requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.

699 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill traceability-audit

The instruction itself

8 sections, as written by the author

Traceability Audit Skill

> [!IMPORTANT]

> Map requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.

Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

Traceability Audit Workflow

Goal: Prove every acceptance criterion has implementation and verification evidence before release or handoff.

Steps

  • Load sources:
  • BRD-lite, PRD, SRS/FRS, AC list, implementation plan, changed files, tests, walkthrough, PR comments, release notes.
  • Jira/GitHub/GitLab/ADO/Zephyr/Confluence MCPs when configured; otherwise use exported files and local evidence.
  • Build trace map:
  • BRD objective -> PRD requirement ID.
  • PRD requirement ID -> SRS/FRS contract.
  • AC -> implementation file/function.
  • AC -> automated test, manual/Zephyr TC, or verification step.
  • Release note -> shipped user-visible change.
  • Classify each AC:
  • Covered: code and verification evidence exists.
  • Partial: code or evidence incomplete.
  • Missing: no implementation or no verification.
  • Out of scope: explicitly deferred with owner/link.
  • Flag gaps:
  • Missing requirement mapping.
  • Missing AC implementation.
  • Missing test or manual coverage.
  • Release note missing shipped user impact.

Runtime Contract

  • Use pre-release or handoff to prove requirement-to-evidence coverage.
  • Required inputs: PRD/SRS with AC list plus implementation, test, and release artifacts to map against.
  • Return BLOCKED only when no requirement or AC list exists to trace.

Handoff Payload

  • slug, requirement map, gap classification, outcome report, next workflow.

Blocking Questions

  • Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# Traceability Audit

## Summary

## Requirement Map

| Requirement | SRS/FRS Contract | Verification | Status |
| --- | --- | --- | --- |
| [REQ] | [contract] | [test/evidence] | [status] |

## Gaps

## Outcome Report
feature_status: implemented | partially_implemented | blocked
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: implement-feature | dev-fix | deploy-release

## Next Workflow

## Cost Report
Call `get_session_cost(workflow="traceability-audit")` before final handoff.

How to use it

Copy the folder

Take hoangnguyen0403/traceability-audit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.