Last reviewed
Correct answer: C. You resume without re-explaining context, and the worker can be briefed from it
Explanation
The principle — a plan you can hand over is worth more than one you can only remember.
Why the key is correct — Anthropic's guidance for work spanning multiple sittings is to pick up where you left off instead of re-explaining context, and a written plan is what makes that possible. The same document does the second job too: a subagent starts fresh and sees none of your conversation history, so a worker that was not there can only be briefed from something written.
Why the others are wrong — coding first risks solving the wrong problem. Equal pieces per sitting is not what a plan is for. And the worker cannot read today's discussion — nothing reaches it unless the brief carries it.
Remember this — write it down and it survives both a break and a hand-off.
Sources — Anthropic's Claude Code common-workflows, best-practices and subagents documentation.
Sources
“When a task spans multiple sittings, pick up where you left off instead of re-explaining context.”
“Letting Claude jump straight to coding can produce code that solves the wrong problem.”
“Each subagent starts with a fresh, isolated context window. It doesn't see your conversation history, the skills you've already invoked, or the files Claude has already read.”
Practise 10 questions on this topic
Take Claude Code Workflows — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.