sync

Compare spec files against Git code changes to surface drift discrepancies.

2|Updated Mar 10, 2026

Search Tags:#validation #diff #archiving #drift #code #specs #lodge

Ready to run

npx skills add https://github.com/tim-hub/powerball --skill sync-tim-hub

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/tim-hub/powerball/tree/main/pbl/skills/sync
Command: npx skills add https://github.com/tim-hub/powerball --skill sync-tim-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift between spec artifacts (tasks, plan, checklist) and actual code changes can lead to misaligned deployments and failed archives. This Skill helps surface discrepancies so you can update specs or revert code before lodging.

Core Features & Use Cases

Drift comparison across specs and code
Clear discrepancy reporting to guide remediation
Use case: validating a spec before lodging to ensure changes are reflected in code

Quick Start

Create a spec directory and run the drift check to surface any mismatches.

Frequently Asked Questions about sync

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

FAQPage Schema

How do I detect drift between spec artifacts and actual code changes?▼

Spec drift is the divergence between planned spec artifacts (tasks.md, plan.md, checklist.md) and actual code changes. Surfacing these discrepancies before archiving ensures deployments match the intended design.

How do I validate a spec before lodging to ensure changes are reflected in code?▼

Running a drift check validates specs before lodging by comparing spec documents against Git history and code changes. This generates a reliable diff report that flags discrepancies for remediation.

Do I need Git history to compare specs and code for discrepancies?▼

Yes, you need Git history and access to the worktree to generate a reliable diff report. This history provides the baseline to accurately compare spec artifacts against corresponding code changes.

What is the best way to surface mismatches between plan documents and repository code?▼

The best way to surface mismatches is to apply a drift comparison across all spec worktrees. This directly compares planning documents against code changes to produce clear discrepancy reports guiding remediation.

Why does spec drift lead to failed archives and misaligned deployments?▼

Spec drift causes failed archives because spec artifacts like tasks, plans, and checklists no longer match actual code changes. Surfacing discrepancies lets you update specs or revert code before lodging.