using-technical-writer

This meta-skill routes documentation tasks by document type and audience. API docs describe endpoints and integration; ADRs capture architectural decisions; runbooks provide operational procedures; security docs address threats and compliance. The router directs you to the appropriate sub-skill based on your deliverable and intended readers.

The API documentation sub-skill provides templates and structure guidance. It covers endpoint description, parameters, responses, error codes, and usage examples aligned to your REST API design. Route through this skill to access standards for clarity and completeness.

ADRs document significant architectural choices, trade-offs, and rationale for future maintainers. Use an ADR when a decision affects system structure, impacts multiple components, or resolves competing approaches. This skill routes ADR requests to the appropriate documentation sub-skill with templates and examples.

Runbooks provide step-by-step procedures for incident response, deployments, and maintenance tasks. This skill routes runbook requests to the correct sub-skill, which supplies structure guidance, templates, and best practices for clarity, automation references, and audience-appropriate detail.

Yes. This meta-skill routes governance documentation tasks alongside API docs, ADRs, runbooks, and security docs. It aligns document type, audience, and delivery format to load the most appropriate sub-skill with relevant templates and structural guidance.

Security documentation is in scope. This skill routes security-docs requests by audience and threat context, directing you to sub-skills with templates, compliance alignment, and structure for threat models, incident procedures, and access controls.