rotation-handoff

Generate and read structured DekSpec session handoff records in dekspec/.scratch/rotation-handoff/.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Dektora/dekspec-public --skill rotation-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rotation-handoff
Source: https://github.com/Dektora/dekspec-public/tree/main/plugins/dekspec/skills/rotation-handoff
Command: npx skills add https://github.com/Dektora/dekspec-public --skill rotation-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures DekSpec work sessions survive context rotation or compaction, enabling resumption from the most recent structured handoff record.

Core Features & Use Cases

  • Session Continuity: Captures and maintains a handoff record of DekSpec sessions, ensuring seamless continuation after context changes.
  • Structured Records: Records objective, artifacts, decisions, and next steps, allowing a fresh session to resume effectively.
  • Native Integration: Fully integrated with DekSpec's native engine for zero dependency on external plugins.

Quick Start

To write a structured handoff record for the current session, use: /dekspec:rotation-handoff --write --at .

Frequently Asked Questions about rotation-handoff

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

FAQPage Schema
How do I maintain session continuity after context rotation or compaction?

You maintain session continuity by generating structured handoff records that capture objectives, artifacts, decisions, and next steps, allowing a fresh session to resume work effectively.

What is the best way to resume a software engineering session after context limits are reached?

The best way to resume a software engineering session is to read the most recent structured handoff record, which preserves the session state across context rotations without external dependencies.

Do I need external memory plugins to persist session state across context changes?

No, you do not need external memory plugins to persist session state. This approach uses native integration to generate and read structured handoff records directly within the file system.

How do I write a structured handoff record for my current session?

You write a structured handoff record by executing a command that captures your current session's objective, artifacts, decisions, and next steps into a designated scratch directory.

What information is included in a structured handoff record for manual session resumption?

A structured handoff record includes the session objective, generated artifacts, decisions made, and next steps, providing a comprehensive state snapshot for manual session resumption.

Can I use session handoff records for manual session resumption without automated context management?

Yes, you can use session handoff records for manual session resumption. They are designed to persist session state locally, allowing you to retrieve and continue work manually at any time.