shelve

Create structured handoff states with completed steps and session details.

2|Updated Feb 6, 2026

Search Tags:#workflow #documentation #handoff #checkpoint #session-management #shelve

Ready to run

npx skills add https://github.com/ashtonian/llm-init --skill shelve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shelve
Source: https://github.com/ashtonian/llm-init/tree/main/templates/.claude/skills/shelve
Command: npx skills add https://github.com/ashtonian/llm-init --skill shelve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checkpointing work across tasks and plans can be error-prone and hard to hand off; this skill provides a standardized handoff state to preserve context and decisions.

Core Features & Use Cases

Create a structured handoff with sections like Completed Steps, Current Step, Files Modified, Key Decisions, Known Issues, Next Actions, and Session ID; ideal for task-based work, plan execution, and multi-person collaboration.
Use when switching between agents, resuming work after idle periods, or handing off tasks to teammates.

Quick Start

Save the current session state as a structured handoff to prepare for future pickup.

Frequently Asked Questions about shelve

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

FAQPage Schema

How do I create a structured handoff state for resuming work across agents?▼

To create a structured handoff state, the skill automates checkpointing by capturing completed steps, current step, modified files, key decisions, known issues, next actions, and session ID into a standardized schema for seamless context preservation.

What is the best way to preserve context when switching between tasks and plans?▼

The best way to preserve context during task execution and plan updates is to generate a structured handoff state that records key decisions and modified files, ensuring no critical information is lost during transitions.

How do I checkpoint my session before handing off work to a teammate?▼

You can checkpoint your session by saving the current state as a structured handoff that includes next actions and known issues, preparing a standardized snapshot for your teammate to pick up seamlessly.

Does this handoff approach work for multi-person collaboration and cross-agent workflows?▼

Yes, this handoff approach is designed for multi-person collaboration and cross-agent workflows, applying structured checkpointing during task execution to maintain continuity and preserve decisions across different contributors.

What sections are required in a structured handoff schema for session management?▼

A structured handoff schema requires sections for Completed Steps, Current Step, Files Modified, Key Decisions, Known Issues, Next Actions, and Session ID to accurately document the workflow state for future pickup.

When should I not use an automated checkpoint for task handoffs?▼

Automated checkpointing for task handoffs is not ideal for isolated, single-step tasks that require no future resumption, as the overhead of generating a structured handoff schema provides minimal value without ongoing workflow context.