ratchet

Record and lock completed RPI workflow gates in a chain ledger.

418|40|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/boshu2/agentops --skill ratchet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ratchet
Source: https://github.com/boshu2/agentops/tree/main/skills/ratchet
Command: npx skills add https://github.com/boshu2/agentops --skill ratchet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ratchet skill solves the problem of preserving irreversible progress in RPI workflows by recording and permanently locking completed gates, ensuring teams cannot regress to earlier stages after critical decisions.

Core Features & Use Cases

  • Permanent progress gating: once a gate is ratcheted, it cannot be undone, providing a robust audit trail.
  • Gate operations: status, check, record, and skip commands to track, validate, and document progress.
  • Chain ledger: maintains a machine-readable log at .agents/ao/chain.jsonl for reproducibility and traceability across teams.

Quick Start

Use the ratchet commands to inspect and advance progress: ao ratchet status ao ratchet check <step> ao ratchet record <step> --output "<artifact-path>" ao ratchet skip <step> --reason "<why>"

Frequently Asked Questions about ratchet

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

FAQPage Schema
How do I permanently lock completed workflow stages so teams cannot regress to earlier steps?

Gated workflow progress is permanently locked by recording completed stages in a chain ledger, ensuring teams cannot regress after critical decisions. Once a gate is ratcheted, it cannot be undone, providing a robust audit trail.

What is the best way to maintain a machine-readable audit trail for sequential workflow stages?

An audit trail for sequential workflow stages is maintained at .agents/ao/chain.jsonl. This machine-readable log provides reproducibility and traceability across teams by permanently recording gate completions and skips.

How do I record or skip steps in a gated workflow with justification?

Steps in a gated workflow are recorded using the record command with an output path, or skipped using the skip command with a reason. These operations validate and document progress within the sequential stages.

Can I integrate permanent progress gating with existing epic loops like /crank or /swarm?

Permanent progress gating integrates with epic loops like /crank or /swarm to enforce discipline across teams. It applies to sequential stages such as research, plan, implement, vibe, and post-mortem.

How do I check the status of a specific stage in a sequential workflow?

The status of a specific stage in a sequential workflow is checked using the status and check commands. These operations inspect and validate current progress before advancing to the next gate.