hyper-handoff

Capture Hyper task session context into a handoff.md file.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyper-handoff
Source: https://github.com/galatanovidiu/hyper7/tree/main/skills/hyper-handoff
Command: npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams pause or hand off a Hyper task, critical session context can be lost. This Skill writes a handoff.md capturing decisions, ruled-out investigations, uncommitted work, open questions, and the immediate next step to ensure a seamless resume.

Core Features & Use Cases

  • Capture decisions and context from the current session to hand off to another person or agent.
  • Record investigation paths tried and ruled out to avoid repetition.
  • List open questions and uncommitted work to prevent loss of critical information.
  • Provide a concise "immediate next step" to orient the next session quickly.

Quick Start

Create a handoff.md for the current Hyper task summarizing decisions, open questions, uncommitted work, and the immediate next step.

Frequently Asked Questions about hyper-handoff

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

FAQPage Schema
How do I capture session context to resume a task after a pause?

To capture session context for task resumption, generate a handoff.md file summarizing decisions, ruled-out paths, uncommitted work, open questions, and the immediate next step. This ensures a seamless resume for another person or agent.

What should be included in a handoff document for task transition?

A task transition handoff document should include decisions made, investigation paths ruled out, uncommitted work, open questions, and the immediate next step. This prevents loss of critical information during agent or personnel handoffs.

When do I need to write a handoff.md file for my session?

You need to write a handoff.md file when pausing or handing off an active Hyper task with ongoing exploration or plan phases. It captures the current session state to ensure a seamless resume for the next person or agent.

Can I record ruled-out investigation paths to avoid repeating work in a session handoff?

Yes, you can record investigation paths tried and ruled out in the handoff.md file. Capturing these ruled-out paths explicitly avoids repetition and prevents loss of critical context during task transitions.

What is the best way to orient another agent quickly when handing off an active task?

The best way to orient another agent is to provide a concise immediate next step in the handoff.md file. Alongside decisions and open questions, this orients the next session quickly for a seamless resume.