bkinnightskytw
/
agent-orchestrator
mirror of https://github.com/ComposioHQ/agent-orchestrator.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix(skill): clarify ao_spawn works without an issue number 

Closes #974
This commit is contained in:
Dhruv Sharma 2026-04-09 17:05:25 +05:30
parent c00618048f
commit 9df82d57af
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
skills/agent-orchestrator/SKILL.md
View File

@ -49,7 +49,11 @@ Any of: "what needs doing", "what's on the board", "any issues", "what's open",
### Any coding request — fix / add / change / build / implement / refactor
Any of: "fix #X", "fix the bug in...", "add a flag to...", "change...", "refactor...", "implement...", "update the code", "build...", "work on #X", "handle #X", "do it", "go for it", "sure", "yes", "go ahead"
Also: ANY request that involves changing, fixing, adding, writing, or modifying code — regardless of size, even if no issue number is mentioned
→ Call `ao_spawn` with the issue number or task description
→ Call `ao_spawn` with the issue number if one exists, or with just the task description if there is no issue
**Issue number is optional.** Both of these are valid:
- With issue: user says "fix #42" → spawn with `issue: "42"`
- Without issue: user says "add a weekly report script" → spawn with no issue, just confirm the task description
### Batch work
Any of: "do them all", "start all", "spawn them all", "batch it", "all of those", "go for all"
@ -92,15 +96,17 @@ When the user asks anything about work, tasks, issues, status, or projects:
After fetching data, present it conversationally. Suggest priorities. Ask if they want to kick things off.
### Rule 3: Confirm before acting
Before spawning agents or batch-spawning, always show the user what you're about to do and get explicit approval. Example:
Before spawning agents or batch-spawning, always show the user what you're about to do and get explicit approval. Examples:
"I'll spawn an agent on #6 (JSON output bug). Go ahead?"
- With issue: "I'll spawn an agent on #6 (JSON output bug). Go ahead?"
- Without issue: "I'll spawn an agent on this task: 'Add weekly report script'. Go ahead?"
Then act on clear confirmation ("yes", "go", "do it"). Don't spawn agents without the user approving first.
### Rule 4: Present actions naturally
Instead of technical tool names, describe what you're doing in plain language.
Example: "On it — spinning up an agent on #6." (not "Calling ao_spawn...")
Instead of technical tool names, describe what you're doing in plain language. Examples:
- With issue: "On it — spinning up an agent on #6." (not "Calling ao_spawn...")
- Without issue: "On it — spinning up an agent on that task." (not "Calling ao_spawn...")
### Rule 5: Follow up with links
After spawning, check `ao_status` for progress. Always include full PR URLs from tool responses.