Give AI the right task context

Keep goals, sources, decisions and handover notes together.

Dataelem · Updated

1. Explain the task and its sources

Context means the background needed for the task: the result, available material, agreed rules and current progress. Choose the relevant workspace and explicitly identify key files. Keep unrelated projects in separate conversations.

Turn the attached interviews and requirements table into a product requirements document. Desktop comes first; version one has three core workflows. Separate confirmed facts from open questions. First list the files you read and your understanding of the task, then wait for confirmation.

2. Record agreed decisions

When a decision changes, ask for an updated task summary identifying the chosen version and abandoned alternatives. State which file is authoritative. Continue the same task in its existing chat and add new constraints when needed. Do not assume every workspace file is automatically included.

Summarize the agreed goal, chosen approach, source files, completed work, remaining tasks and checks. Mark replaced approaches as abandoned and do not use them in later drafts.

3. Prepare a handover before a new session

For a separate task or conversation, carry over a short summary with the goal, constraints, latest files, decisions and next step. Long sources can be processed in batches, but a summary does not replace the original for quotations, amounts or conclusions.

Prepare a handover with the goal, key constraints, latest files, confirmed decisions and next step. Distinguish source facts from discussion assumptions. Recheck the original before quoting it.

4. Correct misunderstandings early

If a reply uses an old approach, misses a file or treats examples as real data, point out the specific error. Ask AI to restate the corrected understanding before continuing. Check sources and delivered files instead of judging correctness by fluent prose.