mirror of
https://github.com/stablyai/orca.git
synced 2026-11-14 01:47:24 +00:00
Trigger on named-agent review requests, define failure in specs, show the reuse commands
This commit is contained in:
Jinwoo-H
Generated
+5
-5
@@ -148,16 +148,16 @@
|
||||
{
|
||||
"name": "orchestration",
|
||||
"sourcePath": "skills/orchestration",
|
||||
"packageDigest": "7fe7130df2c49e869151720d52b7d58bb8e5ab600ef23289a4588bcc4d5c6a38",
|
||||
"packageDigest": "033316337f9c5d070a5b6d7f071d79deeed0e39985e29b1247c5de80a56a3215",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"size": 4106,
|
||||
"size": 4365,
|
||||
"executable": false,
|
||||
"classification": "text",
|
||||
"exactSha256": "332b046294c2356d962cacb9b9f7bcd68919570c1cb69b90c100f0c08be94d99",
|
||||
"textNormalizedSha256": "332b046294c2356d962cacb9b9f7bcd68919570c1cb69b90c100f0c08be94d99",
|
||||
"identitySha256": "332b046294c2356d962cacb9b9f7bcd68919570c1cb69b90c100f0c08be94d99"
|
||||
"exactSha256": "24c5392fe1734c3dcf63d1a05ab4ac75eaa70e4d880f590a4a33ec83e4a2cc6a",
|
||||
"textNormalizedSha256": "24c5392fe1734c3dcf63d1a05ab4ac75eaa70e4d880f590a4a33ec83e4a2cc6a",
|
||||
"identitySha256": "24c5392fe1734c3dcf63d1a05ab4ac75eaa70e4d880f590a4a33ec83e4a2cc6a"
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
Generated
+1
@@ -122,6 +122,7 @@
|
||||
"1150a30d854ad1d6c4f107af4c115bac6afd00122e4b011ee5e8f9c49a9d9bab",
|
||||
"19ffdc1fe0d2c97dae845e8d636edb16781453ce2ec26f65a323c492ef90da18",
|
||||
"1cbb78d008e0a833150096dab7882fdae5b7e72b5b073d4cbcef9642fb421ab0",
|
||||
"24c5392fe1734c3dcf63d1a05ab4ac75eaa70e4d880f590a4a33ec83e4a2cc6a",
|
||||
"277dd8372f4b3b1773f8debe6e02eae575f01d568de328ae06d78ba71fc045cb",
|
||||
"2c1ac3a94ef4ee085147ee48d813bdcce532f5f6c7040d7836ea7b3d2a882628",
|
||||
"332b046294c2356d962cacb9b9f7bcd68919570c1cb69b90c100f0c08be94d99",
|
||||
|
||||
@@ -5,6 +5,8 @@ description: >-
|
||||
the user asks for Orca workers or supervision (monitor, task DAGs, ask/reply,
|
||||
decision gates), or when the work needs something your own subagents cannot
|
||||
give: a different agent (such as Codex from Claude) or its own Orca workspace.
|
||||
"Have Codex (or Claude) review this and report back" means an Orca worker of
|
||||
that agent, even when you have your own model subagents.
|
||||
Also use when you are a dispatched worker (a prompt with Task and Dispatch
|
||||
IDs: ask, worker_done). Otherwise prefer your own subagents,
|
||||
including for long or parallel work. Use `orca-cli` to hand work off with
|
||||
@@ -66,9 +68,12 @@ Finished terminal workers close on their own. To keep one for a follow-up, run
|
||||
## Task spec
|
||||
|
||||
Make each spec self-contained: the target, the change, constraints, what the
|
||||
worker may edit, and the evidence that proves it is done. A review worker's
|
||||
findings are for you to summarize; send fixes to a worker unless the user gave
|
||||
them to you.
|
||||
worker may edit, and the evidence that proves it is done. Say whether a
|
||||
non-zero exit means the Task failed or capturing it is the deliverable. Send
|
||||
fixes to a worker unless the user gave them to you.
|
||||
|
||||
Fetch this guide once. Summarize the worker's evidence; rerun checks only for a
|
||||
gap or contradiction.
|
||||
|
||||
## Safety
|
||||
|
||||
|
||||
@@ -22,10 +22,10 @@ one. `run-use` keeps only the Run it names.
|
||||
|
||||
## Reusing a worker
|
||||
|
||||
To give the same agent follow-up work, start the next Task on its terminal and
|
||||
workspace:
|
||||
To give a finished worker follow-up work, create the Task, then start it on the
|
||||
terminal handle and workspace from that worker's earlier `worker-start` receipt:
|
||||
|
||||
```text
|
||||
ORCA orchestration worker-show --dispatch <dispatch_id> --json
|
||||
ORCA orchestration worker-start --task <next_task_id> --terminal <agent_terminal_handle> --worktree <its_workspace> --json
|
||||
ORCA orchestration task-create --spec "<follow-up>" --json
|
||||
ORCA orchestration worker-start --task <task_id> --terminal <agent_terminal_handle> --worktree <its_workspace> --json
|
||||
```
|
||||
|
||||
@@ -7,8 +7,9 @@ purpose so it can never drift from the binary that will actually run your comman
|
||||
Use Orca orchestration to run work in separate Orca worker agents and get their results
|
||||
back: when the user asks for Orca workers or supervision (monitor, task DAGs, ask/reply,
|
||||
decision gates), or when the work needs something your own subagents cannot give, such as a
|
||||
different agent or its own Orca workspace. Use it as well when you are a dispatched worker
|
||||
sending heartbeats, `ask` questions, or `worker_done`. Otherwise prefer your own subagents,
|
||||
different agent or its own Orca workspace. "Have Codex (or Claude) review this and report
|
||||
back" means an Orca worker of that agent, even when you have your own model subagents. Use
|
||||
it as well when you are a dispatched worker sending `ask` questions or `worker_done`. Otherwise prefer your own subagents,
|
||||
including for long or parallel work. Use the orca-cli skill instead to hand work off with
|
||||
nothing expected back ("hand off", "handoff", "handover", "give this to another agent",
|
||||
"another worktree"), and for ordinary terminal control, shell commands, worktree management,
|
||||
|
||||
@@ -5,6 +5,8 @@ description: >-
|
||||
the user asks for Orca workers or supervision (monitor, task DAGs, ask/reply,
|
||||
decision gates), or when the work needs something your own subagents cannot
|
||||
give: a different agent (such as Codex from Claude) or its own Orca workspace.
|
||||
"Have Codex (or Claude) review this and report back" means an Orca worker of
|
||||
that agent, even when you have your own model subagents.
|
||||
Also use when you are a dispatched worker (a prompt with Task and Dispatch
|
||||
IDs: ask, worker_done). Otherwise prefer your own subagents,
|
||||
including for long or parallel work. Use `orca-cli` to hand work off with
|
||||
@@ -22,8 +24,9 @@ purpose so it can never drift from the binary that will actually run your comman
|
||||
Use Orca orchestration to run work in separate Orca worker agents and get their results
|
||||
back: when the user asks for Orca workers or supervision (monitor, task DAGs, ask/reply,
|
||||
decision gates), or when the work needs something your own subagents cannot give, such as a
|
||||
different agent or its own Orca workspace. Use it as well when you are a dispatched worker
|
||||
sending heartbeats, `ask` questions, or `worker_done`. Otherwise prefer your own subagents,
|
||||
different agent or its own Orca workspace. "Have Codex (or Claude) review this and report
|
||||
back" means an Orca worker of that agent, even when you have your own model subagents. Use
|
||||
it as well when you are a dispatched worker sending `ask` questions or `worker_done`. Otherwise prefer your own subagents,
|
||||
including for long or parallel work. Use the orca-cli skill instead to hand work off with
|
||||
nothing expected back ("hand off", "handoff", "handover", "give this to another agent",
|
||||
"another worktree"), and for ordinary terminal control, shell commands, worktree management,
|
||||
|
||||
@@ -2340,6 +2340,8 @@ const ORCHESTRATION_MARKDOWN = [
|
||||
" the user asks for Orca workers or supervision (monitor, task DAGs, ask/reply,",
|
||||
" decision gates), or when the work needs something your own subagents cannot",
|
||||
" give: a different agent (such as Codex from Claude) or its own Orca workspace.",
|
||||
" \"Have Codex (or Claude) review this and report back\" means an Orca worker of",
|
||||
" that agent, even when you have your own model subagents.",
|
||||
" Also use when you are a dispatched worker (a prompt with Task and Dispatch",
|
||||
" IDs: ask, worker_done). Otherwise prefer your own subagents,",
|
||||
" including for long or parallel work. Use `orca-cli` to hand work off with",
|
||||
@@ -2401,9 +2403,12 @@ const ORCHESTRATION_MARKDOWN = [
|
||||
"## Task spec",
|
||||
"",
|
||||
"Make each spec self-contained: the target, the change, constraints, what the",
|
||||
"worker may edit, and the evidence that proves it is done. A review worker's",
|
||||
"findings are for you to summarize; send fixes to a worker unless the user gave",
|
||||
"them to you.",
|
||||
"worker may edit, and the evidence that proves it is done. Say whether a",
|
||||
"non-zero exit means the Task failed or capturing it is the deliverable. Send",
|
||||
"fixes to a worker unless the user gave them to you.",
|
||||
"",
|
||||
"Fetch this guide once. Summarize the worker's evidence; rerun checks only for a",
|
||||
"gap or contradiction.",
|
||||
"",
|
||||
"## Safety",
|
||||
"",
|
||||
@@ -2451,12 +2456,12 @@ const ORCHESTRATION_COORDINATOR_LOOP_REFERENCE_MARKDOWN = [
|
||||
"",
|
||||
"## Reusing a worker",
|
||||
"",
|
||||
"To give the same agent follow-up work, start the next Task on its terminal and",
|
||||
"workspace:",
|
||||
"To give a finished worker follow-up work, create the Task, then start it on the",
|
||||
"terminal handle and workspace from that worker's earlier `worker-start` receipt:",
|
||||
"",
|
||||
"```text",
|
||||
"ORCA orchestration worker-show --dispatch <dispatch_id> --json",
|
||||
"ORCA orchestration worker-start --task <next_task_id> --terminal <agent_terminal_handle> --worktree <its_workspace> --json",
|
||||
"ORCA orchestration task-create --spec \"<follow-up>\" --json",
|
||||
"ORCA orchestration worker-start --task <task_id> --terminal <agent_terminal_handle> --worktree <its_workspace> --json",
|
||||
"```",
|
||||
"",
|
||||
].join('\n')
|
||||
@@ -2611,7 +2616,7 @@ export const BUNDLED_SKILL_GUIDES = [
|
||||
},
|
||||
{
|
||||
name: "orchestration",
|
||||
description: "Run work in separate Orca worker agents and get their results back. Use when the user asks for Orca workers or supervision (monitor, task DAGs, ask/reply, decision gates), or when the work needs something your own subagents cannot give: a different agent (such as Codex from Claude) or its own Orca workspace. Also use when you are a dispatched worker (a prompt with Task and Dispatch IDs: ask, worker_done). Otherwise prefer your own subagents, including for long or parallel work. Use `orca-cli` to hand work off with nothing expected back (\"hand off\", \"handover\", \"give this to another agent\", \"another worktree\"), and for terminal control, shell commands, worktree management, and reading or waiting on terminals.",
|
||||
description: "Run work in separate Orca worker agents and get their results back. Use when the user asks for Orca workers or supervision (monitor, task DAGs, ask/reply, decision gates), or when the work needs something your own subagents cannot give: a different agent (such as Codex from Claude) or its own Orca workspace. \"Have Codex (or Claude) review this and report back\" means an Orca worker of that agent, even when you have your own model subagents. Also use when you are a dispatched worker (a prompt with Task and Dispatch IDs: ask, worker_done). Otherwise prefer your own subagents, including for long or parallel work. Use `orca-cli` to hand work off with nothing expected back (\"hand off\", \"handover\", \"give this to another agent\", \"another worktree\"), and for terminal control, shell commands, worktree management, and reading or waiting on terminals.",
|
||||
markdown: ORCHESTRATION_MARKDOWN,
|
||||
aliases: [],
|
||||
references: [{ name: "coordinator-loop", markdown: ORCHESTRATION_COORDINATOR_LOOP_REFERENCE_MARKDOWN }, { name: "legacy-contract-migration", markdown: ORCHESTRATION_LEGACY_CONTRACT_MIGRATION_REFERENCE_MARKDOWN }, { name: "low-level-topology", markdown: ORCHESTRATION_LOW_LEVEL_TOPOLOGY_REFERENCE_MARKDOWN }, { name: "messaging-and-gates", markdown: ORCHESTRATION_MESSAGING_AND_GATES_REFERENCE_MARKDOWN }, { name: "placement-and-remote", markdown: ORCHESTRATION_PLACEMENT_AND_REMOTE_REFERENCE_MARKDOWN }, { name: "recovery-and-cleanup", markdown: ORCHESTRATION_RECOVERY_AND_CLEANUP_REFERENCE_MARKDOWN }]
|
||||
|
||||
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user