---
title: "这是我在尝试逆向工程任何东西之前会使用的 REA 框架。给出"
url: "https://reamcp.dev/zh-cn/cases/this-is-the-rea-harness-i-d-use-before-trying-to-reverse-eng-414e9f"
source: "https://x.com/i/status/2110401001719321075"
source_type: "resource"
author: "Ricker"
author_handle: "0xRicker"
stars: 0
category: "文件格式与协议"
categories: ["formats-protocols"]
tags: ["harness", "mcp", "rea", "reverse-engineering", "workflow"]
added: "2026-10-16T16:41:59.060Z"
updated: "2026-10-16T16:41:59.060Z"
locale: "zh-cn"
content_locale: "zh-cn"
---

# 这是我在尝试逆向工程任何东西之前会使用的 REA 框架。给出

这是我在尝试逆向工程任何东西之前会使用的 REA 框架。给出目标，告诉它你想理解什么行为，它就会围绕这个来构建调查，而不是盲目地翻找文件。

## Description

这是我在尝试逆向工程任何东西之前会使用的 REA 框架。

给出目标，告诉它你想理解什么行为，它就会围绕这个来构建调查，而不是盲目地翻找文件。

它会找出路线，端到端地追踪功能，将已确认的事实与猜测分开，并带回你可以实际检查的证据。

有用的部分是输出：

• 系统在做什么
• 行为在哪里
• 哪些文件 / 函数重要

比问 LLM“解释这个应用”并得到一个没有证据的自信故事要好得多。

提示词 + 工作流程如下 ↓

## Original README

This is the REA harness I’d use before trying to reverse engineer anything.

give it the target, tell it what behavior you want to understand, and it builds the investigation around that instead of blindly digging through files.

it figures out the route, traces the feature end-to-end, keeps confirmed facts separate from guesses, and comes back with evidence you can actually inspect.

the useful part is the output:

• what the system is doing
• where the behavior lives
• which files / functions matter

much better than asking an LLM “explain this app” and getting a confident story with no proof.

prompt + workflow below ↓