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 four artifacts. All are required. If any is missing, stop and obtain it before proceeding — an audit with incomplete inputs produces incomplete results. **Spec file path.** The `F-nnn-*.md` the plan was built from. This is where the acceptance criteria are *defined*; the plan only cites them. Auditing against the plan's copy of the criteria cannot detect the failure that matters most here — a criterion the spec states and the plan never picked up — because that criterion is absent from the plan by definition. **Plan file path.** The `.md` plan file the work was executed against. 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