← ClaudeAtlas

okhp3-session-handofflisted

Create a durable continuation record when work pauses, becomes blocked, crosses a machine, or crosses an agent host. Use after substantial work or when the owner asks for a handoff. Record changed files, reasoning, evidence tiers, validation, limitations, and the exact next action without relying on chat memory.
OKHP3/skillz · ★ 3 · AI & Automation · score 70
Install: claude install-skill OKHP3/skillz
# okhp3-session-handoff **OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3) ## Inputs and output Require a project root, handoff destination, objective, and current work inventory. Return the handoff path, source boundary, status, next action, evidence ledger, checks, limitations, and owner decisions. If the destination is not identified, return `BLOCKED` rather than guessing. Run `okhp3-artifact-validation` first when practical. Write a dated Markdown record under the user-approved handoff destination, using a collision-safe filename, containing: - source host and date; - objective and current status; - changed files or artifact inventory; - why non-obvious decisions were made; - confirmed, inferred, proposed, and unknown conclusions where relevant; - checks run, real results, and checks not run; - known defects, limitations, and owner decisions needed; - exact next action and the files needed to resume. Keep paths relative. Do not claim that another copy has received or applied the handoff unless that destination was directly inspected. When new evidence changes an existing handoff, add a dated addendum if the same handoff remains the natural continuity record. Preserve the earlier conclusion and explain why it changed. Do not rewrite history to make the record look consistently correct. ## About Built by [Jamie Hill](https://overkillhill.com) · [OverKill Hill P³](https://overkillhill.com) Published at