← ClaudeAtlas

swarm-ledgerlisted

Turn a plan file (plus any documents written for the work) into one ledger page the operator keeps open in a browser: title, overview, sources, phase checkboxes, open questions with answer boxes, operator notes, follow-ups, and a comments dropdown under every item. A local server stores it as one record in ~/development-ledger/ledgers.sqlite3. Every agent working that plan follows the ledger: operator writes reach it through the inbox in a swarm or a ledger watch outside one, it acts on the operator's checks, answers and notes, and records phase states and follow-ups on the ledger as work lands. Use when the user says "swarm ledger", "make a ledger for this plan", "ledger this plan", or when you work a plan that already has a ledger.
the-cloud-clockwork/agentihooks · ★ 1 · Data & Documents · score 70
Install: claude install-skill the-cloud-clockwork/agentihooks
# Swarm Ledger — The Operator's Live Checklist for a Plan Every tool runs through one command that agentihooks installs (code in its `scripts/swarm_ledger/`, standard library only), so every Bash call and every Monitor resolves it without shell state: ```bash agentihooks ledger new … # build a ledger agentihooks ledger serve … # the local server agentihooks ledger watch … # the Monitor feed agentihooks ledger --slug <slug> --as <name> <command> # the agent CLI ``` A ledger `<slug>` is a record in the SQLite database `ledgers.sqlite3` in `~/development-ledger/` (`$LEDGER_DIR`); no per ledger JSON or HTML file is written. The local server (`$LEDGER_PORT`, default 8765) serves the page shell, stores every operator and agent edit in that record and streams changes to open pages. `agentihooks ledger storage export <slug>` writes the whole ledger as JSON on request, and `storage import <file> --slug <slug>` loads one back losslessly. Use it for a plan with several phases worked across sessions; a single-step task needs no ledger. ## Part A — Create a ledger ### A1. Write the content file (AI-JUDGMENT) Read the plan file and every document named in the arguments. Write `~/scratchpad/<repo>/<task>/ledger-content.json`: ```json { "title": "<plan name>", "overview": "<what the work is for and what done looks like, plain words, ≤ 200 words>", "sources": ["<absolute path of the plan file>"