Documentation Authoring

Use this skill when documentation should feel useful, clear, and worth reading.

Documentation is a product experience. The job is not only to preserve facts; it is to help a real reader build the right mental model with the least frustration.

Do not activate this skill for read-only documentation tasks. If the user only asks to read docs, inspect docs, find facts, summarize existing docs, or gather context from docs, use normal reading and analysis first. Activate this skill only when the expected output is authored documentation, documentation critique, or an edit to a documentation artifact.

Operating Loop

1. Identify the document type and reader.
2. Establish what the reader is trying to do, decide, review, or understand.
3. Infer the reader's likely state: rushed, skeptical, curious, blocked, tired, or new to the topic.
4. Load the smallest reference set that fits the document.
5. Draft around the reader journey first, then add technical detail where it earns its place.
6. Run a calibration pass for clarity, usefulness, tone, and document-specific expectations.

Ask questions only when the missing context would materially change the document. Otherwise, make a reasonable assumption and state it.