sync

Align progress.md with task files and archive completed tasks.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/tdp1999/claude-code-ctx --skill sync-tdp1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/tdp1999/claude-code-ctx/tree/main/plugins/ctx/skills/sync
Command: npx skills add https://github.com/tdp1999/claude-code-ctx --skill sync-tdp1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps progress tracking in sync with the actual state of tasks across .context folders, archives completed work, and refreshes epic and investigation statuses to reflect current progress.

Core Features & Use Cases

  • Progress alignment: Reconciles progress.md with live task files, and archives done tasks for reference.
  • Status synchronization: Updates task, epic, and investigation statuses based on completion.
  • Audit & reporting: Generates corrections and archiving actions to maintain an accurate project view.

Quick Start

Automatically scan context tasks, archive completed work, and refresh progress to reflect the latest task statuses.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I keep progress tracking aligned with actual task states?

Progress tracking stays aligned with actual task states by reconciling progress.md against live task files, reclassifying statuses, and archiving completed work. This prevents drift between planned epics, investigations, and real development progress.

What's the best way to automate archiving completed tasks in .context folders?

Automating task archiving in .context folders involves scanning task files, identifying completed work, and moving done items into tasks-done. This maintains an accurate project view by automatically organizing finished tasks for future reference.

Why does progress.md drift from the real state of my tasks and investigations?

Progress.md drifts from the real state of tasks when task statuses are updated locally without refreshing the overarching progress file. Reconciling these files reclassifies task statuses and updates epic and investigation statuses to match completion.

Can I automatically update epic and investigation statuses based on task completion?

Epic and investigation statuses can be automatically updated based on underlying task completion. The system scans .context folders, evaluates task files, and refreshes these higher-level statuses to accurately reflect current project progress.

Does task synchronization work without external dependencies?

Task synchronization works without external dependencies, relying solely on reading and writing to local .context folders. It processes tasks, tasks-done, investigations, plans, and plans-done directories to generate a report of changes.

What happens to plans and tasks-done folders during status synchronization?

During status synchronization, plans and tasks-done folders receive archived completed work. The process reads these .context directories, updates progress.md, reclassifies active task statuses, and generates an audit report of all corrections and archiving actions.