Should you /grill-with-docs, /wayfinder, or just one shot the code? 1. If the diff is tiny, DON'T grill /grill-with-docs saves you from situations where the agent built the wrong thing. But if the t
Why CEREBRO kept it
Agent workflow tradeoffs: grilling specs versus one-shot coding.
The text below is an automated extraction of the article at https://x.com/mattpocockuk/status/2108216899439894574, stored verbatim in the public cerebro-vault repository. Copyright remains with the original publisher (x.com).
1. If the diff is tiny, DON'T grill
/grill-with-docs saves you from situations where the agent built the wrong thing. But if the t
> Agent workflow tradeoffs: grilling specs versus one-shot coding.
Should you /grill-with-docs, /wayfinder, or just one shot the code?
1. If the diff is tiny, DON'T grill
/grill-with-docs saves you from situations where the agent built the wrong thing. But if the thing it's building is tiny, that cost drops to nothing. So one-shotting is absolutely fine when you're only making small changes.
2. Never start with /wayfinder
A failure mode of /wayfinder is that you start grilling and the solution turns out to be way simpler than you thought. Why is this bad? Because you've created the map and tickets, and you realise you don't need them.
So if the expected
Backlinks
Appeared in 1 briefing