10 posts tagged #plan-mode.
Not all code is equally expensive to get wrong. Stop reviewing your agent's output uniformly and start spending your scrutiny where a mistake double-charges a customer.
Subagents are sold as parallelism. The real win is context hygiene plus model arbitrage: delegate read-heavy investigation to cheap explorers so your expensive model only ever sees distilled findings.
Wiring up Stripe or a database you've never touched by vibe-coding traps you at the first failure. Point the agent at the service's docs over MCP and force it to teach you back — close its codebase gap and your knowledge gap in the same pass.
Stop fighting the context limit with a bigger window. Write an exhaustive plan to a file, then run a relay of fresh sessions that each tick off items — so a migration too big for any single context still ships coherently.
An agent reviewing its own plan shares its own blind spots. Wire a different vendor's model in as a deterministic gate, and a fail verdict re-engages planning before a line of code exists.
Reviewing irreversible actions after the fact is too late. Split tools by reversibility in permissions, force a plan, and gate the destructive step behind a human interrupt — autonomy on reads, a hard stop on anything you can't undo.
Hand the agent two committed documents — a requirements doc that fixes the destination and a phased plan that fixes the journey — and a feature too big for one window ships correctly anyway.
Let peer agents talk freely and a query hot-potatoes between them, each disclaiming the task, while your bill climbs. Route everything through one orchestrator with explicit handoff rules and a turn cap, and the chaos becomes a system you can test.
Your judgment — which tradeoff, which edge cases, which empty states — lives only in your head until something extracts it. A saved procedure that explores the repo, then grills you one branch at a time, turns a vague idea into a codebase-aware spec the agent can build against.
A million-token window won't fix a long build. Externalize state to a plan file and run a relay across fresh sessions, because quality dies long before the window fills.