Traceability Audit Skill
SkillAI & modelsMap requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Traceability Audit Skill skill
What this skill tells your AI
The instructions your AI receives, as published by hoangnguyen0403/agent-skills-standard in .codex/skills/traceability-audit/SKILL.md and read by ahel’s review.
[!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.
Signals
- GitHub stars
- 565
- Forks
- 163
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
traceability-audit- Source
- github.com/hoangnguyen0403/agent-skills-standard