Agent skill
docs-sync
Synchronizes documentation (README.md, CHANGELOG.md, API docs) with implementation. Preserves user content outside speckit markers. Updates are non-destructive and clearly delineated. Always run after /speckit.implement completes.
Install this agent skill to your Project
npx add-skill https://github.com/drillan/speckit-gates/tree/main/skills/docs-sync
Metadata
Additional technical details for this skill
- author
- drillan
- category
- automation
- repository
- https://github.com/drillan/speckit-gates
SKILL.md
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
implementation-verify
Verifies implementation against specifications by checking requirement fulfillment, task completion, and contract implementation. Generates a fulfillment report with coverage metrics. Always run after /speckit.implement completes.
docs-sync
Synchronizes documentation (README.md, CHANGELOG.md, API docs) with implementation. Preserves user content outside speckit markers. Updates are non-destructive and clearly delineated. Always run after /speckit.implement completes.
progress-report
Displays progress dashboard showing phase completion, blocked tasks, and remaining work estimate. Provides at-a-glance view of implementation status. Run anytime to check progress.
release-check
Validates all artifacts are complete and consistent for release. Checks spec kit artifacts, documentation, versioning, and API docs. Run before creating a release to ensure nothing is missing.
planning-validate
Validates planning artifacts (spec.md, plan.md, data-model.md, contracts/) for quality, completeness, and consistency. Checks for mandatory sections, cross-artifact consistency, and constitution compliance. Always run after /speckit.plan completes.
implementation-verify
Verifies implementation against specifications by checking requirement fulfillment, task completion, and contract implementation. Generates a fulfillment report with coverage metrics. Always run after /speckit.implement completes.
Didn't find tool you were looking for?