Re-Anchor After Compaction
After compaction, restate any decision that lived only in chat and have Claude write it where it will survive.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Re-Anchor After Compaction
The conversation just auto-compacted, four hours into building Billbird's new CSV export. Two hours ago you and Claude agreed in chat that the existing `/api/export` endpoint stays exactly as it is until the mobile app ships v5, and all new behavior goes behind a new…
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'.
Course-Correct Early
Interrupt as soon as Claude drifts and say exactly what to change. Waiting for a wrong approach to finish costs more.
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.