auditing-plan-fidelitylisted

# Auditing Plan Fidelity ## Overview Given a plan and the git diff of the work that claims to implement it, this skill answers: was the plan followed? What deviated? Was every deviation justified and recorded? The output is a structured audit report that becomes the first artifact a code reviewer sees before reading a single line of code. This skill runs between execution and code review. It separates "is this code good?" (code review) from "is this the code we planned?" (this audit). A high-deviation audit is a signal to route to `exloom:capturing-learnings` — it is a learning mechanism, not a punishment mechanism. ## Process ### Inputs Before running the audit, gather three artifacts. All three are required. If any is missing, stop and obtain it before proceeding — an audit with incomplete inputs produces incomplete results. **Plan file path.** The `.md` plan file as approved by `exloom:reviewing-plans`. Usually in `.claude/plans/` or a similar location. If the path is unknown, check recent commits for the plan file or ask the PR author. The plan must contain at minimum: - A "Files to Touch" section listing every file expected to be created, modified, or deleted - Acceptance criteria — the testable conditions that define "done" - A Deviation Log section (filled during `exloom:executing-handoff-plans`) If the plan lacks any of these sections, note it in the audit report. A plan without a "Files to Touch" section makes Step 1 impossible. A plan without acceptance crit