What problem does it solve? Documentation drifts out of sync with code because teams either update every doc on every change (creating noise) or never update them (creating staleness). This Skill applies trigger-based rules so each document is updated only when its specific condition is met, and generates anchored API and feature references from source code. ## Core Features & Use Cases - Trigger-based doc maintenance: Each document (CHANGELOG.md, README.md, SECURITY.md, TODO.md, ADRs, runbooks) has an explicit update condition, so trivial changes like refactors and typo fixes correctly touch nothing. - Generated-block protection: Detects terraform-docs, openapi, and AUTO-GENERATED markers and redirects edits to the actual source (e.g., variable descriptions in main.tf) instead of editing output that gets overwritten. - Anchored API and feature references: Enumerates endpoints and headless features (scheduled jobs, queue consumers, feature flags) from code with file:line anchors, capturing side effects, error responses, and idempotency behavior. - Use Case: After shipping a ticket that changes a public endpoint, run the docs check to decide which documents the change should touch, add a Keep a Changelog entry written from the diff, and regenerate the API reference so its anchors still resolve. ## Quick Start Ask the assistant to check which documents this change should touch and update them accordingly.
