AGENT SKILL

handoff

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

License 许可
Apache-2.0
最近更新
2026-11-14
Stars
★ 1.6k
Forks
491

01 前言 Front Matter

name
handoff
kernel
{ "kind": "state_transition", "version": 2, "produces": [ "kernel.handoff/v1" ], "confirmation": "none", "side_effects": "writes_meta" }
description
Save provenance, decisions, phases, context policy, and next steps as kernel.handoff/v1. Triggers: handoff, save, pause, context, continue later.
allowed-tools
Read, Bash, Grep, Glob, Write
user-invocable
true

03 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">

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">

"${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>

04 同仓库更多 Skills

hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-review-with-annotations

Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-find-and-synthesize-context

Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-update-docs

Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-records

Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-interactive-html

Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-collaborate-threads

Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.

★ 1.6k