>
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
| Code | Status | Meaning |
|---|---|---|
| 0 | Success | All updates successful |
| 1 | Partial | Some updates failed |
| 3 | Error | Required files missing |
Sections Updated
README.md
| Section | Marker | Content 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
| Section | Marker | Content Source |
|---|---|---|
| Unreleased | <!-- speckit:start:unreleased --> |
tasks.md completed tasks |
Preservation Rules
- Content before the first marker is always preserved
- Content after the last marker is always preserved
- Content between different marker pairs is always preserved
- Only content within matching marker pairs is updated
- 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
You Might Also Like
Related Skills

update-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
vercel
docstring
Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
pytorch
docs-writer
Always use this skill when the task involves writing, reviewing, or editing files in the `/docs` directory or any `.md` files in the repository.
google-gemini
write-concept
Write or review JavaScript concept documentation pages for the 33 JavaScript Concepts project, following strict structure and quality guidelines
leonardomso
resource-curator
Find, evaluate, and maintain high-quality external resources for JavaScript concept documentation, including auditing for broken and outdated links
leonardomso
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
anthropics