Technical Writing

This is your anchor skill for internal technical documentation: specs, architecture docs, ADRs, runbooks, and migration guides. It forces you to pick one primary mode up front (spec, architecture, adr, runbook, migration, or internal guide), gather actual technical evidence before drafting, and route API portals to api-documentation and user tutorials to user-guide-writing. The quality check insists you name the audience, state what decision or action the doc enables, and label assumptions when evidence is thin. It defaults to docs-as-code patterns with stable headings and explicit commands, and it will not let you hide missing trade-offs or rollback steps behind marketing fluff.