document-writer

Technical documentation using the Diátaxis framework is classified into exactly one of Tutorial, How-to, Reference, or Explanation types to prevent type-mixing confusion. This approach ensures each document serves a specific reader need, producing structured content for engineering and end-user consumption with runnable examples.

Generating an API reference with runnable examples requires following explicit templates and style rules that enforce active voice and consistent formatting. This approach produces high-quality technical documentation artifacts that include error cases and accurate, reader-focused content for engineering consumption.

Writing a runbook for SRE incident response involves specifying prerequisites, exact commands, expected outputs, and escalation procedures for responders. This structured approach ensures the technical documentation artifact is accurate and actionable during alerts like a database latency spike.

Generating Architecture Decision Records and changelogs is supported as task-specific technical documentation outputs. The skill produces these artifacts using consistent terminology and explicit formatting templates, ensuring accurate recording of architectural decisions and software changes for engineering teams.

The documentation writer requires confirmation before creating or overwriting files as part of its documentation planning and safety checks. This mechanism announces intended changes, clarifies the doc type, and asks for user approval to prevent accidental data loss during artifact generation.

A documentation audit evaluates existing content for consistency, accuracy, and completeness, while documentation-site structure involves organizing information architecture for optimal reader access. This skill enforces Diátaxis classification and style guardrails to produce a reader-focused site map.