rpi

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Research, Design, and Implement

研究、设计与实现

Help the user research a change, work through its design, and implement it. Follow their requested step, using the phase instructions below.

$SKILLBASE

means the directory containing this

SKILL.md

<rpi-invocation>

in templates means the host's skill command:

$rpi

in Codex,

/rpi

in Claude Code, or its plugin-qualified name when the host exposes one. Render next commands with that native invocation.

帮助用户对变更进行调研、完成设计并落地实现。请遵循用户要求的步骤，使用下方各阶段的说明执行。

$SKILLBASE

表示包含此

SKILL.md

文件的目录。

模板中的

<rpi-invocation>

指宿主平台的技能命令：Codex 中为

$rpi

，Claude Code 中为

/rpi

，若宿主平台提供了插件限定名称则使用该名称。请使用该原生调用格式渲染后续命令。

Choose the Step

选择步骤

Follow the user's requested step. Read

$SKILLBASE/references/workflow.md

when choosing or explaining a flow or what comes next.

For a task description with no requested step, start with research questions. Ask which flow the user wants: research followed by design discussion, PRD, or TDD, or research only. Wait for their choice before starting the phase, then carry it into suggested next commands.

When asking the user to choose a flow, read

$SKILLBASE/references/workflow-choice.md

and show its box-and-line chart with the question.

Create writes a new document; iterate updates an existing document in place using the user's feedback or resumes the workflow for a partially finished document.

Load the matching process from

$SKILLBASE/references/<step>/process.md

Request	Step
Research questions	`create-research-questions` or `iterate-research-questions`
Research	`create-research` or `iterate-research`
Design discussion	`create-design-discussion` or `iterate-design-discussion`
Product requirements / PRD	`create-prd` or `iterate-prd`
Technical design / TDD	`create-tdd` or `iterate-tdd`
Implementation outline	`create-structure-outline` or `iterate-structure-outline`
Implement	`implement-outline`
Implementation feedback or fixes	`iterate-implementation`

Update an existing document by default; create one when needed or requested. When several match, use the newest and name the chosen file.

请遵循用户要求的步骤。在选择或解释工作流及后续步骤时，请阅读

$SKILLBASE/references/workflow.md

。

若任务描述未指定步骤，请从调研问题启动。询问用户希望采用哪种工作流：调研后进行设计讨论、PRD 或 TDD，还是仅进行调研。请等待用户做出选择后再启动对应阶段，随后将其纳入建议的后续命令中。

在请用户选择工作流时，请阅读

$SKILLBASE/references/workflow-choice.md

，并在提问时展示其中的框图。

创建（Create）操作用于生成新文档；迭代（Iterate）操作用于根据用户反馈就地更新已有文档，或恢复部分完成文档的工作流。

请从

$SKILLBASE/references/<step>/process.md

加载对应流程：

请求类型	对应步骤
调研问题	`create-research-questions` 或 `iterate-research-questions`
调研	`create-research` 或 `iterate-research`
设计讨论	`create-design-discussion` 或 `iterate-design-discussion`
产品需求 / PRD	`create-prd` 或 `iterate-prd`
技术设计 / TDD	`create-tdd` 或 `iterate-tdd`
实现大纲	`create-structure-outline` 或 `iterate-structure-outline`
实现	`implement-outline`
实现反馈或修复	`iterate-implementation`

默认更新已有文档；在需要或用户要求时创建新文档。若有多个匹配项，请使用最新版本，并说明所选文件名。

Use the Task Directory

使用任务目录

Use the directory supplied by the user.

Otherwise, look for existing task directories in

.agents/artifacts/

whose names and workflow filenames match the request or current task branch. Reuse an obvious match without asking. If a directory looks close but could belong to a different task, or several directories look plausible, ask the user which to use before writing. Read only documents allowed by the selected phase when checking a match.

When no existing directory fits, use

.agents/artifacts/<branch-name>

with

replaced by

if the branch identifies the task. On

main

, or when no branch identifies the task, choose a short kebab-case slug from the request and use

.agents/artifacts/<task-slug>

without asking for approval. State the selected path and reuse or create the directory as needed.

Save at the selected path. If the sandbox blocks writes there, ask for scoped write access or a writable task directory and wait for the user's choice.

The RPI framework authors recommend not committing the artifacts.

Number new workflow documents using the next available

NN-

prefix in the task directory. Keep the existing path when updating a document. Save supporting mockups and diagrams beside the documents and link them as ordinary local files.

Workflow document frontmatter includes

repos

, a list of zero or more repositories with

identifier

and

sha

for each entry. Use

repos: []

when none apply. Quote string values as needed for valid YAML.

请使用用户提供的目录。

若用户未提供目录，则在

.agents/artifacts/

目录下查找名称和工作流文件名与请求或当前任务分支匹配的已有任务目录。若存在明显匹配的目录，可直接复用无需询问。如果某个目录看似匹配但可能属于其他任务，或有多个看似合理的目录，请在写入前询问用户要使用哪一个。检查匹配项时，仅读取所选阶段允许访问的文档。

若没有合适的已有目录，且当前分支可标识任务，则使用

.agents/artifacts/<branch-name>

路径，路径中的

需替换为

。若在

main

分支上，或没有可标识任务的分支，请从请求中选择一个短的 kebab-case 格式的任务标识，使用

.agents/artifacts/<task-slug>

路径，无需征求用户同意。请说明所选路径，并根据需要复用或创建目录。

请保存到所选路径。如果沙箱禁止写入该路径，请请求限定范围的写入权限，或请用户提供可写的任务目录，等待用户选择。

RPI 框架作者建议不要提交这些制品。

请使用任务目录中下一个可用的

NN-

前缀为新的工作流文档编号。更新文档时保持原有路径不变。将辅助原型图和图表保存在文档同级目录，并像普通本地文件一样链接它们。

工作流文档的 frontmatter 包含

repos

字段，该字段是零个或多个仓库的列表，每个条目包含

identifier

和

sha

。若无适用仓库，请使用

repos: []

。请根据需要为字符串值添加引号，以确保 YAML 格式有效。

Suggest the Next Step

建议下一步操作

Use the phase's handoff instructions and

$SKILLBASE/references/workflow.md

to choose what comes next. Users run each phase in a separate context window by default. When suggesting a next command, include the task directory and chosen flow. Say they can run it here, after compaction, or in a new session.

Use artifact filenames to locate the current phase when asked what's next, then read its document for unfinished work and settled choices. Recognize

prd

product-requirements

tdd

tech-design

, and

structure-outline

outline

请结合当前阶段的交接说明和

$SKILLBASE/references/workflow.md

选择后续步骤。默认情况下，用户在独立的上下文窗口中运行每个阶段。在建议后续命令时，请包含任务目录和所选工作流。请告知用户可以在此处运行、在上下文压缩后运行，或在新会话中运行。

当被问及下一步操作时，请通过制品文件名定位当前阶段，然后读取对应文档以了解未完成工作和已确定的选择。请识别

prd

或

product-requirements

、

tdd

或

tech-design

以及

structure-outline

或

outline

这类文件名。

Use Subagents

使用子Agent

Use the bundled agent instructions for

codebase-locator

codebase-analyzer

codebase-pattern-finder

web-search-researcher

, and

outline-implementer-agent

as directed by each phase.

<important if="you do not have an Agent() or Task() or other tool for running subagents"> read the subagent instructions from $SKILLBASE/references/subagents/SUBAGENT_NAME.md </important> <important if="you have a tool for running subagents or delegated sessions, but the named subagents are not available"> read the subagent instructions from $SKILLBASE/references/subagents/SUBAGENT_NAME.md and pass them into the subagent with your main prompt, with <instructions> REFERENCE_CONTENTS </instructions> <message> YOUR_MESSAGE ON WHAT TO LOOK FOR OR BUILD </message> </important>

请按照各阶段的指示，使用

codebase-locator

、

codebase-analyzer

、

codebase-pattern-finder

、

web-search-researcher

和

outline-implementer-agent

的内置Agent说明。

<important if="you do not have an Agent() or Task() or other tool for running subagents"> 请从 $SKILLBASE/references/subagents/SUBAGENT_NAME.md 读取子Agent说明 </important> <important if="you have a tool for running subagents or delegated sessions, but the named subagents are not available"> 请从 $SKILLBASE/references/subagents/SUBAGENT_NAME.md 读取子Agent说明，并将其与你的主提示词一起传递给子Agent，格式如下： <instructions> REFERENCE_CONTENTS </instructions> <message> YOUR MESSAGE ON WHAT TO LOOK FOR OR BUILD </message> </important>