Something I recently realized is that the fastest and easiest way to use coding agents is if you apply them to problems where there is just one, obvious solution.
This absolutely relates to architecture. If your system is designed such that any given feature fits in an obvious place, using obvious patterns, with obvious ways to test it... 90% of the time a coding agent will be able to do exactly the right thing from a single, short prompt.
This also makes code review so much less taxing - if the solution is obvious, reviewing and checking that the agent followed that obvious path takes much less time than if you're trying to untangle something a lot more complicated.
Exactly! What I use is a main workflow document where I embed at every step pointers to architecture and templates.
My prompt is ... "We are implementing the X feature. We are at step 6. Plan first"
Then the agent spits out identical plans then identical code for every feature.