flow-issues

Fetch open GitHub issues and generate a prioritized work order dashboard.

25|3|Updated Feb 19, 2026

Search Tags:#github #analysis #dashboard #flow #issues #triage #ranking

Ready to run

npx skills add https://github.com/benkruger/flow --skill flow-issues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flow-issues
Source: https://github.com/benkruger/flow/tree/main/skills/flow-issues
Command: npx skills add https://github.com/benkruger/flow --skill flow-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetches open issues from the current repository, analyzes their potential impact, and presents a prioritized dashboard to guide work.

Core Features & Use Cases

Fetches all open issues via GitHub API.
Analyzes each issue for impact using labels, milestones, age, and activity signals.
Generates a ranked work order and a read-only dashboard for planning.
Supports readiness filters and ready vs blocked differentiation to guide autonomous execution or planning phases.

Quick Start

Execute /flow:flow-issues to fetch and display the prioritized issues dashboard.

Frequently Asked Questions about flow-issues

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

FAQPage Schema

How do I triage GitHub issues to find the most impactful work?▼

To triage GitHub issues, this Skill fetches all open items from your current repository, analyzes their impact using labels, milestones, age, and activity signals, and outputs a prioritized dashboard ranking the most critical work first.

What is the best way to rank ready versus blocked GitHub issues for planning?▼

Ranking ready versus blocked GitHub issues is handled by applying readiness filters to your repository data, differentiating actionable items from blocked ones, and generating a prioritized work order to guide planning phases.

Does this GitHub issue analysis dashboard modify my repository data?▼

No, this GitHub issue analysis dashboard operates strictly in read-only mode. It fetches open issues via the GitHub API to analyze impact and display a ranked work order without modifying any repository data.

Can I use issue labels and milestones to prioritize my repository work order?▼

Yes, you can use issue labels and milestones to prioritize your repository work order. The analysis evaluates these metadata signals alongside issue age and activity to generate a ranked task list.

How do I generate a prioritized work order from open GitHub issues?▼

To generate a prioritized work order from open GitHub issues, run the dashboard command to fetch all open items, apply impact analysis and readiness filters, and output a ranked list with start commands for autonomous execution.