issue-taxonomy

Classify GitHub issues with type and agent-routing labels.

Updated Apr 1, 2026

Search Tags:#workflow #routing #github #issues #triage #tagging

Ready to run

npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill issue-taxonomy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-taxonomy
Source: https://github.com/lilmuckers/agentic-team-plugin/tree/main/skills/issue-taxonomy
Command: npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill issue-taxonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Issue management often lacks consistent labeling, causing confusion and slow triage. This Skill provides a clear taxonomy to classify issues by high-level types and agent-routing labels to streamline workflows.

Core Features & Use Cases

Provides a standard set of issue-type labels (feature, bug, change, chore, docs, investigation, spike).
Ensures every issue carries both an agent-archetype or workflow-routing label and a high-level type label for quick understanding.
Use Case: When creating or refining issues, apply appropriate labels to guide agents and human reviewers through the expected workflow.

Quick Start

Label a new issue with a primary type and an agent-routing label to enable automatic triage.

Frequently Asked Questions about issue-taxonomy

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

FAQPage Schema

How do I automate GitHub issue triage and routing with consistent labels?▼

Automate GitHub issue triage by classifying issues with high-level type labels and agent-routing labels during creation. This enforces a mandatory combination of issue-type and workflow-routing tags to guide review workflows and ensure consistent labeling across software projects.

What high-level issue types should I use to label GitHub issues for triage?▼

Standard high-level issue types for GitHub triage include feature, bug, change, chore, docs, investigation, and spike. Applying these issue-type labels categorizes the core problem, while an additional agent-archetype label routes the work.

Does GitHub issue tagging require an agent-archetype label alongside a type label?▼

GitHub issue tagging requires a mandatory combination of a high-level issue-type label and an agent-archetype or workflow-routing label. This dual-label approach ensures clear taxonomy, guiding both human reviewers and automated agents through the expected triage workflow.

When should I apply workflow-routing labels to GitHub issues?▼

Apply workflow-routing labels during issue creation and refinement across software projects. This timing ensures every issue carries the required agent-archetype and high-level type tags immediately, streamlining subsequent triage, routing, and review processes.

Why does inconsistent issue labeling slow down software project triage?▼

Inconsistent issue labeling slows down triage because unclear tags cause confusion and misrouting. Applying a clear taxonomy with mandatory high-level type and agent-routing labels solves this by providing immediate context for reviewers and automated agents.