Talk in Small Bites | Directing Agents

A situation you may recognize

Door A is on the table: deleted_at, filter defaults, block login, admin restore.

You could demand a twenty-section plan. You could also talk for an hour with no finish line. Both miss the point of this session.

The useful middle is a short conversation that keeps each decision small enough to hold: one trade-off, one blast-radius question, one next step.

Why conversation fits the human

Formal dumps ask you to hold the whole structure while deciding. Conversation offloads that load into turns. You answer one question. Then the next. The agent keeps the thread. You keep judgment.

That is not anti-rigor. It is cognitive fit: smaller bits, same ownership. Plan mode tried to help the model focus. Small-bite talk helps you focus while still aiming the model.

A five-minute soft-delete talk

Use turns like these. Stop when you can retell the road.

Turn 1: path

Propose 2-3 high-level ways to soft-delete users. One paragraph each. No code.

Turn 2: choose

I want smallest safe change. Which door fits, and what are we not doing?

Turn 3: blast radius

For that door, what breaks in auth, default lists, sessions, and billing if we are careless?

Turn 4: next step

What is the single next step you recommend, and what should wait?

Turn 5: stop condition

Restate the chosen road in five lines I can own. Still no implementation.

Each turn has one job. If the answer sprawls, ask it to shrink. Sprawl is the formal dump sneaking back in through chat.

Grill questions that fit in a bite

You do not need twenty questions. You need a few that map to attention:

Question	Focus
Why this road and not the other?	Path choice
What existing code does this assume?	Hidden coupling
What would you refuse to change?	Scope
Where is the blast radius?	Sideways damage
What could look done while still wrong?	False finish
What is the next step only?	Momentum without marathon

Ask for short answers. Fuzzy answers become fuzzy diffs.

When to stop talking

Stop when you can do all three:

Retell the chosen road in your own words
Name the main blast-radius risks you accept or refuse
Name the next step

If those three are clear, more chat is often stalling. Session 5 turns the talk into a short owned summary, then action.

Before Session 5

Session 5 is the lock: write the short plan you now own, then let implementation start against it.

Looking back

“The fastest way to own a plan is to read the whole thing once, carefully.”

If you skipped the question at the start, read the steadier read below and note what you would have written.

The steadier read

Working memory is small. Conversation offloads cognition into smaller bits: one trade-off, one risk, one next step. That is not avoiding rigor. It is matching how humans decide without drowning in a document.

Reflect

Compare the steadier read with what you wrote. Where in your week would a five-minute talk beat a ten-page plan?

Reading a whole formal plan once carefully sounds responsible and often overloads the exact working memory you need for the decision. Small-bite talk is how you keep path, blast radius, and next step decidable. When you can retell the road, stop talking and prepare the summary. That is Session 5.

Next: Session 5: Summarize, Then Act