How do I install the Ce Handoff skill?

Run npx skillmds@latest add sitaggart/ce-handoff in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ce Handoff safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ce Handoff?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ce Handoff free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ce Handoff?

SiTaggart (@sitaggart) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ce Handoff by sitaggart — Agent Skill

Name: Ce Handoff
Rating: 4.5 (4 reviews)
Author: SiTaggart

Ce Handoff

Compact the current conversation into a durable handoff document for another agent or future session. Use when the user asks to hand off, pause with context, summarize work for the next session, or prepare a continuation brief.

SiTaggart Updated Sep 10, 2026

File contents

Handoff

Write a compact continuation brief so a fresh agent can pick up the work without reconstructing the session.

Input

#$ARGUMENTS

If <handoff_focus> is present, treat it as the next session's intended focus. If it is blank, infer the focus from the current conversation and current checkout state.

Contract

The output is one markdown file that preserves decision context, current state, and the next useful move. It should reduce steering in the next session.

Do not duplicate content already captured in canonical artifacts (PRDs, plans, ADRs, issues, PRs, commits, review reports, diffs) — reference them by path, URL, branch, commit, or command instead. Keep the business reason and changed product contract visible, prefer exact paths and verification evidence over prose memory, mark uncertainty explicitly instead of smoothing it over, and suggest only the skills that should actually be used next.

Destination

Write to .ai/handoffs/YYYY-MM-DD-<topic>-handoff.md at the workspace root (repo root when inside a git repo; create the directory if needed; if the path exists, update it only when it is clearly the same handoff). Use an OS temp file only when there is no sensible workspace-local home, and say why.

Context Scan

Gather only the context a useful handoff needs — repo state, matching .ai/ artifacts, referenced docs and PRs — and above all the latest user correction or scope boundary that the next session must not lose.

Document Shape

Use this structure unless the task clearly needs a smaller one:

---
created: YYYY-MM-DD
status: ready|paused|blocked
focus: <next-session focus>
repo: <repo name or path>
branch: <branch if known>
---

# Handoff: <topic>

## Next Session Goal

<The one outcome the next agent should drive toward.>

## Business / Contract Frame

- Business reason:
- Contract being changed or protected:
- Scope boundaries:

## Current State

- What is already done:
- What is partially done:
- What is not started:

## Key Decisions

- <Decision, rationale, and source path/URL if one exists.>

## Files And Artifacts To Read

- `<path or URL>` - why it matters

## Remaining Work

1. <Concrete next step.>
2. <Concrete next step.>

## Verification

- Passed:
- Not run:
- Blocked:

## Risks / Open Questions

- <Only real blockers, uncertainties, or traps.>

## Suggested Skills

- `<skill-name>` - why this is the right next tool

## Starter Prompt

<A short prompt the next session can use verbatim.>

For a tiny handoff, keep only Next Session Goal, Current State, Remaining Work, Verification, Suggested Skills, and Starter Prompt.

Quality Bar

Read the written file back. The bar: the next session must be able to start without asking "what happened?"

Final Response

Keep the user-facing response brief:

Handoff written: <absolute path>
Status: <ready|paused|blocked>
Best next skill: <skill or "none">

---name: ce-handoffdescription: Compact the current conversation into a durable handoff document for another agent or future session. Use when the user asks to hand off, pause with context, summarize work for the next session, or prepare a continuation brief.---# HandoffWrite a compact continuation brief so a fresh agent can pick up the work withoutreconstructing the session.## Input<handoff_focus> #$ARGUMENTS </handoff_focus>If `<handoff_focus>` is present, treat it as the next session's intended focus.If it is blank, infer the focus from the current conversation and currentcheckout state.## ContractThe output is one markdown file that preserves decision context, current state,and the next useful move. It should reduce steering in the next session.Do not duplicate content already captured in canonical artifacts (PRDs, plans,ADRs, issues, PRs, commits, review reports, diffs) — reference them by path,URL, branch, commit, or command instead. Keep the business reason and changedproduct contract visible, prefer exact paths and verification evidence overprose memory, mark uncertainty explicitly instead of smoothing it over, andsuggest only the skills that should actually be used next.## DestinationWrite to `.ai/handoffs/YYYY-MM-DD-<topic>-handoff.md` at the workspace root(repo root when inside a git repo; create the directory if needed; if the pathexists, update it only when it is clearly the same handoff). Use an OS tempfile only when there is no sensible workspace-local home, and say why.## Context ScanGather only the context a useful handoff needs — repo state, matching `.ai/`artifacts, referenced docs and PRs — and above all **the latest usercorrection or scope boundary that the next session must not lose**.## Document ShapeUse this structure unless the task clearly needs a smaller one:```markdown---created: YYYY-MM-DDstatus: ready|paused|blockedfocus: <next-session focus>repo: <repo name or path>branch: <branch if known>---# Handoff: <topic>## Next Session Goal<The one outcome the next agent should drive toward.>## Business / Contract Frame- Business reason:- Contract being changed or protected:- Scope boundaries:## Current State- What is already done:- What is partially done:- What is not started:## Key Decisions- <Decision, rationale, and source path/URL if one exists.>## Files And Artifacts To Read- `<path or URL>` - why it matters## Remaining Work1. <Concrete next step.>2. <Concrete next step.>## Verification- Passed:- Not run:- Blocked:## Risks / Open Questions- <Only real blockers, uncertainties, or traps.>## Suggested Skills- `<skill-name>` - why this is the right next tool## Starter Prompt<A short prompt the next session can use verbatim.>```For a tiny handoff, keep only `Next Session Goal`, `Current State`,`Remaining Work`, `Verification`, `Suggested Skills`, and `Starter Prompt`.## Quality BarRead the written file back. The bar: the next session must be able to startwithout asking "what happened?"## Final ResponseKeep the user-facing response brief:```textHandoff written: <absolute path>Status: <ready|paused|blocked>Best next skill: <skill or "none">```

Frequently asked questions