# 10 prompts for handing a task to AI

## How to use them

Replace the brackets and attach the material for this task. Check permission before using work information, and remove keys and personal details from errors or screenshots. Each prompt stands on its own.

## 1. Clarify the goal

```text
I want to achieve [goal] for [person]. The current situation is [status].
Restate the result you understand, then ask questions that change the approach.
List information I have not supplied as needing confirmation. Do not invent it.
```

## 2. Organise sources and gaps

```text
Here is the material: [original text or file list].
List usable information, sources and dates, plus missing or conflicting details.
Separate source facts, calculations and your inferences. Keep the originals.
```

## 3. Set the scope

```text
Plan a small version we can try against the confirmed goal.
List steps, visible results, what you need from me and what is excluded this time.
If material or a tool is unavailable, explain the effect. Do not add unrequested features.
```

## 4. Compare proposals

```text
Compare [material] against [conditions and dimensions] in a sourced table.
Show cost formulas; use consistent quantity, tax and time definitions.
Mark missing data. Check the conditions and list follow-up questions.
Do not make the final decision for me.
```

## 5. Draft from material

```text
Use [confirmed sources] to draft [report / article / brief] for [reader].
The purpose is [purpose], length and format are [requirements], and tone follows [example].
Keep sources for numbers and facts. Flag gaps; do not invent cases, reviews or quotes.
```

## 6. Make a page I can try

```text
Use [confirmed brief] to make a page with [one interaction].
Use clearly labelled fictional data first.
Explain how to run it and change the content; give inputs and expected results.
List required accounts, APIs and charges before connecting them, and wait for confirmation.
```

## 7. Investigate a specific problem

```text
Expected result: [expected]. Actual result: [what happened].
Steps, errors and relevant material: [details]. Recent changes: [details].
Investigate the cause first. Separate evidence from points needing confirmation.
Propose a fix, retry the original steps and check related existing functions or conclusions.
```

## 8. Check the result

```text
Compare [result] with [requirements and original sources], item by item.
Check sources, numbers, missing information and format.
Say what I should recalculate or try myself.
For a website, include main actions, unusual inputs and relevant account access.
Explicitly identify unchecked points and explain how to check them.
```

## 9. Keep the previous version

```text
Change only [scope]. Preserve the original or a recoverable version first.
Explain possible effects, then list changes, check results and unresolved issues.
Stop for my confirmation before sending, publishing, deleting or paying.
```

## 10. Keep the method

```text
Write a short task guide from the approach that worked.
Include required material, steps, example output, checks and human confirmations.
Mark what must change next time. Do not turn this task's numbers, recommendation
or temporary problem into a rule for every task.
```

## Try one small task

The [three-quote exercise](https://vibecoding.ivheli.com/en/guides/ai-native-workflow/) shows prompts alongside sources, calculations and conclusions. For a longer project, fill in the [task brief](https://vibecoding.ivheli.com/en/skills/project-brief-template/) once and add the changes as you go.