← ClaudeAtlas

parallel-delegationlisted

Use when an authorized multi-task work unit needs its required current Parallel Opportunity Scan, especially when 2 or more ready independent tasks may parallelize, or the orchestrator must decide serial versus parallel execution, or when planning, reviewing, joining, troubleshooting, or boundedly reconciling parallel lanes, leases, structured write ownership, classified managed joins, distinct shared exports or package scripts, backend-specific writes, knowledge coupling, cross-lane finding disposition, semantic conflict between lane artifacts, verification topology, integration rehearsal, or the human merge checkpoint.
bartoszarendt/agenticloop · ★ 2 · AI & Automation · score 69
Install: claude install-skill bartoszarendt/agenticloop
# Parallel Delegation This is the trigger-loaded parallel-lane law. Guarded worktree commands and cleanup behavior are available through `agenticloop help worktree`. ## Parallel Opportunity Scan **Trigger.** Every authorized multi-task work unit receives one current scan per meaningful readiness snapshot. Source plans are inputs only, never scan results or parallel authorization. Before ordering work, Orchestrator records the scan in canonical `## Concurrency Plan`, an authorized task-record surface, or single-writer output, never every task or a shared mutable ledger. Maintainer supplies per-task code/collision and joinability classifications through `## Parallel Safety`; Orchestrator verifies task, artifact, host, liveness, and join inputs and routes the decision without originating or overriding semantic/code classification. **Decide inventory completeness before ready count:** 1. incomplete inventory or decomposition -> `incomplete`; never an eligibility answer, however few tasks are visible. Repair the evidence and rescan. 2. complete inventory, zero ready tasks -> `no_eligible_work`. 3. complete inventory, one ready task or no valid candidate pair -> `not_currently_eligible`, recorded as `not currently eligible - <n> ready task(s)` plus a rescan trigger. 4. only complete, fresh, fully accounted inventory -> `parallel_candidates`; then assess below. Rescan when inventory membership or enumeration coverage, task carrier digests, base or dependency evide