handoff

Generate session progress logs and update project documentation files.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/0xHarbs/agent-setup --skill handoff-0xharbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/0xHarbs/agent-setup/tree/main/claude/skills/lifecycle/handoff
Command: npx skills add https://github.com/0xHarbs/agent-setup --skill handoff-0xharbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The handoff process often lacks a consistent, structured record of session progress and project documentation. This skill automates capturing session state and producing ready-to-publish docs.

Core Features & Use Cases

  • Generates a structured session progress log with current branch, changes, decisions, and next steps.
  • Produces or updates a docs/ folder containing TLDR, ARCHITECTURE, SETUP, API (if applicable), DECISIONS, and CONTRIBUTING files.
  • Keeps manual content intact while auto-generating auto-generated sections, enabling audits and onboarding.

Quick Start

Run /handoff to generate the session progress log and update the docs/.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I automate session handoffs and generate project documentation?

Automating session handoffs involves capturing the current session state and generating structured documentation like logs and architecture diagrams. This skill outputs YAML-driven metadata, progress logs, and ready-to-publish docs.

How does structured session logging work for onboarding new developers?

Structured session logging records the current branch, code changes, decisions, and next steps into a consistent YAML format. This creates a clear progress log that accelerates developer onboarding.

Can I generate architecture diagrams and docs without overwriting manual content?

Yes, documentation generation keeps manual content intact while auto-generating specific sections. It updates the docs folder with TLDR, architecture, setup, and decision files without overwriting your manual edits.

What's the best way to document project decisions for post-ship reviews?

Documenting project decisions requires generating structured decision records within a docs folder. This skill automates capturing session state and producing documentation suitable for audits and post-ship reviews.

Does the handoff workflow require specific dependencies or components to run?

No specific dependencies or components are required to run the handoff workflow. It operates within Claude Code sessions to generate structured progress logs and update repository documentation.

What files are included in the auto-generated docs folder?

The auto-generated docs folder includes TLDR, ARCHITECTURE, SETUP, API (if applicable), DECISIONS, and CONTRIBUTING files. These files are structured for integration with the repository's docs system.