session-checkpoints

To save and restore session state, this Skill produces a standardized `.opencastle/SESSION-CHECKPOINT.md` file containing phase details, task tables, delegation logs, approvals, and resume instructions. It verifies git state and tracker issues before resuming to prevent drift across agent sessions.

Session state management for multi-agent workflows works by producing a standardized checkpoint file containing phase details, delegation logs, and approvals. It verifies git state and tracker issues before resuming to prevent drift and accidental deployment across interrupted development sessions.

The best way to track delegation cost and model tiers is by maintaining a delegation log within the `.opencastle/SESSION-CHECKPOINT.md` file. This protocol audits delegation costs, model tiers, and durations to optimize budgets and facilitate postmortems for multi-session development workflows.

Yes, you can fork an interrupted development phase without re-analyzing the codebase by loading the standardized `.opencastle/SESSION-CHECKPOINT.md` file. This checkpoint protocol enables replay, fork, and resume of interrupted work by providing phase details, task tables, and step-by-step resume instructions.

You need a session checkpoint file for git workflow verification when running multi-session development where agents decompose tasks and may be interrupted during delegation, verification, or long-running tasks. It verifies branch and tracker state before resuming risky operations like DB migrations to prevent accidental deployment.