When should I not use this documentation skill?

It is not necessary for simple, single-purpose README files, code comments, or informal communication like emails and chat messages.

What is the purpose of the using-technical-writer skill?

It acts as a meta-skill or router that identifies your specific documentation task and loads the precise sub-skills needed for that format, such as ADRs, APIs, or runbooks.

Can this skill help with security documentation?

Yes, it features cross-faction routing that combines technical writing patterns with security architect skills to document threat models and compliance controls.

Does it support different target audiences?

Absolutely. It routes to different sub-skills based on whether you are writing for developers (deep technical depth), operators (step-by-step procedures), or executives (high-level summaries).

Technical Documentation Architect

Name: Technical Documentation Architect
Author: tachyon-beep

bytachyon-beep

•

Learning & Documentation

Routes documentation tasks to specialized writing skills for architecture decisions, APIs, runbooks, and security guides.

About

This meta-skill optimizes the technical documentation process by intelligently routing users to specialized templates and style guides based on their specific needs. Whether you are recording critical architectural decisions (ADRs), drafting operational runbooks, or generating comprehensive API references, this skill ensures you use the correct structural patterns and clarity standards. It streamlines the workflow by identifying the target audience—from developers needing diagrams to executives requiring high-level summaries—and loading only the necessary domain-specific guidance.

Key Features

5 GitHub stars
Intelligent routing for ADRs, APIs, and operational runbooks
Audience-specific tailoring for developers, operators, and executives
Cross-faction integration for security and compliance documentation
Structured guidance for complex README and project documentation
Decision logic for loading core vs. specialized extension skills

Use Cases

Generating Architecture Decision Records (ADRs) with context and consequences
Creating comprehensive API references and developer-facing guides
Drafting operational runbooks and incident response procedures

About

Key Features

5 GitHub stars
Intelligent routing for ADRs, APIs, and operational runbooks
Audience-specific tailoring for developers, operators, and executives
Cross-faction integration for security and compliance documentation
Structured guidance for complex README and project documentation
Decision logic for loading core vs. specialized extension skills

Use Cases

Generating Architecture Decision Records (ADRs) with context and consequences
Creating comprehensive API references and developer-facing guides
Drafting operational runbooks and incident response procedures