loom-parallel-worker-coordinationlisted

# loom-parallel-worker-coordination Parallel worker coordination is a Ralph orchestration playbook. It proves tasks are independent, dispatches bounded ticket-owned Ralph runs, integrates returned work deliberately, and records evidence and audit before trusting the combined result. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-plans`, `loom-tickets`, `loom-ralph`, `loom-evidence`, `loom-audit`, `loom-retrospective`, and `loom-knowledge`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. It coordinates child tickets or explicit ticket-defined sub-scopes. It does not make worker reports authoritative. ## Use This Playbook When Use this playbook when: - a plan has independent child tickets or execution units - multiple failures appear in separate files, subsystems, or domains - each worker can start from a self-contained child ticket or ticket-defined sub-scope - write scopes do not overlap - the integration risk is lower than the cost of sequential work Skip it when tasks share state, edit the same files, require a common design decision, depend on each other's output, or need one agent to understand the whole system before splitting. ## Route Use this route: ```text partition -> prove independence -> scope runs -> dispatch -> reconcile -> integrate -> verify -> audit ``` ## Partition Start from a plan, ticket set, failure set, or explicit