ratchet:verdict

Record human verdicts for escalated Ratchet debates and update plan files.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/netbrain/ratchet --skill ratchet-verdict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ratchet:verdict
Source: https://github.com/netbrain/ratchet/tree/main/skills/verdict
Command: npx skills add https://github.com/netbrain/ratchet --skill ratchet-verdict

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear human override for Ratchet debates that have been escalated or left undecided by an automated tiebreaker, preventing stalled issues and ensuring a definitive decision and reasoning are recorded so the workflow can progress.

Core Features & Use Cases

  • Human Verdict Capture: Presents escalated debates, summarizes rounds and key arguments, and collects an Accept, Reject, or Modify decision with human reasoning.
  • State & Plan Management: Writes or updates .ratchet/debates/<id>/verdict.json and meta.json, updates .ratchet/plan.yaml phase_status and issue state, and advances phases when conditions are met.
  • Scoring & Audit Trail: Invokes score update scripts to append outcomes to .ratchet/scores and records timestamps and resolver identity for auditing.
  • Use Case: A reviewer inspects a disputed build change, chooses Accept to advance the issue phase, or selects Modify with required changes to return work to the generative agent.

Quick Start

Use the /ratchet:verdict command with the debate id and your choice (accept, reject, or modify) to record a human decision and update the plan.

Frequently Asked Questions about ratchet:verdict

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record a human tie-breaker decision for an escalated workflow debate?

To record a human tie-breaker for an escalated workflow debate, you submit your decision and reasoning to update the debate's state files. The system captures your verdict and applies it to update the plan status and issue state automatically.

How do I resolve an automated tiebreaker recommendation that is blocking my plan?

Resolving an automated tiebreaker recommendation requires providing a manual override through a human verdict. You choose to accept, reject, or modify the disputed item, which unblocks the stalled issue and advances the workflow phase.

Can I update plan.yaml phase_status manually after a disputed build change?

Yes, you can update plan.yaml phase_status after a disputed build change by issuing a verdict. Providing a manual resolution adjusts the phase status and issue state, ensuring the repository-managed workflow progresses from its stalled condition.

Does the human-in-the-loop verdict process maintain an audit trail for workflow automation?

The human-in-the-loop verdict process maintains an audit trail by recording timestamps and resolver identity. It also invokes score update scripts to append outcomes, ensuring the automation workflow has a complete history of the decision.

What happens to the issue state when I select Modify during a debate resolution?

When you select Modify during a debate resolution, the issue state is updated to return work to the generative agent. This action requires you to specify the required changes before the workflow can proceed to the next phase.

Do I need specific repository files to run a human verdict on an escalated debate?

Yes, you need specific repository files to run a human verdict, specifically the .ratchet/debates directory containing meta.json and verdict.json, and the .ratchet/plan.yaml file to ensure the workflow state updates correctly.