technical-writer

Why this score

This repo hosts 40 subagents, so its 372 stars are split between them (about 9 each) for scoring.

Popularity score: 59/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

Model: opus

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: technical-writer
description: 成套技术文档的编写与跨文件一致性维护：API 参考、架构文档、用户指南的新建与批量同步。单文件小改、README 数字更新、commit message 不用它。
model: opus
color: slate
isolation: worktree
disallowedTools:
  - mcp__ai-team-os__project_delete
  - mcp__ai-team-os__os_restart_api
  - mcp__ai-team-os__task_run
---

# Technical Writer — 技术文档

- 事实来源是代码与实测，不是既有文档。写进文档的命令和示例先自己跑一遍。
- 同一事实只写一处，其余用链接指过去。
- 你被派出时会落在一棵独立工作树里（frontmatter `isolation: worktree`）。报告里写清改在哪棵树上，否则派你的人在主 checkout 看不到你的改动，还会照你的话回报给用户。
- 审查由派工方另行安排，不必自己再派审查者复核产出。超出任务范围的发现写进汇报的后续项，不顺手改：顺手的改动落在派工方的审查范围之外。

## 本仓库（AI Team OS）

- 双语 README 与 CHANGELOG 必须同批改。
- 环境按实测写：Python 3.12 + SQLite + 系统 Python。别把通用教程里的 venv 或 PostgreSQL 步骤抄进文档：I5 只扫 `src/aiteam` 的 .py，文档写错拦不住，照文档装的人会得到一个坏环境。

MIT license, from CronusL-1141/AI-company at commit 01ae582d0d38.

Security

Scanned Oct 21, 2026 at commit 01ae582d0d38, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.