/checkpoint

Checkpoint

Save current workflow progress for potential session handoff.

When to Use

Use /exarchos:checkpoint when:

• Context is getting heavy (many tool calls, large outputs)
• Before a long-running operation
• At natural workflow boundaries
• Before stepping away from the keyboard

Skill Reference

• Workflow state: @skills/workflow-state/SKILL.md

Process

Step 1: Identify Active Workflow

The SessionStart hook automatically discovers active workflows on session start. To manually discover workflows, query the MCP pipeline view:

exarchos_view pipeline

Step 2: Ensure State is Current

Update state file with latest progress:

• Current phase
• Task completion status
• Worktree locations
• Any pending items

Step 3: Reconcile State

The SessionStart hook automatically verifies state matches git reality on resume. If manual reconciliation is needed, review state file contents against actual worktree and branch state.

Fix any discrepancies.

Step 4: Output Checkpoint Summary

## Checkpoint Saved

**Feature:** <feature-id>
**Phase:** <current-phase>
### Progress
- Tasks: X/Y complete
- Current: <what's in progress>
- Next: <suggested next action>

### House Rules (apply every action this turn forward)
**Skill:** <phasePlaybook.skillRef or "(no playbook for this phase)">
**Tools:** <phasePlaybook.tools rendered as bullets>
**Required model-emitted events:** <phasePlaybook.events rendered as bullets — e.g. `task.progressed`, `phase.advanced`>
**Auto-emitted events (runtime fires these):** <phasePlaybook.autoEmittedEvents rendered as bullets>
**Transition:** <phasePlaybook.transitionCriteria> | Guard: <phasePlaybook.guardPrerequisites>
**Validation scripts:** <phasePlaybook.validationScripts joined>

### Event Emission Hints
<_eventHints.missing rendered as bullets, or "(none — phase machinery satisfied)">

### Resume Instructions

To continue this workflow in a new session:

/exarchos:rehydrate

Or start Claude Code fresh — the SessionStart hook will auto-discover active workflows.

> **Discipline reminder:** every task transition this turn forward MUST land on the workflow event stream via `exarchos_event.append` or `/exarchos:delegate` subagent emission. Direct `Edit` / `Bash` / `git` actions on task branches without corresponding events will desync the workflow tracker (see RCA `docs/rca/2026-05-08-rehydrate-behavioral-gap.md`).

Auto-Checkpoint Triggers

The orchestrator should suggest /exarchos:checkpoint when:

1. After /exarchos:delegate completes - All tasks done, before review
2. After PR created - In /exarchos:synthesize, before feedback loop
3. After 3+ feedback iterations - Context accumulation risk
4. When user mentions context issues - Proactive save

Output

After checkpointing, provide:

1. Confirmation that state is saved
2. Summary of current progress
3. Clear instructions for resuming
4. The exact /exarchos:rehydrate command to use