oh-my-issues

1# oh-my-issues
2 
3Turn 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.
4 
5## Core principle
6 
7Stop 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 whose body is the design), 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.
8 
9This 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.
10 
11## When to use
12 
13- The repo has 20+ open issues and many feel like duplicates or platform-specific symptoms of the same defect.
14- The user asks to "triage", "consolidate", "cluster", "dedupe", "group", or "make a plan from" the issue list.
15- A new bug is filed and the user wants to know whether it belongs to existing work.
16- The user wants to ship a focused PR that resolves a cluster of related issues.
17 
18## When NOT to use
19 
20- Fewer than ~15 open issues: just close them.
21- Issues are genuinely independent (no shared root causes): one fix per issue is correct.
22…