# The check before I trust a workflow with AI in it

Source: https://aaronmakelky.com/checklist
Last updated: 2026-05-02

A short checklist Aaron uses before trusting a workflow with AI in it more than once.

Checklist

Six questions I use before a prompt, tool, template, or workflow turns into another half-finished experiment.

Rule of thumb

## If you cannot run it twice, it is not a workflow yet.

I use this before buying a tool, building a prompt, or handing the process to someone else.

### Outcome

Can you name the result in one sentence?

If the finish line is fuzzy, the output will be fuzzy too.

### Inputs

Do you know what source material the tool should use?

A good run starts with the right files, notes, examples, or constraints.

### Judgment

Where does a human make the call?

Keep the human call where it matters.

### Repeatability

Could someone run it again next week?

A useful workflow leaves instructions behind. A lucky output does not.

### Risk

What would be embarrassing, wrong, or expensive if missed?

Name what can go wrong before the tool starts sounding confident.

### Handoff

Can the next person use the result without a translator?

If the handoff needs a second explanation, the workflow is not done yet.

Next step

## Write down the version that worked.

When the same check fails twice, write down the working steps so someone can run them again.

[See the kits](/shop) [Read the blog](/blog)

## Related pages

- [About Aaron Makelky](/about)
- [AI notes](/blog)
- [Tools and downloads](/tools)
- [OpenClaw kits](/shop)

## Sources and references

- [Descript](https://www.descript.com/)