Flow
Menu

Example

Break a feature into work several agents can pick up at once

Say what a piece truly waits on and nothing else, and the order tells you how many agents you can start right now.

8 steps, driven by an agent. Every step is a step in an end-to-end test, run against a listening server on every pull request, so the graph moves the way the run moved it.

Why it is shaped this way

There is no sub-task here, and that is the point. A piece names a blocker only where starting early would produce work that has to be thrown away; everything else about where it belongs is a tag, which groups without pretending to hold anything up. A tracker with only the sub-issue forces the two into one list, and a list can only be read as four waves of one — a plan that keeps three agents idle. Left as dependencies, the waves are the dispatch batches: everything inside one runs at the same time, and finishing a wave frees the next with no label for anyone to remember to update.