writing-technical

What problem does it solve?

Writing that assumes prior knowledge leaves readers stuck, and gaps in audience calibration, sequence, precision, and examples make even “complete” technical documentation unusable.

Core Features & Use Cases

• Audience-calibrated audit: Reframes the documentation test around whether the assumed reader can complete the task using only the document.
• Completeness, sequence, precision, and examples checks: Identifies missing prerequisites, ordering mistakes, ambiguous instructions, inconsistent terminology, and non-obvious steps without concrete examples.
• Rewrite guidance: Produces targeted rewrite suggestions to repair the worst failures and restore clarity.

Use it when your API docs are missing steps, your user guide leaves gaps, or your specification is hard to follow for readers who do not already know the system’s mental model.

Quick Start

Use the writing-technical skill to audit a document you are shipping and return an actionable technical writing audit plus rewrite suggestions.