메뉴
Check orchestra message inboxes for messages from teams, coordinator, or human. Use when the user wants to see what messages have been sent during an orchestra run.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Take a design doc through to a PR with reviews requested. Implements in a worktree, opens the PR, iterates locally on CI until green, then schedules a remote agent to push-notify when reviews land.
Monitor an orchestra run — team status, unread messages, costs, failures, and live activity. Designed to run with /loop for continuous monitoring as a human coordinator.
Monitor an orchestra run — team status, unread messages, costs, failures, and live activity. Designed to run with /loop for continuous monitoring as a human coordinator.
Designate this session as the human coordinator for an orchestra run. Reads the project config, shows current status, starts a monitor loop, and primes the session to handle messages and interventions.
Interactively create an orchestra.yaml config for multi-team project orchestration.
Send a message to a team or the coordinator via the orchestra message bus. Use when the user wants to communicate with teams during an orchestra run — corrections, answers, decisions, or broadcasts.
| name | orchestra-inbox |
| description | Check orchestra message inboxes for messages from teams, coordinator, or human. Use when the user wants to see what messages have been sent during an orchestra run. |
| argument-hint | [inbox-name] — e.g., coordinator, human, data-engine, all |
| user_invocable | true |
Check message inboxes in the orchestra messages directory.
Default path: .orchestra/messages/ (relative to current working directory).
If the user specifies a different path, use that instead.
<user_argument> is provided, use it as the inbox to check:
coordinator → 1-coordinatorhuman → 0-humanall → check every inboxdata-engine → find the matching N-<name> folderLocate the messages directory (see above).
List all participant folders:
ls -d $MESSAGES/*/
If no argument was provided, present the available inboxes and ask which to check:
Available inboxes:
0-human
1-coordinator
2-data-engine
3-full-stack
...
shared (artifacts)
Which inbox to check? (or "all")
Wait for the user's response before proceeding.
For the selected inbox(es), list all .json files:
ls $MESSAGES/<folder>/inbox/*.json 2>/dev/null
If no messages, report "No messages in <folder> inbox."
If messages exist, read each one and present a summary table:
| # | From | Type | Subject | Priority | Read |
|---|---|---|---|---|---|
| 1 | 2-data-engine | blocking-issue | Missing dep | high | no |
| 2 | 3-full-stack | status-update | API done | normal | yes |
For any unread messages, show the full content below the table.
Also check $MESSAGES/shared/ and list any shared artifacts (interface contracts, schemas).
Keep it concise. The summary table is the primary output. Only expand unread messages. If the user asks about a specific message, read and display it in full. When checking "all", group messages by inbox with a header per inbox.