Working solo the hardest part isn’t writing code. Its the fact that nobody tells you your idea has gaps before you’re 4 hours deep. I keep running into the same thing. I start building, everything makes sense in my head, then halfway through I realize I didn’t think about some obvious edge case. The kind of thing someone would’ve caught in a 10 minute design review. I tried writing specs but it’s pointless when you’re reviewing your own work. You just agree with yourself. So I made this Claude Code skill for myself that basically interviews me before I start coding. You give it a requirement and it reads your codebase first, then goes through questions one at a time. The part I didn’t expect to like is that it actually pushes back. Like if you’re overcomplicating something or skipping security stuff it won’t just let you move on. Been using it for a couple weeks on my own projects and it’s caught things I would’ve definitely missed. Not every time, but enough that I don’t start building without running it first now. Open sourced it if anyone wants to try: https://github.com/Sorbh/interview-me One file, takes 30 seconds to install. Would be curious to hear how it works for someone else’s workflow or if you guys have a better way of handling this. Disclosure: This is my own project. I built it and open sourced it. submitted by /u/Fragrant-Phase-1072
Originally posted by u/Fragrant-Phase-1072 on r/ClaudeCode