ss-workflow-generating-handoff

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.

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.

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.

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.

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.

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.