skills.rest
doubleflannel
doubleflannelCOMMUNITY
Explore all skills by this author →
GitHub

handoff

Generate an 8-step handoff checklist covering scope, status, and next steps.

Updated Aug 27, 2026
Search Tags:#collaboration#checklist#onboarding#handoff#teams#knowledge-transfer#transition
One-click install
npx skills add https://github.com/doubleflannel/12-30-test-codex-ip --skill handoff-doubleflannel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/doubleflannel/12-30-test-codex-ip/tree/main/skills/handoff
Command: npx skills add https://github.com/doubleflannel/12-30-test-codex-ip --skill handoff-doubleflannel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminate context loss during transitions by providing a structured handoff checklist.

Core Features & Use Cases

  • Scope/status: what you were doing, what’s done, what’s pending, and any blockers.
  • Working tree: git status -sb summary and any local commits not pushed.
  • Branch/PR: current branch, relevant PR number/URL, CI status if known.
  • Running processes: list tmux sessions/panes and how to attach.
  • Tests/checks: which commands were run, results, and what still needs to run.
  • Changelog + docs: mention if CHANGELOG.md or docs were updated and why.
  • Next steps: ordered bullets the next agent should do first.
  • Risks/gotchas: any flaky tests, credentials, feature flags, or brittle areas.

Quick Start

Summarize your current scope, status, blockers, and next steps using the handoff checklist.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I prevent context loss during project handoffs or shift changes?▼

To prevent context loss during project handoffs, you need a structured handoff checklist detailing scope, status, pending tasks, and blockers. This ensures a consistent 8-step framework for seamless transitions.

What is the best way to document running tmux sessions and git status for a knowledge transfer?▼

The best way to document running tmux sessions and git status for knowledge transfer is using a structured checklist that captures your working tree summary, local commits, and pane attachment commands.

How do I create a project handover checklist that includes CI status and branch details?▼

Create a project handover checklist by explicitly listing your current branch, relevant PR number or URL, and known CI status alongside scope and next steps to ensure continuation agents can validate work.

Can I use a standard handoff template for both developer onboarding and shift changes?▼

Yes, you can use a standard handoff template for both developer onboarding and shift changes. The same 8-step framework applies to any transition, detailing processes, risks, and next steps in a shareable format.

What should I include in an agent handoff checklist to cover risks and gotchas?▼

An agent handoff checklist should include risks and gotchas by listing flaky tests, credentials, feature flags, and brittle areas. This ensures the next agent knows exactly what to validate before continuing.

Related Skills

Explore More Content & Communication Skills→
elithrarelithrar
190

summarize-work

Analyze session history and git state to generate structured commit-message summaries.

Community
Basic
darkroomengineeringdarkroomengineering
41

resume-handoff

Load previous session state, progress, and decisions to resume work.

Official
Intermediate
marchattonmarchatton
5

handoff

Persist a handoff checklist as a git-tracked Markdown note.

Community
Intermediate
terakoya76terakoya76

explain-code

Explain code snippets with structured analysis of logic and data flow.

Community
Advanced