handofflisted

Coordinate progressive repository work across agents with a shared HANDOFF.md ledger. Use in repositories with a ledger, or on explicit handoff requests: /handoff:init, 'initialise the handoff', /handoff:continue, /handoff:status, /handoff:view, /handoff:purge, or 'use handoff'. After activation: handoff_guard.py name --root <repo> claims the session name; handoff_guard.py read --root <repo> returns ledger text and version in one snapshot. Audit later entries and code before treating unchecked boxes as unfinished. For ledger writes: handoff_guard.py apply --root <repo> --expect-version V with --entry FILE or --content FILE. On exit 3, re-read and re-audit; never retry the stale write. A user viewer assignment is required queued work: finish your current task, then audit and complete it without another prompt. Track investigations before research, even without code edits; a name claim is not a task.
divijshrivastava/handoff-skill · ★ 1 · AI & Automation · score 78

Install: claude install-skill divijshrivastava/handoff-skill

# Handoff contract Treat the ledger as progressive history, not a flat todo list. An old unchecked box is an investigation cue. It is not proof that work remains: a later task, commit, or source change may have completed, absorbed, narrowed, replaced, or superseded it. The repository's own instructions remain authoritative. This skill supplies a reusable workflow; it never weakens `AGENTS.md`, `CLAUDE.md`, contribution rules, ownership boundaries, verification requirements, or safety policy. ## Activation Handoff work starts in a repository that already keeps a ledger, and elsewhere only when the user asks for it. The triggers are: - an existing `HANDOFF.md` in the repository. Someone put it there to track work this way, and a ledger nobody reads is worse than none: entries go stale, and the next agent trusts checkboxes no one has audited; - the `/handoff:init` command, or the phrase "initialise the handoff" in a host without slash commands (Codex's default prompt supplies it); - another explicit handoff request: `/handoff:continue`, `/handoff:status`, `/handoff:view`, `/handoff:purge`, or a direct instruction such as "use handoff", "record this in the ledger", "purge the handoff", or "take over <owner>'s tasks". In a repository with no ledger and no such request, do none of this skill's work: no session name, no preflight, no ledger creation, no task entry. Multiple agents sharing the tree, or work that merely looks unfinished, do not by themselves make a r