I personally have not had good luck with loops due to similar issues as the post author - but if you were to port your flow to "looping" it would be something like:

- An automation that periodically checks for PRD's at a given location that have not yet been implemented.

- If it sees one not implemented, it puts a lock on it (so other agents later don't pick it up while its still working) and implements the PRD in code, assuming it has the figma link and all specs required.

- When its done it makes a PR, waits for if it passes and even in some cases automatically merges into your staging/preview enironments and just pings you with a build/URL. You can then leave feedback or something and it can also also poll for pending feedback. Or you just mark it looks good, the agent then merges the PR, moves the PRD to implemented status, maybe even writes/updates docs and cleans up any temporary work.

- Repeat checking for new PRD's every T unit time. (10 minutes, 1 hour, etc)

This is how people say you should be looping - you never even cared or looked at the code, and also never prompted the agent yourself.

But I find most agents are often pretty bad still at replicating UI vs making something from scratch and most design specs are still not as detailed around how things look at all sizes, in all scenarios etc. Design seems to be one of those things that still requires a human to validate. And then all the things the post author mentions about it not being willing to apply hard constraints, minimize impossible states, validate at edges and prevent horrendous overchecking of things. etc.