Supply readable project material
Share the protected QERA handoff and the matching dossier number when the receiving workflow asks for it. Ask Claude Code to confirm the actual document it read. If its environment cannot retrieve the document, use the available document or file handoff instead of treating access failure as a completed review.
State facts and constraints plainly
Name the audience, workflow, required data, permissions and external systems. Mark proposed defaults separately. Do not disguise an authentication secret as a harmless identifier or ask a provider to bypass its security controls. A matching dossier number identifies the intended project; it does not authorize unrelated access.
Ask for a review before the build
Have Claude Code summarize scope, call out missing requirements and explain the first milestone, estimated work and assumptions. Check that the result matches your original answers. Only then move to implementation under the permissions and approval rules of your own environment.
Check before handing it over
- Actual document read confirmed
- Customer facts kept separate from defaults
- Data and permission boundaries
- Missing decisions stated openly
- First response reviewed before implementation