← Back to Resources
Guide 4 min read

Organizing Tasks with Dependencies

Use dependencies to ensure tasks are completed in the right order and manage complex projects effectively.

Best Practices Tasks Dependencies
1

Understanding Dependencies

Dependencies define the order tasks must be completed. If Task B depends on Task A, then Task A must be finished before Task B can start.

This prevents agents from:

  • Working on tasks before prerequisites are done
  • Creating merge conflicts from parallel changes
  • Building on incomplete foundations
2

When to Use Dependencies

Add dependencies when:

  • One task builds on another's work
  • Tasks modify the same files
  • There's a logical sequence (design → implement → test)
  • Database migrations must happen before code changes
Don't over-use dependencies—only add them when truly needed.
3

Creating Dependencies

When creating or editing a task:

1. Find the Dependencies field
2. Select tasks that must complete first
3. The dependent task will be blocked until prerequisites finish

Blocked tasks show which dependencies are incomplete.

4

Dependency Best Practices

Best practices:

  • Keep chains short: Long dependency chains slow down work
  • Avoid cycles: A can't depend on B if B depends on A
  • Group related work: Use Goals to organize related tasks
  • Review regularly: Remove dependencies when no longer needed

You're all set!

You've completed all the steps in this guide.

Next →
Using Complexity and Priority Effectively
Back to all resources