end-session

Redirect deprecated session handoff requests to current governance workflows.

8|Updated Apr 12, 2026

Search Tags:#state management #deprecation #governance #session handoff #workflow routing #release process

Ready to run

npx skills add https://github.com/Gold-b/claude-code-governance --skill end-session-gold-b

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: end-session
Source: https://github.com/Gold-b/claude-code-governance/tree/main/bundle/skills/end-session
Command: npx skills add https://github.com/Gold-b/claude-code-governance --skill end-session-gold-b

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents users from relying on an outdated session-closing workflow by clearly redirecting them to the supported governance tools for handoff, documentation, and state synchronization.

Core Features & Use Cases

Deprecation Guidance: Explicitly marks the skill as deprecated and points users to the replacement workflow.
Routing to Current Tools: Directs full release and handoff needs to full-finish, and documentation-only state management to live-state-orchestrator.
Governance Continuity: Helps teams avoid broken or duplicated handoff processes when ending Claude Code sessions under the repository's governance model.

Quick Start

Ask the AI to use full-finish for a complete release handoff, or live-state-orchestrator if you only need session state documents updated before ending work.

Frequently Asked Questions about end-session

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

FAQPage Schema

How do I handle Claude Code session handoff at the end of a release?▼

For a complete release handoff, Claude Code session handoff should be routed to the full-finish workflow to ensure complete pipeline closure and state synchronization.

What is the best way to manage session state documentation before ending work?▼

To manage session state documentation before ending work, route your session handoff to the live-state-orchestrator workflow for document lifecycle management and state synchronization.

Why does my end-of-session workflow say it is deprecated?▼

Your end-of-session workflow is deprecated to prevent reliance on outdated session-closing processes, redirecting you to current governance tools for proper handoff and documentation continuity.

How do I route a deprecated session handoff request to current governance workflows?▼

Route deprecated session handoff requests by redirecting full release needs to full-finish and documentation-only state management to live-state-orchestrator under the repository's governance model.

When do I need to use full-finish versus live-state-orchestrator for session handoff?▼

Use full-finish for complete release pipelines and end-of-session handoff, whereas live-state-orchestrator is for document lifecycle management only when updating session state documents.

Does end-session handle state synchronization for broken handoff processes?▼

End-session prevents broken or duplicated handoff processes by providing deprecation guidance and routing users to supported governance tools for state synchronization and continuity.