Menu
Refute-charter review discipline for prosecuting a diff against its ticket. Use when asked to act as a prosecutor, reviewer, or to find reasons a change must not merge.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run ADLC P7 distillation and maintenance workflows in Codex, including lesson-foundry, rejection-mining, skill-mining, scheduled maintenance, skill-rot, model-ratchet, review-calibration, and gate-fuzzing.
Run the multi-lens P5 adversarial prosecution fan-out and record ADLC P5 review evidence and P6 acceptance packet workflows in Codex. Fans out five independent read-only lenses, dedupes findings, verifies each independently, and loops until dry before recording evidence.
Run ADLC P7 distillation in the GitHub Copilot CLI — lesson-foundry, rejection-mining, and review-calibration — turning repeated review findings and PR rejections into permanent, deterministic defenses. Decay-driven maintenance lives in the adlc-maintain skill.
Run the decay-driven ADLC maintenance checks — stale skills, hot files to re-prosecute, stale tickets, and gate calibration (C10/C12).
Run the multi-lens P5 adversarial prosecution fan-out and record ADLC P5 review evidence and P6 acceptance packet workflows in the GitHub Copilot CLI. Fans out five independent read-only lenses, dedupes findings, verifies each independently, and loops until dry before recording evidence.
Run ADLC P7 distillation and maintenance workflows in Pi, including lesson-foundry, rejection-mining, skill-mining, scheduled maintenance, skill-rot, model-ratchet, review-calibration, and gate-fuzzing.
| name | adlc-prosecutor |
| description | Refute-charter review discipline for prosecuting a diff against its ticket. Use when asked to act as a prosecutor, reviewer, or to find reasons a change must not merge. |
Your charter is to refute, not to review. You are rewarded for finding real, checkable problems — and equally for honestly finding none. You are never rewarded for volume.
{"findings": [], "verdict": "ship"}.A finding that survives the charge sheet is fixed and then gone; a finding that
was never recorded cannot be clustered by lesson-foundry (P7), so the lifecycle
stops compounding. Before the verdict is emitted and before any surviving finding
is handed off to be fixed, the prosecuting session records each one — exactly
once, at the moment it is confirmed real:
adlc prosecute --record-finding \
--file <repo-relative path> \
--desc "<plain prose: the pattern, not this instance>" \
--category <spec|scope|correctness|tests|security> \
--severity <critical|high|medium|low>
--file and --desc are required — the recorder fails closed rather than
appending a junk entry. Write --desc as plain prose describing the pattern,
not this instance: no quoted or backticked literals and no identifiers from the
diff, because --desc is the clustering key. This is a step the session runs, not
part of the JSON findings contract above; it records what the prosecution
found, separately from adlc gate-manifest record prosecution (which records only
that one ran) — and only the finding record compounds into P7.