start-work

Identifies the next Ready GitHub issue and moves it to In Progress via gh CLI.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/eygraber/jellyfin-kmp --skill start-work-eygraber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-work
Source: https://github.com/eygraber/jellyfin-kmp/tree/main/.claude/skills/start-work
Command: npx skills add https://github.com/eygraber/jellyfin-kmp --skill start-work-eygraber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

This skill helps software teams quickly identify and begin work on the most important GitHub issues, reducing context switching and delays by prioritizing Ready items and enabling targeted filtering by epic, label, or description.

Core Features & Use Cases

  • Prioritized issue discovery: finds the highest-priority Ready items first.
  • Flexible filtering: supports epic, label, and description-based searches to narrow scope.
  • Fast start: moves selected issue to In Progress and provides context for immediate work.

Use Case: A developer wants to pick up the next Epic's first sub-issue that is ready and unblocked.

Quick Start

Run /start-work to fetch and begin the next ready issue on your project.

Frequently Asked Questions about start-work

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

FAQPage Schema
How do I start the next ready GitHub issue from my project board automatically?

To start the next ready GitHub issue automatically, this skill identifies the highest-priority Ready items using gh CLI commands and moves the selected issue to In Progress. It prioritizes issues by project priority and presents options for immediate work.

Can I filter GitHub issues by epic, label, or description before starting work?

Yes, you can filter GitHub issues by epic, label, or description before starting work. The skill supports optional filtering to target specific work items, allowing you to narrow the scope of automated issue discovery to match your current sprint or epic focus.

Do I need gh CLI and jq installed to automate GitHub issue prioritization?

Yes, you need gh CLI and jq installed to automate GitHub issue prioritization. The skill relies on gh CLI commands to interact with repository metadata and jq to parse JSON responses, moving Ready items to In Progress based on project priority.

What is the best way to pick up the highest priority unblocked issue from a GitHub kanban board?

The best way to pick up the highest priority unblocked issue from a GitHub kanban board is using this skill. It queries Ready items, sorts them by priority, and moves the selected issue to In Progress, reducing context switching and delays for software teams.

How does the start-work skill move issues to In Progress on GitHub Projects?

The start-work skill moves issues to In Progress on GitHub Projects by executing gh CLI commands against repository metadata. After identifying and filtering the next Ready issue by priority, it updates the project status and provides context for immediate development.

Are there limitations when filtering GitHub issues by description for automated workflow selection?

When filtering GitHub issues by description for automated workflow selection, limitations depend on the gh CLI query capabilities and repository metadata accuracy. The skill targets Ready items specifically, so issues not in the Ready column will not be discovered or moved to In Progress.