Question 1 · choose 1
You need to replace a date library across about 60 files. There are two plausible strategies, a thin wrapper module or direct calls to the new library, and parts of the codebase use the old library in unusual ways. How should you run this in Claude Code?
- AStart in plan mode to explore the usages and settle the strategy, then approve the plan and let Claude implement it
- BDelegate the 60 files to parallel subagents, each converting its files in whichever way it judges best
- CHave Claude convert one typical file each way in acceptEdits mode, then pick the strategy from those two diffs
- DWrite the wrapper module yourself, then have Claude convert all 60 files to use it directly
Show the answer and why
AStart in plan mode to explore the usages and settle the strategy, then approve the plan and let Claude implement it
Correct
Plan mode separates exploration and design from editing, which suits multi-file work with competing approaches; execution follows the approved plan.
BDelegate the 60 files to parallel subagents, each converting its files in whichever way it judges best
Incorrect
Each subagent would pick its own strategy, so the codebase could end up with both approaches and no one decision behind them.
CHave Claude convert one typical file each way in acceptEdits mode, then pick the strategy from those two diffs
Incorrect
One typical file does not show the unusual usages that decide between the strategies, and edits start before the approach is settled.
DWrite the wrapper module yourself, then have Claude convert all 60 files to use it directly
Incorrect
This commits to one strategy before anyone has explored how the unusual usages would fit it.
Use plan mode for large, multi-file changes with more than one valid approach, and combine it with execution: explore and plan the migration, approve the plan, then implement it.
Anthropic documentation