实验室Lab / 可跑路径Playbooks / 工程工头(专科 Bot + Cloud Agent) Engineering foreman (specialist bots + Cloud Agents)
工程工头(专科 Bot + Cloud Agent) Engineering foreman (specialist bots + Cloud Agents)
Engineering foreman (specialist bots + Cloud Agents)
复用 Lingxi 的方法:专科工头 Bot 拉起 Cloud Agent,共享状态,用截图或 CI 当证据。人守合入。不要追「200 agents / 2000 PRs」——那是作者场景,本实验室未核实。 Reuse Lingxi’s method: specialist boss bots spawn Cloud Agents, share state, and accept screenshot or CI evidence. A human holds merge. Do not chase “200 agents / 2000 PRs” — that is the author’s scene, unverified for this lab.
丢到这桌Drop into this desk 工程工头 丢给工程工头 Bot / 工程频道(人守合入) Engineering foreman Paste to the engineering-foreman bot / engineering channel (human holds merge)
复制后丢进对应桌。本站不代发。Copy, then drop into the desk. This site does not send.
【开跑 brief · 2026-09-12】 路径:工程工头(专科 Bot + Cloud Agent) 丢到:工程工头 粘贴处:丢给工程工头 Bot / 工程频道(人守合入) 任务: 复用 Lingxi 的方法:专科工头 Bot 拉起 Cloud Agent,共享状态,用截图或 CI 当证据。人守合入。不要追「200 agents / 2000 PRs」——那是作者场景,本实验室未核实。 步骤: 1. 先定一个专科工头 — 只覆盖一类活:复现、草稿 PR、或过夜巡检。不要一上来编成「工程组织」。 2. 工头拉 Cloud Agent — 对照官方 Cloud Agent Orchestrator:拉起 run、追卡住的、交汇总。工头分派,不自己改生产。 3. 共享状态 — 用 Notion 或本仓库的 issue/PR 当状态机。谁在跑、卡在哪、证据在哪,写在同一处。 4. 证据验收 — 截图、CI、或可复现步骤。没有证据不算完成。不要用未核实的规模数字当成功标准。 5. 人守合入 — 低风险可过夜巡检;合入、改线上、花钱必须人审。复用方法,不追「200 / 2000」。 硬闸门: - 无人审不合入:不合并无人审的结果,不改生产,不扩大权限。 - 不追未核实规模:「200+ agent / 月合 2000+ PR」是 Lingxi 原文场景,本实验室未核实。只复用窄席、共享状态、证据验收。 完成定义: - 只覆盖一类活:复现、草稿 PR、或过夜巡检 - 工头分派,不自己改生产 - 截图、CI、或可复现步骤才算完成 - 合入必须人审;不追未核实的「200 / 2000」 - 本 brief 只交任务,站点不代合入
【Run brief · 2026-09-12】 Path: Engineering foreman (specialist bots + Cloud Agents) Desk: Engineering foreman Paste to: Paste to the engineering-foreman bot / engineering channel (human holds merge) Task: Reuse Lingxi’s method: specialist boss bots spawn Cloud Agents, share state, and accept screenshot or CI evidence. A human holds merge. Do not chase “200 agents / 2000 PRs” — that is the author’s scene, unverified for this lab. Steps: 1. Name one specialist foreman — Cover one kind of work: repros, draft PRs, or overnight patrols. Do not stand up an “engineering org” on day one. 2. The foreman spawns Cloud Agents — Follow the official Cloud Agent Orchestrator: start runs, chase stuck ones, return the summary. The foreman assigns; it does not change production. 3. Share one state — Use Notion or this repo’s issues/PRs as the state machine. Who is running, what is stuck, and where the evidence lives — one place. 4. Accept with evidence — A screenshot, CI, or a reproducible step. No evidence, not done. Unverified headcount is not a success metric. 5. A human holds merge — Low-risk overnight patrols are fine. Merges, live edits, and spending need a human. Reuse the method; do not chase “200 / 2000.” Hard gates: - No unreviewed merge:Do not merge unreviewed results, change production, or expand permissions. - Do not chase unverified scale:“200+ agents / 2000+ PRs a month” is Lingxi’s scene, unverified here. Reuse narrow seats, shared state, and evidence — not the numbers. Definition of done: - Cover one kind of work: repros, draft PRs, or overnight patrols - The foreman assigns; it does not change production - Screenshot, CI, or a reproducible step — or it is not done - A human holds merge. Do not chase unverified “200 / 2000” - This brief hands off a task. The site does not merge