skills.rest
TechCorp25
TechCorp25COMMUNITY
Explore all skills by this author →
GitHub

handover

Generates structured Markdown continuation files that let new sessions resume prior work.

Updated May 20, 2026
Search Tags:#git#workflow#documentation#markdown#session continuity#handover#context compaction
One-click install
npx skills add https://github.com/TechCorp25/kingdom --skill handover-techcorp25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/TechCorp25/kingdom/tree/main/.claude/skills/handover
Command: npx skills add https://github.com/TechCorp25/kingdom --skill handover-techcorp25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI-assisted development session ends or its context window fills up, all working knowledge is lost. This Skill produces a detailed handover document so a fresh session can resume the exact same work with zero loss of fidelity, preventing continuity failures before context compaction. ## Core Features & Use Cases - Structured Continuation Files: Generates a Markdown file with mandatory sections covering git state, closed work, open workstreams, verification commands, and the next action. - Git State Verification: Reconstructs the true repository state with commands like git log and git status before recording any SHAs, avoiding stale assumptions. - Supersession Chain: Links each new handover to the prior one via frontmatter, keeping a clean history of session continuity. - Use Case: Before compacting a long coding session in the Kingdom repo, trigger the handover to write docs/<area>/kingdom-continuation-<ISO8601>.md, commit it in isolation, then safely clear context. ## Quick Start Ask the assistant to write a handover file for the current session before compacting the context.

Frequently Asked Questions about handover

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

FAQPage Schema
How do I hand over an AI coding session to a new session?▼

Trigger the handover skill before closing or compacting the session. It writes a Markdown continuation file with git state, closed work, open items, verification commands, and the next action, then commits that file in isolation.

When should I write a session handover document?▼

Write one when a task closes clean, all todos are complete, or before a context compact. Keep 15-20% of the context window in reserve so the file can be written faithfully before compaction occurs.

What should a session continuation file include?▼

It must include frontmatter with supersedes, verified git state with re-verification commands, closed work, open workstreams with next steps, untracked files, copy-paste verification commands, standing rules, and the single next action.

Can I trust git SHAs recorded in an old handover file?▼

No. SHAs are last-observed values, not facts. The handover includes exact commands like git log --oneline -5 and git status -sb so the next session re-verifies the repository state before trusting anything.

Where are handover files stored in a repository?▼

In the Kingdom control plane they go to docs/<project-slug-or-area>/kingdom-continuation-<ISO8601>.md. Tracked projects use their own continuation location, and each new file supersedes the prior one via frontmatter.

Related Skills

Explore More Software Engineering Skills→
manuscomanusco

handover

Writes an end-of-session handover document covering completed work, decisions, and open TODOs.

Community
Basic
garyjgaryj

pickup

Load a handoff file from .claude/handoffs to resume work.

Community
Basic
multica-aimultica-ai
44.9k

multica-working-on-issues

Automate issue-PR contract enforcement and link/close intents across Multica workflows.

Official
Intermediate
spontus-reachspontus-reach
1

handoff

Summarize an ongoing conversation into a compact handoff document.

Official
Basic