knowledge-mcp: Skill for Claude Code

AUDIT-PLAN — the adversarial audit procedure detail

Intent-fidelity audit

For every rule the plan asserts, locate the ORIGINAL statement (ticket quote, recorded decision) and diff semantically: duty-holder, cost-bearer, prevent-vs-compensate, absolute-vs-best-effort. Drift is T1/T2 — it invalidates every downstream artifact. A mechanism that only executes in a state the rule forbids is evidence the premise twisted upstream — the mechanism's existence is the finding even when its implementation is flawless. Vocabulary sweeps cover inflections and verb forms; a suspiciously clean census widens the pattern.

Requirement → criterion coverage

Walk In Scope as a checklist; every required behavior maps to a criterion that would FAIL if absent; decompose compounds ("X and Y" is two behaviors — the silent-omission path ships X, drops Y, looks complete). A specified behavior with no failing-when-absent catcher is T2.

Check each rule against the number beside it

For every RULE a plan states, check the FIGURE reported beside it is reachable under the rule AS WRITTEN. The recurring defect: the author probed one way and wrote the spec another, so the measurement was taken under corrected behavior while the prose describes the uncorrected one. The tell: a figure that cannot be derived from the rule printed next to it, or one BELOW an unfixed baseline. On a heavily revised plan this is the single highest-yield check.

Synthesize the post-edit artifact

Build the artifact the plan's own mandated text WOULD produce, then run every gate against it. It answers in one pass whether any criterion is unsatisfiable by the text its own step prescribes, and whether two criteria contradict each other. Cheap whenever the edits are enumerable. Build the faithful variant too (see the probe-a-gate rulebook).

Walk criteria to their artifacts

For every criterion, identify the EXACT artifact it reads and verify against THAT artifact, never the paragraph describing it. Two directed probes per plan: CROSS-NODE CONTRACT DIFF (where two nodes produce and consume the same field, diff exact spellings — two gates demanding opposite spellings of one field is a proven finding class) and SCOPE CHECK (what scope does each rule sentence bind, and does any gate apply it at a different scope?).