Traceability Audit Skill
[!IMPORTANT]
Map requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, 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.
1---2name: traceability-audit3description: Map requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.4---5# Traceability Audit Skill
6
7> [!IMPORTANT]
8> Map requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.
9
10Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.
11
12## Instructions
13
14When the user asks to perform this workflow, execute the following steps:
15
16
17# Traceability Audit Workflow
18
19Goal: Prove every acceptance criterion has implementation and verification evidence before release or handoff.
20
21## Steps
22
231. Load sources:
24 - BRD-lite, PRD, SRS/FRS, AC list, implementation plan, changed files, tests, walkthrough, PR comments, release notes.
25 - Jira/GitHub/GitLab/ADO/Zephyr/Confluence MCPs when configured; otherwise use exported files and local evidence.
262. Build trace map:
27 - BRD objective -> PRD requirement ID.
28 - PRD requirement ID -> SRS/FRS contract.
29 - AC -> implementation file/function.
30 - AC -> automated test, manual/Zephyr TC, or verification step.
31 - Release note -> shipped user-visible change.
323. Classify each AC:
33 - Covered: code and verification evidence exists.
34 - Partial: code or evidence incomplete.
35 - Missing: no implementation or no verification.
36 - Out of scope: explicitly deferred with owner/link.
374. Flag gaps:
38 - Missing requirement mapping.
39 - Missing AC implementation.
40 - Missing test or manual coverage.
41 - Release note missing shipped user impact.
42
43## Runtime Contract
44- Use pre-release or handoff to prove requirement-to-evidence coverage.
45- Required inputs: PRD/SRS with AC list plus implementation, test, and release artifacts to map against.
46- Return BLOCKED only when no requirement or AC list exists to trace.
47## Handoff Payload
48- `slug`, requirement map, gap classification, outcome report, next workflow.
49## Blocking Questions
50- Ask max 3 at a time with a recommended default and 2-3 options.
51
52## Output Template
53
54```md
55# Traceability Audit
56
57## Summary
58
59## Requirement Map
60
61| Requirement | SRS/FRS Contract | Verification | Status |
62| --- | --- | --- | --- |
63| [REQ] | [contract] | [test/evidence] | [status] |
64
65## Gaps
66
67## Outcome Report
68feature_status: implemented | partially_implemented | blocked
69requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
70completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: implement-feature | dev-fix | deploy-release
71
72## Next Workflow
73
74## Cost Report
75Call `get_session_cost(workflow="traceability-audit")` before final handoff.
76```
77
HoangNguyen0403