Farzam

I asked an AI assistant to review a repo before shipping it.

It came back with a clean report, a confident tone, and a long list of passes. Then I checked one of the lines it cited.

The line said something else. The mistake itself didn't bother me that much. What bothered me was that there was no shape in the output for "I don't know."

Everything was either a problem or a pass. And the passes were doing a lot of unearned work.

I built a whole SaaS landing page with auth and pricing in one prompt and felt like a genius. Showed everyone, tweeted about it, the whole thing.

Then I went back to fix one small bug- the signup button. Instead of just fixing it, the AI assumed I meant a completely different button and changed that instead.
When I corrected it, it "fixed" the issue by rewriting a chunk of the auth logic I never asked it to touch- and broke login entirely in the process.
By the time I pointed that out, it had made three more assumptions to "fix" its own fix, and none of them matched what I'd actually built two hours earlier.

I ended up scrolling back through the entire conversation trying to reconstruct decisions I'd already made, just to get back to square one.

Has anyone actually found a real fix for this, or is everyone just quietly rebuilding the same project for the fifth time?

Hi everyone, I m Farzam
I m building Arioo, and while getting it ready to launch, I realized I couldn t find a checklist that covered everything I was actually shipping:
Backend
Web app
Native clients
Deployment pipeline
AI agents with real tools attached
Most checklists covered only a fraction of that stack. So I built one for my own stack, pulled out the product-specific parts, and turned it into a general open-source checklist. It s now open source, and I m sharing it here mostly to learn from people who have shipped more than I have.
Would love to hear what I m missing.