save-game

Capture and serialize current project state into a structured HANDOFF.md document.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/augustscl/awesome-xiawang-skills --skill save-game-augustscl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-game
Source: https://github.com/augustscl/awesome-xiawang-skills/tree/main/save-game
Command: npx skills add https://github.com/augustscl/awesome-xiawang-skills --skill save-game-augustscl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save Game formalizes the end-of-session work review and creates a single, readable handoff so the next agent or future you can pick up without guessing what happened or what to do next. It prevents lost context when conversations or projects are paused, compacted, or transferred.

Core Features & Use Cases

  • Structured review: Guide a focused retrospective of completed work, produced artifacts, and outstanding items.
  • Handoff authoring: Produce a HANDOFF.md containing goals, current progress, next steps, critical IDs, and lessons learned so a new agent can resume immediately.
  • Checkpoint & follow-up: Optionally register a cron check to re-open the project later and report status.
  • Use cases: ending a work session, preparing an agent-to-agent transfer, creating a checkpoint before compaction, or wrapping up a sprint segment.

Quick Start

Tell the agent to save the current project by creating a HANDOFF.md that summarizes goals, progress, outputs and paths, next steps, key IDs, lessons learned, and optionally schedules a follow-up check.

Frequently Asked Questions about save-game

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

FAQPage Schema
How do I create a project handoff document for agent-to-agent transfer?

A project handoff document is a structured HANDOFF.md that captures goals, current progress, next steps, critical IDs, and lessons learned so a new agent can resume work immediately without guessing context or prior decisions.

How do I save project state before context compaction?

Saving project state before compaction involves serializing current progress, outputs, and critical numbers into a checkpoint HANDOFF.md file, ensuring reliable resumption after the conversation context is truncated or cleared.

What should a session checkpoint include for reliable project resumption?

A reliable session checkpoint must include the project goal, current progress, next steps, critical numbers and IDs, and lessons learned, optionally adding a cron-based follow-up to automatically re-open and report project status later.

Can I schedule an automated follow-up check after ending a work session?

Yes, you can schedule an automated follow-up by registering a cron-based check during the handoff creation, which will re-open the project later and report its current status automatically without requiring manual intervention.

What is the best way to document project progress for future reference?

The best way to document project progress is to formalize an end-of-session review into a readable HANDOFF.md, capturing completed work, produced artifacts, outstanding items, and key IDs to prevent lost context when pausing or transferring ownership.

Do I need any dependencies to serialize a project state into a handoff file?

No dependencies are required to serialize a project state into a handoff file, as the process focuses on guiding a structured retrospective and authoring a standard HANDOFF.md document using existing project context and conversation history.