skills.rest
vanman2024
vanman2024COMMUNITY
Explore all skills by this author →
GitHub

sync-patterns

Compare specification requirements against codebase implementation evidence and generate sync reports.

3|1|Updated Oct 23, 2025
Search Tags:#code quality#automation#reports#documentation#CI/CD#status updates#implementation tracking#spec sync
One-click install
npx skills add https://github.com/vanman2024/dev-lifecycle-marketplace --skill sync-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-patterns
Source: https://github.com/vanman2024/dev-lifecycle-marketplace/tree/main/plugins/iterate/skills/sync-patterns
Command: npx skills add https://github.com/vanman2024/dev-lifecycle-marketplace --skill sync-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

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.

Frequently Asked Questions about sync-patterns

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

FAQPage Schema
How do I compare specifications against code implementation to track what's been built?▼

Spec-code comparison identifies gaps between documented requirements and actual implementation by scanning your codebase for evidence of completed features, tests, and configs. It calculates coverage percentage and reports which requirements are implemented, in-progress, pending, or blocked.

Can I automatically update spec document status markers when code changes?▼

Yes. Automated status updates modify frontmatter fields in spec documents with completion markers, timestamps, and historical records, ensuring your documentation reflects current implementation reality without manual rewrites.

What's the best way to identify completed tasks in code that aren't yet marked in specifications?▼

Completed task identification scans your codebase for implementation evidence—passing tests, implemented functions, configuration changes—and surfaces tasks marked complete in code but not yet updated in specs, prompting necessary documentation updates.

How do I generate comprehensive sync reports showing spec-to-code alignment across my entire project?▼

Comprehensive sync reports output multi-format reports (Markdown, JSON, HTML) detailing sync percentages, discrepancies between specs and code, and recommendations for next steps across your entire project or specific specification files.

Do I need jq installed to run spec synchronization?▼

Yes. jq is a required dependency for filtering and processing specification and code metadata during the comparison and report generation process.

Related Skills

Explore More Product & Management Skills→
bodangrenbodangren
11

doc-indexer

Scan Markdown files in docs/ and extract YAML frontmatter metadata.

Community
Basic
fcamacholfcamachol

seguimiento

Monitor registration process statuses and trigger change notifications.

Community
Basic
QuilibriumNetworkQuilibriumNetwork
34

Changelog Generator

Generate Markdown and plain-text changelogs from git commits.

Official
Basic
moasadimoasadi
5

ddd-api-generator

Generate NestJS REST API endpoints with DTOs, controllers, and OpenAPI documentation.

Community
Advanced