1---2name: technical-writing3description: Invoke this skill whenever you need to create, update, review, restructure, or audit technical documentation such as README files, user manuals, API documentation, architecture notes, setup guides, troubleshooting guides, or developer docs. Use it to align docs with source code, existing project conventions, and the intended audience.4---56## Source First78- Read relevant project instructions and existing documentation before writing. Check for files such as `AGENTS.md`, `README.md`, `docs/`, `.agents/`, `.codex/`, or repository-specific documentation guidance.9- Verify technical claims against source code, schemas, configuration, command output, APIs, or authoritative references. Do not rely on plausible implementation guesses when the repository can answer the question.10- Preserve existing documentation conventions for headings, tone, formatting, examples, terminology, and file placement unless the user asks for a broader rewrite.11- When updating existing docs, rewrite stale content in place. Avoid appending correction notes unless the document intentionally keeps historical context.12- Keep the documentation scoped to what the user asked for. Link to adjacent topics instead of explaining unrelated systems in detail.1314## Target Audience1516- Identify the likely audience from the document type, repository context, and user request. State or apply that assumption when it affects depth, examples, or terminology.17- Ask for clarification only when the audience ambiguity would materially change the structure or technical level of the documentation.1819## Language and Structure2021- Use clear, direct language. Avoid jargon, complex sentences, and unnecessary technical terms.22- Use the repository's established terminology. Do not introduce synonyms for existing concepts unless you are intentionally standardizing inconsistent language.23- Organize content with headings, bullets, numbered steps, tables, or examples when they make the material easier to scan.24- Include code snippets, commands, API examples, diagrams, or screenshots only when they help the reader complete the task or understand the system.25- Avoid duplicate content. If existing documentation already covers a topic, link to it or update the source document instead of copying it into a new place.2627## Review and Edit2829- Proofread for grammar, spelling, formatting, and consistency.30- Verify that links, references, commands, examples, and file paths are correct and functional when practical.31- Check that the final document answers the user's request, matches the intended audience, and does not over-document auxiliary topics.
hmans