ss-workflow-generating-handoff

Generate a single markdown handoff file with YAML frontmatter and redacted secrets.

Updated May 19, 2026

Search Tags:#workflow #documentation #markdown #handoff #git status #redaction #session context

Ready to run

npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-workflow-generating-handoff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ss-workflow-generating-handoff
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/workflow/ss-workflow-generating-handoff
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-workflow-generating-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an active development session into a clear, self-contained handoff document so a fresh agent or human can immediately continue without losing context.

Core Features & Use Cases

Session-to-handoff bridging: Captures goal, what was done, decisions, what’s left, and what’s blocked based on conversation context plus lightweight git state.
Safe, single-file output: Writes exactly one markdown file under $HOME/.sublime-skills/handoffs/<repo-basename>/ with a date-stamped name, without modifying repo files.
Redaction-first: Performs a sweep to avoid including secrets, tokens, or sensitive values in the handoff.

Quick Start

Use the ss-workflow-generating-handoff skill to write a new handoff file for this session in your $HOME/.sublime-skills/handoffs directory.

Frequently Asked Questions about ss-workflow-generating-handoff

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

FAQPage Schema

How do I generate a handoff document for an in-progress development session?▼

To generate a session handoff document, summarize conversation history and lightweight git status into a single markdown file with YAML frontmatter. This creates a self-contained note that helps a new agent or human resume work without context loss.

What is a session handoff note and when do I need one for my workflow?▼

A session handoff note is a markdown file capturing goals, decisions, completed work, and blockers from an active development effort. You need one when transferring context to a fresh agent or human to ensure seamless work continuation.

Can I store the handoff markdown file directly inside my git repository?▼

No, the handoff markdown file is stored strictly outside the repository in $HOME/.sublime-skills/handoffs/<repo-basename>/ with a date-stamped name. This ensures the single-file output does not modify any existing repo files.

Does generating a handoff note automatically redact secrets and tokens from the output?▼

Yes, generating a handoff note performs a mandatory redaction sweep to avoid including secrets, tokens, or sensitive values in the output. This ensures the session context markdown file remains safe for sharing.

What is the best way to document session context for another developer to continue?▼

The best way to document session context is summarizing conversation history and git state into a markdown handoff note with required sections and YAML frontmatter. This provides a structured, single-file summary that unblocks the next agent.

Are there limitations on what to include when creating a markdown handoff document?▼

Yes, limitations when creating a markdown handoff document include strict single-file output, mandatory YAML frontmatter, and exclusion of diagrams or interactive tool usage. The document must only contain required handoff sections and redacted content.