start

Hydrate session context and organize tasks for handoff.

4|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/ramonclaudio/skills --skill start-ramonclaudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/ramonclaudio/skills/tree/main/plugins/handoff/skills/start
Command: npx skills add https://github.com/ramonclaudio/skills --skill start-ramonclaudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the preparation of a live session context for handoffs by hydrating tasks, surfacing blockers, and summarizing the current state to guide the incoming team.

Core Features & Use Cases

  • Hydration of pre-loaded state into actionable tasks.
  • Identify blockers and resume points across sessions.
  • Provide a concise session summary for handoffs.

Quick Start

Execute the handoff start skill to hydrate the current session state and surface next actions.

Frequently Asked Questions about start

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

FAQPage Schema
How do I hydrate session context for a smooth handoff?

To hydrate session context for a handoff, the skill reads pre-loaded state, analyzes drift, and organizes tasks with metadata. It specifically surfaces unresolved blockers and resume points to guide the incoming team on what to work on next.

What is the best way to track unresolved blockers across critical sessions?

Tracking unresolved blockers across critical sessions involves reading the current state and analyzing drift. This skill identifies those blockers and creates specific resume tasks with metadata to ensure no critical context is lost during transitions.

How do I prepare task-management state for an incoming team?

Preparing task-management state for an incoming team requires hydrating pre-loaded state into actionable tasks. The skill summarizes the session, establishes dependencies, and creates concise resume points to guide the incoming team on next actions.

When do I need to hydrate context for session handoffs?

You need to hydrate context for session handoffs when dealing with critical sessions, unresolved blockers, or when asking what to work on next. It is essential for preventing context loss and ensuring seamless task-management continuity.

Does this session hydration approach work without external dependencies?

Yes, this session hydration approach works without external dependencies. It operates by reading pre-loaded state directly and analyzing drift to establish task dependencies and metadata for the handoff.

Why does session state drift happen and how is it managed for handoffs?

Session state drift happens when live context changes over time. It is managed for handoffs by analyzing the drift, creating blocker and resume tasks with metadata, and establishing dependencies to organize the current state accurately.