sync-task

Align OpenSpec change documentation with current source code and report drift.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/minhquan2904/vibe-check-scam --skill sync-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-task
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/sync-task
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill sync-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often drifts from the actual implementation as changes accumulate. This Skill detects and fixes drift by aligning artifacts with current source code, ensuring consistency across OpenSpec changes and metadata.

Core Features & Use Cases

  • Drift detection and reporting against active and archived changes in openspec/changes
  • Auto-correction of documentation to reflect the implemented code
  • Update of last-sync metadata and generation of a concise sync report for audits

Quick Start

Run the sync-task skill on a change to begin drift detection and auto-correction against the current source.

Frequently Asked Questions about sync-task

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

FAQPage Schema
How do I fix documentation drift between OpenSpec changes and my source code?

To detect documentation drift, the Skill searches active and archived OpenSpec changes, reads metadata, and reports drift status against the current source code. It then auto-corrects the documentation to reflect the implemented code.

How do I synchronize OpenSpec artifacts with current implementations automatically?

Synchronize OpenSpec artifacts by running the Skill on a change to align documentation with implemented code. It then annotates corrections with warnings and updates last-sync metadata to generate a concise sync report.

Does the sync-task Skill work with archived changes in openspec/changes?

Yes, the Skill explicitly searches both active and archived changes within the openspec/changes directory. It reads metadata from these locations to identify and fix drift against the current source code.

What is the best way to audit documentation corrections after syncing code?

Review the generated sync report and warning annotations to audit documentation corrections after syncing code. The Skill updates last-sync metadata and produces a concise sync report specifically for audit purposes.

Why does my documentation drift after accumulating code changes?

Documentation drifts because change artifacts fail to reflect new source code implementations as changes accumulate. The Skill resolves this by detecting the drift, auto-correcting the documentation, and re-aligning it with the current codebase.