- 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
- Pick one input and record the expected output on a synthetic fixture.
- Give the assistant the build identifier, intended action and artifacts it can inspect.
- 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.
- Skills/reap-02-feature-tracing-any-program/SKILL.md
REA Investigation Prompts · JoasASantos ·
9756618f25·Source license MIT
Related prompts
Compare two builds to triage a crash
Use a known-good and failing build of your application to isolate what changed around a reproducible crash and hand the evidence to a maintainer.
Reverse Engineering Prompts · REA
Plan a WebAssembly port of your game
Identify the portable simulation code in an authorized game and plan a small browser proof of concept before migrating rendering, audio or platform integrations.
Reverse Engineering Prompts · REA
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.
Reverse Engineering Prompts · REA