due-process

Installation
SKILL.md

Due Process

Use read-only checks only. Do not edit files, install dependencies, generate artifacts, run mutating commands, change external systems, or implement fixes.

Prepare

  1. Define the raw artifact, decision, success criteria, scope, source locations, and minimum necessary context.
  2. Locate the actual artifact and applicable repository instructions, code, tests, configuration, history, plans, internal documents, dependencies, vendors, and versions.

Review

Require exactly two fresh reviewer agents in parallel, followed by one fresh referee agent. If this topology or either report is unavailable, stop and report the review incomplete; do not substitute, retry, or self-review. Attempt each reviewer creation once with valid runtime parameters. In Codex, omit agent_type, model, and reasoning_effort when inheriting context; any creation error means stop, not retry. Attempt the referee once under the same rule. Report the topology and whether every agent was created successfully on its first call. Give reviewers identical raw artifacts, sources, criteria, and context plus only their role brief. Withhold prior conclusions and prohibit shared reviewer-written artifacts.

  • Counsel for: Build the strongest evidence-based case. Identify proven strengths, preserved value, and conditions for success; avoid generic praise.
  • Counsel against: Try to disprove the artifact. Find material defects, unsupported assumptions, incompatibilities, failure modes, and simpler alternatives; avoid performative pessimism.
Installs
1
First Seen
Aug 2, 2026