parallel-dispatch-ownership
CommunityPrevent merge chaos with exclusive file ownership.
Software Engineering#agent integration#file ownership#merge conflict prevention#parallel dispatch#contract immutability#MECE decomposition#DAG orchestration
Authorirahardianto
Version1.0.0
Installs0
System Documentation
What problem does it solve?
It prevents AI agent merge conflicts by enforcing a deterministic, MECE ownership model so parallel write agents never modify the same files.
Core Features & Use Cases
- Exclusive write conflict prevention: Validates that each parallel sub-task has a disjoint write scope so two writers cannot claim overlapping paths.
- Coverage and contract immutability checks: Ensures every required change is assigned to exactly one owner and that BUILD-phase writers do not modify frozen contracts produced in DESIGN.
- Correct integration timing: Guarantees integration sub-tasks run after parallel write tasks so aggregation files (routers, mains, registries, global config) are assembled safely.
Quick Start
In your orchestrator, run parallel-dispatch-ownership as a pre-flight validation step before dispatching each DAG level and again after each merge to abort on any ownership violations.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: parallel-dispatch-ownership Download link: https://github.com/irahardianto/awesome-agv/archive/main.zip#parallel-dispatch-ownership Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.