codely-plan-phase-implement

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

🫡 Implement a plan phase

🫡 实施计划阶段

[!CRITICAL] Implement ONLY ONE phase per invocation. After completing the current phase, STOP and wait for the user to review the changes. Never proceed to the next phase without explicit user approval.

[!CRITICAL] Never commit or push changes automatically. Only suggest commit messages. The user decides when to commit.

[!CRITICAL] 每次调用仅实施一个阶段。完成当前阶段后，停止并等待用户审查更改。未经用户明确批准，绝不进入下一阶段。

[!CRITICAL] 绝不自动 commit 或 push 更改。 只能建议 commit message，由用户决定何时 commit。

🔍 Determining the current phase

🔍 确定当前阶段

The current phase is the first phase in the plan that has at least one unchecked (

- [ ]

) to-do item. If all phases are fully checked, inform the user that all phases are complete and do not re-implement.

当前阶段是计划中第一个至少包含一个未勾选（

- [ ]

）待办事项的阶段。如果所有阶段都已完全勾选，则告知用户所有阶段均已完成，不要重新实施。

🪜 Steps to implement a plan phase

🪜 实施计划阶段的步骤

Ask the user for the plan to implement if not already specified.
Identify the current phase using the rule above.
Implement the to-do actions of the current phase only. Do NOT implement any other phase.
Update the plan file according to the considerations below specified.
STOP. Tell the user to review the changes and suggest 3 alternative commit messages. Follow the commit message convention defined in the
```
commit-messages.md
```
file. Use different plausible commit message types in the 3 alternatives. In the suggestion, make it simple to reply something like "commit with message 1", and use the
```
/codely-git-conventional-commit
```
skill to commit the changes specifying the chosen message.
If this is the implementation of the last phase of the plan, suggest the user to export the conversation (using their IDE) and store it as a
```
.md
```
file alongside the related plan. Example: if the plan is
```
.agents/plans/2026_02_11-sync_cbd_with_stripe/2026_02_11-sync_cbd_with_stripe-plan.md
```
, suggest storing the conversation as
```
.agents/plans/2026_02_11-sync_cbd_with_stripe/2026_02_11-sync_cbd_with_stripe-conversation.md
```
.

如果尚未指定要实施的计划，向用户询问该计划。
按照上述规则确定当前阶段。
仅实施当前阶段的待办事项。不要实施任何其他阶段。
根据下文所述注意事项更新计划文件。
停止。 告知用户审查更改，并建议 3 条备选的 commit message。遵循
```
commit-messages.md
```
文件中定义的 commit message 规范。3 条备选建议应使用不同且合理的 commit message 类型。让用户可以简单地回复类似“commit with message 1”的内容，并使用
```
/codely-git-conventional-commit
```
skill，按照用户选择的 message commit 更改。
如果当前实施的是计划的最后一个阶段，建议用户通过其 IDE 导出对话，并将对话保存为相关计划旁边的
```
.md
```
文件。例如：如果计划为
```
.agents/plans/2026_02_11-sync_cbd_with_stripe/2026_02_11-sync_cbd_with_stripe-plan.md
```
，则建议将对话保存为
```
.agents/plans/2026_02_11-sync_cbd_with_stripe/2026_02_11-sync_cbd_with_stripe-conversation.md
```
。

🔄 How to update the plan file

🔄 如何更新计划文件

1. Update the plan file frontmatter

1. 更新计划文件 frontmatter

Do not modify the current plan file frontmatter, only add or update the following information to it:

markdown

---
implemented_by:
  tool: "{ tool }"
  model:
    name: "{ model.name }"
    version: "{ model.version }"
    reasoning_effort: "{ model.reasoning_effort }"

last_implementation_at: "{ current_date }"
has_completed_all_phases: "{ true | false }"
---

implemented_by.tool

: The AI coding tool used (e.g.

Claude Code

Cursor

Copilot

Codex

)

implemented_by.model.name

: The name of the model used to make the change (e.g.

Claude Opus

Cursor Composer

OpenAI GPT

)

```
implemented_by.model.version
```
: The version of the model used to make the change (e.g.
```
4.6
```
,
```
1.5
```
,
```
5.4
```
)
```
implemented_by.model.reasoning_effort
```
: The reasoning effort of the model used to make the change (e.g.
```
low
```
,
```
medium
```
,
```
high
```
)
```
last_implementation_at
```
: The current date in the format ISO 8601 RFC 3339 (
```
YYYY-MM-DDTHH:MM:SSZ
```
).
```
has_completed_all_phases
```
: Whether this has been the last implementation of the plan and all phases have been completed or not.

不要修改当前计划文件中已有的 frontmatter，只能在其中添加或更新以下信息：

markdown

---
implemented_by:
  tool: "{ tool }"
  model:
    name: "{ model.name }"
    version: "{ model.version }"
    reasoning_effort: "{ model.reasoning_effort }"

last_implementation_at: "{ current_date }"
has_completed_all_phases: "{ true | false }"
---

```
implemented_by.tool
```
：用于进行更改的 AI 编程工具（例如
```
Claude Code
```
、
```
Cursor
```
、
```
Copilot
```
、
```
Codex
```
）

implemented_by.model.name

：用于进行更改的模型名称（例如

Claude Opus

、

Cursor Composer

、

OpenAI GPT

）

```
implemented_by.model.version
```
：用于进行更改的模型版本（例如
```
4.6
```
、
```
1.5
```
、
```
5.4
```
）
```
implemented_by.model.reasoning_effort
```
：用于进行更改的模型的推理强度（例如
```
low
```
、
```
medium
```
、
```
high
```
）
```
last_implementation_at
```
：当前日期，格式为 ISO 8601 RFC 3339（
```
YYYY-MM-DDTHH:MM:SSZ
```
）
```
has_completed_all_phases
```
：本次是否为计划的最后一次实施，以及所有阶段是否均已完成。

2. Update the plan file content

2. 更新计划文件内容

Check the checkboxes of the current phase to-do list that have been completed.
Update the plan next step section with the next phase to be completed.
Replace the plan last sentence regarding Codely adding a new random emoji that explains a story together with the previous ones. For instance, if the previous last sentence was "Plan powered by Codely 🐢 💨", the new last sentence could be "Bugs squashed thanks to Codely AI tooling. 🐛 < 🐢 💨".

勾选当前阶段待办列表中已完成事项的复选框。
更新计划中的“下一步”部分，注明接下来需要完成的阶段。
替换计划末尾关于 Codely 的最后一句话，并添加一个新的随机 emoji，与之前的 emoji 共同表达一个连贯的故事。例如，如果之前的最后一句是“计划由 Codely 驱动 🐢 💨”，新的最后一句可以是“得益于 Codely AI 工具，Bug 已被消灭。🐛 < 🐢 💨”。

☝️ General considerations

☝️ 通用注意事项

🧠 Logical reasoning

🧠 逻辑推理

Use AGENTS.md file as a reference while:
- Proposing application services, domain events, tests, etc.
- Following code conventions and architecture decisions (all inside the docs/ directory).
- Determining the test suites and tests cases to be created/modified/deleted.
Use available agent tools while offering different alternatives for the user to choose from:
- ```
AskQuestion
```
  tool if you are Cursor and have this tool available (only available in certain models such as Opus 4.5, not in others such as Composer 1).
- ```
AskUserQuestion
```
  tool if you are Claude Code.

在以下场景中，使用 AGENTS.md 文件作为参考：
- 提出应用服务、领域事件、测试等方案时。
- 遵循代码规范和架构决策时（相关内容均位于 docs/ 目录中）。
- 确定需要创建、修改或删除的测试套件和测试用例时。
使用可用的 Agent 工具，同时为用户提供不同的可选方案：
- 如果使用 Cursor 且支持
```
AskQuestion
```
  工具，则使用该工具（该工具仅适用于部分模型，例如 Opus 4.5，不适用于 Composer 1 等模型）。
- 如果使用 Claude Code，则使用
```
AskUserQuestion
```
  工具。