メニュー
Dispatch a task via any generic CLI tool such as aider, cursor CLI, or other AI coding assistants. Use when the supervisor needs to delegate implementation to a non-Codex, non-Claude CLI tool.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Perform pass confirmation bookkeeping after a task validates successfully. Use after a PASS evidence line has been written. Handles checkbox toggle, feature_list.json update, progress.txt append, and optional checkpoint commit.
Supervise one OpenSpec task at a time through any configured dispatcher while preserving strict role boundaries and auditable evidence. Use when a change is tracked in an OpenSpec tasks.md and a worker must implement exactly one eligible task, produce a validation bundle, and leave final validation and bookkeeping to the supervisor.
Validate an OpenSpec validation bundle and produce auditable evidence. Use when a worker has produced a BUNDLE and the supervisor needs to run validation and record a formal EVIDENCE line. Can be used standalone (after manual implementation) or as part of the supervisor workflow.
Dispatch a task to Codex CLI for execution. Use when the supervisor needs to delegate implementation to Codex running in full-auto mode. Codex will run in a sandboxed environment and apply file changes via patch.
Hand off a task to a human for manual implementation. Use when no automated dispatcher is available, the task requires human judgment, or the supervisor wants explicit human confirmation before proceeding.
Dispatch a task via an MCP tool call. Use when an MCP server provides a code generation or task execution tool that can receive a task prompt and produce implementation output.
| name | dispatch-cli |
| description | Dispatch a task via any generic CLI tool such as aider, cursor CLI, or other AI coding assistants. Use when the supervisor needs to delegate implementation to a non-Codex, non-Claude CLI tool. |
Use when:
All settings are read from .orchestra/config.json → dispatchers.cli:
| Setting | Config Key | Default |
|---|---|---|
| Command | dispatchers.cli.command | not set (must be configured) |
| Prompt mode | dispatchers.cli.prompt_mode | argument |
| Timeout | dispatchers.cli.timeout_seconds | 300 |
| Mode | Description |
|---|---|
argument | Prompt is appended as a quoted argument: <command> "<TASK_PROMPT>" |
stdin | Prompt is piped via stdin: echo "<TASK_PROMPT>" | <command> |
file | Prompt is written to a temp file: <command> /tmp/task-prompt.txt |
.orchestra/config.json → dispatchers.cli.<command_base> --version
TASK_PROMPT string.dispatchers.cli.prompt_mode:
<command> "<TASK_PROMPT>"printf '%s' "<TASK_PROMPT>" | <command>/tmp/orchestra-task-prompt-<timestamp>.txt, then <command> /tmp/orchestra-task-prompt-<timestamp>.txtprompt_mode is file.dispatchers.cli.timeout_seconds in .orchestra/config.json.prompt_mode: file.--yes-always for aider).tasks.md.tasks.md directly to verify the BUNDLE line.