Check Before You Build
Search the marketplaces you trust before building, then recommend adopt, adapt, or build with reasons.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Check Before You Build
Dana has the shipkit brief and part map and wants to start building today. Priya asks first whether someone has already built this. A search of the team's two added marketplaces, its own `acme-tools` and a public community one, turned up three release-notes and changelog…
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.
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.
Describe Environments and Stages
Map the release path: each environment, what sends changes there, and the checks that must pass first.