unlazy

Install

npx skillfoxx add skills/unlazy

npx skills add leonxlnx/unlazy --skill unlazy -a claude-code -y

npx skills add leonxlnx/unlazy --skill unlazy -a cursor -y

npx skills add leonxlnx/unlazy --skill unlazy -a github-copilot -y

npx skills add leonxlnx/unlazy --skill unlazy -a codex -y

npx skills add leonxlnx/unlazy --skill unlazy -a gemini-cli -y

npx skills add leonxlnx/unlazy --skill unlazy -a cline -y

npx skills add leonxlnx/unlazy --skill unlazy -a roo -y

npx skills add leonxlnx/unlazy --skill unlazy -a opencode -y

npx skills add Leonxlnx/unlazy

This is third-party code. Review the repository files before installing.

What it does

The skill makes the agent state its acceptance criteria before doing the work. Each ledger item gets one observable outcome and, where possible, a CHECK command with an expected EXPECT output. An item counts as met only when the command exits zero, its output matches the expectation, and the record carries a fingerprint of the check definition. The Depth Tree method splits a large task into leaves with a narrow contract and their own ledger, with modes for solo, orchestrated and parallel work. CHECK lines are shell code: the agent reads them and runs them only after explicit approval, and treats inputs and output as untrusted.

Who it is for. For engineers who hand the agent large or multi-step tasks and want verifiable completion instead of a confident done report.

Example request

/unlazy tree 5 refactor the payment module and verify every migration path

Limitations

The checker can prove only the command oracle you declare: it cannot tell whether a gate's English title matches what the command really does, so it is worth exactly as much as the checks you write. CHECK lines run as shell code after your approval; the definition binding catches structural drift but not tampering by anyone who can edit the ledger. The scripts and the optional Stop hook need Node 16 or newer and pull no third-party packages. The source targets version 2.1.0 with no tagged release, so pin an exact commit for an immutable install.

How to disable. Remove the unlazy folder from the agent's skills directory, for example ~/.claude/skills/unlazy or ~/.codex/skills/unlazy. If you installed the Stop hook, remove it with the same install script.

Security check

• Runs shell commands from the check ledger, but only after explicit approval
• Can install an optional Stop hook that fires when the agent stops

README in short

The README lays out the approach: write the acceptance ledger first, run reviewed checks, reverify returned work, and report only what the evidence supports. Install goes through the skills CLI (npx skills add) for supported agents or by copying manually into the Claude Code and Codex CLI directories. The core is SKILL.md, and the gate-check.mjs checker validates the ledger format, exit codes and EXPECT matches, with a non-executing --status mode. Depth Tree modes cover orchestration and parallel work with per-leaf and per-branch contracts. The method is grounded in 2025 and 2026 research on model laziness, underthinking and premature completion.

SKILL.md

---
name: unlazy
description: Enforces completion discipline for substantial autonomous work by writing acceptance gates before execution, decomposing work with the Depth Tree, running approved checks, and re-verifying evidence before reporting. Use when an agent faces a long or multi-part task, work that has returned half-done, an exhaustive audit or build, parallel leaves or pipelines, or explicit triggers such as /unlazy, $unlazy, "tree N", "gates", and "do not stop until it is done".
---

# Unlazy

Make incomplete work visible and make completion testable. Prove outcomes against a ledger instead of relying on a confident done report.

## Write gates before real work

For solo work, create `GATES.md` from the local file `templates/gates-leaf.md` before implementing (orchestrated mode instead starts from `templates/PLAN.md` plus per-leaf `templates/gates-leaf.md` and per-branch `templates/gates-node.md` under `.unlazy/<scope>/`; see Build the Depth Tree below). State one observable outcome per gate. Give every runnable gate an indented `CHECK:` and `EXPECT:`; use a manual gate only when no command can decide the outcome.

Treat `CHECK:` as code. Before executing an inherited ledger, parse it without running anything and read every command and called script.

Related