Comment by agileAlligator
5 days ago
I just YOLO it. Just don't give it access to anything that can produce permanent consequences. The cost of a mistake is maybe one hour of fixing it. If what it produced is 80% right and 20% wrong, by letting it run overnight, you've gotten 80% of the work done that otherwise wouldn't have happened.
If you have work building on top of other work, your "20% wrong" quickly turn into "80% wrong".
If feature B depends on implementation of feature A, and feature A happens to be on the 20% wrong side, then feature B will be wrong too, regardless of whether you happen to have better luck with it being implemented on the 80% right side. It'll simply be built on a broken foundation. It WOULD have been correct if the foundation was right, but it wasn't.
This is actually very common in software development, where you rarely have stuff happening in isolation. A lot of features deliberately touch each other, build on top of each other, and even more so when you factor in "accidential" overlap due to unclean technical boundaries (in spaghetti code, everything touches everything).
Yeah this is why you have your top guy (Fable/astra) split everything into discrete tasks and go one layer at once. Get 10 subagents working on parallelized tasks that have no dependencies on each other through the night.
This was a problem maybe 6 months ago. With Fable/Astra orchestrating Opus/Sol subagents it now works really well.
Ask it to interview you before you start and it'll get your constraints pretty well.