Twice this week, a handoff between two AI systems stalled out instead of finishing the job. One cost four days before I caught it. Here's what actually fixed it, and the reusable check that catches it next time.
I fixed a font-loading bug on the site you're reading right now, on a stack that still hasn't cost me a dollar to run. Here's what broke and the prompt to build your own.
I spent two days building a mission-control dashboard for my one-person business, then froze it and went back to running my day off a single page of plain text. Here's the file, the one question that keeps me on the real work, and the prompt I use to kill my own shiny objects.
I built a pipeline that scans YouTube, ranks topics by who I'm writing for, and drafts my blog, Substack post, and Note before I wake up. This week it produced the first drafts of two published posts. I just edited them.
I tested Kit #3's actual workflows on my own inbox before selling it. One came back almost silent. The other found a commitment I'd forgotten I owed someone for twelve days.
My membership had an August launch date. I deleted it and wrote a number in its place: 50 subscribers before launch. Then I checked the current count. Four, and one of them is me.
My first product sat finished in a folder for two months while I waited to feel ready for the launch infrastructure. I treated the launch as a checklist instead of a department and shipped it in three evenings, for the price of a one-dollar test purchase.
I read one line about how AI memory works, then audited the three files my assistant loads before every session. They were three to four times heavier than they should be, and trimming them surfaced three processes I thought were running but weren't.
I built a stalest-first view of every open project in my vault and immediately discovered I was running the same onboarding initiative as two separate workstreams.
I built an AI workflow to cut 90 minutes off weekly newsletter prep, and somehow ended up with half the company on the distribution list.