What I'm building, and the one part I'm still not sure about

Hey everyone, Adrian here. I'm a software developer and indie maker, and I've been lurking long enough that it's time to actually put something out there.

Quick context on me. I like building software, I like experimenting with new tech, and I'm happiest when I find a simpler way to solve something that everyone else has accepted as complicated. My interests live around developer tools, automation, open source, and AI-assisted development.

So here's what I'm working on. I've been building a tool aimed at the exact problem I kept running into myself: the gap between the stuff I write down and the stuff that actually gets built. Every side project I've ever started died in the same place, in the pile of notes and half-formed plans that never turned into working software.

The idea is simple. You describe what you want in plain language, and the tool turns it into something you can actually run and iterate on, rather than a document that gathers dust.

I'm not going to pretend it's finished or polished. It's early, it's opinionated, and it makes some decisions for you on purpose because I've learned that flexibility is usually where my projects go to die.

The one part I'm genuinely unsure about is how much to automate versus how much to keep in the user's hands.

Automate too much and you get something that feels like a black box you can't trust. Automate too little and it's just another tool that needs babysitting.

I'd love for anyone interested to take a look and tell me which side I've landed on. And if you've built something in this space, I'd genuinely like to hear what you learned, because I'm still figuring this out one week at a time.

Link is in my profile. Happy to answer anything.