handoff-context

Compacts a conversation into a resumable handoff document with decisions, state, and next action.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill handoff-context-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff-context
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/handoff-context
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill handoff-context-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a session ends or context runs low, the next agent or future-you loses everything that was decided and must re-read the entire conversation to continue. This Skill compacts a live conversation into a structured handoff document carrying decisions, current state, open threads, and the single next action — never a transcript dump. ## Core Features & Use Cases - Mode-switchable output: A 3-line quick handoff for warm same-thread continuations, or a full state dump aligned to the ARIA Hub session-report schema for cold handoffs to fresh agents. - Carry-forward discipline: Extracts decisions with one-line reasoning, snapshots state by reference (linking specs, ADRs, commits, and diffs by path), marks claims as verified or unverified, and redacts secrets before saving. - Registry-aware filing: Saves full handoffs to aria/projects/{project_id}/reports/ so they feed the Hub registry, and pre-routes the continuation with suggested skills. - Use Case: At the end of a debugging session, ask for a handoff and receive a Markdown document naming the one decision made, the verified/unverified state split, the open thread with its next step, and the single first action the next agent should take. ## Quick Start Ask the agent to write a handoff for this session so a fresh agent can pick up the work tomorrow.

Frequently Asked Questions about handoff-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off work to another AI agent between sessions?

Write a handoff document containing decisions with one-line reasoning, a state snapshot linking artifacts by path, open threads with next steps, and one concrete next action. Avoid pasting the conversation transcript, which forces the next agent to re-derive everything.

What should a session handoff document include?

Include a summary, decisions made with reasoning, current state (branch, files touched, what is verified versus unverified), open threads with next steps, blockers, the single next action, and suggested skills for the continuation. Mark empty fields as None rather than inventing content.

When should I use a quick handoff versus a full state dump?

Use a quick 3-line handoff for warm same-thread continuations where the receiver shares your context. Use the full schema for cold handoffs to fresh agents, cross-domain passes, or anything filed into a shared reports registry. When unsure, choose full.

Can a handoff document replace a decision record?

No. A handoff links to durable decision records by path rather than reproducing them. If a choice deserves a permanent record with a What Would Change This section, author a dedicated decision record and reference it from the handoff.

Why should handoffs avoid pasting the conversation transcript?

Transcript dumps bury decisions and open threads in narration, forcing the next agent to re-read everything and blurring verified claims with unverified ones. A structured handoff surfaces the decision, the state split, and the next action so work resumes cold.