Picking what to build next is the part of running a side project I'm worst at. Open the issue tracker, stare at it, close the issue tracker. Repeat next weekend. A few weeks ago I tried something different: instead of asking myself, I asked the people who already left a competitor. There's a specific kind of useful buried in a 1-star G2 review — someone took the time to write down what they wanted and didn't get. That's a roadmap. The problem is reading hundreds of them. So I built GapHunter, a Claude Code skill that does it for me. You run it like this: /gaphunter DBeaver TablePlus Enter fullscreen mode Exit fullscreen mode It searches G2, Capterra, TrustRadius, Reddit, GitHub Issues and Hacker News in parallel, clusters near-duplicate complaints (so "no dark mode" and "lacks dark theme" collapse into one finding), then reads your own repo : package.json, Cargo.toml, the src/ tree — and cross-references the gaps against what you've already shipped.…