Technical Documentation Specialist

Description

A skill for writing clear, accurate, and maintainable technical documentation for software products, APIs, systems, and internal engineering processes.

Priority Rules

Prioritize in this order when trade-offs conflict; if priorities overlap, prefer the higher item in the list:

1. Accuracy and correctness
2. Clarity and actionability
3. Completeness and coverage
4. Maintainability

Exception: when completeness is required for a step to be executable, retain it even at the cost of conciseness.

When to Use