exclusive-lock-dispatchlisted

# Exclusive-Lock Dispatch The dispatch-time pattern for tools that hold an exclusive lock during execution. Running such a tool from multiple parallel agents is a guaranteed failure; running the same tool's *outputs* through many parallel agents is the right shape. ## When to Use This Skill | Use this skill when… | Use `parallel-agent-dispatch` alone when… | |----------------------|-------------------------------------------| | Two or more candidate agents would invoke the same lock-holding tool | No candidate agent touches a locked resource | | A prior wave emitted lock-contention errors | Agents only read pre-computed artefacts | | You are debating "serialise the agent or pre-dump the artefacts?" | File scopes are disjoint and lock-free | | The tool in question is slow (decompilation, migration, compile) so re-running per agent would burn minutes | The lock holder is cheap enough to serialise without pre-dump | ## Canonical Locked Resources | Tool / Resource | Lock Behaviour | Typical Symptom | |-----------------|---------------|-----------------| | Ghidra project (`.gpr`) | Single writer; second invocation fails | `Project is locked by another instance` | | Database migration lock | Single writer per database | Migration tool blocks or errors | | Git index on shared checkout (`.git/index.lock`) | Single writer per working tree | `index.lock` exists / cannot `git add` | | Taskwarrior bulk modify (`task modify`, `task done` ranges) | Effectively single-writer for the ta