skills.rest
gmickel
gmickelCOMMUNITY
Explore all skills by this author →
Website𝕏@gmickelGitHub

flow-next-deps

Visualize epic dependencies and blocking chains for Flow-Next epics.

674|52|Updated Dec 26, 2025
Search Tags:#workflow#planning#blockers#epics#dependency-graph#execution-phases
One-click install
npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-deps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-next-deps
Source: https://github.com/gmickel/gmickel-claude-marketplace/tree/main/plugins/flow-next/skills/flow-next-deps
Command: npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-deps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams building Flow-Next plugins often struggle to understand how epics depend on each other, identify blockers, and plan execution order across multiple initiatives. This Skill provides a clear visualization of dependencies, blocking chains, and phased delivery.

Core Features & Use Cases

  • Dependency graph: visualize epic interdependencies and blockers for that project.
  • Execution planning: determine which epics can run in parallel and assign stages.
  • Use Case: during sprint planning, quickly see which epics are ready to start and which are blocked by others.

Quick Start

Use this skill to generate a live dependency report and an execution plan for all epics in Flow-Next.

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 and identify blockers for Flow-Next plugins?▼

Epic dependency visualization maps Flow-Next plugin interdependencies and blocking chains into a clear graph. It helps teams understand cross-epic relationships and identify what blocks specific initiatives during development.

How do I plan sprint execution order across multiple epics with dependencies?▼

Sprint execution planning is done by computing epic readiness and assigning execution phases to determine which epics can run in parallel. This identifies the critical path and stages for phased delivery across initiatives.

What is the best way to find the critical path across multiple Flow-Next epics?▼

Finding the critical path across Flow-Next epics involves computing readiness and blockers to map the longest blocking chain. This reveals the sequential dependencies that dictate the minimum project delivery timeline.

Does this dependency graph tool work for cross-epic coordination during sprint planning?▼

Yes, the dependency graph tool supports cross-epic coordination during sprint planning by quickly showing which epics are ready to start and which are blocked. It computes execution phases to align parallel work across initiatives.

How do I determine which Flow-Next epics can run in parallel?▼

You determine parallel Flow-Next epics by analyzing the dependency graph to identify epics with no mutual blockers, then assigning them to the same execution phase. This allows concurrent development across independent initiatives.

Related Skills

Explore More Software Engineering Skills→
tractorjuicetractorjuice

arckit-navigator

Analyze project documentation coverage against the ArcKit baseline.

Community
Intermediate
ngochuy13ngochuy13

timeline-generator

Generate project timelines with dependencies, milestones, and buffered end dates.

Community
Intermediate
danilonovaisvdanilonovaisv
1

github-project-management

Coordinate GitHub issues, boards, and sprint planning across repositories.

Community
Advanced
ChimeraFoundationaChimeraFoundationa

ascii-art

Render text as decorative ASCII art using local CLI tools.

Community
Intermediate