Audit Trail
npx machina-cli add skill a5c-ai/babysitter/audit-trail --openclawFiles (1)
SKILL.md
896 B
Audit Trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
Traceability Chain
PRD -> Epic -> Task -> GitHub Issue -> Code Commit
Capabilities
- PRD user story to task mapping
- Task to GitHub issue linking
- Commit to issue cross-referencing
- Coverage matrix generation
- Audit completeness verification
File Structure
.claude/
prds/<feature-name>.md # PRD with user stories
epics/<feature-name>/
epic.md # Technical epic
1.md, 2.md, ... # Individual tasks
tasks-index.md # Task index with traceability
Audit Verification
The tracking process (ccpm-tracking.js) verifies:
- Every PRD user story maps to at least one task
- Every task maps to a GitHub issue (if sync enabled)
- Every completed task has associated commits
- Coverage percentage is reported
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/ccpm/skills/audit-trail/SKILL.mdView on GitHub Overview
Audit Trail provides end-to-end traceability for CCPM pipelines, linking PRD to Epics, Tasks, GitHub Issues, and Code Commits. It supports coverage matrix generation and audit completeness verification to ensure every change is traceable from requirements to delivery.
How This Skill Works
The skill enforces a traceability chain: PRD -> Epic -> Task -> GitHub Issue -> Code Commit. It includes capabilities for mapping PRD stories to tasks, linking tasks to issues, and cross-referencing commits to issues, with a coverage matrix and audit checks powered by the ccpm-tracking.js script.
When to Use It
- Releasing a CCPM-driven feature and needing end-to-end traceability from PRD to commit
- Onboarding new team members who require context across PRD, tasks, and code
- Auditing for compliance or audit readiness with verifiable trace links
- Measuring traceability health with a coverage matrix to identify gaps
- Synchronizing PRD changes to tasks and maintaining persistent linkage
Quick Start
- Step 1: Ensure PRD markdowns are in .claude/prds and corresponding epics/tasks exist
- Step 2: Map PRD user stories to tasks and link each task to a GitHub issue
- Step 3: Run the ccpm-tracking.js audit and review the generated coverage percentage
Best Practices
- Enforce PRD-to-task mapping for all user stories to maintain traceability
- Link every task to a corresponding GitHub issue for visibility
- Reference related issues in commit messages to enable cross-referencing
- Regularly generate and review the coverage matrix to spot gaps
- Run ccpm-tracking.js after sprints or feature completions to verify audit completeness
Example Use Cases
- Feature rollout: end-to-end traceability from PRD to the final commit in a payment flow
- Critical bug fix: audit trail demonstrates linkage from reported issue to fix commit
- New user onboarding flow: full traceability from PRD through tasks to code changes
- Refactoring initiative: traceability from epics and tasks to commits for safety checks
- Regulatory compliance project: audit-ready artifacts with complete trace links
Frequently Asked Questions
Add this skill to your agents
