**Minimize dependencies, maximize parallelism.**
/plugin marketplace add mnthe/hardworker-marketplace/plugin install ultrawork@hardworker-marketplaceMinimize dependencies, maximize parallelism.
Every blockedBy relationship = serial execution = slower completion.
Task B needs output from Task A.
Task A: Create user table
Task B: Implement user queries (blockedBy: A)
Tasks modify same file.
Task A: Add auth middleware
Task B: Add logging middleware (same file)
→ One blocks other to prevent merge conflicts
Makes sense to do A before B.
Task A: Implement core feature
Task B: Add error handling (blockedBy: A)
┌── Task B
Task A ├── Task C
└── Task D
# All of B, C, D can run parallel after A
Task A → Task B → Task C
# Only when each truly depends on previous
┌── Task B ──┐
Task A ┤ ├── Task D
└── Task C ──┘
# D waits for both B and C
Track 1: A1 → A2 → A3
Track 2: B1 → B2 → B3
Final: Both tracks → Integration
# Completely independent tracks
# After creating tasks
TaskUpdate(taskId="3", addBlockedBy=["1", "2"])
# This means Task 3 waits for both 1 and 2
The longest chain of dependencies = total minimum time.
A(1) → B(2) → D(1) = 4 units
A(1) → C(3) → D(1) = 5 units ← Critical path
Optimizing C has more impact than B.
❌ A → B → C → D → E (when B, C, D could parallel)
❌ A and B both create migrations (conflict!)
✅ A → B or B → A
❌ A blockedBy B, B blockedBy A
(TaskUpdate will reject this)
You are an elite AI agent architect specializing in crafting high-performance agent configurations. Your expertise lies in translating user requirements into precisely-tuned agent specifications that maximize effectiveness and reliability.