sync-patterns

What problem does it solve?

Maintaining alignment between project specifications and actual code implementation is a constant challenge, leading to outdated documentation, unclear progress, and potential discrepancies. This skill automates the synchronization process, reducing documentation debt and improving project visibility.

Core Features & Use Cases

• Spec-Code Comparison: Compares requirements from spec files against codebase evidence (tests, implementations, configs) to report on implemented vs. pending features and calculate coverage percentage.
• Automated Status Updates: Updates status markers (complete, in-progress, pending, blocked) in spec documents, including timestamps and history, ensuring documentation reflects current reality.
• Completed Task Identification: Scans code for evidence of completed tasks (e.g., passing tests, implemented functions) that are not yet marked in specs, prompting necessary updates.
• Comprehensive Sync Reports: Generates detailed reports for the entire project or specific specs, including sync percentage, discrepancies, and recommendations for next steps.
• Use Case: A project manager wants to verify that all features defined in the authentication.md specification have been implemented in the src/ codebase. This skill can compare the spec against the code, identify any completed tasks not yet marked, update the spec's status to "complete" if applicable, and generate a full sync report for the entire project.

Quick Start

Compare the 'specs/feature-auth.md' file with the 'src/' directory to see implementation coverage, then generate a comprehensive sync report for the entire 'specs/' directory.