Skill: Validate Documentation

What This Skill Does

Answers the question: "Are my docs still accurate?" — without reading a single source file.

Uses git metadata (timestamps, diff stats, file lists) to detect which documentation is stale and which is current. Produces a structured staleness report that tells update-docs exactly which modules to target.

This is the CHECK path between generate-docs (create) and update-docs (update). Without it, update-docs must perform an expensive full-scan of all docs and all source files to determine what changed.

When to Use

• Before running update-docs — to scope the update to only stale modules
• At the start of a session — to understand documentation health before working
• When the user asks "are my docs up to date?" or "what's stale?"
• As part of smart-start — automatically invoked during session bootstrap
• After a series of commits — to check if documentation needs attention

Do NOT use this skill to actually update documentation — use update-docs with the staleness report as input.