blackboard

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Blackboard 黑板

Blackboard

blackboard = 当前目录的

.yomi/boards/<feature>.md

,一个 feature 一块 board。一个目录可能同时有 n 个 feature 在跑,每个 feature 的 agent 团队各看各的 board。同一块 board 上的所有 agent 读同一个文件,一眼看到 peers 的 task、progress、findings——这是 task-tickets 没有的视角(ticket 里 worker 只看得到自己的那张)。

分工:派单/签收/状态机/验收走 task-tickets;blackboard 管 peer visibility(progress 与 findings),不是 task 的 system of record。

blackboard =

.yomi/boards/<feature>.md

in the current directory, one board per feature. A directory may have n features running simultaneously, and the agent teams for each feature view their own respective boards. All agents on the same board read the same file, and can see peers' tasks, progress, and findings at a glance — this is a perspective that task-tickets don't offer (workers only see their own ticket in the ticket system).

Division of responsibilities: Task assignment/sign-off/state machine/acceptance are handled via task-tickets; blackboard manages peer visibility (progress and findings), and is not the system of record for tasks.

位置与命名

Location and Naming

```
<feature>
```
= 开局者起的 feature slug(如
```
auth-refactor
```
);谁开局谁建 board(通常是 leader),按模板创建。
```
ls .yomi/boards/
```
列出本目录全部 in-flight 的 feature board。
spawn 子 agent 时在 prompt 里给 board 的绝对路径,不靠对方用自己的 CWD 猜(子目录里会建错 board);同一 feature 的所有 agent 必须拿到同一路径。
feature 收尾:leader 验收后删掉该 board,不让 board 越积越多。

```
<feature>
```
= the feature slug set by the initiator (e.g.,
```
auth-refactor
```
); the initiator (usually the leader) creates the board according to the template.
```
ls .yomi/boards/
```
lists all in-flight feature boards in the current directory.
When spawning a sub-agent, provide the absolute path of the board in the prompt, instead of relying on the other party to guess using their own CWD (which may lead to incorrect board creation in subdirectories); all agents of the same feature must receive the same path.
Feature wrap-up: After the leader accepts the work, delete the board to prevent accumulation of boards.

模板

Template

markdown

undefined

markdown

undefined

Board

Agents

<who>

task: <ticket id + title>
status: doing | done
progress: ...(最新一条)
updated_at: HH:MM
notes: ...(对 peers 有用的 findings)

undefined

task: <ticket id + title>
status: doing | done
progress: ...(latest entry)
updated_at: HH:MM
notes: ...(findings useful to peers)

undefined

规则

Rules

先 check-in 再开工 —— 领到活后在 Agents 下加自己的
```
### <who>
```
section,写上 task(ticket id + 标题)和第一条 progress。who = 角色名 + 自己系统提示 Environment 段的 session id 前缀,如
```
worker-auth sub_01KZ
```
(主 session 是
```
sess_*
```
,subagent 是
```
sub_*
```
;与 ticket 的 owner_session_id 同源)。
只改自己的 section —— progress 只留最新一条,顺手刷新 updated_at;对 peers 有用的 finding 写进自己的 notes 行。永不动别人的 section。
收工标 done —— status 改
```
done
```
,result 摘要写进 progress 行;leader 验收后删 section(整块 board 的删除见「位置与命名」)。
读 board —— 开工前、卡住时读一遍自己 feature 的 board:peer 可能已解决了你的问题,或在改你要改的文件。
并发 —— 同时写靠 edit 的精确匹配兜底:edit 失败 = 有人刚改过,re-read 再改。

完成判据:Agents 下的 section 与真实在跑的 agent 一一对应;每个 done section 带 result 摘要。

Check-in before starting work — After receiving a task, add your own
```
### <who>
```
section under Agents, write the task (ticket id + title) and the first progress entry. who = role name + the session id prefix from your system prompt's Environment section, e.g.,
```
worker-auth sub_01KZ
```
(main session is
```
sess_*
```
, subagent is
```
sub_*
```
; same source as the ticket's owner_session_id).
Only modify your own section — Keep only the latest progress entry, and refresh updated_at conveniently; write findings useful to peers into your notes line. Never modify others' sections.
Mark as done when finished — Change status to
```
done
```
, write a summary of the result into the progress line; after the leader accepts the work, delete the section (see "Location and Naming" for deleting the entire board).
Read the board — Read the board of your feature before starting work or when stuck: peers may have already solved your problem, or be modifying the file you need to change.
Concurrency — Concurrent writing is guaranteed by precise matching during editing: edit failure = someone just modified it, re-read and then edit again.

Completion criteria: The sections under Agents correspond one-to-one with the actually running agents; each done section includes a result summary.