sync-status_skill

Overview

This skill inspects project implementation vs Plans.md and reports the current location of work. It identifies mismatches between task markers and actual commits/edits, updates Plans.md suggestions, and recommends the next high-priority action. Use it to get a factual, up-to-date progress snapshot and an actionable next step.

How this skill works

The skill collects Plans.md state, recent Git status/commits, and the agent trace of recently edited files to compare declared task markers (cc:TODO, cc:WIP, cc:done) with reality. It detects classes of differences (started but still TODO, committed but still WIP, done but uncommitted), proposes concrete Plans.md updates, and outputs a concise progress summary with prioritized next actions. It can flag anomalies such as many concurrent WIP tasks or unprocessed PM requests.

When to use it

• When you run the command '/sync-status' explicitly
• When you need an authoritative progress check tied to Plans.md
• Before a handoff or review to ensure Plans.md reflects reality
• When you want a suggested next action based on actual edits and commits
• When you need to detect drift between planned tasks and recent work

Best practices

• Run only for explicit status-sync intents (avoid for casual status chat)
• Ensure recent commits are present locally before invoking to get accurate results
• Review the proposed Plans.md updates before applying them to keep semantic intent
• Use alongside /work or /harness-review to move from insight to action
• Address flagged anomalies (multiple WIPs, unprocessed requests) before expanding scope

Example use cases

• You suspect work progressed but Plans.md still shows cc:WIP — run /sync-status to reconcile and mark completed items
• A reviewer needs current project progress and a suggested next task before starting a review session
• Before a release or demo, verify that Plans.md and commits align and update markers where necessary
• When multiple agents edited files recently, generate an authoritative list of changed files and which tasks they affect
• Automate a periodic check in a CI step to surface drift between Plans.md and repository state