Every brief here started as somebody complaining in public. Shipbrief keeps the quotes, counts how often the complaint comes back, and writes up what you would actually have to build.
17 briefs published, each one linked back to the posts it came from.
2 briefs
In Jan 2026 curl, tldraw, and Ghostty all instituted hard bans on AI-generated contributions because LLM-spam PRs and fake CVE reports are now a primary maintainer-burnout vector. Daniel Stenberg (curl): 'Fake and otherwise made up security problems effectively prevent us from doing real project work and waste time and resources.' GitHub provides zero native filtering.
Supabase users repeatedly hit a wall where local supabase/migrations stops matching what's actually applied in the remote Postgres. The tool then refuses to push, refuses to pull cleanly, and offers no first-party 'baseline + reconcile' path. Users end up doing manual SQL surgery on prod or abandoning the migration system entirely. From farmhutsoftwareteam: 'We cannot sync existing production databases when local migration files don't match the 141 migrations already applied remotely.'
A scraper reads public posts on X, Reddit and Hacker News every day — the ones where somebody is describing a problem rather than launching something.
Claude pulls the specific complaint out of each post. The same complaint, from different people in different places, collapses into one node in a graph that keeps growing.
Once a cluster has enough corroboration it becomes a brief: the problem, who has it, who already tried to solve it, and what you would have to build. Nothing is published off a single post.