checkpointing

To save session context, this skill captures Git history, CLI consultations, and design decisions into a Markdown checkpoint file. It also appends a concise summary to CLAUDE.md to maintain persistent session history across future interactions.

Recording agent teams activity and CLI consultations is handled by generating a comprehensive checkpoint file. This file logs all team interactions and command-line outputs, ensuring no work is lost and providing a foundation for future learning.

You can discover reusable skills because this tool analyzes your saved checkpoint files to identify recurring patterns. It suggests new automated skills based on the design decisions and activities recorded in your session history.

Creating a persistent session history file involves appending a concise summary of your current work to CLAUDE.md. This ensures cross-session context is maintained by capturing code changes and team activities in a durable format.

Checkpointing works without external dependencies to log design decisions. It operates independently using internal scripts to capture your complete session state and generate detailed Markdown summaries.

Generating a Markdown checkpoint file preserves the complete state of your sprint, including code changes and command-line interactions. This detailed record prevents work loss and helps identify patterns that can be turned into new automated skills.