What problem does it solve? After a feature passes implementation, evaluation, or UAT in an Agentic SDLC workflow, project-facing docs like README, changelog, usage guides, and examples often drift from actual behavior. This skill synchronizes those documents with verified implementation evidence without touching requirements or design specs. ## Core Features & Use Cases - Evidence-backed doc updates: Updates README, changelog, usage docs, examples, and generated docs only when implementation, validation, test, and evaluation evidence exists. - Steering integration: Consumes resolved docs-update steering entries and records their disposition as resolved, blocked, or superseded. - Changelog maintenance: Adds a single [Unreleased] entry when user-facing behavior changes, preserving existing grouping. - Use Case: After a feature passes evaluation, the SDLC coordinator routes to this skill to refresh the README and changelog, record documentation evidence under the private run directory, and hand off to spec alignment or PR creation. ## Quick Start Ask the Agentic SDLC coordinator to run the documentation update phase after feature evaluation so project docs match the implemented behavior.