/offboard

Capture orchestrator-session state into a persistent handoff note and commit it to git.

8|1|Updated Jan 21, 2024

Search Tags:#git commit #session handoff #bash automation #token cost #context compaction #orchestrator state

Ready to run

npx skills add https://github.com/azigler/dotfiles --skill offboard-azigler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: /offboard
Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/offboard
Command: npx skills add https://github.com/azigler/dotfiles --skill offboard-azigler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents lost context at the end of an orchestrator session by producing a durable handoff note (and optional cost log) before compaction or handover.

Core Features & Use Cases

Writes a session handoff snapshot to .claude/plans/session-handoff.md, including branch, last commit, bead status, dirty files, and in-flight subagents.
Optionally computes orchestrator token cost by reading session JSONL and updating .claude/plans/cost-tracking.md via the global /cost-tracking compute script (with an edge-case jq fallback described in the skill).
Cleans up and commits the handoff by clearing .offboard-pending, committing the updated plans, and pushing to the remote.

Quick Start

Run the /offboard skill at the natural end of an orchestrator session so it writes the session handoff note (and logs cost if enabled) before context compaction.

Frequently Asked Questions about /offboard

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

FAQPage Schema

How do I preserve orchestrator session state before context compaction truncates my working memory?▼

Capturing orchestrator session state into a persistent handoff note preserves branch details, last commits, bead status, dirty files, and in-flight subagents before context auto-compaction clears your working memory.

What is the best way to hand off an active development session to another developer?▼

Writing a session handoff snapshot to `.claude/plans/session-handoff.md`, clearing pending states, and committing the results to git provides a clean, durable transfer of orchestrator session ownership to another person.

How do I track and log orchestrator token cost at the end of a coding session?▼

Computing orchestrator token cost involves reading session JSONL files and updating `.claude/plans/cost-tracking.md` via a compute script, with a jq fallback for edge cases, to maintain cost continuity across sessions.

Can I record session handoff notes inside subagent worktrees?▼

Session handoff explicitly detects and skips subagent worktrees, applying only to primary orchestrator sessions to prevent duplicate or irrelevant state snapshots from being committed to your git history.

When should I run a session handoff capture for my development workflow?▼

Session handoff should run at the natural end of an orchestrator session, before context auto-compaction triggers, or when handing off ownership to another person to prevent lost context.

Does session handoff automatically commit the captured state to git?▼

Session handoff cleans up by clearing `.offboard-pending`, committing the updated `.claude/plans/` files, and pushing the results to the remote repository to ensure durable state persistence.