rpi-implement-plan

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

RPI Implement Plan

RPI 计划实施

Use this skill to execute an approved implementation plan from

rpi/plans/

with disciplined progress tracking and validation.

使用本skill可执行

rpi/plans/

中的已获批实施计划，并进行规范的进度跟踪与验证。

Initial Behavior

初始行为

If the user provides a plan path, begin immediately.
If no plan path is provided, ask for one.

Use this prompt when no path is provided:

text

I'm ready to implement the plan. Please share the plan file path (typically under `rpi/plans/`) and I’ll execute it phase-by-phase, run verification checks, and update progress checkboxes in the plan as work completes.

若用户提供了计划路径，立即开始执行。
若未提供计划路径，询问用户获取。

当未提供路径时，使用以下提示语：

text

我已准备好实施计划。请提供计划文件路径（通常位于`rpi/plans/`下），我会分阶段执行计划、运行验证检查，并在工作完成后更新计划中的进度复选框。

Getting Started

开始执行

When a plan path is provided:

Read the plan completely.
Check for existing
```
- [x]
```
items to detect prior progress.
Read all files referenced by the plan, fully.
Create a task list that mirrors phases and key checklist items.
Start implementation when requirements are clear.

当提供计划路径后：

完整读取计划内容。
检查已有的
```
- [x]
```
项以识别过往进度。
完整读取计划中引用的所有文件。
创建与阶段及关键检查项对应的任务列表。
当需求明确后开始实施。

Implementation Philosophy

实施理念

Follow the plan's intent while adapting to current code reality.
Complete each phase fully before moving to the next.
Verify changes in context, not in isolation.
Update plan checkboxes as items are completed.

If the codebase conflicts with the plan, pause and surface the mismatch clearly:

text

Issue in Phase [N]:
Expected: [what the plan says]
Found: [actual situation]
Why this matters: [explanation]

How should I proceed?

遵循计划的核心意图，同时适配当前代码实际情况。
完全完成一个阶段后再进入下一阶段。
在实际环境中验证变更，而非孤立验证。
完成任务后更新计划中的复选框。

若代码库与计划存在冲突，暂停执行并清晰说明不匹配之处：

text

第[N]阶段问题：
预期：[计划中的描述]
实际：[实际情况]
影响：[相关说明]

我应如何推进？

Working Process

工作流程

1) Implement phase-by-phase

1) 分阶段实施

Finish one phase before starting the next.
Make all required code/file changes for that phase.
Run the phase's automated checks before proceeding.
Mark completed checklist items in the plan file like so:
```
- [x] 
```
.

完成一个阶段后再开始下一个阶段。
完成该阶段所需的所有代码/文件变更。
进入下一阶段前运行该阶段的自动化检查。
在计划文件中标记已完成的检查项，格式如下：
```
- [x] 
```
。

2) Verify after each phase

2) 阶段后验证

Run success criteria checks from the plan (tests, lint, typecheck, build, or equivalent).
If necessary to confirm changes were made correctly, you can write and run temporary scripts to verify the behavior; clean them up afterwards.
Fix issues before advancing.
Record progress in your task list and in the plan checkboxes.

运行计划中定义的成功标准检查（测试、代码扫描、类型检查、构建或同类操作）。
若需确认变更是否正确实施，可编写并运行临时脚本进行验证，事后需清理这些脚本。
解决问题后再推进。
在任务列表和计划复选框中记录进度。

3) Handle blockers pragmatically

3) 务实处理阻塞问题

Re-read relevant code and requirements before escalating.
Account for plan drift when code has changed since planning.
Ask for guidance only after presenting a concrete mismatch and options.

升级问题前重新阅读相关代码与需求。
考虑计划制定后代码变更导致的计划偏差。
仅在明确说明具体不匹配情况及可选方案后，再请求指导。

Resuming Existing Work

恢复已有工作

If the plan already has checked items:

Treat checked work as completed by default.
Resume from the first meaningful unchecked item.
Re-verify prior work only if current behavior suggests a regression or inconsistency.

若计划中已有已勾选的项：

默认将已勾选的工作视为已完成。
从第一个有意义的未勾选项处恢复工作。
仅当当前行为表明存在回归或不一致时，才重新验证过往工作。

Output Expectations

输出要求

When reporting progress to the user:

Summarize what was implemented in the current phase.
List verification commands run and outcomes.
Call out any deviations from plan and why.
Link the updated plan path so progress is auditable.

向用户汇报进度时：

总结当前阶段已完成的实施内容。
列出已运行的验证命令及结果。
指出任何与计划的偏差及原因。
提供更新后的计划路径，以便进度可被审计。

Quality Bar

质量标准

Prioritize working software over mechanical checkbox completion.
Keep momentum while maintaining correctness.
Do not skip verification gates defined by the plan.
Keep plan checkboxes truthful and up to date.

优先保证可用软件，而非机械完成复选框勾选。
在保持正确性的同时维持推进节奏。
不得跳过计划中定义的验证环节。
确保计划复选框的标记真实且及时更新。