OpenParable
Skip to content
← Back to skills

Dependency Tracking

Productivity
dependency-tracking

Dependency Tracking is an Agent Skill for productivity published in the aj-geddes/useful-ai-prompts repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Map, track, and manage project dependencies across teams, systems, and organizations. Identify critical path items and prevent blocking issues through proactive dependency management.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/aj-geddes/useful-ai-prompts/blob/HEAD/skills/dependency-tracking/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dependency-tracking, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Dependency Tracking

Table of Contents

Overview

Dependency tracking ensures visibility of task relationships, identifies blocking issues early, and enables better resource planning and risk mitigation.

When to Use

  • Multi-team projects and programs
  • Complex technical integrations
  • Cross-organizational initiatives
  • Identifying critical path items
  • Resource allocation planning
  • Preventing schedule delays
  • Onboarding new team members

Quick Start

Minimal working example:

# Dependency mapping and tracking

class DependencyTracker:
    DEPENDENCY_TYPES = {
        'Finish-to-Start': 'Task B cannot start until Task A is complete',
        'Start-to-Start': 'Task B cannot start until Task A starts',
        'Finish-to-Finish': 'Task B cannot finish until Task A is complete',
        'Start-to-Finish': 'Task B cannot finish until Task A starts'
    }

    def __init__(self):
        self.tasks = []
        self.dependencies = []
        self.critical_path = []

    def create_dependency_map(self, tasks):
        """Create visual dependency network"""
        dependency_graph = {
            'nodes': [],
            'edges': [],
            'critical_items': []
        }

        for task in tasks:
            dependency_graph['nodes'].append({
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Dependency MappingDependency Mapping
Dependency Management BoardDependency Management Board
Dependency ResolutionDependency Resolution
Dependency Dashboard MetricsDependency Dashboard Metrics

Best Practices

✅ DO

  • Map dependencies early in planning
  • Update dependency tracking weekly
  • Identify and monitor critical path items
  • Proactively communicate blockers
  • Have contingency plans for key dependencies
  • Break complex dependencies into smaller pieces
  • Track external dependencies separately
  • Escalate blocked critical path items immediately
  • Remove unnecessary dependencies
  • Build in buffer time for risky dependencies

❌ DON'T

  • Ignore external dependencies
  • Leave circular dependencies unresolved
  • Assume dependencies will "work out"
  • Skip daily monitoring of critical path
  • Communicate issues only in status meetings
  • Create too many dependencies (couples systems)
  • Forget to document dependency rationale
  • Avoid escalating blocked critical work
  • Plan at 100% utilization (no buffer for dependencies)
  • Treat all dependencies as equal priority