메뉴
Use when root reef must supervise the fleet, maintain continuity across turns, detect drift or stalls, and decide when to steer, recover, schedule follow-up, or clean up.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | root-supervision |
| description | Use when root reef must supervise the fleet, maintain continuity across turns, detect drift or stalls, and decide when to steer, recover, schedule follow-up, or clean up. |
Use this skill only when you are root (infra_vm) or are explicitly acting on root's behalf.
Root is the fleet overseer. Supervision is continuous across turns, but a single turn should end once:
Do not keep a turn open just to keep watching the fleet.
Build the operational picture from:
reef_fleet_statusvm_tree_view()reef_inboxreef_scheduledreef_usagereef_logsCheck for:
If the fleet is healthy:
If future attention is needed:
If a child is drifting or stuck:
If you assigned a slice to a child, do not quietly perform that same slice yourself. Root may do:
Root should not shadow its children while still pretending the child owns the work.
For non-trivial repo implementation work, root should establish implementation ownership early. Once orientation is complete, root should usually move into:
Root should not stay as the default leaf implementer unless the work is still one coherent slice.
infra_vm as protected infrastructureresource_vm as protected-by-default infrastructurerunning just to superviseUse when doing code work that must be integration-friendly: branches, commits, tests, PR-ready receipts, owned paths, and parent-friendly handoff.
Use when implementing and exposing a product/application service or UI that should run outside Reef root. Choose child/resource VM placement, stand up the app, and report how to reach it.
Use when handling parent commands such as steer, abort, pause, or resume, or when deciding how urgently to react to inbox messages from above.
Use when agents need to coordinate through reef store, peer signals, barriers, rendezvous, or child/peer communication without breaking authority boundaries.
Create a new service module for reef. Use when adding a new capability to the server — a new store, API routes, LLM tools, behaviors, or dashboard widget.
Use when a task has multiple independent subsystems, needs recursive delegation, or requires a parent to split implementation and then integrate the results.