supervisor-review
Playbook for the lead agent in titi that dispatches workers and accepts or rejects their output — verify artifacts not reports, return wrong work to the same worker, serialize shared files. Use when orchestrating subagents or reviewing a subagent's result.
- License 许可
- MIT
- 所属仓库
- robertt3kuk/titi
- 最近更新
- 2026-11-02
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- supervisor-review
- description
- Playbook for the lead agent in titi that dispatches workers and accepts or rejects their output — verify artifacts not reports, return wrong work to the same worker, serialize shared files. Use when orchestrating subagents or reviewing a subagent's result.
03 SKILL.md 正文
supervisor-review
You are the Integrator from docs/CONVEYOR.md. Workers (Scout, Worker,
Reviewer) report to you; you decide what lands on master.
Dispatch
- Each task states: goal, result format, files the worker owns, sources to read, and the DoD from the theme doc. Vague tasks duplicate work.
- 1 worker for a simple node, 2–4 for a medium one, cap ~6 per wave.
- Workers commit locally and do not push. Only you push accepted work
(skill
commit), so nothing lands onmasterbefore review. - File ownership: one writer per file at a time. Shared files (
Cargo.toml,Cargo.lock,crates/titi-cli/src/chat.rs,docs/research/STATE.md,AGENTS.md) — you grant access one worker at a time and release it when that worker reports.
omp mapping (when omp is the harness)
- Spawn with
task: implementation →task/grok-builder(@coding); review →reviewer(@review); a contested call →second-opinion(another model family, read-only); secrets/auth/injection →security. - Coordination through
hub:sendto a worker by exact roster id,jobsfor a status snapshot,waitonly when fully blocked. Messages are plain prose; artifacts go bylocal:///file path. - Other harnesses: use their subagent + message primitive the same way.
Status cadence
- Workers
sendafter every subtask: what changed (paths), what is left, blockers. No status → ask once viasend, don't poll with shell tools.
Accepting work — check the artifact, not the summary
- Read the diff yourself. Does it match the task and file ownership?
- Tests exist for the new contract and would fail without the change.
- Run skill
code-reviewagainst the diff. - Before pushing: the reviewer agent's verdict with file:line evidence.
After pushing: CI green on that commit (skill
ci-and-tests); red → fix forward with a focused commit. - "completed" from a worker means it stopped, not that it is correct.
Rejecting work
- Send it back to the same worker with concrete file:line feedback and the failed check. Do not accept partial fixes.
- Disagreement between worker and reviewer →
second-opinion, then decide. - 3 rework rounds on the same artifact → stop and escalate to the user with what was tried (CONVEYOR stop rule).
Integrate
- Land accepted work as focused commits (skill
commit), updatedocs/research/STATE.mdright after each status change.
04 同仓库更多 Skills
tui-smoke
Manually verify a titi TUI change in a real terminal and record it in docs/QA_STATUS.md. Use after changing titi-tui or titi-cli screen code, keys, slash commands, rendering, or when asked to smoke-test the chat.
skill-authoring
How to turn a recurring multi-step procedure in titi into a new project skill under .agents/skills, and wire it for every agent. Use when a 3+ step routine repeats, or the user says "make this a skill".
security-review
titi project security checklist for changes touching keys, providers, tools, approval, sessions, memory, or prompts. Use when a change handles credentials, runs commands, reads/writes files for the model, or when asked for a security review.
dependency-update
Add, bump, or remove a crate dependency in the titi workspace safely — justification, RustSec check, lockfile, one commit. Use when a change needs a new crate or a version bump.
commit
Commit and push a change in titi the project way — one concern per commit, Conventional Commits with a prose body, straight to origin master, never force. Use when asked to commit, push, save, or ship a change.
code-review
titi project self-review checklist for a titi change before calling it done — error handling, tests, engine boundary, secrets, commit hygiene. Use before reporting a task complete, or when asked to review a diff.