plan-two

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Think harder. Activate

plan

skill.

CRITICAL: Do NOT use
EnterPlanMode
tool — it blocks Write/Edit/Task tools needed for plan creation. Follow the workflow below. Planning is collaborative: Validate plan, ask user to confirm, surface decision questions with recommendations.

深入思考。激活

plan

skill。

重要提示： 请勿使用
EnterPlanMode
工具——它会阻碍计划创建所需的Write/Edit/Task工具。请遵循以下工作流。 规划是协作式的： 验证计划，请求用户确认，提出决策问题并给出建议。

Your mission

你的任务

Use the

planner

subagent to create 2 detailed implementation plans for this following task: <task> $ARGUMENTS </task>

使用

planner

子Agent为以下任务制定2份详细的实施计划： <task> $ARGUMENTS </task>

Workflow

工作流

First: Create a directory using naming pattern from
```
## Naming
```
section in injected context. Make sure you pass the directory path to every subagent during the process.
Follow strictly to the "Plan Creation & Organization" rules of
```
plan
```
skill.
Use multiple
```
researcher
```
agents in parallel to research for this task, each agent research for a different aspect of the task and perform max 5 researches (max 5 tool calls).
Use
```
scout
```
agent to search the codebase for files needed to complete the task.
Main agent gathers all research and scout report filepaths, and pass them to
```
planner
```
subagent with the detailed instructions prompt to create an implementation plan of this task. Output: Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
Main agent receives the implementation plan from
```
planner
```
subagent, and ask user to review the plan

第一步：使用注入上下文中
```
## 命名
```
部分的命名规则创建一个目录。确保在流程中向每个子Agent传递该目录路径。
严格遵循
```
plan
```
skill中的“计划创建与组织”规则。
并行使用多个
```
researcher
```
agents进行任务调研，每个Agent负责任务的不同方面，最多执行5次调研（最多5次工具调用）。
使用
```
scout
```
agent搜索代码库中完成任务所需的文件。
主Agent收集所有调研结果和scout报告的文件路径，并将其与详细指令提示一起传递给
```
planner
```
子Agent，以制定该任务的实施计划。 输出： 提供至少2种实现方案，明确说明各方案的权衡点，解释每种方案的优缺点，并给出推荐方案。
主Agent从
```
planner
```
子Agent处接收实施计划后，请求用户审阅该计划

Plan File Specification

计划文件规范

Every

plan.md

MUST start with YAML frontmatter:

yaml

---
title: "{Brief title}"
description: "{One sentence for card preview}"
status: pending
priority: P2
effort: {sum of phases, e.g., 4h}
branch: {current git branch}
tags: [relevant, tags]
created: {YYYY-MM-DD}
---

每个

plan.md

必须以YAML前置元数据开头：

yaml

---
title: "{Brief title}"
description: "{One sentence for card preview}"
status: pending
priority: P2
effort: {sum of phases, e.g., 4h}
branch: {current git branch}
tags: [relevant, tags]
created: {YYYY-MM-DD}
---

MANDATORY: Plan Collaboration Protocol (READ THIS)

强制要求：计划协作协议（请务必阅读）

Do NOT use
EnterPlanMode
tool — it blocks Write/Edit/Task tools needed to create plan files and launch subagents
Do NOT start implementing — plan only, wait for user approval
ALWAYS validate: After plan creation, execute
```
/plan-review
```
to validate the plan
ALWAYS confirm: Ask user to review and approve the plan using
```
AskUserQuestion
```
with a recommendation
ALWAYS surface decisions: Use
```
AskUserQuestion
```
with recommended options for key architectural/design decisions
Planning = Collaboration: The plan is shaped by user input — never treat it as a unilateral output
Always plan and break many small todo tasks
Always add a final review todo task to review the works done at the end
Sacrifice grammar for concision. List unresolved questions at the end

请勿使用
EnterPlanMode
工具——它会阻碍创建计划文件和启动子Agent所需的Write/Edit/Task工具
请勿开始实施——仅制定计划，等待用户批准
必须验证： 计划创建完成后，执行
```
/plan-review
```
以验证计划
必须确认： 使用
```
AskUserQuestion
```
请求用户审阅并批准计划，并给出推荐意见
必须提出决策： 对于关键架构/设计决策，使用
```
AskUserQuestion
```
提供推荐选项
规划=协作： 计划由用户输入塑造——切勿将其视为单方面输出
始终将计划拆分为多个小型待办任务
始终添加一个最终审阅待办任务，用于在末尾检查已完成的工作
为简洁性可适当忽略语法规范。在末尾列出未解决的问题