documentation-verificationlisted

# Documentation Verification Use this skill when a docs change needs evidence, not just a writing pass. - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## Activation Conditions Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below. - Reviewing docs before merge or release - Checking README, setup, or config accuracy - Verifying local links, commands, and code samples - Confirming docs changed alongside user-facing behavior ## Verification Workflow 1. Confirm the docs cover the changed behavior. 2. Check relative links and referenced files. 3. Validate commands and snippets where feasible. 4. Report missing coverage and stale claims explicitly. ## Documentation Stack Reference Inherit the shared stack from [documentation-patterns](../documentation-patterns/SKILL.md#shared-documentation-stack): source-of-truth discovery, audience framing, structure selection, verification, and freshness checks. Keep this skill focused on final evidence checks instead of restating the full stack. ## Anti-Patterns - Writing for the author instead of the reader: It bakes in unstated context and leaves the actual audience unsure what to do next. - Skipping concrete examples or commands: Abstract guidance is easy to approve and hard to apply correctly. - Letting links, screenshots, or versions drift: Polished formatting does not help if the instructions are no longer true. ## Verification Protocol B