← 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. Worktree lifecycle and Git rules remain in `agenticloop/AGENTIC_LOOP.md`. ## Parallel Opportunity Scan **Trigger.** Every authorized multi-task work unit (phase, group, milestone, epic, task set, or other bounded multi-task unit) receives one current scan after decomposition, once per meaningful readiness snapshot. Source plans, roadmaps, architecture documents, issue groupings, and maintainer proposals are inputs only; none is a scan result or parallel authorization. Before selecting an execution order, the orchestrator records the scan in the canonical `## Concurrency Plan`, an authorized task-record surface, or a single-writer coordination output. Do not duplicate it into every task or create a shared mutable findings ledger. The maintainer supplies per-task code/collision and joinability classifications through `## Parallel Safety`; the orchestrator verifies required task, artifact, host, liveness, and join inputs, then records and routes the batch decision. The orchestrator does not originate or override a semantic/code classification. **Decide inventory completeness before ready count.** A ready count over an inventory never proven complete is not an answer: 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