Sub-task stages now actually run in order
Sub-task stages weren't starting their agents or waking the parent task; promoting a task to active work now reliably starts it.
Summary
Shortly after sub-task stages launched, they weren't working end to end: sub-tasks sat untouched, a finished stage never released the next one, and the parent task never woke back up. That chain is fixed — moving a staged sub-task into active work now reliably starts its agent.
What You Gain
A staged breakdown is only useful if each stage genuinely kicks off the next. Before this fix, sub-tasks created as part of a stage sat with nobody actually working on them, so the whole breakdown stalled at the first step and never progressed, however it was assigned.
Now, moving an agent-assigned sub-task into active work — whether that's an automatic stage promotion or you dragging the card yourself — reliably starts that agent. A sub-task created but deliberately held back correctly waits until it's promoted, so later stages still hold off as intended.
How It Works
The guidance given to agents working with staged sub-tasks was corrected at the same time, so the instructions they follow now match how staged work actually runs.
Where to Find It
This fix applies automatically to every project using sub-task stages.
See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.