handoff

Create a redacted Markdown context-transfer document summarizing current state and blockers.

Updated May 3, 2026
One-click install
npx skills add https://github.com/druejaramillo/skills --skill handoff-druejaramillo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/druejaramillo/skills/tree/main/productivity/handoff
Command: npx skills add https://github.com/druejaramillo/skills --skill handoff-druejaramillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of context loss during transitions between work sessions or handovers to other team members by creating a structured, verified, and redacted summary of the current state.

Core Features & Use Cases

  • Context Preservation: Captures verified facts, decisions, and blockers in a standardized format.
  • Security-First Design: Automatically redacts sensitive information like API tokens and credentials.
  • Use Case: Use this when you need to pause a complex debugging session and want to ensure that when you or a colleague return, the next steps, canonical references, and current blockers are immediately clear.

Quick Start

Use the handoff skill to generate a summary of our current progress on the billing retry implementation and save it to the temporary directory.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer context between work sessions without losing progress?

To transfer context between work sessions, you need a standardized context-transfer document that synthesizes the current state, verified facts, and pending blockers into a readable Markdown format for seamless resumption.

What is the best way to document current work state for a team handoff?

The best way to document work state for a team handoff is to generate a self-contained summary that captures canonical artifacts, current progress, and pending blockers so the next person can immediately understand the context.

How do you securely redact sensitive credentials when creating documentation?

Securely redacting sensitive credentials when creating documentation requires a process that automatically identifies and removes sensitive information like API tokens, ensuring the final context-transfer file is safe to share.

Can I use this context preservation approach for complex debugging sessions?

Yes, you can use context preservation for complex debugging sessions. It captures the exact blockers and verified facts, ensuring that when you pause and return, the next steps and canonical references are immediately clear.

Does this handoff process require external tools or dependencies to work?

No, this handoff process does not require external dependencies. It operates independently to synthesize your work state into a standardized format, though it requires explicit user confirmation before performing any external actions.

What limitations exist when redacting credentials for workflow documentation?

A key limitation when redacting credentials for workflow documentation is that the redaction process strictly targets sensitive information like API tokens, meaning users must still manually ensure all other non-automated sensitive context is appropriately managed.