Auto-sync: wiki-ingest 3 sources (2026-04-16)

This commit is contained in:
2026-04-16 00:08:35 +08:00
parent 9688f3f54b
commit 5ae9550d8c
267 changed files with 9537 additions and 1163 deletions

View File

@@ -1,44 +1,37 @@
---
title: "Multi-Agent Specialized Team (Solo Founder Setup)"
title: "Multi-Agent Specialized TeamSolo Founder 模式)"
type: source
tags: [openclaw, multi-agent, telegram, solo-founder, workflow]
date: 2026-04-15
tags: [multi-agent, openclaw, solo-founder, team, telegram]
date: 2026-04-13
---
## Source File
- [[raw/Agent/usecases/multi-agent-team.md]]
## Summary
- 核心主题Solo founder 通过多 Agent 虚拟团队实现 24/7 全天候工作能力
- 问题域:单一 Agent 无法高效处理多领域工作Context 切换破坏深度工作;知识孤岛导致洞察无法跨 Agent 流动
- 方法/机制:专业化 Agent(各角色独立模型/人格)+ 共享记忆GOALS.md/DECISIONS.md+ 私有上下文 + Telegram 统一入口 + 定时主动任务
- 结论/价值:从 2 Agent 开始按瓶颈扩展;定时任务是价值飞轮;团队协作产生真正价值
- 核心主题Solo Founder 如何通过多 Agent 专精团队实现 24/7 全天候工作能力
- 问题域:单一 Agent 无法同时擅长战略/开发/营销/销售;角色切换破坏深度工作
- 方法/机制:每个 Agent 独立角色+人格+模型,通过共享内存协作,Telegram 统一入口
- 结论/价值:从"管理一个工具"到"指挥一个团队"的范式转变Agent 主动推送而非被动响应
## Key Claims
- 单一 Agent 无法高效处理战略/开发/营销/分析多领域context window 快速填满
- 共享记忆GOALS.md/DECISIONS.md+ 私有上下文是多 Agent 协作核心
- 所有 Agent 通过同一 Telegram 群聊控制,各自只响应被 @ 的消息
- 定时主动任务(早会摘要/指标推送/内容创意)是价值飞轮
- 从 2 Agent 开始,不是一上来建 4 个团队
- [[Trebuh]] 的实践4 个 AgentMilo/Josh/Marketing/Dev+ Telegram + VPS描述为"真正的 24/7 小团队"
- 2 Agent 起步Lead + 1 专精),按瓶颈扩展,而非一上来建 4 个团队
- 共享内存GOALS.md/DECISIONS.md/PROJECT_STATUS.md+ 私有上下文是关键组合
- 定时主动任务(早会摘要/指标推送/内容创意)是真正的价值杠杆
- Telegram 单群聊入口 + @AgentName 路由 + 无@默认 Lead
## Key Quotes
> "Start with 2, not 4: Begin with a lead + one specialist, then add agents as you identify bottlenecks" — 实践总结
> "The real value emerges when agents proactively surface insights, not just when you ask" — 定时任务价值
> "Personality matters more than you'd think: Giving agents distinct names and communication styles makes it natural to talk to your team" — Trebuh
## Key Concepts
- [[共享记忆模式]]GOALS.mdOKR与优先级所有Agent可读+ DECISIONS.md关键决策日志+ PROJECT_STATUS.md当前项目状态
- [[定时主动任务]]Agent 主动在后台工作并推送结果,而非等待用户请求
- [[Multi-Agent Hierarchy]]团队层级架构Lead Agent 协调 + Specialist Agent 执行
- [[Telegram路由]]:单群聊入口 + @AgentName 路由 + 无@默认 Lead Agent
> "A real small team available 24/7." — [[Trebuh]] 描述其 4 Agent 团队
## Key Entities
- [[Trebuh]]Solo founder4 Agent 团队实践者,通过 X 分享案例
- [[OpenClaw]]:多 Agent 管理平台,支持 sessions_spawn/sessions_send/Telegram skill
- [[Trebuh]]Solo founder4 Agent 团队Milo/Josh/Marketing/Dev+ Telegram + VPS 实践者
- [[OpenClaw]]:多 Agent 协作框架,支持 sessions_spawn/sessions_send/共享文件系统
- [[Claude Code]]深度代码任务执行Agent 模式)
- [[Telegram]]:统一控制平面,单群聊入口实现多 Agent 路由
## Connections
- [[Trebuh]] ← 实践者 ← [[Multi-Agent Specialized Team]]
- [[OpenClaw]] ← 平台 ← [[Multi-Agent Specialized Team]]
- [[共享记忆模式]] ← 核心机制 ← [[Multi-Agent Specialized Team]]
- [[定时主动任务]] ← 价值飞轮 ← [[Multi-Agent Specialized Team]]
- [[Multi-Agent-Specialized-Team-Solo-Founder-Setup]] ← implements ← [[Multi-Agent Hierarchy]]Supervisor=LeadWorker=专精 Agent
- [[Multi-Agent-Specialized-Team-Solo-Founder-Setup]] ← shares_pattern ← [[Autonomous-Project-Management]](共享状态协调模式)
- [[Multi-Agent-Specialized-Team-Solo-Founder-Setup]] ← extends ← [[Multi-Agent-System-Reliability-Alex-Ewerlof]]Hierarchy 模式的 OpenClaw 具体实践)
- [[Multi-Agent-Specialized-Team-Solo-Founder-Setup]] ← uses ← [[共享内存模式]]GOALS.md/DECISIONS.md/PROJECT_STATUS.md
- [[Multi-Agent-Specialized-Team-Solo-Founder-Setup]] ← enables ← [[定时主动任务]]Agent 主动后台工作推送结果)