riverho/agents-playbook

A portable, agent-first playbook you drop into any folder: an agent orients on one master file (playbook.yaml), picks a task, does the work, proves it with executable acceptance checks (shell commands), records, and rolls the records up into a human-readable report. pb record --status done re-runs each task's checks and refuses on failure, and v0.7.0 adds layered planning with a provably read-only dry run, human-gated branches and multi-agent leases.

Agents-Playbook is a portable, agent-first playbook you drop into any folder, and its DSH plugin (dsh-agents-playbook) exposes the playbook's kernel to DeepSeek Harness. An agent orients on one master file (playbook.yaml, the "fixation", kept salient by cheap re-injection so long context and compaction never lose the plot), picks a task, does the work, proves it with executable acceptance checks, records, and rolls the records up into a human-readable report. The core thesis is that done is an exit code, not prose: pb record --status done re-runs each task's shell acceptance_checks and refuses to record if any fail, and durable state on disk (a backlog plus an append-only journal) means context loss never means work loss. v0.7.0 adds layered planning — a named stratum (substrate → data → domain → interface) may carry a gate that must exit 0 before anything in a higher layer is claimable, with pb plan --layers printing a provably read-only dry run that fingerprints state and exits 3 if anything changed — plus human-gated branches batched into a single WAITING ON A HUMAN hand-off, multi-agent leases, complete worktrees and crash recovery.

Workflow & Automation ★ 1
View on GitHub ↗

Install

dsh plugin --profile web add dsh-agents-playbook@^0.7.1

Adapted from the README's compatibility table, which writes the profile as a placeholder (dsh plugin --profile <p> add dsh-agents-playbook@^0.7.1) and notes the install needs pnpm — a plain npm install does not enable it. The concrete web profile is substituted here; the quoted range ^0.7.1 is verbatim from the README.

Compatibility

Installed into a DSH profile; the README's compatibility table notes that on dsh 0.2.0-rc.2 only 0.7.1 installs — 0.7.0 declares ^0.1.5-rc.2 peers, which that runtime's compatibility gate rejects — and that pnpm is required (plain npm install does not enable it). The underlying playbook is portable: everything lives inside its folder, so copying it anywhere still works (carry-on).

Details

Alternatives

940842546/dsh-permissions · adithya-hmt/fullstack-expert · alib8b8/dsh-plugin-aflare

More plugins in Workflow & Automation

Browse more in Workflow & Automation

Guides for Workflow & Automation plugins