context-save

Name: context-save
Availability: InStock
Author: Jason

Save current working state as dev-log entry and checkpoint without modifying source code.

Updated May 11, 2026

Search Tags:#workflow #handoff #checkpoint #sessions #dev-log #feature-id #context-save

Ready to run

npx skills add https://github.com/jason660519/Project-Manager --skill context-save-jason660519

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/jason660519/Project-Manager/tree/main/.agents/skills/context-save
Command: npx skills add https://github.com/jason660519/Project-Manager --skill context-save-jason660519

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures the current working state into a repo-native handoff by appending a dev-log entry under .project-manager/features/<ID>/dev-log.md and a lightweight checkpoint under .context/sessions/, enabling pause-and-resume workflows without touching source code.

Core Features & Use Cases

Writes an append-only dev-log entry to the feature's dev-log and creates a .context/sessions/ checkpoint.
Pairs with the context-restore workflow to reconstruct past states.
Enforces a hard guard to never modify source code during saves.

Quick Start

Instruct the agent to save the current context by issuing /context-save with the active feature ID (e.g., F46) and then review the resulting checkpoint and dev-log files.

Frequently Asked Questions about context-save

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

FAQPage Schema

How do I save the current working state into a repo-native handoff without modifying source code?▼

To save your working state into a repo-native handoff, append a dev-log entry under .project-manager/features/<ID>/dev-log.md and create a checkpoint under .context/sessions/. This enforces a hard guard to never modify source code during saves.

What is a checkpoint session in a pause-and-resume development workflow?▼

A checkpoint session is a lightweight save file created under .context/sessions/ that captures your current working state. It pairs with a dev-log entry to enable pause-and-resume workflows by allowing past states to be reconstructed without touching source code.

How do I create a context checkpoint for an active feature ID?▼

To create a context checkpoint, invoke the save operation with an active feature ID like F46. The process appends an entry to the feature's dev-log.md and generates a new checkpoint under the .context/sessions/ directory.

Does context-save modify feature-spec, tdd-spec, or test-scenarios files?▼

No, context-save enforces a hard gate that refuses to alter feature-spec, tdd-spec, or test-scenarios files. The operation only touches the dev-log and the checkpoint, ensuring source code and specifications remain unchanged.

Can I use a dev-log checkpoint to reconstruct past project states?▼

Yes, the dev-log checkpoint reconstructs past states by pairing the saved checkpoint under .context/sessions/ with the context-restore workflow. This allows you to pause and resume work by loading the exact artifact paths documented during the save.

When should I not use a repo-native handoff checkpoint for my workflow?▼

You should not use a repo-native handoff checkpoint if your workflow requires modifying source code or altering feature-spec and tdd-spec files. This checkpoint mechanism is strictly append-only for dev-logs and sessions, enforcing a hard guard against code alterations.