← All skills · Automation · Handoff Notes

Handoff Notes — finished output
Runs inClaude Code Codex Cursor Muse Dot Grok Bot Cue OpenClaw Hermes
Install guidesClaude Code Codex Cursor Muse
Needs:Your session-end notes: handoff.txt (Session and Goal lines, then one Decision line per decision — decision | why it matters — one Done line per completed item — what was completed | evidence or file — one Next line per next step — next step | owner | status: ready, waiting, or blocked — one Open line per open question — question | who can answer — one Blocker line per blocker — blocker | impact | optional workaround — and optional Context lines).

Similar Skills

View all skills →

What you get

  • A decisions table: each decision with why it matters, so the next session can stand on the reasoning
  • What got done, each item with its evidence or file
  • Next steps ordered ready first, then waiting, then blocked, each with an owner and a status
  • Every open question with who can answer it, every blocker with its impact and workaround — or 'no workaround yet'
  • Every gap, input error, and warning named in the report

Good fit

  • Ending a session and handing the work to another session or agent
  • Keeping the reasoning behind decisions, not just the decisions
  • Seeing at a glance what is ready, what is waiting, and what is blocked

Not for

  • Inventing decisions, done items, or next steps the file does not contain
  • Inventing a workaround for a blocker that has none yet
  • Answering open questions or clearing blockers — the handoff is a document

Sample output

An example of what this Skill produces. Sample content, shown for illustration.

Handoff Notes report — sample

Decisions: 3 | Done: 4 | Next steps: 4 (ready 2 · waiting 1 · blocked 1) | Open questions: 2 | Blockers: 1 | Gaps: 1 | Errors: 0 | Warnings: 0

Decisions: Use a one-time link sent by email, not a password — passwords add a reset flow buyers never finish; the link expires after 30 minutes — a longer window lets a forwarded link stay live too long; show a "check your inbox" screen immediately — buyers assumed the link was broken when nothing visibly happened.

Next steps (ready first, then waiting, then blocked): [ready] Add a resend-link button on the confirmation screen — owner: Peak; [ready] Log how many links expire unused — owner: Peak; [waiting] Write the login help page for buyers who never get the email — owner: Peak; [blocked] Move the email sender behind the paid-worker queue — owner: Peak.

Gaps: 2 open question(s) are unanswered — 'Should the link also work for the GIF generator's login, or only the main site?' (ask SkillU login owner); 'What should the error say when a link is used twice?' (ask Support lead).

About this Skill

You say
Turn this session into a handoff doc another session can continue from — decisions, what got done, next steps in order, open questions, and blockers.

How to install

  1. Copy the install prompt into your agent: Read https://skillu.dev/install/agent.md, then install the Handoff Notes skill (handoff-notes).
  2. Or download the Skill package from this page after launch and place its folder in your agent’s skills directory.
  3. Call it with a slash command, e.g. /handoff-notes, and describe what you want in plain words.

FAQ

How are next steps ordered?

Only by the status you wrote: ready first, then waiting, then blocked. Within one status, the order you wrote them is kept. A step marked blocked is not hidden and not promoted — it stays at the end of the list, where the next session can see it is stuck.

What happens to a blocker with no workaround?

It stays in the handoff and is listed as having no workaround yet, with a gap naming how many blockers have none — the doc never invents a workaround. Add the workaround to the Blocker line (blocker | impact | workaround) and re-run.

Get Premium access Browse more skills