Gate 09 · Dependencies & Sequence

You can’t build the checkout before the cart, or anything user-scoped before auth. This gate works out those constraints across your whole backlog, so your agent builds in an order that holds together, foundations first, then the things that stand on them.

It reads the brief, your features, the tech stack, and the schema, and produces a dependency graph over your functionalities. That graph is what powers cubedot work: the CLI walks it and lists only the functionalities whose prerequisites are already done, so nothing gets started that can’t be finished.

Good dependencies reflect real build constraints, not an arbitrary line. Auth comes before anything user-scoped; the schema comes before the features that use it. And it’s a graph, not a queue, several things are usually unblocked at once, which is exactly what lets you (or several agents) work in parallel.

Watch for cycles. If A needs B and B needs A, one of them is really two functionalities wearing a trench coat, split it.

Output: dependencies-sequence.md, and it drives cubedot work.