This skill should be used when deciding whether to execute multiple Atoms in parallel, detecting side-effect conflicts between concurrent operations, or integrating results from parallel Worker agents. Use it in the coordinator agent when multiple Atoms are ready for execution.
Executes multiple independent operations simultaneously when no side-effect conflicts exist. Used by the coordinator agent to run ready sub-tasks in parallel, integrating results from successful workers while handling failures and resource contention.
/plugin marketplace add yodakeisuke/ralph-wiggum-aot/plugin install yodakeisuke-ralph-wiggum-aot@yodakeisuke/ralph-wiggum-aotThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Determine parallel execution of Sub Agents and integrate results.
| Characteristic | Description | Design Implication |
|---|---|---|
| Context isolation | Independent workspace from parent | Exploration failures don't pollute main |
| Concurrent operation | Multiple agents run simultaneously | Solve AND-independent Atoms together |
| Failure localization | Child failures don't propagate to parent | Lightweight backtrack cost |
| Summary return | Returns only results to parent | Naturally aligns with DAG contraction |
def get_parallel_ready_atoms(state):
"""Return Atoms ready for parallel execution"""
ready = []
for atom in state.atoms:
if atom.status != 'pending':
continue
# Check if all dependencies are resolved
deps_resolved = all(
get_atom(state, dep).status == 'resolved'
for dep in atom.depends_on
)
if deps_resolved:
ready.append(atom)
# Apply parallel limit
max_parallel = state.objective.constraints.max_parallel_agents
return ready[:max_parallel]
Conflict examples:
| Atom A | Atom B | Conflict Reason |
|---|---|---|
Create src/auth.ts | Edit src/auth.ts | Same file operation |
| Run DB migration | Reference DB schema | DB state dependency |
| Use port 3000 | Test port 3000 | Resource contention |
Conflict detection heuristics:
Work graph:
A (resolved)
├─ B (AND) ← executable
└─ C (AND) ← executable (independent of B)
└─ D (AND) ← depends on B, C, waiting
→ Execute B, C in parallel
→ After both succeed, D becomes executable
speculative: trueDefault is sequential execution. Speculative parallel only when explicitly specified.
OR_group: "auth_method"
├─ choice_1: JWT implementation
└─ choice_2: Session implementation
If speculative: true
→ Execute both in parallel
→ Adopt whichever succeeds first, abort the other
| Result | Action |
|---|---|
| One success | Adopt successful choice, abort others |
| Multiple success | Adopt first success, abort others |
| All fail | Record all results in Trail, backtrack |
| Agent Type | Parallel | Reason |
|---|---|---|
| Worker | Yes | Simultaneous resolution of independent Atoms |
| Probe | Yes | Investigation has no side effects |
| Verifier | No | base_case evaluated sequentially |
| Coordinator | No | Single parent |
def integrate_results(results):
"""Integrate parallel execution results"""
for result in results:
atom_id = result['atom_id']
if result['success']:
# Reflect in Bindings
state.bindings[atom_id] = {
'summary': result['summary'],
'artifacts': result['artifacts']
}
# Mark Atom as resolved
set_atom_status(atom_id, 'resolved')
else:
# Failure: reset to pending
set_atom_status(atom_id, 'pending')
# For OR branch, record selection history in Trail
if atom.or_group:
record_or_selection(atom.or_group, atom_id, result['reason'])
constraints:
max_parallel_agents: 3 # Concurrent execution limit
When exceeding limit:
Priority criteria:
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.