task-dep-analysis

Analyze task dependency graphs to produce execution order, cycle detection, critical path, and sprint groupings.

133|9|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/lync-cyber/CataForge --skill task-dep-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-dep-analysis
Source: https://github.com/lync-cyber/CataForge/tree/main/.cataforge/skills/task-dep-analysis
Command: npx skills add https://github.com/lync-cyber/CataForge --skill task-dep-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a dev-plan task list into a deterministic dependency model so teams can see execution order, spot blocking cycles, and plan work with fewer scheduling mistakes.

Core Features & Use Cases

  • Dependency Modeling: Extracts task edges from sprint tables, dependency text, and task metadata into a clean DAG.
  • Validation & Planning: Detects cycles, produces a topological order, computes the critical path, and suggests Sprint groupings.
  • Use Case: When a dev-plan contains dozens of tasks with hidden blockers, use this Skill to identify what can run in parallel and what must wait.

Quick Start

Ask the skill to analyze the dev-plan document path and return dependency order, cycle status, critical path, and Sprint grouping suggestions.

Frequently Asked Questions about task-dep-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the critical path for a dev-plan task list with complex dependencies?

Finding the critical path for a dev-plan involves analyzing task dependency graphs to calculate weighted execution times. This Skill extracts task edges from metadata and applies deterministic graph processing to compute the critical path and suggest Sprint groupings.

What is the best way to detect circular dependencies in a sprint planning task table?

Detecting circular dependencies in a sprint planning task table requires cycle detection on a directed graph. This Skill parses dependency lists and task card depends_on fields to identify blocking cycles and produces structured JSON results indicating cycle status.

How do I generate a topological sort execution order for task dependencies?

Generating a topological sort execution order for task dependencies involves processing a directed acyclic graph. This Skill extracts task edges from sprint tables into a clean DAG and produces a deterministic topological order for dispatch coordination.

Can I use this for sprint planning with dozens of tasks and hidden blockers?

Yes, you can use this for sprint planning with dozens of tasks and hidden blockers. The Skill models dependencies from dev-plan task lists to identify what tasks can run in parallel and what must wait, reducing scheduling mistakes.

What formats and fields does the task dependency analysis require for cycle checks?

Task dependency analysis requires dev-plan task tables, dependency text, or task card depends_on fields as input. The Skill extracts these edges into a clean DAG to perform topology checks, cycle detection, and weighted critical path calculation.

Why does my task dependency graph fail to produce an execution order?

A task dependency graph fails to produce an execution order when cycles exist between tasks, preventing a topological sort. The Skill applies cycle detection to identify these blocking loops and returns the cycle status in structured JSON results.