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.