technical writer

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: Technical Writer
slug: technical-writer
description: Create clear, accurate technical documentation for developers and end users
category: writing
complexity: complex
version: "1.0.0"
author: "ID8Labs"
triggers:
  - "write documentation"
  - "create docs"
  - "technical writing"
  - "api documentation"
  - "user guide"
tags:
  - documentation
  - api-docs
  - user-guides
  - technical-communication
---

# Technical Writer

Transform complex technical concepts into clear, accessible documentation that helps users succeed. This skill specializes in creating API documentation, user guides, README files, tutorials, and reference materials that balance technical accuracy with readability.

Whether you're documenting code libraries, software products, system architectures, or processes, this skill ensures your documentation is comprehensive, well-organized, and genuinely helpful. It follows industry best practices for structure, formatting, and content organization.

Ideal for software developers, DevOps engineers, product managers, and technical teams who need to create documentation that both technical and non-technical audiences can understand and use effectively.

## Core Workflows

### Workflow 1: API Documentation
1. **Analyze Codebase** - Review API endpoints, parameters, responses
2. **Structure Reference** - Organize by resource/endpoint with consistent formatting
3. **Document Endpoints** - Write clear descriptions, parameters, request/response examples
4. **Add Code Samples** - Include examples in multiple languages
5. **Create Quick Start** - Write getting-started guide with authentication
6. **Build Error Reference** - Document error codes and troubleshooting
7. **Generate OpenAPI Spec** - Create machine-readable API specification

### Workflow 2: User Guide Creation
1. **Audience Analysis** - Identify user personas and skill levels
2. **Task Mapping** - List all user tasks and workflows
3. **Content Outline** - Structure guide by user journey, not features
4. **Write Procedures** - Create step-by-step instructions with screenshots
5. **Add Context** - Explain why and when, not just how
6. **Build Navigation** - Create clear TOC, index, and search keywords
7. **Test Documentation** - Validate against real user scenarios

### Workflow 3: README Excellence
1. **Project Overview** - One-paragraph description of what it does
2. **Installation** - Clear setup instructions with prerequisites
3. **Quick Start** - Minimal example to get running fast
4. **Usage Examples** - Real-world code samples with explanations
5. **Configuration** - Document all options, environment variables, flags
6. **Contributing** - Guidelines for contributions and development setup
7. **License & Credits** - Legal info and acknowledgments

### Workflow 4: Architecture Documentation
1. **System Overview** - High-level diagram and description
2. **Component Breakdown** - Detail each major component and responsibility
3. **Data Flow** - Document how information moves through system
4. **Deployment** - Infrastructure, scaling, monitoring considerations
5. **Security Model** - Authentication, authorization, data protection
6. **Decision Records** - Document architectural decisions and rationale

## Quick Reference

| Action | Command/Trigger |
|--------|-----------------|
| Create API docs | "Document this API" |
| Write README | "Create README for this project" |
| User guide | "Write user guide for [feature]" |
| Troubleshooting section | "Create troubleshooting guide" |
| Tutorial | "Write tutorial for [task]" |
| Release notes | "Generate release notes from changes" |
| Migration guide | "Write migration guide to [version]" |
| Code comments | "Document this code" |

## Best Practices

- **Start with why** - Explain purpose and use cases before diving into details
- **Show working examples** - Every concept needs a concrete code sample
- **Be consistent** - Use same terminology, formatting, and structure throughout
- **Write for scanning** -