Sub-Tasks Now Run In Order, Each Merged First
A parent task's sub-tasks now run in a clear, ordered sequence instead of all at once, with each one's work merged in before the next begins.
Summary
A parent task and its sub-tasks now run as one ordered line of work instead of several agents working on them all at once. Each sub-task's work is merged in before the next one starts, so the work builds cleanly on what came before it, and a problem anywhere in the sequence is visible exactly where it happened.
What You Gain
Running several sub-tasks of the same parent at the same time could mean each one started from a slightly different starting point, and reconciling their separate pieces of work back together afterward took more coordination than it should have. It also made it harder to tell, at a glance, what order things were actually happening in, or where a breakdown of work currently stood — even after sub-tasks stopped running at the same time as their parent, they could still run out of order with each other.
Now the sequence is explicit and visible. The parent task runs first to confirm the plan, then its sub-tasks run one after another — each one's work is completed and merged in before the next begins, so every sub-task builds on a known, up-to-date foundation. If something in the sequence runs into trouble, the whole line pauses right there with a clear explanation, rather than other sub-tasks continuing on top of an unresolved problem.
How It Works
- The parent task runs first, checking that the breakdown of sub-tasks makes sense before anything else starts.
- Sub-tasks then run one at a time, in a clear order based on how they're organized on the board.
- Each sub-task's work is merged in before the next one begins.
- The parent runs once more at the end, after every sub-task is finished, to bring everything together.
- A problem stops the sequence visibly where it happened, with the reason shown on the affected sub-task. Resuming it picks the sequence back up.
Where to Find It
This applies automatically to every task broken into sub-tasks — there's nothing to configure. Keeping the desktop app and CLI current ensures agents are given the clearest picture of where the sequence stands.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.