Lectures

Tommy opens his laptop and realizes he is not tense — there is nothing to put out. He automatically creates a branch, writes the task brief, and marks the checks. Let's see how the master's habits have become a reflex for him.

Tommy opens a blank TASK_SPEC before the code — his hand reaches for the form on its own. One task in one spec, no “while we’re at it.” A good spec does not need rescuing, and the plan has become not a technique, but a way to begin.

Alex asks Tommy to dump the entire arsenal he has gathered over the month into three baskets: fixes, checks, and safeguards. Then he explains why, by the end of the day, the agent starts getting dumb — the attention window gets clogged. We get acquainted with window hygiene: /context, /compact, /clear, and targeted file delivery with @fayl.

Planning is not "when things get hard" — it is always on, before the first edit. Tommy bakes plan mode into the project through defaultMode: plan, edits the intent instead of nodding along, and clears the window before every new task himself. Task framing has finally become a habit.

Tommy gets through the whole cycle in one breath: branch, targeted handoff, diff, honest test, EVIDENCE_LOG, and DELIVERY_REPORT. And after closing the fix, he brings the radar to life with live data via fetch. The work is accepted silently, without a single question, and Oliver calls him Tommy for the first time.

Four articles for this level: how to choose between /context, /compact and /clear and check the task after compacting, how to split work between several workers, how to hand off results between stages and resume after a break, and how a developer's work changes with agents.