Reconcile AUD artifacts by dispositioning findings and routing them to specs.
npx skills add https://github.com/davidlee/spec-driver --skill audit-change
Please help me install this Agent Skill. Skill: audit-change Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/audit-change Command: npx skills add https://github.com/davidlee/spec-driver --skill audit-change
It prevents audits from becoming half-done notes by forcing every AUD finding to be evidenced, dispositioned, reconciled into authoritative specs/contracts, and only then considered closure-grade.
Run audit-change to reconcile your AUD findings by creating or updating the AUD-* artifact, routing each finding to the correct spec or follow-up path, and handing off to close only when every finding is dispositioned and reconciled.
High-intent search queries and answers about installing and using this skill.
To ensure audit findings are dispositioned, you must reconcile them into authoritative specs or contracts using explicit routing rules like spec_patch. This prevents half-done audit notes by requiring machine-checkable inline dispositions before closure.
Running a conformance audit requires applying mode-aware auditing tied to your post-implementation delta. This process checks implementation drift against authoritative specs and routes every required verification check into the canonical lifecycle.
When audit finding routing is ambiguous, you should consult the authority source to determine the correct path. The reconciliation loop prefers resolving in-scope authority via spec_patch, then shifts to revision for broader authority changes.
Yes, discovery auditing supports existing-code investigation and backfill scenarios. It maps correct delta ownership while requiring explicit dispositions per finding to ensure all discoveries are reconciled into authoritative specs.
Yes, closure-grade audit handoff requires every finding to have a machine-checkable inline disposition. The canonical lifecycle mandates sync and validate steps to ensure all findings are fully reconciled before completion.
When spec reconciliation encounters authority shifts during an audit, the routing rules trigger a revision instead of a standard spec_patch. This ensures the specification accurately reflects the new authoritative contract before closure.
jason-c-devConfigures CloudWatch, CloudTrail, AWS Config, and Security Hub across accounts and regions.
kevintsengtwArchive completed changes with status checks and optional delta spec sync.
davidleeCreate or update spec revisions when requirements move between source and destination specs.
deepklarityAudit AI agents' autonomous loop closure from symptom discovery to verified fix.
