Back to Details

working-on

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Working On

工作跟踪

You are managing a tracking document that serves as the source of truth for the current task or feature.
The tracking document is: 
$path
你正在管理一份作为当前任务或功能唯一可信来源的跟踪文档。
该跟踪文档路径为：
$path

Behavior

行为规范

Once activated, treat the tracking document as a living record. Update it after:
  • Any decision is made (architectural, design, scope, naming, etc.)
  • A new problem, bug, or edge case is discovered
  • A new sub-feature or requirement emerges
  • An issue is raised or resolved
  • Any significant implementation work is completed
  • A key part of a conversation with the user that would be useful to recall later
  • Any time you commit files — a commit is a strong signal that the tracking document should also be reviewed and updated
If in doubt, update the document. It is better to over-document than to lose context.
激活后，请将跟踪文档视为动态记录。在以下情况发生后更新文档：
  • 做出任何决策（架构、设计、范围、命名等）
  • 发现新问题、Bug或边缘情况
  • 出现新的子功能或需求
  • 问题被提出或解决
  • 完成任何重要的实现工作
  • 与用户对话中需要日后回顾的关键内容
  • 任何提交文件的时刻——提交是一个明确信号，表明应同时检查并更新跟踪文档
如有疑问，就更新文档。过度记录总比丢失上下文信息要好。

Git Handling

Git 处理规则

Do NOT commit the tracking document unless it already appears in the repository's git history. If the file is not tracked by git, leave it out of any commits.
除非跟踪文档已存在于仓库的Git历史记录中，否则不要提交该文档。如果文件未被Git追踪，请勿将其纳入任何提交。

Guidelines

指南

  • Keep updates concise — bullet points and short paragraphs are preferred over prose
  • Use timestamps or date headers when the document spans multiple sessions
  • Record the why behind decisions, not just the what
  • When a section becomes stale or irrelevant, move it to an "Archive" or "Resolved" section rather than deleting it
  • If the document doesn't exist yet, create it with a sensible structure based on the task at hand
  • 保持更新简洁——优先使用项目符号和简短段落，而非冗长的散文
  • 当文档跨多个工作时段时，使用时间戳或日期标题
  • 记录决策背后的原因，而不仅仅是决策内容
  • 当某个部分过时或无关时，将其移至“归档”或“已解决”部分，而非直接删除
  • 如果文档尚未存在，请根据当前任务创建结构合理的文档