documentation-qualitylisted

# Documentation Quality Standards Use this skill when documentation should be judged against explicit standards instead of subjective preference. - 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 - Creating or updating a style guide - Defining expectations for examples, structure, and terminology - Auditing a docs set for consistency and readability ## Core Standards - Clear audience and scope - Stable heading hierarchy - Runnable or honest examples - Consistent terminology - Explicit edge cases, constraints, and failure modes ## 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 quality gates 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 Before claiming "ski