workflow-end

Close active work sessions with status review and checkpoint persistence.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill workflow-end
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-end
Source: https://github.com/ribatshepo/cc-auto-orchestrate/tree/main/claude-code/skills/workflow-end
Command: npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill workflow-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Properly close your current work session with status review and wrap-up.

Core Features & Use Cases

  • Determine and store the Session Checkpoint Path based on SESSION_ID presence
  • Review current state and identify active tasks requiring user input
  • Complete or gracefully pause in-progress tasks and generate a session summary
  • Persist final checkpoint to the designated path with a structured payload

Quick Start

Instruct the agent to end the current session and save the final checkpoint.

Frequently Asked Questions about workflow-end

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

FAQPage Schema
How do I end a Claude Code work session and save a checkpoint?▼

To end a Claude Code work session, instruct the agent to run the session wrap-up process. This resolves active task checkpoints, handles in-progress items, saves the final state to a designated path, and captures optional notes for future sessions.

What is session checkpointing and why do I need it for multi-task workflows?▼

Session checkpointing is the process of persisting your current work state to a structured payload path. It is needed for multi-task workflows to deterministically save progress, review active tasks, and ensure no work is lost when ending a session.

Can I pause in-progress tasks instead of completing them during session wrap-up?▼

Yes, session wrap-up allows you to gracefully pause in-progress tasks. The workflow reviews current state, identifies tasks requiring input, and either completes them or pauses them before generating a final session summary.

Does session checkpointing work without a SESSION_ID?▼

Session checkpointing relies on the presence of a SESSION_ID to determine and store the checkpoint path. Without it, the workflow cannot resolve the designated path to persist the final structured payload.

What's the best way to generate an end-of-session summary for active tasks?▼

The best way to generate an end-of-session summary is to trigger a status review workflow. This reviews current state, identifies active tasks requiring input, resolves checkpoints, and persists a structured summary payload.