Include five elements#

Element	What to specify
Objective	A concrete outcome
Sources	Attachments, sources, folders and revisions
Constraints	Facts that must not be guessed; content to preserve
Output	Table, checklist, report or specific file format
Review	When to propose a plan and wait for approval

Reusable request#

Task: Organize the lobby material candidates for the demo hotel.
Evidence: Use this conversation's attachments, prioritizing documents identified as the latest revision.
Requirements: Record material ID, specification, location and source filename. Mark missing facts “To confirm”.
Output: First provide a table and questions. Preserve the original files.
Review: Explain the targets and scope before writing files or sending externally, and wait for my confirmation.
Acceptance: Every conclusion has a source; units and revisions are consistent.

Give specific corrections#

Identify the incorrect row, the right source and what to preserve. For example: “The price in row two comes from an old quote. Use the new attachment and keep the other columns.” A request to make something “more professional” cannot replace a clear objective.

Confirm sources can be read#

Attachment readability, image clarity and enabled sources affect the answer. Ask the model to list the files it actually read and anything it could not read. Unknown information should remain visibly unknown.

Expected outcome#

The model should understand the task, identify gaps and return an inspectable result. If it cannot, narrow the task to one file or material ID, then expand it.