メニュー
Use when agents need to coordinate through reef store, peer signals, barriers, rendezvous, or child/peer communication without breaking authority boundaries.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/hdresearch/reef --skill coordination-patternsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
Use 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.
SKILL.md を表示中
| name | coordination-patterns |
| description | Use when agents need to coordinate through reef store, peer signals, barriers, rendezvous, or child/peer communication without breaking authority boundaries. |
Use this skill when you need coordination, not just raw messaging.
Use:
reef_command for parent -> descendant controlreef_signal for child -> parent reportingreef_peer_signal for same-parent sibling coordinationreef_inbox_wait for waiting on message arrival inside the current turnreef_swarm_wait for swarm-task completion when you already dispatched work through the swarm helper toolsreef_store_list for discoveryreef_store_wait for synchronizationreef_schedule_check for future attention beyond the current turnreef_store_putreef_store_listskill-agent, write skill-agent:coord/phase, not wait-swarm:coord/phasereef_store_listreef_store_wait(prefix)reef_peer_signal only while both peers are alivePrefer:
reef_inbox_wait when you are waiting for a child/parent/peer message to arrive nowreef_swarm_wait when you need completion/results from swarm workers you tasked via reef_swarm_taskreef_store_wait(prefix) for barriers and rendezvousreef_store_wait(key) for exact logical conditionsreef_schedule_check when the attention should outlive the current turnAfter finishing your current work, do one final reef_inbox pass before you fully conclude.
Use this bounded catch-up to notice:
If something meaningful arrived:
Do not turn this into an infinite linger loop. One bounded catch-up pass is the rule.
Use reef_peer_signal for:
Do not use it for:
If the coordination must survive peer shutdown, persist it in the store.
Do not invent polling loops for child completion if inbox/signals already answer it.
Prefer:
reef_inbox({ direction: "up" }) for child done / blocked / failedreef_inbox_wait({ direction: "up" }) when you need to block briefly for the next child signal inside the current turnreef_swarm_wait when the child is a swarm worker you already dispatched through the swarm tools and you want the swarm-specific completion/result pathFor swarm workers:
reef_swarm_wait when you are the parent agent collecting swarm completion/resultsreef_swarm_wait, treat it as the authoritative swarm completion path; matching worker done signals are operationally consumed rather than fresh pending attentionreef_inbox — read what is already waiting for you nowreef_inbox_wait — wait briefly for message arrival inside the current turnreef_swarm_wait — wait for swarm-task completion/results through the swarm helper layerreef_store_wait — wait for shared state conditions, barriers, or rendezvousreef_schedule_check — durable follow-up when attention must survive after the current turn ends