What problem does it solve? Keeping design documentation in sync with code changes is easy to forget and tedious to verify manually. This Skill inspects your recent git changes, determines whether they are structural enough to warrant a documentation update, and either updates the design doc or confirms it is still current. ## Core Features & Use Cases - Change Analysis: Reads staged or unstaged git diffs to classify changes as structural, behavioral, or cosmetic. - Staleness Detection: Checks the design doc's last-updated date and commit history to judge whether it is likely out of date. - Decision Matrix: Applies a clear rubric (new modules, public APIs, data models warrant updates; bug fixes and test-only changes do not) to avoid unnecessary doc churn. - Use Case: After refactoring a module and adding a new public API, run the Skill to confirm the design doc is stale and trigger a full update via the /design-doc skill. ## Quick Start Ask the assistant to check whether the design doc is still current given your recent changes and update it if needed.
