docs-updater
Automatically updates living documentation to reflect implementation progress by syncing task completion, changing [DRAFT] to [COMPLETE], and maintaining bidirectional links between code and docs.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install anton-abyzov-specweave-docs-updater
Repository
Skill path: plugins/specweave/skills/docs-updater
Automatically updates living documentation to reflect implementation progress by syncing task completion, changing [DRAFT] to [COMPLETE], and maintaining bidirectional links between code and docs.
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Full Stack, Tech Writer.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: anton-abyzov.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install docs-updater into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/anton-abyzov/specweave before adding docs-updater to shared team environments
- Use docs-updater for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: docs-updater description: Updates living documentation during implementation. Syncs task completion to docs, changes [DRAFT] to [COMPLETE], maintains bidirectional links. Activates for update docs, sync documentation, mark complete, documentation updates, living docs sync. --- # Documentation Updater Updates product documentation (.specweave/docs/) based on implementation progress. ## When to Use - Task specifies documentation updates in tasks.md - Feature implementation is complete - User says "update documentation" or "sync docs" - After closing increment to ensure docs reflect reality ## What It Does 1. **Reads task requirements** - Understands what was implemented from tasks.md 2. **Updates living docs** - Modifies `.specweave/docs/` files with actual implementation 3. **Status tracking** - Changes `[DRAFT]` � `[COMPLETE]` on doc sections 4. **Bidirectional links** - Maintains links between docs and increments 5. **Format adaptation** - Matches existing doc structure (features/ or modules/) ## Workflow ``` 1. Read tasks.md � Find documentation tasks 2. Read implementation � Understand what changed 3. Update docs � Add real code examples, endpoints, configs 4. Mark complete � Change [DRAFT] to [COMPLETE] 5. Verify links � Ensure increment � doc references work ``` ## Example **tasks.md says:** ```markdown **Documentation Updates**: - [ ] .specweave/docs/features/payment.md [DRAFT] - [ ] .specweave/docs/api/payments.md [DRAFT] ``` **docs-updater does:** 1. Reads payment implementation code 2. Updates `payment.md` with actual code examples 3. Updates API docs with real endpoints discovered in code 4. Changes status to `[COMPLETE]` ## Integration Points - **Called by**: spec-generator, task completion hooks - **Updates**: `.specweave/docs/**/*.md` - **Reads**: `tasks.md`, implementation code ## Best Practices - Run after completing feature tasks, not during - Verify doc links are valid (use relative paths) - Keep examples in sync with actual code - Don't over-document - focus on what users need