菜单
Outbox sweep — dispatches the `outbox-sweeper` subagent to find new PM messages across every sibling project, archive them, and roll up agent feedback. The subagent returns a JSON summary; Lilo only relays to the operator if anything was found. Use when the operator says "/sweep" or "sweep now".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
First-run setup script Lilo follows on a fresh clone. Walks the operator through `.mcp.json`, the tools-bridge venv, `USER.md`, optional platform MCPs (`ios-simulator` on macOS), Telegram setup, the optional Notion pipeline dashboard, and an optional smoke-test project. Use when the operator says "bootstrap", "walk me through setup", "first-time setup", or anything clearly equivalent. Skip steps that are already done (e.g. if `USER.md` exists and looks complete, confirm it and move on).
Scaffold a new Claude Code project as a sibling of the orchestrator repo. Use when the operator says "new project <name>", "start a project called X", "spin up X", "scaffold X", or anything equivalent. All projects scaffold with the team template (PM + specialist agents) and auto-launch the PM in tmux. Accepts an optional `--profile mvp|work` to layer a config overlay on top of the base team template (default: `mvp`). Use `--profile work` for paid-client projects that need tighter permissions and work-only MCP connectors (HubSpot, GitHub, ClickUp, Figma).
Run `/sweep`, then run `/pipeline` only if the sweeper returned non-empty messages. Use when the operator says "/sync" or "sweep and refresh now".
Package a sibling project into the tools framework so it's callable via the custom MCP bridge. Use when the operator says to toolify a project or asks to expose a project as a tool.
Pre-exit scan for this Lilo session — save memory-worthy lessons silently, commit and push routine changes, branch off anything risky. Use when the operator says "/kill", "kill the session", "wrap up", or signals the session is ending. NOT for killing PM tmux sessions.
Pre-exit scan for this PM session — finalize outbox, persist state, commit and push routine changes, branch off anything risky. Use when Lilo or the operator says "/kill", "wrap up", "save and close", or signals the PM session is ending. NOT for killing tmux sessions of other projects.
| name | sweep |
| description | Outbox sweep — dispatches the `outbox-sweeper` subagent to find new PM messages across every sibling project, archive them, and roll up agent feedback. The subagent returns a JSON summary; Lilo only relays to the operator if anything was found. Use when the operator says "/sweep" or "sweep now". |
Thin dispatcher. The real work happens in the outbox-sweeper subagent — Lilo only spends context when the sweep finds something.
Always dispatch with run_in_background: true so the cron tick (or manual fire) does not block Lilo's main loop. You will be notified when the subagent completes, and you handle Step 2 then.
Agent({
subagent_type: "outbox-sweeper",
description: "Outbox sweep",
prompt: "Sweep all sibling outboxes. Return the JSON summary.",
run_in_background: true
})
The subagent does all the filesystem work, archives to processed/, appends done-message ratings to agent-feedback.jsonl, and runs aggregate-feedback.sh if any done was processed. Returns:
{
"messages": [{path_original, path_archived, content}, ...],
"feedback_aggregation": {flagged, summary} | null,
"errors": [...]
}
messages empty AND errors empty: stay completely silent. This is the common case (no operator-visible output).messages non-empty: route each per the routing table in team-ops SKILL section 2 (blocker/high → immediate; status/low → batch; etc.). Lead with summary, include project: as context, quote detail verbatim. If the operator is at the terminal, reply terse there; do not dual-post to Telegram.feedback_aggregation.flagged_count > 0: for each flagged agent, read templates/team/.claude/agent-registry/<agent>.md, eyeball the adequate-notes themes, decide whether to refine the spec. Tell the operator what changed (or that you looked and nothing needed action).errors non-empty: surface briefly to the operator regardless of cron vs manual — broken telemetry should not be silent.