state-persistence

Save workflow state to Serena MCP memory with YAML frontmatter.

3|Updated Nov 19, 2025

Search Tags:#workflow #memory #resume #persistence #checkpoint #state

Ready to run

npx skills add https://github.com/seanGSISG/crispy-claude --skill state-persistence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: state-persistence
Source: https://github.com/seanGSISG/crispy-claude/tree/main/cc/skills/state-persistence
Command: npx skills add https://github.com/seanGSISG/crispy-claude --skill state-persistence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill saves workflow state to Serena MCP memory so you can resume work later from research, planning, execution, or completion stages.

Core Features & Use Cases

Memory file format: Standardized naming and frontmatter for memory files.
Automatic and manual saves: Supports automatic saves at milestones and manual saves during planning/execution.
Resume capability: /cc:resume restores state from the latest memory file.

Quick Start

Save current progress with /cc:save or resume with /cc:resume.

Frequently Asked Questions about state-persistence

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

FAQPage Schema

How do I save my workflow state so I can resume it later?▼

Save workflow state using /cc:save to store your current progress to Serena MCP memory with automatic naming and YAML frontmatter. Resume anytime with /cc:resume to restore from the latest checkpoint across research, planning, execution, or completion stages.

What happens to my work if I stop mid-workflow and come back later?▼

Workflow state persists in memory files using standardized naming (YYYY-MM-DD-<feature>-<stage>.md) with frontmatter tracking date, git commit, branch, repository, topic, tags, and status. /cc:resume automatically restores your exact position.

When should I manually save versus letting saves happen automatically?▼

Automatic saves trigger after research and completion stages. Use manual saves via /cc:save during planning and execution phases to checkpoint progress at critical decision points before moving forward.

What information gets stored in my checkpoint files?▼

Checkpoint files store YAML frontmatter including date, git_commit, branch, repository, topic, tags, status, last_updated, and type, enabling precise workflow recovery with full context about your project state and progress.

Can I resume a workflow from any stage, or only from where I stopped?▼

Resume from your latest checkpoint across any stage—research, planning, execution, or completion—using /cc:resume. The system restores the most recent memory file regardless of which workflow phase you're resuming into.