create-upsert-documentation

Documentation drift happens when code updates outpace wiki updates, leaving stale references. This Skill prevents drift by detecting outdated references, managing cross-links, and validating that functional descriptions and architecture notes reflect the latest implementation changes.

Updating wiki pages after an API change requires reading existing indexes, modifying affected pages, and creating new cross-links. This Skill orchestrates that synchronization workflow to ensure architecture notes, API documentation, and functional descriptions are updated together accurately.

Detecting stale references requires indexing documentation routing and validating links against recent implementation changes. This Skill identifies outdated cross-links and references across technical and functional documentation layers during feature development cycles.

Yes, this Skill is designed for dual-layer documentation updates, maintaining both developer-facing technical docs and product-facing functional docs. It routes each change to the appropriate documentation layer to keep your knowledge base accurate and discoverable.

You need a documentation synchronization workflow during feature development cycles, documentation refresh requests, or knowledge base maintenance. Run it after implementation changes to update indexes, manage cross-links, and validate that linked wiki pages remain accurate.