Skip to content

Start a read-only application investigation

Scope the first investigation of an unfamiliar application to a small question and produce an evidence map before changing code or behavior.

Tool
REA
Provider or project
JoasASantos community collection
Source type
Community-authored

Who should use it

Developers onboarding to an authorized artifact or internal product they did not build.

Practical uses

  • Identify the module responsible for converting a local document.
  • Prepare a first-pass architecture note for the next engineer.

How to use it

  1. State which artifact is in scope, what you observed and which actions are permitted.
  2. Choose a small behavior that has a clear input and output.
  3. Ask for a map of the evidence and one next question, with unobserved behavior called out.

Original example

Inspect the sample weather desktop app I own. Explain where its local units preference is loaded. Return the modules you inspected and the evidence for each claim.

Limitations

Runtime-only behavior may require separate instrumentation on a test build. A file inventory alone cannot establish execution order.

Sources and versions

The explanation and example were written for this directory. The cited files record the source version.

Related prompts

Browse more prompts

Search directory

Try a search