Claude Code
Today
Explore
Practice
Library
Exam
Certificate
Search
⌘K
ខ្មែរ
◐
Sign in
Today
Explore
Practice
Library
Profile
Fan-Out and Batch Work
Today
6. Optional: Automation · 2 of 4
Mark read
Prev
Next
Orient
Enumerate, pilot, then scale
Catch the twenty files during the pilot
Predict
Run a small fan-out end to end
Close
Practice
Related
Fan-Out and Batch Work
Advanced
☆
📑
Two thousand files, one prompt, and the three files you test it on first
Orient
Enumerate, pilot, then scale
Catch the twenty files during the pilot
Predict
Run a small fan-out end to end
Close
Practice
Related
Practice activities and scenarios are optional. Mark the lesson complete after reading, and return to practice whenever it helps.
Restoring your saved work…
07
Optional practice
🧠 Optional scenario practice
Q1
Why use one
claude -p
invocation per file rather than one session for the whole batch?
A
It is cheaper in total tokens
B
Each run gets fresh context, failures stay isolated, and the unit of retry is a single file
C
Sessions cannot edit more than one file
D
Only per-file runs support --allowedTools
Q2
All 800 per-file runs report OK but the build fails. What was missing from the design?
A
A larger --max-turns value
B
A project-level build and test run after the loop, since per-file checks cannot see cross-file inconsistency
C
The --output-format json flag
D
A wider allow list
08
Up Next
Advanced
Scheduled and CI Work
Advanced
Team Rollout and Governance
📝 Notes
Mark lesson complete
Next: Scheduled and CI Work →