OpenParable
Skip to content
← Back to skills

Judgment Day

Testing & Quality
judgment-day

Judgment Day is an Agent Skill for testing & quality published in the Gentleman-Programming/gentle-ai repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Trigger: judgment day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix/re-judgment rounds.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Gentleman-Programming/gentle-ai/blob/HEAD/internal/assets/skills/judgment-day/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/judgment-day, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Activation Contract

Load only when the user explicitly requests Judgment Day or equivalent dual/adversarial review for a concrete target. Judgment Day replaces ordinary 4R for that target; never run both.

Hard Rules

  • Resolve matching project skills before starting and pass the same paths to both judges and any fix actor.
  • Build one complete immutable target, then launch two blind read-only judges in parallel with identical scope and criteria.
  • Each judge returns one neutral findings result and terminates. Wait for both; never accept a partial judgment.
  • Never launch review-refuter; two-judge agreement is the corroboration mechanism.
  • Only the parent orchestrator merges/persists findings, launches the fix actor, launches scoped re-judgment, and updates native counters.
  • Fix only severe findings confirmed by both judges. WARNING/SUGGESTION rows remain info.
  • Permit at most two fix rounds and two scoped re-judgments. Re-judgment sees only the frozen ledger plus fix delta and may record fix-caused defects.
  • Terminal transaction states are only approved | escalated; never reset or extend an exhausted lineage.

Decision Gates

ConditionAction
Target unclearAsk one scope question and stop.
Both judges confirm severe findingAsk before round-one correction; then use the bounded fix actor.
One judge reports itRecord suspect; do not auto-fix.
Judges contradictEscalate for explicit human decision.
Scoped re-judgment fails before round twoParent may launch the final bounded fix round.
Any issue remains after round twoEscalate and stop.

Execution Steps

  1. Start review/start(target, mode=judgment_day) and persist the transaction.
  2. Launch both read-only judges against the same immutable target.
  3. Merge findings into the frozen ledger and persist it through the selected artifact store.
  4. Ask before round-one correction; run the fix actor only for confirmed severe IDs.
  5. Run both judges again only over the frozen ledger plus immutable fix delta.
  6. Repeat once at most, then run independent final verification and emit the terminal receipt.

Output Contract

Return target identity, round, confirmed/suspect/contradiction/INFO counts, correction work units, scoped re-judgment result, artifact references, skill resolution, and exactly one final JUDGMENT: APPROVED ✅ or JUDGMENT: ESCALATED ⚠️.

References