Back to Details

planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Planning

规划

Overview

概述

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the planning skill to create the implementation plan."
Save plans to: 
<repository-root>/plans/YYYY-MM-DD_<plan-name>.md
假设工程师对我们的代码库完全不了解，且缺乏良好的编码品味，撰写全面的实施计划。记录他们需要了解的所有信息：每个任务需要修改哪些文件、需要查看的代码、测试内容和文档，以及如何进行测试。将整个计划拆分为一个个易于处理的小任务。
假设他们是熟练的开发者，但对我们的工具集或问题领域几乎一无所知。同时假设他们不太了解良好的测试设计方法。
开始时声明： "我正在使用规划技能来创建实施计划。"
计划保存路径： 
<repository-root>/plans/YYYY-MM-DD_<plan-name>.md

Plan Structure

计划结构

markdown
undefined
markdown
undefined

Plan: <Feature Name>

Plan: <Feature Name>

Summary

Summary

<One paragraph describing what this builds>
<One paragraph describing what this builds>

Prerequisites

Prerequisites

<Setup steps, deps to install, docs to read — skip if none>
<Setup steps, deps to install, docs to read — skip if none>

Open Questions

Open Questions

<Unknowns or decisions to resolve before/during implementation — skip if none>
<Unknowns or decisions to resolve before/during implementation — skip if none>

Out of Scope

Out of Scope

<What this plan explicitly does NOT cover>
<What this plan explicitly does NOT cover>

Overview

Overview

<A couple of paragraphs about approach>
<A couple of paragraphs about approach>

Task <n>: <name>

Task <n>: <name>

Files: 
path/to/file.ts:42
, ... Depends on: Task <m> (if any)
<What to do and why. Verbose — include code when useful.>
Verify: <How to confirm this task is done — command, test, manual check>
undefined
Files: 
path/to/file.ts:42
, ... Depends on: Task <m> (if any)
<What to do and why. Verbose — include code when useful.>
Verify: <How to confirm this task is done — command, test, manual check>
undefined

Remember

注意事项

  • Exact file paths always, with line-numbers if relevant
  • Verbose description of implementation, or even complete code in plan (not "add validation")
  • Exact commands with expected output
  • Reference relevant skills
  • Order tasks by dependency; call out blocking relationships
  • Each task should be independently verifiable
  • 始终提供精确的文件路径，如有相关需包含行号
  • 详细描述实现内容，甚至可以在计划中写入完整代码（不要只写"添加验证"）
  • 提供精确的命令及预期输出
  • 参考相关技能
  • 根据依赖关系排序任务；明确标注阻塞关系
  • 每个任务都应可独立验证