Handoff

Skill byerlikaya/claude-starter-kit/claude-starter/skills/handoff

Enterprise engineering workflow for Claude Code — not just prompts. AI agents that plan, build, audit, and ship with security gates, privacy checks, and approval-controlled commits. Safely adopt it into new or existing repositories.

Install

npx -y skills add byerlikaya/claude-starter-kit --skill handoff

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Session handover: when context fills, a phase closes, or the topic changes, write an action-oriented handover to docs/SESSION_STATE.md, then recommend /clear. Trigger phrases: "handoff", "hand off", "session summary", "session state", "clear context", "I'll continue"

SKILL.md

1.6 KB, as published. Nobody here has run it

Session Handover (Handoff)

When

/context > 75% · phase closure · topic change. Goal: the next session should not start from scratch.

Output (docs/SESSION_STATE.md, local)

# Session Handover — <date>
## Done
- <completed work + which files>
## In progress
- <what's half-finished + exactly where it was left off>
## Next step
- <a clear, single high-value step>
## Open decisions
- <pending decision + options>
## File pointers
- docs/PLAN.md, relevant modules...
## Blockers / risks
- <if any>

Principles

Action-oriented: focused not on "what was done" but on "exactly where to resume now."
Preserve the rationale behind decisions (why this path was chosen) — so context isn't lost.
Once written, start a fresh session with /clear.

Redaction (`<private>` marker)

docs/SESSION_STATE.md is a shared, often committed artifact — never persist a secret, token, credential, or personal note into it. Any content wrapped in <private>…</private> is a redaction marker: strip it from the written handover and leave a [redacted] placeholder in its place. If a resume genuinely needs a sensitive value, point to where it lives (env var, secret manager, the person to ask) — never the value itself.

DoD

A handover file; a new session can resume where it left off by reading only this file.