Codev looks like it has a lot of good similarities to spec-kit, and like it's something I need to pay close attention to. That said, I'll encourage you to do another pass on your command names, intros, and cheat-sheet.
I suspect most developers using codev will mostly use a very small fraction of the codev commands most of the time, similar to the way spec-kit is mostly /specify, /plan, /tasks, and /implement, with a bit of /clarify and /analyze once you really get comfortable with it. If I'm right, having some docs where you emphasize the simplicity of your core flow would be very helpful.
For calibration, five minutes into reading your home page and medium post and some of your repo docs, I'm ready to believe this is true, but I have no idea what that core flow is or looks like. Five minutes is actually a pretty long time, and I suspect most visitors will end up bouncing if they don't get clarity on what the experience is ultimately going to be like for them in five minutes (or, more likely, much less than five minutes).