Menu
Record ADLC P5 review evidence and P6 acceptance packet workflows in Pi. Use after skeptical review to record verified findings, dry-pass evidence, and behavior acceptance evidence.
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
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.
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.
| name | adlc-prosecute |
| description | Record ADLC P5 review evidence and P6 acceptance packet workflows in Pi. Use after skeptical review to record verified findings, dry-pass evidence, and behavior acceptance evidence. |
This skill does not run the reviewer by itself. Run the skeptical review first, capture the transcript, then record the reviewer-produced evidence with adlc prosecute.
The transcript must name the ticket and reviewed git-worktree:<hash> revision that P5 records. Do not pass --revision in normal git worktrees; auto-resolved revisions keep P6 staleness protection active.
The P5 input must also include review_packet with prompt path/hash, reviewed-input path/hash, and clean_worktree equal to the reviewed revision.
For scoped P5 evidence:
adlc prosecute --input .adlc/p5-passes.json --ticket <ticket-id> --dir .adlc --json
adlc run p5 --ticket <ticket-id> --dir .adlc --json
P6 strict mode requires P5 evidence:
adlc behavior-diff capture --config behavior.json --out .adlc/before.json
adlc behavior-diff compare .adlc/before.json .adlc/after.json --json
adlc accept --ticket <ticket-id> --packet .adlc/packet.json --before .adlc/before.json --after .adlc/after.json --dir .adlc --json
adlc run p6 --ticket <ticket-id> --dir .adlc --json
The bundled docs fixture is static. Use it only with its fixture revision:
adlc prosecute --input docs/examples/p5-passes.json --ticket T1 --revision docs-example-revision --dir .adlc --json