
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.
- skills.sh installs
- 218
- GitHub stars
- 22
- last updated
- Jun 3, 2026
Install
$ npx -y skills add akillness/oh-my-skills --skill technical-writing --agent claude-codeInstalls into .claude/skills of the current project.
Files
Technical Writing
Use this skill when the deliverable is internal technical documentation for builders and operators.
technical-writing is the documentation-cluster anchor for:
- technical specs
- architecture docs
- ADRs / decision records
- runbooks and incident procedures
- rollout / rollback / migration guides
- developer-facing implementation or maintenance guides
Read these support docs before choosing the mode or boundary:
Sponsors
Details
- Repository
- github.com/akillness/oh-my-skills
- Category
- Documentation
- First seen
- Jun 3, 2026
More from akillness/oh-my-skills
All 81- Frontend Design System216
- Backend Testing211
- Rtk210
- Remotion Video Production206
- Video Production203
- Research Paper Writing196
- Web Accessibility192
- Graphify191
- Presentation Builder189
- Web Design Guidelines189
- Task Planning188
- User Guide Writing188
- Responsive Design187
- File Organization185
- Vibe Kanban185
- Codebase Search182
- Omc180
- Omx180
- Looker Studio Bigquery179
- Bmad Gds178
- Survey178
- Autoresearch177
- Design System177
- Google Workspace177