Handoff
A collection of rigorous, phase-isolated SDLC skills to tether autonomous agents to real-world engineering standards.
npx -y skills add NjoyimPeguy/augments --skill handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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
Use when a session is ending or work is passing to a fresh session or another agent — so the next one resumes without re-deriving goal, state, decisions, and the next step. Skip for a finished, self-contained task that needs no continuation.
SKILL.md
1.9 KB, 413 tokens by cl100k_base, as published. Nobody here has run it
Handoff
Write down what the next session needs to continue, so it doesn't reconstruct it from scratch. A good handoff is resumable: someone reads it and knows exactly where to pick up.
When to use
- A conversation is ending mid-work, or work is passing to a fresh session or a different agent.
- Skip when the task is finished and self-contained — there's nothing to resume.
What to capture
Write it to a scratch location outside the workspace (the OS temp directory), so it doesn't pollute the repo. Include:
- The goal — what this work is trying to achieve, in a line or two.
- State — what's done, what's in flight, the current branch, and any uncommitted changes.
- Decisions — the choices made and why, so they aren't relitigated.
- Gotchas — traps discovered, with file and line references.
- The next step — the single concrete thing to do next.
- Suggested skills — which skills the next session should reach for. Put this in the document, not in passing chat.
Rules
- Reference, don't duplicate. Point to existing artifacts (specs, plans, ADRs, issues, commits) by path or URL — don't copy their content in.
- Redact secrets. No keys, tokens, passwords, or personal data in the handoff.
- A handoff is a one-shot transfer of current state — not a durable project-lessons store.
Common mistakes
- A summary of the conversation instead of the state to resume from.
- Duplicating a plan or spec that already exists — link it.
- Omitting the one concrete next step, leaving the next session to guess.
For a fill-in template, a worked bad-vs-good example, and what to leave out, see references/handoff-template.md.
Gives 2 of the 12 instructions most agent orchestration skills give in 413 tokens
Counted across 742 of the 995 authors here whose files we hold, read 2026-08-07
- reference existing artifacts by path or URLhere, and in 53 of 742, across 25 files
- run the full test suite after integrating changesin 51 of 742, across 19 files
- dispatch one agent per independent problem domainin 50 of 742, across 17 files
- verify fixes do not conflictin 45 of 742, across 13 files
- include a suggested skills section in the documenthere, and in 45 of 742, across 17 files
- redact sensitive informationin 41 of 742, across 11 files
- save to the temporary directory of the operating systemin 39 of 742, across 10 files
- tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
- spot check agent changes for systematic errorsin 34 of 742, across 7 files
- write a handoff document summarising the current conversationin 31 of 742, across 6 files
- Assign each agent a specific scopein 23 of 742, across 8 files
- provide specific scope and clear goalin 23 of 742, across 5 files
Said here and by no other author read
- write handoff to os temp directory outside workspace
- record the work goal concisely
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.