Triage and resolve issues reported by beta users across FlowInCash and Crispi apps
Use this skill when Bob forwards a user-reported issue or monitoring detects user-facing errors.
| Symptom | Likely Cause | First Check |
|---|---|---|
| "Balance is wrong" | Plaid sync stale | Last sync timestamp |
| "App won't load" | API server down | Express logs |
| "ChatGPT tool broken" | MCP server crashed | See mcp-protocol-recovery |
| "Goals disappeared" | goal-tracker restarted | Expected (in-memory) |
| "Can't sign in" | Auth token expired | Auth service logs |
When fixing: state the cause, what you'll change, which project. Run tests, commit.
When escalating to Bob: include what user reported, what you found, 2-3 possible causes ranked by likelihood. Never contact users directly — all communication goes through Bob.