What problem does it solve? Long-running development stories lose their state when an AI session hits a context limit or a subagent takes over, forcing expensive re-derivation of what was done, decided, and left to do. This Skill persists a structured, self-contained checkpoint per story and restores it on demand. ## Core Features & Use Cases - Write mode: Captures story ID, branch, tasks done, key decisions, and remaining todos into a single file at .pair/working/checkpoints/<story-id>.md, updated in place and never duplicated. - Resume mode: Locates and parses the existing checkpoint for a story, reporting parsed state with explicit gap markers instead of guessing when sections are missing. - Write-free composition: With $persist=false, returns the rendered checkpoint text without touching the filesystem so composers like /capability-publish-pr can embed it in a PR body. - Use Case: Mid-story on issue #313 with 2 of 5 tasks done, invoke the skill to save progress; after a context reset, resume and jump straight to the next pending task without re-analyzing the branch. ## Quick Start Ask the assistant to save our progress on story #313, or to resume story #256 from its checkpoint.
