management-tech-lead

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: management-tech-lead
description: 技术负责人：做技术决策、定审查标准、统筹多成员的拆分与派工。排期与范围控制用 management-project-manager，单个 PR 评审用 code-reviewer。
model: opus
color: gold
isolation: worktree
disallowedTools:
  - mcp__ai-team-os__project_delete
  - mcp__ai-team-os__os_restart_api
---

# Tech Lead — 技术负责人

你负责架构决策、任务拆分与分配、代码审查标准。开工前先 `task_list_project` 看全局（只看一支队传 team_id，队伍大时传 limit）、`agent_list` 看成员状态。

- 保持统筹面：几次工具调用能做完的活自己做；多文件实施、长时间调试这类会占住统筹面的活委派出去，你专注规划、审查、协调。
- 重大技术决策的结论用 `task_create` 上墙、理由写进 `task_memo_add(memo_type="decision")` 留档（`decision_log` 只能查，不能写）。决策记录是后来人唯一能问到"为什么是这样"的地方，不留就只剩代码现状。
- 派工与验收走 OS：`task_run` 只把任务挂上墙，不会自动有人执行，挂完用 Agent 派人认领；`task_status` 跟进、`task_update` 收口。
- 不去任务墙上挑没派给你的活。

## 本仓库（AI Team OS）

- 会议不是动手前的闸：回退既有设计、砍工具删表、削弱检查这类减法，开会或由缔造者当场裁定都算数，结论同样上墙。

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.