I built a Claude Code workflow for people who know what they want to build, but not how to build it

Wait 5 sec.

I have ideas I want to turn into real projects, but I’m not a developer. I started with no-code tools, but eventually I wanted something more robust — something that could actually build software properly, not just help me piece things together. That’s what led me to Claude Code. What I wanted was simple: I explain what I want to build, and Claude handles how to build it. But I kept running into technical questions I wasn’t really in a position to answer: “Which library do you want?” “Which architecture should I use?” “Should I implement it this way or that way?” And my answer was basically: **I don’t know. That’s why I’m asking you to build it.** Then there was the constant intervention: **Continue. Proceed. Run the tests. Review it. Fix it. Continue again.** So I built **Meta-XoT-OSS-Rail**, a free, open-source Claude Code plugin. The idea came from one question: **What if writing the code wasn’t the agent’s goal? What if completing the development process was?** So I turned the process into a scoring game. Every step gets a score, together forming a target vector, and the agent tries to push that vector to its maximum. That means producing code isn’t “done”. It has to keep moving through: **study → plan → implement → test → review → fix** until the implementation is actually delivered. The workflow is enforced with hooks, rather than relying only on instructions in a prompt, and the implementation also goes through independent AI review/orchestration instead of the same agent simply declaring its own work good enough. My role is supposed to stay simple: **I explain what I want. Claude decides how to build it.** It should stop only when it has delivered the implementation or genuinely needs a business decision from me. It has now grown to **29 skills, 6 hooks and 15+ supporting code files**, but the original goal hasn’t changed: **I want to give Claude a business requirement, not manage an AI developer.** If you want to try it: Meta-XoT-OSS-Rail This is probably not aimed at experienced developers who already know exactly how they want their software built and are comfortable making all the technical decisions themselves. But if you’ve had the same problem I had — you know what you want to build, but you don’t want to manage every technical decision or keep pushing Claude through the process, give it a try and let me know how it works for you, what breaks, or what you think should be different.   submitted by   /u/morreus1 [link]   [comments]