Skip to content

Trace one feature in an application you own

Follow a single visible action from the user interface to its output. Keep observations, source evidence and hypotheses distinct so the next maintainer can verify the trace.

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

Who should use it

Maintainers documenting an internal application or checking how one of their own legacy features works.

Practical uses

  • Find where a CSV export chooses its headers.
  • Connect a settings toggle to the preference it changes.

How to use it

  1. Pick one input and record the expected output on a synthetic fixture.
  2. Give the assistant the build identifier, intended action and artifacts it can inspect.
  3. Ask for the shortest trace supported by evidence, with open questions listed separately.

Original example

Our demo app exports a three-column CSV. Identify which module supplies the header names. Cite the evidence for each step and mark any branch you could not observe.

Limitations

A trace covers the inspected build and fixture. Exercise separate inputs before drawing conclusions about optional behavior.

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