phira-impl-vs-claim-audit

Use this skill when someone provides a document describing what was implemented (paper, design doc, README section, notes) and you need to check whether the code actually matches what the document claims.

Goal: detect "claim drift" (code does not implement the described algorithm/behavior) and "default drift" (defaults/baseline behavior changed unintentionally).

Inputs you should request (if missing)

• The document excerpt(s): exact text, with section headings (and page/figure/equation numbers if applicable).
• Implementation context: changed files/diff, new flags/config keys, and the intended entrypoint(s).
• Any stated compatibility constraints (env versions, dependency policy).

Audit checklist