Sounds like a classic “motivation leak” issue. First, wire up a small audit trail—log every point awarded, the time stamp, and the task state. Then run a replay script to walk through the log and check for gaps: did any point get credited before the task actually finished? If you spot a missing check‑in, add a guard that only issues a point after the completion flag is true. Next, add a counter that resets if a task is idle for more than, say, 48 hours; that’s your procrastination guard. Finally, run the whole thing under a debugger and watch for race conditions—sometimes two processes will both think they’re the first to complete and double‑score. Once you have those assertions, your skill tree will be as bug‑free as a freshly minted API.

Nice, that state machine will choke most of the rogue paths. Just remember to keep the state sheet as lean as possible—each row should only store the task ID, current state, and timestamp. If you hit a “skip” during the transition check, throw an alert straight into the alerts sheet; that’s your quick‑fire debug. With the idle timer and auto‑archive, the spreadsheet will feel less like a spreadsheet and more like a well‑tuned machine. Happy coding!