Dependency Analyzer
List your tasks and what each one depends on — this tool detects circular dependencies and computes a valid execution order automatically.
Define Tasks & Dependencies
Format: TaskName: dependency1, dependency2. Leave blank after the colon for tasks with no dependencies.
Valid Execution Order
How to use Dependency Analyzer
- Enter one task per line as
Task: dependency1, dependency2. Leave the dependency list empty after the colon for a task with no prerequisites. Use identical task names wherever they are referenced. - Select Load Sample to see a working example, then choose Analyze.
- If a cycle is reported, revise the tasks involved and analyze again. Otherwise, read the execution order by level; tasks in one level are eligible to run in parallel.
- Choose Export Order (CSV) to save the schedule. Review dependency names before using the order in another project plan.
Turn a task list into a dependency graph
Enter one task per line using Task: dependency 1, dependency 2. The analyzer builds a directed graph, detects circular dependencies, and uses a topological sort to place prerequisites before the work that depends on them. The result is grouped into levels, making it easier to see which tasks can start together and which must wait.
When to check task dependencies
Use a task dependency checker before starting a software release, coordinating a project handoff, or sequencing work across a team. A valid order helps expose blocked work early; a cycle points to a planning problem such as two tasks that each require the other to be finished first. This is an ordering aid, not a replacement for estimating effort, assigning owners, or tracking progress.
What input format does the dependency analyzer accept?
Use one task per line, followed by a colon and an optional comma-separated list of prerequisites. For example, Testing: Backend, Frontend. A task with no prerequisites can be written as Design:.
Can independent tasks run in parallel?
Tasks shown at the same level have no unresolved prerequisites between them, so they may be eligible to run in parallel. The tool does not account for staffing, durations, or resource limits.
What does a circular dependency mean?
A cycle means the listed prerequisites form a loop, so no valid starting order exists for the tasks in that loop. Review the reported task names and revise the dependency list before using the exported order.