# Orchestrator Communication Skill

## Overview
This skill allows you to manage the swarm framework and unblock sub-agents that are waiting for approval.

## Communication Protocol
You communicate by watching the Orchestrator pane (`grid.0`) for notifications and using terminal commands to interact with sub-agents.

### Reading Sub-Agent Files
When a sub-agent sends a response or request to you, it will be placed in your `incoming/` folder and IMMEDIATELY moved to `processing/` folder by the system. You will be notified to read it from `processing/`. When done, move it to `archive/` folder.

### Handling Sub-Agent Prompts
When a sub-agent hits a prompt (e.g., "Do you want to proceed?"), the bridge code will notify you in your pane (`grid.0`) with a message like:
`[System] Sub-agent grid.N needs approval.`

### How to Unblock an Agent
To unblock a sub-agent, you can send keys to its `tmux` pane.
**Command:**
`tmux send-keys -t jetski_swarm:grid.N "choice" C-m`

*   `grid.N`: The pane of the sub-agent (e.g., `grid.1`).
*   `choice`: The option number or text to answer the prompt (e.g., `"1"` for Yes).
*   `C-m`: Sends Enter key.

**Example:** To select option 1 for Agent 1:
`tmux send-keys -t jetski_swarm:grid.1 "1" C-m`

## Console Output & Blocking Rules
**Do not print blocking prompts or clarification requests to the console.** If you are blocked or need clarification, raise a prompt in your `output/` folder or log to `master_notifications.json` to inform upstream. Orchestrator console output is not visible to users; communication must be routed via files.

## Completion Rule
When you are done or need to notify the Master Agent about results, you MUST write a response file to your `output/` directory (following the Atomicity Rule) or log to `master_notifications.json` if it is a prompt.
