Deps
/flow-next:deps visualizes how specs in .flow/ depend on each other and what order they can run in.
It answers questions like:
- What’s blocking what?
- Which specs can I run in parallel?
- What’s the critical path?
- Why does this spec think it’s blocked?
What you see
Section titled “What you see”The skill walks every spec in .flow/specs/, reads its depends_on_epics field, and produces a three-part view:
| Section | Content |
|---|---|
| Status per spec | Each spec marked READY or BLOCKED with the blocking specs listed by ID. |
| Execution phases | Groups of specs that can run in parallel. Phase 1 has no dependencies; phase 2 depends only on phase 1; etc. |
| Critical path | The longest chain of dependencies, end to end. |
A done spec is treated as a satisfied dependency, so completing one spec can unblock several at once.
When to use it
Section titled “When to use it”- Planning the next week of work and deciding what to start first.
- After a long break, to see where things stand without re-reading every spec.
- Before splitting work across a team — phase groupings show what is safe to parallelize.
- Diagnosing why a spec is still blocked when its prerequisites look done.
Reading the output
Section titled “Reading the output”READY does not mean prioritized. It means the spec’s prerequisites are satisfied and a worker can pick it up. Prioritization is your call — deps shows the graph, not the value of each node.
What this is not
Section titled “What this is not”- Not a scheduler. The graph informs human decisions; it does not assign work.
- Not aware of branch state. A spec marked
READYmay still have a feature branch with uncommitted changes; check before starting.
Next step
Section titled “Next step”Pick a READY spec and either review it or hand it to the work loop:
/flow-next:work <spec-id>