handoff
Writes a HANDOFF.md plus a pasteable prompt to continue in a new session.
Skill by stage2dev
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/stage2dev-handoff
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/handoff
Tools it pre-approves 4
From allowed-tools in SKILL.md: the agent may use these without asking you each time.
Bash(sh"${CLAUDE_PLUGIN_ROOT}/scripts/py"scripts/guarda.pyinfo)
What's inside
- Skill name
handoff- Description
- Writes a HANDOFF.md plus a pasteable prompt to continue in a new session. Use on: continue in new session, handoff, context is big, I will compact; prompt para continuar, nova sessão, vou compactar.
- License
- MIT
- Allowed tools
- Bash(sh, "${CLAUDE_PLUGIN_ROOT}/scripts/py", scripts/guarda.py, info)
- Instructions
- 40 lines in SKILL.md · view on GitHub
Before installing
- Pre-approves some shell commands
Files (1)
- SKILL.md
SKILL.md (first lines)
# Handoff to a new session
Focus: $ARGUMENTS
## Context (injected)
Context: !`sh "${CLAUDE_PLUGIN_ROOT}/scripts/py" scripts/guarda.py info`
Fields: `language`, `owner`, `reply_style`, `names{}`, `models{}`, `forbidden_subagent_models` (default `["fable"]`), `profile_path`, `plans_dir`, `setup_done`, `tools`, `plugin_source`, `catalog_path`. Write every reply and document in `language`. Never hardcode marker or document names: use the values in `names` (keys such as `need_you`, `progress`, `part_closed`). Call the user `owner`. If the JSON did not load, run the command once with Bash.
The new text must stand alone: whoever opens it has not read this conversation.
## Steps
1. **Verify the real state**, not from memory: `git branch --show-current`, `git status --short`, `git fetch`, hash of `origin/<main branch>`, `gh pr list --author @me --state open`, migrations applied or pending (per the project profile at `profile_path`), agents still running.
2. **Write `HANDOFF.md`** in the active phase folder under `plans_dir` (or in the scratchpad if there is no phase), in `language`, with:
- Goal in 1 sentence.
- Verified state: branch, PRs (number + state), migrations, what is committed and what is not.
- Files to read: the goal, progress (`names.progress`) and handoff files. Nothing else; the rest is a point lookup.
- The EXACT next step (command or action) and whose it is (owner or Claude).
- Pitfalls of this session: what nearly went wrong, what was discarded, "do NOT re-investigate X".
- What is left to decide (numbered questions, recommended one marked).
3. **Pasteable block** in the reply, short, in a code block: the opening prompt of the new session pointing at `HANDOFF.md` by absolute path, plus a `/goal` command with an exit condition of ONE Part:
`/goal <goal of the Part> - finish when the Part is closed in the progress file (marker: names.part_closed) OR when you write names.need_you OR after 40 turns`
4. Update the progress file and the phase memory if they changed in this session.
## Rules
- Never paste a secret, token, password or customer personal data into the HANDOFF or the block.
- Do not invent: if something was not verified, write "not verified".
- Do not summarize the whole conversation. Only what is needed to continue.
- Anything that depends on the owner goes under `names.need_you` at the top of the HANDOFF.
## Answer
Absolute path of `HANDOFF.md` + the pasteable block. Nothing else.From stage2dev/tune-up, MIT.
More from stage2dev/tune-up
- 0.567score
setup
stage2dev
First-run setup of tune-up - language, owner, reply style, kinds of use, user.json, optional tools (gh, claude-mem, fast-jev, Caveman, Ponytail, Graphify, ECC).
SkillAFreshness: AClaude Code +9 - 0.567score
design
stage2dev
Builds the design system (DESIGN.md with tokens) and a static HTML prototype made from it.
SkillAFreshness: AClaude Code +9 - 0.561score
evaluate
stage2dev
Evaluates a third-party repo, skill or plugin before importing it.
SkillAFreshness: AClaude Code +9 - 0.561score
investigate
stage2dev
Investigates a bug, pasted error, "stopped answering", failed booking or customer conversation.
SkillAFreshness: AClaude Code +9 - 0.561score
learn
stage2dev
Records a new rule in memory, project or user rules (or the plugin source, if set).
SkillAFreshness: AClaude Code +9 - 0.561score
migration
stage2dev
Applies a database migration/SQL to production with a safe protocol.
SkillAFreshness: AClaude Code +9 - 0.561score
new-project
stage2dev
Creates a new project folder with git, docs, plans, tests, CI and agent rules from the talk's vision; the user picks the stack.
SkillAFreshness: AClaude Code +9 - 0.561score
part
stage2dev
Runs ONE Part of an already planned phase item by item, with Opus reviewers and a gate, then STOPS.
SkillAFreshness: AClaude Code +9 - 0.561score
profile
stage2dev
Creates or updates the project profile (.tune-up/project.md and config.json) by detecting git, stack, tests, database and deploy.
SkillAFreshness: AClaude Code +9 - 0.561score
research
stage2dev
Research that changes NOTHING.
SkillAFreshness: AClaude Code +9 - 0.561score
ship
stage2dev
Commits and opens the PR with an honest body.
SkillAFreshness: AClaude Code +9 - 0.561score
skills
stage2dev
Finds the right skill for a task in the tune-up skills catalog and loads only that one.
SkillAFreshness: AClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 20, 2026 (8 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/stage2dev/tune-up
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from stage2dev
- 0.567score
design
stage2dev
Builds the design system (DESIGN.md with tokens) and a static HTML prototype made from it.
SkillAFreshness: AClaude Code +9 - 0.567score
setup
stage2dev
First-run setup of tune-up - language, owner, reply style, kinds of use, user.json, optional tools (gh, claude-mem, fast-jev, Caveman, Ponytail, Graphify, ECC).
SkillAFreshness: AClaude Code +9 - 0.561score
learn
stage2dev
Records a new rule in memory, project or user rules (or the plugin source, if set).
SkillAFreshness: AClaude Code +9 - 0.561score
investigate
stage2dev
Investigates a bug, pasted error, "stopped answering", failed booking or customer conversation.
SkillAFreshness: AClaude Code +9 - 0.561score
evaluate
stage2dev
Evaluates a third-party repo, skill or plugin before importing it.
SkillAFreshness: AClaude Code +9 - 0.561score
talk
stage2dev
Talk mode - interview, brainstorm and persona debate that turns an idea into project documents, no code.
SkillAFreshness: AClaude Code +9
Cite this page
handoff skill. Agent Mart. https://agentmart.dev/skills/stage2dev-handoff (last updated 2026-10-24)