# Cluster Issue Backlog

Groups a GitHub issue backlog by root cause and bundles fixes into atomic PRs.

- Repository: https://github.com/thedotmack/claude-mem (109099 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add thedotmack/claude-mem --skill oh-my-issues -g -a claude-code -y`
Codex: `npx skills add thedotmack/claude-mem --skill oh-my-issues -g -a codex -y`
Cursor: `npx skills add thedotmack/claude-mem --skill oh-my-issues -g -a cursor -y`
Gemini CLI: `npx skills add thedotmack/claude-mem --skill oh-my-issues -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add thedotmack/claude-mem`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 N_plans masters in one operation.

The rest: https://github.com/thedotmack/claude-mem/blob/HEAD/plugin/skills/oh-my-issues/SKILL.md