agentleFS
Sign inStart free
ariaxhanariaxhan/kernel-claude/skills/handoff/SKILL.md

handoff

Skill15 starsChanged 4 months agoMITView on GitHub

Save provenance, decisions, phases, context policy, and next steps as kernel.handoff/v1. Triggers: handoff, save, pause, context, continue later.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-mapping, setup-ts-deep-modules and 10 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.
  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 8 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 93 projects that use this

  • GoogleSkill

    ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 87 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 51 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 54 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 3

    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:

    Use AskUserQuestion when: state extraction complete, before writing the manifest Ask: "Anything to add to the handoff?

    line 63
  2. Distinctive:

    Ask: "Anything to add to the handoff?

    line 64
  3. Very specific:

    Write _meta/handoffs/{name}-{date}.json conforming to schemas/kernel.handoff.v1.schema.json.

    line 74
  4. Distinctive:

    Commit: "docs: handoff manifest for {name}"

    line 107

“Common” is measured: kept by at least 6 in 10 of the 172 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
<skill id="handoff"><purpose> Compile the current task into an authoritative, resumable JSON manifest. The JSON file is CANONICAL. A markdown rendering may be generated for humans but is never a second source of truth.

Why manifest-first + bounded (EXP-L21): what a decision needs is flat (~50-70k tokens) regardless of session length; the accumulating transcript is almost pure decoration by late session. A handoff that says "read the conversation" recreates the waste. A handoff that pins exact selectors + phases lets the next session reconstruct ONLY the load-bearing state.

Reference: skills/context-mgmt/SKILL.md </purpose>

<on_start>

agentdb read-start

</on_start>

<phase id="1_extract" name="EXTRACT STATE"> Capture (these become manifest sections, not prose): - objective: goal, success_conditions (observable), non_goals - contract: governing _meta/contracts/ file if one exists, invariants, assumptions, decisions_accepted (+rationale), alternatives_rejected (+reason, REQUIRED by the schema even when empty) — every idea the user or you ruled out this session, so the next session never re-proposes it - workflow.phases: name each phase of the work; status inherited (done, with evidence) | required (still to do). Add invalidation_rules: what live-state change would flip an inherited phase back to required. Rules use typed `when.event` plus optional `when.path_glob`; never prose trigger strings. - open_threads, warnings (failed approaches — never re-explore silently) - tier (1/2/3) in identity </phase><phase id="2_gather" name="GATHER EVIDENCE"> ```bash git branch --show-current && git rev-parse HEAD && git status --short git log --oneline -10 agentdb query "SELECT * FROM context WHERE type IN ('contract','checkpoint') ORDER BY ts DESC LIMIT 5" ``` Pin artifacts: for each file the next session must trust unchanged, `shasum -a 256 <path>` → provenance.artifacts[{path, sha256, purpose}]. </phase>

<ask_user> Use AskUserQuestion when: state extraction complete, before writing the manifest Ask: "Anything to add to the handoff? Blockers, decisions, or context I might have missed?" Options: looks complete, add context, skip handoff </ask_user>

<phase id="3_hygiene" name="GIT HYGIENE"> uncommitted: commit with "wip: checkpoint before handoff" or stash (document it) push: push current branch to remote — a local-only handoff is stranded work </phase><phase id="4_compile" name="COMPILE THE MANIFEST"> Write `_meta/handoffs/{name}-{date}.json` conforming to schemas/kernel.handoff.v1.schema.json.

Context section — the attention budget is the design center:

  • policy.mode: advisory (default) | bounded (extra loads must be justified + ledgered) | sealed (forbidden globs hook-blocked; for controlled experiments)
  • required: SELECTORS, not whole files, wherever a section suffices: {path, heading: "## X"} · {path, lines: "A-B"} · {path, grep: "pat", context: N} · {git_diff: "revA..revB"} — each with a reason
  • forbidden: globs the resume must NOT touch (sealed mode enforces via guard-context hook)
  • budget: target_tokens (aim: boot + manifest + 2-12k selected history, per EXP-L21), max_tokens (hard stop)

Execution section: entry_phase, entrypoint (the literal first operation), stop_conditions, checkpoints (when to emit kernel.checkpoint/v1 during the resumed work).

Resume section: one-line continuation prompt: /kernel:ingest resume from _meta/handoffs/{file}.json

JSON strings are always quoted, so sha/commit fields cannot type-drift (the old YAML fails validation). </phase>

<phase id="5_validate" name="VALIDATE — MANDATORY"> ```bash "${CLAUDE_PLUGIN_ROOT:-.}/orchestration/manifest/kernel-manifest" validate _meta/handoffs/{file}.json ``` A handoff that does not validate DOES NOT EXIST. Fix and re-validate before reporting done. Optional human rendering: a .md next to it, first line `# RENDERED FROM {file}.json — NOT AUTHORITATIVE`. </phase><delivery> 1. `kernel-manifest validate` passes (above) 2. Commit: "docs: handoff manifest for {name}" 3. Push to remote </delivery>

<on_complete>

agentdb write-end '{"skill":"handoff","saved_to":"_meta/handoffs/{file}.json","branch":"X","tier":N}'
# If non-local profile: post handoff summary to GitHub Discussions (Agent Logs category)
# Suggest /kernel:retrospective if learnings accumulated across sessions

</on_complete>

</skill>

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