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, 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.