session-handoff

Summarize active work into a compact HANDOFF block for the next session.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/special-place-administrator/citadel_codex --skill session-handoff-special-place-administrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/special-place-administrator/citadel_codex/tree/main/skills/session-handoff
Command: npx skills add https://github.com/special-place-administrator/citadel_codex --skill session-handoff-special-place-administrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform ongoing work into a compact HANDOFF block that preserves context for the next session or delegated agent.

Core Features & Use Cases

  • Capture what changed, key decisions and reasons, blockers or open items, and the immediate next step.
  • Reference active campaign or fleet state in .citadel/ when relevant to ensure continuity.
  • Produce a ready-to-share handoff block that is concise and actionable for the next assignee.

Quick Start

Use this skill to generate a HANDOFF block from the current session input.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I create a session handoff summary for a delegated agent?

To create a session handoff summary, extract what changed, key decisions and rationale, blockers, and the immediate next step, then format this context into a compact HANDOFF block for the next assignee.

What should be included in a handoff block for ongoing campaign state?

A handoff block for ongoing campaign state must include specific changes made, key decisions and their rationale, current blockers or open items, the immediate next step, and active fleet state references to ensure continuity.

When do I need to generate a handoff block for my workflow?

You need to generate a handoff block when passing responsibility to another agent or team, or when ending a session involving ongoing campaigns or fleet state that requires preserving context for the next assignee.

Does generating a session handoff require any specific dependencies?

Generating a session handoff requires no external dependencies, but it does require the ability to extract changes, decisions, blockers, and next steps from the active session input to format the output correctly.

Can I reference active fleet state in .citadel/ when summarizing my session?

Yes, you can reference active campaign or fleet state stored in .citadel/ when generating your handoff block to ensure the next session or delegated agent has the necessary continuity context.