Skip to content

ShockRock2004/kamar-taj / handoff

handoff

Verified

Use when the user invokes /handoff, and ALWAYS when starting work in a repo that already contains a HANDOFF.md — reading that file is the first job before exploring the codebase. Creates and maintains a git-ignored HANDOFF.md at the repo root that carries task state between sessions and agents.

FileKindSize
README.mdmarkdown1.4 KB
SKILL.mdskill md4.8 KB
# handoff

You open a fresh session and Claude knows nothing about your project. So you explain it again. The stack and the goal and the thing you were halfway through fixing. You do this every morning. You do it again every time the context runs out.

This skill kills that ritual.

It keeps a HANDOFF.md at the root of your repo. The objective. The current state. What is in flight. What is blocking you. Why the strange decisions were made. A fresh agent reads that file before it touches a single line of source. It starts warm instead of grepping around for ten minutes trying to work out what you want.

It never overwrites what is already there. It updates in place and prunes whatever stopped being true. Stale notes are worse than missing ones. When the file grows past five hundred lines it folds the old session log into a condensed history so the thing stays readable.

It hides the file in .git/info/exclude and not in .gitignore. Your working notes are your business. They do not belong in a commit your teammates have to read.

No dependencies. No config. It works in any repo and it degrades to the plain working directory if you are not even in git.

## Install

It comes in the main kamar-taj bundle at https://github.com/ShockRock2004/kamar-taj
or you can just grab this single folder.

```bash
cp -R handoff ~/.claude/skills/
```

Restart Claude Code and run /handoff. Find the full protocol in SKILL.md.

Your repo now remembers things. You still will not.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall