handoff

Writes dated end-of-slice handoff blocks and kickoff lines into build docs.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/line7works/tony-skills --skill handoff-line7works
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/line7works/tony-skills/tree/main/plugins/handoff/skills/handoff
Command: npx skills add https://github.com/line7works/tony-skills --skill handoff-line7works

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Claude Code thread is cleared at the end of a build slice, everything the session knew — unanswered questions, rulings, workarounds, repo state — is destroyed. This Skill captures that perishable context into the build doc and memory before the thread is cleared, so the next session cold-starts with an exact kickoff line instead of guesswork. ## Core Features & Use Cases - Question gate: Collects unanswered questions from signoff/recheck outputs, chat rulings, and slice ambiguity, and pauses the run until they are answered — nothing is written before the gate resolves. - Ledger recording: Appends dated WAIVED/REOPENED lines to the punch-list ledger and updates slice status cards according to the loop's verdict rules. - Repo photograph: Verifies branch, commits ahead of main, and working-tree state against git in real time, creating a local checkpoint commit for loose work. - Handoff block and memory pointer: Writes one dated handoff block per run into the build doc and maintains a single superseding auto-memory file per feature with the exact kickoff line. - Use Case: After finishing slice 3 of a feature build, invoke /handoff to record open questions, checkpoint uncommitted work, and receive the exact /ship slice-4 docs/plans/... line to type in the fresh session. ## Quick Start Run /handoff after finishing a build slice to record the session state and get the kickoff line for the next session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve context before clearing a Claude Code thread?

Invoke /handoff before running /clear. It records unanswered questions, repo state, and perishable session notes into a dated block in the build doc, then gives you the exact kickoff line to type in the fresh session.

How does the handoff question gate work?

The gate collects unanswered questions from signoff/recheck outputs, chat-only rulings, and next-slice ambiguity, then pauses before any write. If any question stays unanswered, the run ends with nothing written and the thread is reported as not safe to clear.

Does handoff push commits or open pull requests?

No. It only creates a local checkpoint commit for loose working-tree changes. Pushing, opening PRs, and merging remain manual git gates that are never performed by the skill.

When should I not use the handoff skill?

Do not use it for machine or terminal settle-up (that is /shutdown) or for cross-machine hand-offs between computers (that is the claude-relay protocol). It is strictly for end-of-slice thread prep within the build loop.

What happens if a build slice still has open BLOCKER findings?

Open BLOCKERs or MAJORs do not stop the handoff run. Instead, the kickoff line becomes the fix list — the open items followed by /recheck — rather than a clean /ship of the next slice.