technical-documentation-writer

Provide the repo contents and target audience, and the Skill builds a doc brief first, then drafts a README with prerequisites, installation steps, a first success path, verification, and common failure troubleshooting. It grounds every step in evidence from the repo rather than guessing.

API usage guides are treated as reference documents covering authentication, version scope, endpoints, request parameters, success and failure response examples, limits, and common errors. Uncertain fields are explicitly marked as to-be-confirmed instead of being fabricated.

Diataxis classifies documentation into four types: tutorials for learning, how-to guides for tasks, reference for lookup, and explanation for understanding. This Skill routes each document to one primary type before drafting so content structure matches reader intent.

Yes, docs gap analysis produces a documentation map listing existing docs, missing docs, target audiences, priorities with rationale, and recommended templates. It also includes a Python script that scores Markdown drafts against required sections for each document type.

It is out of scope for PRDs, product specs, acceptance criteria, marketing copy, and slide decks. Requests to define requirements for features that do not exist yet should go to a spec or requirements workflow instead.