Use this skill whenever you need the allowed_tools / skills preset for a sub-agent role before calling spawn_subagent. Trigger especially when user mentions: "role", "spawn_subagent", "allowed_tools", or any OMP role name (executor, architect, analyst, critic, security-reviewer, code-reviewer, qa-tester, planner, explore, debugger, verifier). Also use when a /ultrawork, /ralph, /autopilot, /ultraqa, or /team workflow step asks for role tool/skill configuration.
76
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
When using spawn_subagent (single or batch mode) to dispatch sub-agents, set the corresponding allowed_tools and skills parameters based on the sub-agent's role.
Canonical source of truth in code:
plugins/bundle/omp_workflows/shared/constants.py
(ROLE_ALLOWED_TOOLS, ROLE_SKILLS, TOOL_* names) and
shared/role_prompts.py (ROLE_PROMPTS, build_worker_prompt,
format_spawn_call). Tool strings must match registered ToolRegistry
names — do not invent aliases.
spawn_subagent(
task="<role identity from ROLE_PROMPTS>\n\n## Task\n<task description>",
allowed_tools=<ROLE_ALLOWED_TOOLS[role] or omit if null>,
skills=<ROLE_SKILLS[role] or omit if null>,
fork=True, # if worktree isolation needed
background=True, # if background execution needed
)When allowed_tools or skills is null, omit the parameter (uses default None).
For batch mode, pass task="" and put per-item role config in each batch dict.
f6dbc1d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.