How do I install the Stacks Handoff skill?

Run npx skillmds@latest add stacksjs/stacks-handoff in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Stacks Handoff safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Stacks Handoff?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Stacks Handoff free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Stacks Handoff?

stacksjs (@stacksjs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Stacks Handoff by stacksjs — Agent Skill

Name: Stacks Handoff
Author: stacksjs

File contents

Handoff

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it to the OS temp directory, not the workspace: a handoff is scaffolding for one hop, and a stray HANDOFF.md in the repo is sediment.

If the user passed an argument, treat it as a description of what the next session will focus on and tailor the document to that.

Credit: adapted from Matt Pocock's handoff skill (MIT), https://github.com/mattpocock/skills.

What goes in

The goal, in one paragraph. What the next session is trying to achieve.
Where things stand. What is done, what is in flight, what is untouched.
The decisions already made, and why. This is the part a summary of the diff cannot recover, so it is the part worth the most words.
What is known to be broken or unverified. Name the command that would prove it either way.
Suggested skills. Name which stacks-* skills the next agent should call the Skill tool for. A handoff that does not point at stacks-orm before a model change is handing over a landmine.
Open questions the next session has to resolve, or take back to the user.

What stays out

Do not duplicate content already captured elsewhere. Reference it by path, branch, URL or commit instead:

Committed code and its diff.
A spec, plan or ADR already written to disk.
An issue or PR on the tracker.
Anything a stacks-* skill already documents. Point at the skill.

Redact before you write

The document leaves this session, so treat it as publishable. Write <REDACTED> in place of:

Anything from .env, .env.production or config/services.ts.
APP_KEY, AWS keys, HCLOUD_TOKEN, registrar and DNS API tokens, database URLs with credentials in them.
Personal data pulled out of a database during the session.

Reference the variable name and where it lives, never the value.

Finish

Tell the user the absolute path, and say in one line what the next session should do first.

Before you hand off at all

A handoff is narrow. It buys portability, and you only need it when something is actually travelling: a different agent, a different directory or repo, a colleague, or a side task forked mid-phase. If none of those apply, the cheaper moves are to continue, to clear, or to compact. stacks-flow has the ordered tree.

---name: stacks-handoffdescription: Compact the current conversation into a portable handoff document for another agent or session to pick up.license: MIT---# HandoffWrite a handoff document summarising the current conversation so a fresh agentcan continue the work. Save it to the OS temp directory, not the workspace: ahandoff is scaffolding for one hop, and a stray `HANDOFF.md` in the repo issediment.If the user passed an argument, treat it as a description of what the nextsession will focus on and tailor the document to that.Credit: adapted from Matt Pocock's `handoff` skill (MIT),<https://github.com/mattpocock/skills>.## What goes in- **The goal**, in one paragraph. What the next session is trying to achieve.- **Where things stand.** What is done, what is in flight, what is untouched.- **The decisions already made, and why.** This is the part a summary of the diff cannot recover, so it is the part worth the most words.- **What is known to be broken or unverified.** Name the command that would prove it either way.- **Suggested skills.** Name which `stacks-*` skills the next agent should call the Skill tool for. A handoff that does not point at `stacks-orm` before a model change is handing over a landmine.- **Open questions** the next session has to resolve, or take back to the user.## What stays outDo not duplicate content already captured elsewhere. Reference it by path,branch, URL or commit instead:- Committed code and its diff.- A spec, plan or ADR already written to disk.- An issue or PR on the tracker.- Anything a `stacks-*` skill already documents. Point at the skill.## Redact before you writeThe document leaves this session, so treat it as publishable. Write`<REDACTED>` in place of:- Anything from `.env`, `.env.production` or `config/services.ts`.- `APP_KEY`, AWS keys, `HCLOUD_TOKEN`, registrar and DNS API tokens, database URLs with credentials in them.- Personal data pulled out of a database during the session.Reference the variable name and where it lives, never the value.## FinishTell the user the absolute path, and say in one line what the next sessionshould do first.## Before you hand off at allA handoff is narrow. It buys **portability**, and you only need it whensomething is actually travelling: a different agent, a different directory orrepo, a colleague, or a side task forked mid-phase. If none of those apply, thecheaper moves are to continue, to clear, or to compact. `stacks-flow` has theordered tree.

Frequently asked questions

Stacks Handoff