Agent skill · product strategy · thedotmack
oh-my-issues
Cluster a GitHub issue backlog by root cause into a small set of plan-master issues, redirect children with a standardized comment, and bundle architectural-fix PRs that close clusters atomically. Use when an issue tracker has accumulated dozens of reports that share underlying defects, when asked to triage / consolidate / cluster / dedupe issues, when asked to build a plan series or roadmap from open issues, or when routing a new incoming bug into an existing plan.
Why this skill is useful
Provides a structured workflow for clustering GitHub issues into architectural plans, which the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. About 7k tokens when loaded. Last updated 2026-08-05. 89,894 stars on the source repository.
What this skill does
oh-my-issues Turn an issue backlog into a roadmap. Issues are symptom data, not units of work — the unit of work is the architectural defect that produces them. The end state is open issues == open plans, 1:1. Core principle Stop closing issues one at a time. Group symptoms that share a single architectural fix into a cluster, give the cluster one canonical home (a plan-master issue + a plans/0X-.md design doc), close every child with a standardized redirect, and ship one PR per cluster that closes all children atomically. New incoming bugs get appended to the matching master as a "Round N" comment, not opened as new tracked issues. This compounds three ways: architectural fixes retire whole symptom families, the plan's test matrix institutionalizes prevention in CI, and standardized triage makes residual inflow cheap. When to use The repo has 20+ open issues and many feel like duplicates or platform-specific symptoms of the same defect. The user asks to "triage", "consolidate", "cluster", "dedupe", "group", or "make a plan from" the issue list. A new bug is filed and the user wants to know whether it belongs to existing work. The user wants to ship a focused PR that resolves a cluster of related issues. When NOT to use Fewer than ~15 open issues: just close them. Issues are genuinely independent (no shared root causes): one fix per issue is correct. The repo lacks plans/ discipline and the user does not want to introduce one — propose first, do not impose. Three modes Mode 1: Cluster pass (initial reduction) Use when the backlog has never been consolidated. Goal: go from N issues to Nplans masters in one operation. 1. Read everything in full. Fetch every open issue's body and its comment thread — not just titles. Surface-level grouping fails without full text, and reproduction steps, linked duplicates, and diagnostic output often live in comments rather than the original body. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thedotmack/oh-my-issues