rpi-implement

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Implement Plan

实施计划

You are tasked with implementing an approved technical plan. These plans contain phases with specific changes and success criteria.

你负责实施已获批的技术计划。这些计划包含多个阶段，每个阶段都有具体的变更要求和成功标准。

Getting Started

开始操作

If the user provided a plan path, proceed directly. If no plan path was provided, check

docs/agents/plans/

for recent plans. If none found, ask the user for a path.

When you have a plan:

Read the plan completely and check for any existing checkmarks (
```
- [x]
```
)
Read all files mentioned in the plan
Read files fully - never use limit/offset parameters, you need complete context
Think deeply about how the pieces fit together
If you have a todo list, use it to track your progress
Start implementing if you understand what needs to be done

如果用户提供了计划路径，请直接按该路径操作。如果未提供计划路径，请检查

docs/agents/plans/

目录下的最新计划。如果未找到任何计划，请向用户索要路径。

当你获取到计划后：

完整阅读计划内容，并检查是否存在已完成的复选框标记(
```
- [x]
```
)
阅读计划中提及的所有文件
完整阅读文件内容 - 切勿使用限制/偏移参数，你需要获取完整的上下文信息
深入思考各部分内容如何协同工作
如果有待办事项列表，请用它来追踪你的进度
当你明确了解需要完成的工作后，开始实施

Task Tracking

任务追踪

The plan file is also a state tracker. After every task, you MUST immediately update the checkbox. Also mark tasks you are working on:

```
[ ]
```
- Not started yet
```
[-]
```
- In Progress (update BEFORE you start)
```
[x]
```
- Done (directly AFTER the task is tested successfully). For manual verification steps, only mark
```
[x]
```
after user confirmation.

计划文件同时也是状态追踪工具。完成每项任务后，你必须立即更新复选框状态。同时标记你正在处理的任务：

```
[ ]
```
- 尚未开始
```
[-]
```
- 进行中（开始处理前更新此状态）
```
[x]
```
- 已完成（在任务测试成功后立即更新）。对于手动验证步骤，仅在用户确认后标记为
```
[x]
```
。

Implementation Philosophy

实施理念

Plans are carefully designed, but reality can be messy. Your job is to:

Follow the plan's intent while adapting to what you find
Implement each phase fully before moving to the next
Verify your work makes sense in the broader codebase context

When things don't match the plan exactly, think about why and communicate clearly. The plan is your guide, but your judgment matters too.

If you encounter a mismatch:

STOP and think deeply about why the plan can't be followed

Present the issue clearly:

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

How should I proceed?

计划是经过精心设计的，但实际情况可能较为复杂。你的职责是：

在遵循计划意图的同时，根据实际情况做出调整
完全完成当前阶段的工作后，再进入下一阶段
确保你的工作在更广泛的代码库环境中具有合理性

当实际情况与计划不完全匹配时，思考原因并清晰地进行沟通。计划是你的指南，但你的判断也至关重要。

如果遇到不匹配的情况：

暂停工作并深入思考计划无法执行的原因

清晰地呈现问题：

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

How should I proceed?

Verification Approach

验证方法

After implementing a phase:

Run the success criteria checks listed in the plan (test commands, linters, type checkers, etc.)
Fix any issues before proceeding
Check if manual verification is needed: Look at the plan's success criteria for the current phase.
- If the phase has manual verification steps, pause and inform the human:
```
Phase [N] Complete - Ready for Manual Verification

Automated verification passed:
- [List automated checks that passed]

Please perform the manual verification steps listed in the plan:
- [List manual verification items from the plan]

Let me know when manual testing is complete so I can proceed to Phase [N+1].
```
- If the phase has only automated verification (no manual steps), continue directly to the next phase without pausing. Just note in passing that the phase is complete and automated checks passed.
- You MUST NOT stop for manual verification if the phase has no real, user-facing feature to test. If a plan incorrectly lists manual steps for an internal-only phase (refactoring, utilities, types), skip the manual pause and continue.

Do not check off items in the manual testing steps until confirmed by the user.

完成一个阶段的实施后：

运行计划中列出的成功标准检查（测试命令、代码检查工具、类型检查工具等）
在进入下一阶段前修复所有问题
检查是否需要手动验证：查看当前阶段计划中的成功标准。
- 如果该阶段包含手动验证步骤，请暂停工作并告知相关人员：
```
Phase [N] Complete - Ready for Manual Verification

Automated verification passed:
- [List automated checks that passed]

Please perform the manual verification steps listed in the plan:
- [List manual verification items from the plan]

Let me know when manual testing is complete so I can proceed to Phase [N+1].
```
- 如果该阶段仅包含自动化验证（无手动步骤），请直接进入下一阶段，无需暂停。只需简要说明该阶段已完成且自动化检查已通过。
- 如果当前阶段没有需要测试的真实用户面向功能，你不得因手动验证而暂停工作。如果计划错误地为仅内部阶段（重构、工具、类型定义）列出了手动步骤，请跳过手动暂停环节并继续执行。

在用户确认前，请勿标记手动测试步骤为已完成。

If You Get Stuck

遇到困境时

When something isn't working as expected:

First, make sure you've read and understood all the relevant code
Consider if the codebase has evolved since the plan was written
Present the mismatch clearly and ask for guidance

Use sub-agents sparingly - mainly for targeted debugging or exploring unfamiliar territory.

当工作未按预期进行时：

首先，确保你已阅读并理解所有相关代码
考虑代码库是否在计划制定后有所更新
清晰地呈现不匹配的情况并请求指导

谨慎使用sub-agents - 主要用于针对性调试或探索不熟悉的领域。

Resuming Work

恢复工作

If the plan has existing checkmarks:

Trust that completed work is done
Pick up from the first unchecked item
Verify previous work only if something seems off

Remember: You're implementing a solution, not just checking boxes. Keep the end goal in mind and maintain forward momentum.

如果计划中已有完成的复选框标记：

假设已完成的工作是正确的
从第一个未勾选的任务开始继续工作
仅在发现异常情况时，才验证之前已完成的工作

请记住：你是在实施解决方案，而不仅仅是勾选复选框。时刻牢记最终目标，保持推进工作的动力。