Comment by prohobo

Bringing model-driven development to coding agents with a desktop tool called Scryer:

https://github.com/aklos/scryer

It's still pretty experimental, but I think now that AI can feasibly generate code from intent/specs it's worth doing... especially with how much vibe coding is both a blessing and a curse.

Basically, what if we took those markdown specs everyone likes using and systematized them into a model graph, anchored claims to code, then represented that as a wiki? And what if we surfaced a planned change to a codebase as a diff of the definition of that model? You can then properly keep track of what gets implemented and how, because you're no longer reading an essay from the agent as a plan, you see a complete diff of everything it plans to do.

I've been using it myself for work, but it'd be nice to get some feedback from other people's perspectives.