Skip to content

Writing good investigation prompts

Practical habits for asking a coding agent to investigate software with REA: one feature, a clear deliverable, and proof you can check.

Updated Oct 19, 2026

The difference between a vague answer and a useful one is usually the prompt. These habits keep an investigation focused and checkable.

Habits that work

  • One feature per session. "How does export work" beats "explain this app".
  • Say what done looks like: a rule, a diagram, a test or a small rebuild.
  • Ask for evidence: the function, string or captured call behind each claim.
  • Ask it to say what it could not confirm instead of filling gaps.
  • Finish with a check: change one input and compare against the original.

A template

Prompt
Use REA to inspect <program>. Find how <feature> works.
Show the code or runtime evidence for each step.
Then build a minimal version I can run, and tell me one input to test it with.
List anything you could not confirm.