dependency-analysis

Dependency Analysis Skill

This skill helps identify, validate, and manage dependencies between tasks.

Types of Dependencies

1. Technical Dependencies

One task requires another's output:

• "Create user type" must precede "Create user repository"
• "Set up database" must precede "Write migrations"
• "Define API contract" must precede "Implement API client"

2. Logical Dependencies

Natural ordering based on workflow:

• "Design UI mockup" before "Implement UI"
• "Write tests" before "Implement feature" (TDD)
• "Create component" before "Style component"

3. Resource Dependencies

Shared resources or infrastructure:

• "Set up CI/CD" enables "Automated testing"
• "Configure environment" enables "Deploy to staging"

Identifying Dependencies

Questions to Ask

1. Input Requirements: What data/types does this task need?
2. API/Interface: What functions/methods does this call?
3. Infrastructure: What systems must exist?
4. Knowledge: What decisions must be made first?

Dependency Indicators

Code-level:

• Imports a module that doesn't exist yet
• Calls a function not yet implemented
• Uses a type not yet defined
• Queries data not yet modeled

Process-level:

• "After we decide on X..."
• "Once Y is set up..."
• "When Z is available..."
• "Building on the work from..."

Dependency Graph Concepts

In-Degree and Out-Degree

• In-Degree: Number of tasks this depends ON
• Out-Degree: Number of tasks that depend on THIS

High out-degree = Critical blocker (do first) High in-degree = Wait for dependencies (do later)

Critical Path

The longest chain of dependencies from start to finish:

A -> B -> C -> D -> E (critical path = 5)
     \-> F -> G      (parallel path = 3)

Tasks on the critical path determine minimum completion time.

Cycles (Bad!)

Circular dependencies prevent completion:

A depends on B
B depends on C
C depends on A  <- CYCLE!

Always check for and eliminate cycles.

Dependency Patterns