stacks-handoff

Write a portable handoff document summarizing the current conversation for another agent session.

625|19|Updated Apr 26, 2022
One-click install
npx skills add https://github.com/stacksjs/stacks --skill stacks-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-handoff
Source: https://github.com/stacksjs/stacks/tree/main/storage/framework/defaults/ai/skills/stacks-handoff
Command: npx skills add https://github.com/stacksjs/stacks --skill stacks-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When work must move to a different agent, directory, repository, or colleague, context is lost. This Skill compacts the current conversation into a portable handoff document so a fresh session can continue the work without re-discovering decisions, open questions, or known-broken state.

Core Features & Use Cases

  • Structured handoff content: Captures the goal, current progress, decisions and their rationale, known-broken or unverified areas, suggested stacks-* skills for the next agent, and open questions.
  • Secret redaction: Replaces values from .env, config/services.ts, API tokens, and credential-bearing database URLs with <REDACTED> before the document leaves the session.
  • Safe output location: Saves the document to the OS temp directory instead of polluting the repository workspace.
  • Use Case: Mid-way through a database schema change, you need a different agent to finish the migration. Invoke the handoff to produce a document pointing the next session at the goal, the decisions made, and the stacks-orm skill it should call first.

Quick Start

Ask the assistant to create a handoff document for the next session, optionally describing what that session will focus on.

Frequently Asked Questions about stacks-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off work to another AI agent session?

Invoke the handoff skill to summarize the current conversation into a portable document saved to the OS temp directory. Optionally pass an argument describing what the next session will focus on so the document is tailored to that goal.

What should a handoff document between coding agents include?

It should state the goal in one paragraph, what is done versus in flight, decisions already made and why, what is known broken or unverified, suggested skills for the next agent, and open questions. It should reference committed code and specs by path rather than duplicating them.

Where is the handoff document saved?

The document is written to the OS temp directory, not the workspace. This keeps the repository clean since a handoff is one-hop scaffolding, and the skill reports the absolute path when finished.

Does the handoff document protect secrets and credentials?

Yes. Before writing, values from .env files, config/services.ts, APP_KEY, AWS keys, tokens, and credential-bearing database URLs are replaced with <REDACTED>. Only the variable name and its location are referenced, never the value.

When should I not create a handoff document?

Skip it when nothing is actually travelling to a different agent, directory, repo, or colleague. If the work stays in the current session, continuing, clearing, or compacting the conversation is cheaper than writing a handoff.