ftown-orchestratorlisted

# ftown orchestrator playbook You are running inside an ftown session (your id is in `$FTOWN_SESSION_ID`) and can coordinate worker agent sessions on this machine using the `~/.ftown/ftown-sessions` CLI. See the **ftown-sessions** skill for the full CLI reference. ## Spawning workers `--shell` accepts `claude`, `cursor`, `shell`, `opencode`, …; `--parent` sets the worker's parent to `$FTOWN_SESSION_ID`. ```bash ~/.ftown/ftown-sessions create \ --shell claude \ --parent \ --workdir /path/to/repo \ --name review-auth \ --prompt "Review the auth module and summarize findings" ``` Returns JSON containing `session.id` — save it to poll the worker later. Workers spawned with `--parent` are auto-briefed to report back via `mail send --parent`; their reports arrive in **your** inbox and are delivered automatically as `[ftown mail]` context at your turn boundaries. ## Monitoring workers ```bash # See what's on screen right now ~/.ftown/ftown-sessions screen <session-id> --limit 100 # Search for errors / completion markers ~/.ftown/ftown-sessions grep <session-id> --pattern 'FAIL|done|error' # Check if the process is still alive ~/.ftown/ftown-sessions running <session-id> ``` Poll `screen` or `grep` rather than waiting blindly — workers don't always remember to mail you when they finish. ## Messaging (mail) Each session has an inbox. Mail is delivered into the recipient's context automatically at turn boundaries — no keystroke injection needed. ```bash # Send w