Course-Correct Early
Interrupt as soon as Claude drifts and say exactly what to change. Waiting for a wrong approach to finish costs more.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Pull It Back on Track
A one-line request went to Claude: rename the `id` parameter of `getUserById` to `userId` in `src/services/users.ts`. The session log below shows what came next, until you pressed Esc partway through its `package.json` update. The rename itself looks right. Femi is reviewing…
Other principles in Multi-Step
Ask for a Plan First
For multi-file work, ask for a plan first: files, risks, and open questions. Approve it, then let Claude edit.
Break the Workflow into Steps
Describe each stage and what it hands on, and have Claude test each one before connecting the next.
Check Before You Build
Search the marketplaces you trust before building, then recommend adopt, adapt, or build with reasons.
Coordinate Across Files
For a change across many parts, say what differs between them, not just 'add it everywhere'.
Delegate to a Subagent
Send big searches to a subagent with a clear brief: what to find, no edits, and the shape of the report.
Describe Environments and Stages
Map the release path: each environment, what sends changes there, and the checks that must pass first.