Yesterday I shared mav. I have been thinking a lot about validation: making sure changes satisfy a given rule like tests passing.I tried everything but it still required manual intervention from me. That did not scale.
Some example cases: if swift code changed review using this skill. If a view was changed ensure this was used. If this module changed build only this changes.
So today I'm introducing musts, a small Rust CLI that creates a validation loop. The agent runs musts validate when it thinks it's done. musts knows what changed in your project and returns the validations that have to run before the task can close.
The agent records evidence. When musts is happy, the loop closes and the changes are done, for real. Please give it a try and let me know if it works for you.
https://github.com/bitomule/musts
https://blog.bitomule.com/posts/introducing-musts
GitHub - bitomule/musts: The validation loop that stops AI coding agents from claiming work is done before it actually is.

The validation loop that stops AI coding agents from claiming work is done before it actually is. - bitomule/musts

GitHub
With this, I'm closing the loop with three nice tools: Koubou, which automates screenshots for the app store; Mav, which enables the agent to drive the simulator and record evidence; and Musts, which puts everything together.