github-issues

Manage agent work items through GitHub Issues lifecycle labels.

1|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/EmmittJ/guild --skill github-issues-emmittj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/EmmittJ/guild/tree/main/plugin/skills/setup/assets/skills/github-issues
Command: npx skills add https://github.com/EmmittJ/guild --skill github-issues-emmittj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Issues provide a lightweight, centralized store for coordinating a team of agents by mapping work status to labels and using open/closed states to indicate progress. It enables ready work discovery, claims, blockers, and completion tracking without a complex runtime.

Core Features & Use Cases

  • Lifecycle tracking: open issues with no labels are ready, open issues with in-progress are claimed, open issues with blocked denote blockers, and closed issues signify completion.
  • Label-driven priorities: optional priority labels (priority: high/medium/low) help sort work by importance.
  • Structured work creation: create issues with a clear What/Done when/Context pattern, and reference discoveries to maintain lineage.
  • Use Case: a team creates an issue for a feature, marks it ready, then transitions to in-progress, blocks issues when blocked, and closes when done.

Quick Start

Create a GitHub issue in your repository, then apply a priority label and use in-progress and blocked labels to manage work.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I track team tasks using GitHub Issues and labels?▼

Track team tasks using GitHub Issues by mapping work status to labels like ready, in-progress, and blocked, while using open and closed states to monitor progress and completion across sessions.

What is the best way to coordinate work claims and handoffs for a team of agents?▼

Coordinate work claims and handoffs by enforcing lifecycle rules on GitHub Issues, applying in-progress labels to claim tasks, and transitioning through blocked states to signal handoffs.

How does the GitHub Issues lifecycle model work for task tracking?▼

The GitHub Issues lifecycle works by treating open unlabeled issues as ready, applying in-progress labels when claimed, marking blocked for obstacles, and closing issues to signify done.

Can I use priority labels to sort team work items in GitHub?▼

You can use optional priority labels like priority: high, medium, or low to sort team work items by importance, helping agents identify and claim the most critical GitHub Issues first.

How do I structure new work items when creating GitHub Issues for agents?▼

Structure new work items by creating GitHub Issues with a clear What, Done when, and Context pattern, and reference existing discoveries to maintain lineage across the team workflow.

Do I need a complex runtime environment to manage agent task tracking with GitHub?▼

You do not need a complex runtime to manage agent task tracking; GitHub Issues provide a lightweight, centralized store for coordinating claims, blockers, and completion without extra infrastructure.