agentleFS
Sign inStart free
gjoranvgjoranv/claude-plan-skills/handover/SKILL.md

handover

Skill5 starsChanged 51 days agoMITView on GitHub

Prepare a handover for continuing work in a new session. Use when the user asks to "hand over", "prepare handover", "wrap up for a new session", or "context dump".

51 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use harness-init, incident and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • steptianSkill

    harness-init

    初始化 .harness 开发框架，集成代码修改影响范围评估和测试覆盖建议功能。触发词：'初始化新项目'、'harness init'、'更新 harness'、'分析影响范围'、'评估修改影响'

    Also in 3 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

  • GoogleSkill

    to-tickets

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • MicrosoftSkill

    caveman

    Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Offer to persist state: before handing over:

    line 17
  2. Very specific:

    Update the plan issue (/gh-update-plan)

    line 18
  3. Distinctive:

    Ask the user which of these to do.

    line 20
  4. Distinctive:

    Keep the handover prompt concise.

    line 35
  5. Distinctive:

    Do not include implementation details the plan issue already captures.

    line 36
  6. Distinctive:

    If there's no plan issue, still generate a useful handover prompt with the repo, branch, and summary.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Prepare everything needed for a new conversation to continue the current work seamlessly.

  1. Gather state:
    • Current repo and branch
    • Uncommitted changes (git status, git diff --stat)
    • Recent commits on this branch
    • The plan issue (from argument, or the one referenced earlier in this conversation, or ask the user)
  2. Summarize the session: What was done, key decisions made, what's still in progress, any blockers or open questions.
  3. Offer to persist state before handing over:
    • Update the plan issue (/gh-update-plan)
    • Commit uncommitted changes Ask the user which of these to do. Skip any already done.

  4. Capture learnings: Review the conversation for surprises, gotchas, corrections, and non-obvious decisions. Propose where each belongs:

    • Instructions file (CLAUDE.md, AGENTS.md, or similar): conventions, build quirks
    • Repo docs: architecture insights, design rationale
    • Agent memory: cross-project patterns, user preferences

    User approves, edits, or drops each suggestion.

  5. Generate a handover prompt that the user can paste into a new session. Include:
    • The plan issue reference (e.g. /gh-read-plan owner/repo#12)
    • The repo and branch to work in
    • A 3-5 sentence summary of where things left off
    • The specific next step to work on
    • Any gotchas or context the new session needs (e.g. "the tests pass locally but CI needs a config change first")

Rules:

  • Keep the handover prompt concise. It should be copy-pasteable in one go.
  • Do not include implementation details the plan issue already captures.
  • If there's no plan issue, still generate a useful handover prompt with the repo, branch, and summary.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free