skills.rest
tiendung
tiendungCOMMUNITY
Explore all skills by this author →
GitHub

flow-next-deps

Identify and visualize epic dependencies and blocking chains with FLOWCTL and jq.

Updated Jan 15, 2026
Search Tags:#workflow#planning#blockers#epics#visualization#dependency-graph#execution-order
One-click install
npx skills add https://github.com/tiendung/flow-next --skill flow-next-deps-tiendung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-next-deps
Source: https://github.com/tiendung/flow-next/tree/main/skills/flow-next-deps
Command: npx skills add https://github.com/tiendung/flow-next --skill flow-next-deps-tiendung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dependencies and blocking relationships between epics are often opaque, hindering planning and timely delivery.

Core Features & Use Cases

  • Visualize epic dependency graphs and identifying blocking chains to reveal execution order.
  • Determine which epics can run in parallel and outline the critical path for project planning.
  • Generate actionable insights for sprint prioritization and risk assessment across epics.

Quick Start

Run the FLOWCTL and jq-based commands to generate and inspect your epic dependency graph.

Frequently Asked Questions about flow-next-deps

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

FAQPage Schema
How do I visualize epic dependencies to determine execution order?▼

To visualize epic dependencies, you must extract dependency data and compute readiness to group epics into execution phases. This identifies blocking chains and reveals the exact execution order for your project planning.

What is the critical path and how do I find epics that can run in parallel?▼

The critical path is the longest sequence of dependent epics blocking project completion. You find parallel epics by mapping the dependency graph to compute readiness, which isolates independent tasks from the blocking chains.

Do I need CLI tools to generate an epic dependency graph?▼

Yes, you need the FLOWCTL CLI tool and jq installed to generate an epic dependency graph. These tools extract, query, and present dependency data to compute readiness and group epics into execution phases.

How can I assess sprint risk by identifying blocking chains across epics?▼

You assess sprint risk by visualizing epic dependency graphs to expose blocking chains. Identifying these blocking relationships generates actionable insights for sprint prioritization and highlights potential bottlenecks.

What is the best way to plan release workflows when epic dependencies are opaque?▼

The best way to plan release workflows with opaque dependencies is to visualize the epic dependency graph. This computes readiness and groups epics into execution phases, clarifying what blocks what and optimizing delivery.

Related Skills

Explore More Product & Management Skills→
raydocsraydocs

flow-next

Manage Flow epics and tasks within a repository using the flowctl CLI.

Community
Intermediate
nmoralescybernmoralescyber

sprint-planning

Plan and prioritize sprint backlog items for solo founder workflows.

Community
Basic
korchasakorchasa

epic

Generate dependency-ordered epic plans with phases, tasks, and status tracking.

Community
Advanced
dkyazzentwatwadkyazzentwatwa
86

gantt-chart-creator

Generate Gantt charts from CSV or code with dependencies and milestones.

Community
Intermediate