Give Claude a long task with a checkable deliverable
Separate evidence, decisions and constraints, specify the output and ask for missing information rather than an invented completion.
In brief
For a long task, Claude needs a clear deliverable and boundaries: what material is evidence, which decisions are fixed and what a finished result must contain. A long background story alone does not define success.
A structured brief lets you inspect whether a draft addressed the requirements without relying on polished wording.
Organize the material
Use clear headings or supported document structures for evidence and requirements. Include only context relevant to the task. For a report, specify the audience, questions to answer and what counts as a supported conclusion rather than asking for impressive length.
Make the deliverable inspectable
Request a draft with references and a list of unresolved evidence, or a file change with an explanation of the expected behaviour. If tool use is available, define what is authorized before connecting write tools. A document instruction is not permission to act outside the task.
Review meaning, not surface confidence
Check that the answer did not silently change a fixed decision or invent a test. Compare key claims with the supplied material. Correct the missing or conflicting requirement and ask for a bounded revision instead of repeatedly starting the whole task again.
Before you act
Delimiters help organization but do not create a security boundary. Do not place private or untrusted material into a request without considering access and processing.
What to do next
- State the deliverable and the evidence the answer must use.
- Separate confirmed decisions, constraints and open questions.
- Review the result against the requested output, checking references and unresolved items.
