Domain 1 · 14% of the exam
Prompting and Task Execution
Write prompts that give Claude what a capable colleague would need, break big requests into checkable steps, improve results with specific feedback, and tune your approach to the kind of task.
Task statements
- 1.1
Effective Business Prompts
A strong business prompt reads like a clear brief to a capable new colleague. It states the role Claude should take, the context behind the request, the constraints that matter, and the format the result should arrive in. Structure beats intensifiers: adding 'be thorough' helps far less than adding the missing context.
- 1.2
Task Decomposition
Compound requests fail quietly because Claude has to juggle too many goals in one pass. Splitting the work into a chain of smaller prompts, each with a checkable output, gives you a point to inspect and correct before errors carry forward.
- 1.3
Iterative Prompt Improvement
The first response is a draft to refine, not a verdict. Improvement comes from specific feedback that says what to keep, what to change, and why. Regenerating and hoping gives you a new random draw instead of progress.
- 1.4
Prompt Strategy by Task Type
Different tasks need different prompting. Analysis wants source material and a clear question. Research wants scope and a way to check claims. Drafting wants audience, voice, and examples. Brainstorming wants room to explore before you narrow.