AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Task Handoff

skill-aberson-claude-skills-task-handoff · by aberson

Checkpoint library — orchestrators call this (build-phase, build-step, plan-expedite, user-draft); operators usually want /session-wrap. Modes: --loop [--no-commit] (write current.md), --next-task [label] (durable task-boundary save), --resume (read current.md + orient), --end (delegates to /session-wrap).

— No reviews yet
0 installs
36 views
0.0% view→install

Install

$ agentstack add skill-aberson-claude-skills-task-handoff

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-aberson-claude-skills-task-handoff)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Task Handoff? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

task-handoff

Checkpoint library for current.md writes and reads. Its callers are orchestrating skills — build-phase, build-step, plan-expedite, user-draft — that need a durable checkpoint or an in-window resume. Operators wanting a session transition should use /session-wrap. Bare /task-handoff (no flag) defaults to --resume.

current.md contract: file format, field definitions, overwrite-vs-append rules, path resolution, staleness, and lifecycle are owned by .claude/references/task-state-schema.md (workspace reference, not published in this mirror) — follow it for every read and write. Safety-critical minimum: resolve the path via git rev-parse --show-toplevel, never cwd-relative (worktree writes are deleted on cleanup).

None of these modes emits /compact or /clear — auto-compaction plus the SessionStart re-inject hook handle context in-window (CLAUDE.md § Session wrap & commit discipline).


--loop — checkpoint write

Cost: ~5 seconds, no user interaction. Output one line: "Checkpoint written."

Read-merge-write current.md — read the existing file first, then apply the schema doc's per-field append-vs-overwrite rules (it owns that split; do not re-derive it here). Then commit: chore: task-state checkpoint [task] [status].

Callers invoke it after each meaningful action — tests pass, a hypothesis is ruled out, before a new iteration. It should feel nearly zero-cost.

--loop --no-commit — same write, NO git commit. Required inside build-phase: its Step 2e checkpoint commit picks up current.md, so a separate commit here would double-commit and break 2d/2e race detection (which compares HEAD against origin before committing).


--next-task [label] — task-boundary save

Cost: ~30 seconds. Durable boundary write when switching tasks within the same goal (e.g. plan-expedite → build-phase): the same read-merge-write as --loop — the finished task's entries land in Completed (append); WIP, Next Action, and Status are overwritten to point at the next task ([label]) — plus a MEMORY.md update, commit, and push.

Then keep working in-window. No manual /compact is needed to cross a task boundary. If a deliberate focused reset is genuinely wanted (not the default), emit a /compact [focus] line for the user to type — /compact has no programmatic trigger.


--resume — in-window orient

Reads current.md (path per the schema doc) plus git state and outputs an orientation block — no window switch. Use after a compaction or /clear.

Resuming [Task field]: [Status]
[Next Action field verbatim]

Then proceed with the next action — do NOT ask for confirmation.


--end — true session end

Delegates to /session-wrap, which triages.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.