create_handoff

Generate a standardized handoff document with frontmatter and next steps.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill create-handoff-brightblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create_handoff
Source: https://github.com/BrightBlock/hyprlayer-cli/tree/main/claude/skills/create_handoff
Command: npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill create-handoff-brightblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a concise, structured handoff document to transfer ongoing work to a new session or agent, ensuring context is preserved for continuity.

Core Features & Use Cases

  • Generate a standardized handoff with title, date, task summary, references, and actionable next steps.
  • Support cross-session handoffs across common storage backends (e.g., git/obsidian) with consistent formatting and metadata.
  • Use Case: when ending a session or handing off to a successor, produce a ready-to-use artifact that guides the next agent.

Quick Start

Provide a concise, action-oriented handoff document summarizing your session and next steps.

Frequently Asked Questions about create_handoff

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

FAQPage Schema
How do I create a handoff document to transfer work to a new AI session?

To create a session handoff document, generate a standardized artifact containing the task title, date, summary, references, and actionable next steps to preserve context for the next agent.

What is the best way to summarize work for cross-session AI workflow management?

The best way to summarize work for cross-session AI workflows is to output a standardized frontmatter and body content that captures task progress and next steps for your successor.

Does this handoff artifact generation work with git and obsidian storage backends?

Yes, the handoff artifact generation follows storage backend rules for common platforms like git and obsidian, ensuring consistent formatting and metadata across different environments.

When do I need to generate a standardized handoff document for session transfer?

You need to generate a standardized handoff document when ending a session, handing off work to a successor, or restarting work after an interruption to ensure context is preserved.

What metadata schema is required for an AI workflow session transfer document?

The session transfer document requires a standardized metadata schema applied via frontmatter, ensuring the next agent can parse the task summary, references, and actionable next steps.

Can I use this workflow management skill to restart work after an interruption across backends?

Yes, you can use this workflow management skill to restart work after an interruption across backends by generating a ready-to-use artifact that guides the next agent through next steps.