onex-handoff

Capture session context, summarize progress, and document remaining work in a handoff manifest.

2|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/Julian0444/omnicursor --skill onex-handoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onex-handoff
Source: https://github.com/Julian0444/omnicursor/tree/main/.cursor/skills/onex-handoff
Command: npx skills add https://github.com/Julian0444/omnicursor --skill onex-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the challenge of losing context at the end of a session, which can lead to wasted time and inefficient workflow transitions.

Core Features & Use Cases

  • Session Context Capture: Automatically records the current state of a session, including branch commits, modified files, and active tasks.
  • Progress Summarization: Provides a structured summary of the work accomplished during the session.
  • Remaining Work Documentation: Lists the remaining tasks and any blockers, ensuring a clear path forward for the next session.
  • Handoff Manifest Creation: Generates a self-contained handoff document that can be used to resume the session from where it left off.
  • Use Case: Ideal for developers, project managers, or anyone working in collaborative environments where context preservation is crucial for efficient workflow transitions.

Quick Start

Use the onex-handoff skill to create a handoff document for your current session.

Frequently Asked Questions about onex-handoff

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

FAQPage Schema
How do I preserve session context for a seamless workflow handoff?▼

To achieve seamless workflow handoff, capture session context by automatically recording your current state, summarizing progress, and documenting remaining tasks into a structured handoff manifest for the next session.

What is the best way to document remaining work and blockers at the end of a development session?▼

The best way to document remaining work is to generate a self-contained handoff manifest that lists outstanding tasks and blockers, ensuring a clear path forward for the next collaborative session.

How does session context capture work for collaborative development environments?▼

Session context capture works by automatically recording the current session state, including branch commits, modified files, and active tasks, to facilitate efficient workflow transitions in collaborative environments.

Can I use this to create a structured progress summary of my modified files and commits?▼

Yes, you can use it to automatically capture modified files and branch commits, providing a structured progress summary of the work accomplished during your session for effective context preservation.

Do I need any external dependencies to generate a handoff manifest?▼

No, you do not need external dependencies to generate a handoff manifest; the skill operates independently using its internal scripts to create the self-contained handoff documentation.

When should I not rely on a handoff document for workflow transitions?▼

You should not rely solely on a handoff document if your workflow requires real-time synchronization rather than context preservation, as it is specifically designed for summarizing progress at the end of a session.