User Pain Tracker

Track user pains, feedback, and feature requests. Count how many users hit each one, then prioritize by count.

A dead-simple, dependency-free system: one CSV as the source of truth, one HTML file to view it.

1. Clone the repo.
2. Open index.html in a browser to view current pains.
3. Add feedback (see below).

Open index.html directly. If the browser blocks loading the CSV (the file:// protocol blocks fetch), serve the folder over HTTP:

python3 -m http.server

Then visit http://localhost:8000.

pains.csv is just a CSV — edit it by hand or let a tool do it.

1. Summarize the feedback into one short, canonical pain statement (a generic problem, not a verbatim quote). E.g. "App crashes when uploading large file" → Crashes on large file upload.
2. Look for an existing row covering the same pain (match by meaning, not exact text).
3. If it exists, increment that row's n_requests by 1.
4. If it's new, append a row with n_requests = 1.

This repo ships a /pain command. Run it with raw feedback and Claude handles the summarize → dedupe → increment/append flow for you:

/pain users keep complaining the balance doesn't refresh after deleting a transaction

See CLAUDE.md for the full flow.

• Keep the header row: pain,n_requests.
• If a pain text contains a comma, wrap it in double quotes: "Slow, laggy search",3.
• One pain per row. Keep statements short and de-duplicated.

MIT