Back to Details

simplify-work

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Simplify Work

简化工作

Make the selected area easier to understand, change, and verify while preserving intended behavior.
Use engineering-discipline.md. Accept a direct scope, handoff, review finding, or Plan as input.
在保留预期行为的前提下，让选定区域更易于理解、修改和验证。
请参考engineering-discipline.md。接受直接范围、工作交接、评审结论或Plan作为输入。

Boundaries

边界规则

  • Read repo instructions and relevant current docs; inspect the workspace so preexisting changes are not mistaken for task work.
  • Confirm the bounded surface, intended behavior, callers, constraints, and proof before editing.
  • Do not scan the whole repo, create a Plan or handoff, run an interview, or produce HTML by default.
  • Do not use line count as the goal. Prefer fewer concepts, branches, layers, mutable states, and duplicated rules when that reduces reader load.
  • Preserve unrelated dirty work and preexisting drafts or prototypes. Clean only task-created artifacts whose disposition is clear.
  • If the change requires new product behavior, changing a declared compatibility contract, or unresolved architecture placement, stop for owner judgment or route discovery to 
    improve-architecture
    .
  • 阅读仓库说明和相关现有文档；检查工作区，避免将已存在的变更误认为任务工作内容。
  • 在编辑前，确认划定的范围、预期行为、调用方、约束条件以及验证依据。
  • 默认情况下，不要扫描整个仓库、创建Plan或工作交接文档、进行访谈，也不要生成HTML。
  • 不要以代码行数作为目标。当减少概念、分支、层级、可变状态和重复规则能够降低读者理解负担时，优先选择这些方式。
  • 保留无关的未完成工作以及已存在的草稿或原型。仅清理任务产生的、处置方式明确的产物。
  • 如果变更需要新增产品行为、修改已声明的兼容性协议，或架构位置尚未确定，请暂停工作等待负责人判断，或转向
    improve-architecture
    流程进行架构探索。

Simplify

简化步骤

  1. Establish a focused behavior check. Add characterization coverage only when existing evidence cannot protect consequential behavior.
  2. Trace the relevant caller, data, component, or control flow and find the accidental structure carrying the cost.
  3. Prefer deletion, direct data flow, canonical ownership, and types or data models that remove invalid states and spread-out branching.
  4. Keep each change small enough to reason about and verify. Avoid unrelated cleanup and speculative abstraction.
  5. Run focused checks as the work proceeds, then the relevant regression or acceptance gate. Read the results.
For Plan-backed work, select the requested or next unchecked Phase, follow its checkpoints, and update Tasks or acceptance criteria only after evidence supports them. Apply only that Phase's Doc Delta and referenced-draft work; after fresh review and fixes, update the Plan/docs before marking it complete. Leave Plan or Roadmap cleanup to final review. Without a Plan, do not invent Plan mechanics.
  1. 建立聚焦的行为检查机制。只有当现有证据无法保障关键行为时，才添加特征覆盖测试。
  2. 追踪相关的调用方、数据、组件或控制流，找出增加理解成本的冗余结构。
  3. 优先选择删除操作、直接数据流、规范所有权，以及能够消除无效状态和分散分支的类型或数据模型。
  4. 确保每次变更足够小，便于推理和验证。避免进行无关的清理工作和推测性抽象。
  5. 在工作推进过程中运行聚焦检查，之后执行相关的回归测试或验收关卡，并查看结果。
对于基于Plan的工作，选择要求的或下一个未检查的阶段，遵循其检查点，仅在有证据支持时更新任务或验收标准。仅应用该阶段的文档变更（Doc Delta）和参考草稿内容；在完成新的评审和修复后，更新Plan/文档，再标记该阶段完成。将Plan或路线图的清理工作留到最终评审阶段。若无Plan，请勿自行创建Plan相关机制。

Close the scope

收尾工作

Self-check behavior preservation and whether the result materially lowers reader load. Send the entire scope, not only the latest patch, to an independent fresh-context reviewer through 
review-work
; verify accepted claims against primary evidence, fix authorized blocking findings, and rerun affected checks. Report the simplification, behavior evidence, and residual risk concisely.
自行检查行为是否得到保留，以及结果是否切实降低了读者的理解负担。通过
review-work
将整个范围（而非仅最新补丁）发送给独立的、拥有全新上下文的评审者；对照原始证据验证已接受的结论，修复经授权的阻塞性问题，并重新运行受影响的检查。简洁地汇报简化成果、行为验证证据以及剩余风险。