Skills · Workflow

WorkflowSkillDugout-created

/handoff

Writes a handoff note so your next AI session picks up without re-explaining.

Created by Piyush Baheti · Source: piyush-tkd/skillsdugout/tree/main/plugins/handoff

Who it is for

Anyone who runs long AI sessions on one piece of work and loses context between them.

Started as a note we kept retyping at the end of long sessions. Now it writes itself.

When to use it

  • A session is getting long or slow and you want to start fresh without losing the thread.
  • You are switching to another task and will come back later.
  • Someone else, or another agent, will continue the work.

Example

You ask

Write a handoff. I'm switching to the billing bug and will come back to this tomorrow.

It writes HANDOFF.md

Handoff — 2026-10-03 — Add retry to payment webhook

Goal

Webhook retries failed deliveries 3 times with backoff.

State

  • Done: retry wrapper in src/webhooks/retry.ts
  • In progress: backoff config in src/config/webhooks.ts (delay not wired)
  • Not started: alert when all retries fail

Decisions

  • Exponential backoff, max 3 tries — matches provider limits

Next action

Wire WEBHOOK_BACKOFF_MS into retry.ts and run the webhook tests.

Verify

npm test -- webhooks

Output is Markdown (.md), shown formatted.

Evidence

Our test

No baseline test yet. We will publish one, with and without the skill, when testing is done.

Reported by the community, by app

Claude Code: Tested
No outcomes reported yet
Claude apps: Not tested
No outcomes reported yet
Cursor: Not tested
No outcomes reported yet
Codex: Not tested
No outcomes reported yet
GitHub Copilot: Not tested
No outcomes reported yet

Compatibility labels come from our tests only. Community reports add detail but cannot mark an app as tested.

Editorial assessment · not a community rating

Editorial review in progress

We have not finished testing this listing against doing the task without it. The verdict appears here when we have. Our team made this skill; it gets the same test as external work.

How we review

Setup and customization

  • Works with no setup after install.
  • Writes HANDOFF.md in the project folder; add it to .gitignore if you do not want it committed.
  • Say "resume" in a new session to pick up from the note.

What it can access

Reads
The current conversation; Files already open in the session
Changes
Creates or overwrites HANDOFF.md in the project folder

Install

Claude Code: Tested
  1. Add the Skills Dugout marketplace once.
    /plugin marketplace add piyush-tkd/skillsdugout
  2. Install /handoff.
    /plugin install handoff@skillsdugout
  3. Start a new session and ask for it, for example "write a handoff".

Community reviews

No reviews yet. Be the first to rate it after you try it.

Each review records the app, version, task and outcome; those outcomes feed the Evidence section. One rating per person; creators reply but cannot rate their own work.

No reviews yet. Be the first to rate it after you try it.

Source, license and versions

Source
github.com/piyush-tkd/skillsdugout/tree/main/plugins/handoff
License
MIT, as stated in the repository
  • 0.1.0 · 2026-10-03 · First release.
Show the full skill instructions

Handoff

Compress the current session into one file a fresh session can act on immediately.

Steps

  1. Write HANDOFF.md in the project root (overwrite any existing one).
  2. Use exactly the sections below. Skip a section only if it is truly empty.
  3. Keep it under 60 lines. Facts and paths only; no narrative.
  4. Reply with one line: the file path and the single next action.

Template

# Handoff — <YYYY-MM-DD> — <task in 5–8 words>

## Goal
<one sentence: what done looks like>

## State
- Done: <completed items, with file paths>
- In progress: <item, exact file and function>
- Not started: <remaining items>

## Decisions
- <decision> — <one-line reason>

## Open questions
- <question> — <who decides>

## Gotchas
- <thing that broke or misled; how it was resolved>

## Next action
<one concrete step the next session should take first>

## Verify
<command or check that proves the work is correct>

Rules

  • Record decisions the user made, not suggestions they did not adopt.
  • Reference files by path; never paste large code blocks.
  • Mark anything unverified as (unverified).
  • Do not include secrets, tokens, or personal data.

Resuming

When a session starts and HANDOFF.md exists, and the user says "continue", "resume" or "pick up": read it first, confirm the next action in one line, then do it.