mtk-agent-toolkit: Skill for Claude Code

Handoff

Current Session State

echo "--- Branch ---"
git branch --show-current 2>/dev/null || echo "(detached)"
echo "--- Uncommitted changes ---"
git status --short 2>/dev/null | head -20 || echo "(not a git repo)"
echo "--- Recent commits (this branch) ---"
git log --oneline -5 2>/dev/null || echo "(no commits)"

Overview

A handoff captures the current session state — branch, in-progress work, decisions, blockers, and key files — into a small markdown artifact so the next session (yours after compaction, a new conversation tomorrow, or a teammate) can resume without re-discovering the context. The artifact is a pointer, not a transcript: it tells the next reader where to look, not what every step was.

When To Use

• Context is approaching its limit and compaction is imminent — including when the context-budget hook nudges that the session is past MTK_CONTEXT_BUDGET_PCT% (default 60) of the window: reset deliberately before quality degrades rather than riding it to compaction
• Ending a long session that has unfinished, non-trivial work
• Handing off to a teammate who will continue the work
• Switching branches or features mid-stream and the current state needs to survive
• The user explicitly asks to "save state", "snapshot", or "hand off"

When NOT To Use

• Short sessions where the next session can re-derive everything from git status + the last commit
• Work that is fully committed with a clear commit message — the commit IS the handoff
• Trivial or exploratory work where there is nothing meaningful to resume
• Already produced a handoff in this session and nothing material has changed since

Workflow

1. Gather state. Collect the facts that the next reader will need:
   • Current branch: git branch --show-current
   • Recent commits on this branch: git log --oneline -10
   • Uncommitted changes: git status --short
   • Open tasks: read tasks/todo.md if it exists
   • Active spec or plan: check docs/specs/ and docs/plans/ for recent files. Record the full path of the active spec including any version suffix (e.g., docs/specs/2026-04-23-foo-v2.md) — this becomes spec_path in the artifact.
   • Lessons captured this session: check tasks/lessons.md for today's entries