[yodon]

I'm a huge fan of spec-kit, and am actively looking for a replacement for it because spec-kit is no longer maintained by the team at GitHub.

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).

[waleedk]

Yes, this is spec kit on steroids. In particular specs + protocol enforcement works _really_ well. The protocol enforcement is the game changer: I would find the AI just wouldn't stick to specs or plans.

Great suggestions. I will do that. Did you notice any specific issues in those?

Got it about the core flow. Appreciate it. I plan to record a video showing how to kick off a new project and another one showing how to use it in maintenance mode. Would that be helpful?

@yodon if you would like to reach out to me at [e-mail] I'd love to get your feedback once those assets are ready.