Comment by twosdai

I have run into the same problem, and started calling the phenomenon vision drift.

I noticed that the issue tracker I built was well suited to address this problem, as it handles board time-travel. So a simple command like ":replay 4h" gives you a clear overview of how the workflow has evolved over time, and you can checkout previous states at will.

Wrote more about it here:

https://dev.to/ljtn/vision-drift-addressing-the-next-problem...

Drift is huge between any large spec and agent implementations.

I've done a ton of testing and the model doesn't matter, fable or sol still miss a ton of detail and drift.

I'm building http://engine.build which closes the gap and makes sure the implementation matches the spec.

It's not the same as the satisfaction you get when solving complex problems with code yourself but writing clear specs and thinking through the problem is still very satisfying to me.