Stay Organized Under Pressure
When a change touches multiple files, list every file and what changes in each. A numbered list or per-file breakdown keeps both you and Claude from losing track under time pressure.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Multi-File Under Pressure
You're adding a new `status` field to your Order model. This requires changes in the database schema, the API route handler, and the frontend type definition. All three files need to stay in sync.
Other principles in Multi-Step
Architect Before You Ask
Ask for a Plan First
Request a plan before any multi-file change — approve the approach, then let it code.
Break the Workflow into Steps
Number each step so Claude builds pieces, not monoliths.
Combine Context with Action
Coordinate Across Files
Delegate to a Subagent
Spawn a subagent for research-heavy subtasks; brief it on scope, limits, and report shape.