Handoff

Skill photostructure/coding-skills/plugins/coding/skills/handoff

Opinionated Claude Code and Codex workflow skills: iterative planning, proof-based review, and clean Conventional Commits.

Install

npx -y skills add photostructure/coding-skills --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

2 stars2 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

Update the active Technical Project Plan for handoff when context is running low or the session is ending, so the next session continues instead of restarting.

SKILL.md

1.6 KB, as published. Nobody here has run it

TPP Handoff

Documented in depth: Claude Code has amnesia. So do PRs, changelogs, and your future self.

We're out of time and need to hand off the remaining work. The Technical Project Plan (TPP) is the handoff document — whatever this session learned must land in the file, or the next session re-learns it the hard way.

Required Reading First

Before any work, you MUST read:

The project's instructions: AGENTS.md, plus CLAUDE.md when present
The project's TPP guide: docs/TPP-GUIDE.md if it exists; otherwise the bundled reference TPP-GUIDE.md

Your Task

Re-read the TPP and update progress.
Mark completed tasks and update the current phase.
Document discoveries, gotchas, and insights.
Record failed approaches and why they failed — the next session must not re-explore dead ends.
Clarify exactly what remains and any blockers.
Trim redundancy before saving: the TPP is a curated brief, not a transcript. Keep it under 400 lines; if that's impossible, propose splitting it.

The bar: the next session should be able to invoke the tpp skill with the plan path and continue without asking what happened last time.

Adapting for your project

Extend the required reading list with the same project docs your tpp skill reads — the two skills should share one list.
Tune the length budget if your project's guide sets a different limit.