Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
drillan avatar

Docs Sync

  • 56 installs
  • 3 repo stars
  • Updated January 21, 2026
  • drillan/speckit-gates

Keeps documentation in sync with implementation as a spec-kit workflow progresses, so a solo builder's docs never drift from the code.

About

docs-sync is a Claude Code skill from the speckit-gates package, which adds automated quality gates to the spec-kit workflow. It synchronizes your documentation with the current implementation and reports a GREEN/YELLOW/RED status, so a solo builder catches docs that have drifted out of date instead of shipping stale references.

  • Syncs docs with implementation
  • Runs as a spec-kit quality gate
  • GREEN/YELLOW/RED status output

Docs Sync by the numbers

  • 56 all-time installs (skills.sh)
  • Ranked #784 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/drillan/speckit-gates --skill docs-sync

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs56
repo stars3
Last updatedJanuary 21, 2026
Repositorydrillan/speckit-gates

What it does

Keeps documentation in sync with implementation as a spec-kit workflow progresses, so a solo builder's docs never drift from the code.

Who is it for?

Developers using spec-kit who want docs to track implementation

When should I use this skill?

After an implementation step, to sync documentation

Files

SKILL.mdMarkdownGitHub ↗

docs-sync

Synchronizes documentation with implementation after /speckit.implement completes.

Purpose

This skill automatically updates documentation to reflect the implemented features. It:

  • Updates README.md: Adds/updates usage section with implementation details
  • Updates CHANGELOG.md: Adds entries for new features and changes
  • Updates API docs: Synchronizes API documentation with contracts
  • Preserves user content: Content outside speckit markers is never modified

Marker System

docs-sync uses HTML comment markers to delineate auto-generated sections:

<!-- speckit:start:section-name -->
Auto-generated content here
<!-- speckit:end:section-name -->

Content outside these markers is preserved exactly as-is.

Output

The skill outputs a DocsSyncResult showing:

  • Files created, updated, or unchanged
  • Sections modified within each file
  • Diff summary (lines added/removed/changed)
  • Any errors encountered

Usage

This skill runs automatically after /speckit.implement. You can also run it manually:

npx skills run docs-sync

Exit Codes

CodeStatusMeaning
0SuccessAll updates successful
1PartialSome updates failed
3ErrorRequired files missing

Sections Updated

README.md

SectionMarkerContent Source
Usage<!-- speckit:start:usage -->spec.md user stories
Installation<!-- speckit:start:installation -->plan.md dependencies
Features<!-- speckit:start:features -->spec.md functional requirements

CHANGELOG.md

SectionMarkerContent Source
Unreleased<!-- speckit:start:unreleased -->tasks.md completed tasks

Preservation Rules

1. Content before the first marker is always preserved 2. Content after the last marker is always preserved 3. Content between different marker pairs is always preserved 4. Only content within matching marker pairs is updated 5. If no markers exist, content is appended with new markers

Error Handling

  • Missing markers: Creates new markers and adds content
  • Malformed markers: Reports error, skips that section
  • File permissions: Reports error, continues with other files
  • Missing source files: Reports which sources are unavailable

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.