Skip to content

Commit 32e5796

Browse files
committed
feat: update update-plan prompt draft
1 parent 33bcd48 commit 32e5796

2 files changed

Lines changed: 25 additions & 25 deletions

File tree

docs/SKILL_new.md

Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -116,55 +116,55 @@ After all tasks are completed (`[x]`):
116116

117117
**Example requirements:**
118118
```markdown
119-
# Feature: Add dark mode toggle
119+
# 新功能:添加深色模式切换
120120

121-
Users should be able to switch between light and dark themes.
122-
The toggle should be in the settings page.
121+
用户应该能够在浅色和深色主题之间切换。
122+
切换开关应放在设置页面中。
123123
```
124124

125-
**UpdatePlan call after analysis:**
125+
**分析后的 UpdatePlan 调用:**
126126
```markdown
127127
## Task List
128128

129-
- [ ] Create dark mode toggle component in Settings page
130-
- [ ] Add dark mode state management (context/store)
131-
- [ ] Implement CSS-in-JS styles for dark theme
132-
- [ ] Update existing components to support theme switching
133-
- [ ] Run tests and verify functionality
129+
- [ ] 在设置页面创建深色模式切换组件
130+
- [ ] 添加深色模式状态管理(context/store
131+
- [ ] 实现深色主题的 CSS-in-JS 样式
132+
- [ ] 更新现有组件以支持主题切换
133+
- [ ] 运行测试并验证功能
134134
```
135135

136136
**UpdatePlan call during execution:**
137137
```markdown
138138
## Task List
139139

140-
- [x] Create dark mode toggle component in Settings page
141-
- [>] Add dark mode state management (context/store)
142-
- [ ] Implement CSS-in-JS styles for dark theme
143-
- [ ] Update existing components to support theme switching
144-
- [ ] Run tests and verify functionality
140+
- [x] 在设置页面创建深色模式切换组件
141+
- [>] 添加深色模式状态管理(context/store
142+
- [ ] 实现深色主题的 CSS-in-JS 样式
143+
- [ ] 更新现有组件以支持主题切换
144+
- [ ] 运行测试并验证功能
145145
```
146146

147147
### Example 2: Bug fix with investigation
148148

149149
**Example requirements:**
150150
```markdown
151-
# Bug: Login form crashes on submit
151+
# Fix bug:登录表单提交时崩溃
152152

153-
When users click submit, the app crashes.
154-
Error message: "Cannot read property 'email' of undefined"
153+
当用户点击提交时,应用崩溃。
154+
错误信息:"Cannot read property 'email' of undefined"
155155
```
156156

157157
**UpdatePlan call after analysis:**
158158
```markdown
159159
## Task List
160160

161-
- [ ] Reproduce the bug locally
162-
- [ ] Investigate the error in login form component
163-
- [ ] Identify root cause of undefined email property
164-
- [ ] Implement fix
165-
- [ ] Add validation to prevent similar issues
166-
- [ ] Test the fix with various inputs
167-
- [ ] Update error handling
161+
- [ ] 在本地复现缺陷
162+
- [ ] 调查登录表单组件中的错误
163+
- [ ] 定位 undefined email 属性的根本原因
164+
- [ ] 实施修复
165+
- [ ] 添加验证以防止类似问题
166+
- [ ] 使用各种输入测试修复
167+
- [ ] 更新错误处理
168168
```
169169

170170
## When to Use This Skill

templates/tools/update-plan.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Updates the current task plan and progress display.
55
Usage:
66
- Use this tool for non-trivial multi-step tasks when a task list helps track execution progress.
77
- Pass the complete current task list every time. The latest call replaces the previous visible plan.
8-
- The `plan` argument is a markdown string, not an array of step objects.
8+
- The `plan` argument is a markdown string, not an array of step objects. If the requirement is in Chinese, then use Chinese for the markdown as well.
99
- Keep exactly one task marked `[>]` while work is in progress.
1010
- Update the plan before starting a task, immediately after completing a task, and whenever tasks are split, merged, reordered, blocked, or changed.
1111
- Before executing the first task and after completing each task, re-evaluate the latest conversation and project context, then revise the remaining plan if needed.

0 commit comments

Comments
 (0)