sync

Checkpoint session decisions and detect Command Center and To-Do drift.

89|13|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/jdpolasky/ai-chief-of-staff --skill sync-jdpolasky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/jdpolasky/ai-chief-of-staff/tree/main/.claude/skills/sync
Command: npx skills add https://github.com/jdpolasky/ai-chief-of-staff --skill sync-jdpolasky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents session progress from being lost by saving key decisions mid-session and catching drift between your Command Center and your To-Do status.

Core Features & Use Cases

  • Save to memory: Updates existing files in .claude/memory/ (rather than creating new ones) with the latest session_context, keeping entries current for the last 7 days.
  • Detect Command Center drift: If lane status, priorities, or check state changed this session, it proposes specific edits and asks before applying them.
  • Handle To-Do drift: If new tasks or new “waiting-for” items emerged, it proposes what to add to To-Do.md and asks for approval before updating.

Quick Start

Use the sync skill when you have a long session (2+ hours) and want the AI to checkpoint decisions, update your session context in memory, and confirm any Command Center or To-Do changes.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I checkpoint session context to prevent losing mid-session decisions?

Command Center drift occurs when lane statuses, priorities, or check states change during a session. You can detect this drift by using a sync tool that proposes specific edits to reconcile the differences and asks for approval before applying them.

How do I handle To-Do drift when new tasks emerge during a long work session?

To handle To-Do drift when new tasks or waiting-for items emerge, a sync process proposes additions to your To-Do.md file. It catches these discrepancies and asks for your approval before updating the task list.

How does memory checkpointing manage older session_context entries?

Memory checkpointing manages older session_context entries by updating existing files in the .claude/memory directory and automatically trimming entries that are older than 7 days, keeping the context current without manual cleanup.

When should I run a session checkpoint for updating core memory files?

You should run a session checkpoint after a long session of two or more hours where priorities, lane statuses, or newly discovered tasks may have shifted. This ensures your core memory files and To-Do status remain accurately synchronized.

Can I apply memory updates silently in the background during a session?

No, you cannot apply memory updates silently. The sync process proposes specific edits for your core memory files and To-Do status, requiring your explicit approval before making any changes to prevent unwanted modifications.