Back to Details

implement-work

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Implement Work

开展落地工作

Execute the authorized outcome without imposing a Plan-shaped process on other inputs.
Use engineering-discipline.md. For Plan-backed work, also use workflow-language.md, document-conventions.md, and phase-review-template.md.
执行已授权的工作成果，无需对其他输入套用Plan型流程。
请遵循engineering-discipline.md。对于基于Plan的工作，还需遵循workflow-language.md、document-conventions.md和phase-review-template.md。

Establish the work scope

确定工作范围

  1. Read repo instructions, the governing input, relevant current docs, source, tests, and any referenced artifacts.
  2. Identify the authorized outcome, boundaries, acceptance evidence, doc impact, and unresolved decisions. Research only gaps that can materially change the implementation.
  3. If a Plan governs the work, select the requested Phase(s), or the next unchecked Phase when asked to continue, and note its review checkpoints and Doc Delta.
  4. Ask only for real ambiguity, credentials, product judgment, risky authority, or an explicit human checkpoint. Otherwise proceed.
Do not create a Plan, interview loop, handoff, worktree, commit, or PR unless the input or authorized workflow calls for it.
  1. 阅读仓库说明、指导性输入文件、相关现有文档、源代码、测试用例及所有参考工件。
  2. 明确已授权的工作成果、边界、验收依据、文档影响及未解决的决策事项。仅研究可能对实现产生实质性影响的信息缺口。
  3. 如果工作受Plan管控，选择要求的阶段，或在需要跟进时选择下一个未完成的阶段，并记录其评审检查点和文档变更（Doc Delta）。
  4. 仅在存在实际歧义、需要权限、产品判断、高风险授权或明确人工检查点时才提出疑问。否则直接推进工作。
除非输入或授权工作流要求，否则不要创建Plan、访谈流程、工作交接、工作树、提交或PR。

Execute and verify

执行与验证

  • Work through the bounded scope without absorbing adjacent cleanup.
  • Use the fastest meaningful feedback loop: focused red/green checks for cheap behavior, same-scope checks for setup-heavy behavior, and acceptance gates for slow end-to-end, full-suite, or visual behavior. Use manual evidence only when automation is impractical and record the residual risk.
  • Verify through public or intentionally stable interfaces when practical. Read fresh command or observation results before claiming success.
  • Keep canonical docs current as behavior lands. Preserve unrelated dirty work and preexisting drafts or prototypes.
  • Follow Plan-defined high-impact review checkpoints. Low-impact Tasks can wait for the end-of-Phase review.
  • For Plan-backed work, check Tasks and acceptance criteria only after evidence supports them; apply only the selected Phase's Doc Delta and route non-required work to 
    Discovered Follow-ups
    .
  • Without a Plan, do not invent Plan bookkeeping. Treat the authorized work as one review scope and keep only state another worker or reviewer needs.
  • 在限定范围内开展工作，不要额外处理无关的清理工作。
  • 采用最快速的有效反馈循环：针对简单行为使用聚焦式红/绿检查，针对依赖环境搭建的行为使用同范围检查，针对慢节奏的端到端、全套件或可视化行为使用验收闸门。仅在自动化不可行时使用人工验证证据，并记录剩余风险。
  • 尽可能通过公开或稳定的接口进行验证。在宣称成功前，务必查看最新的命令执行结果或观测数据。
  • 随着功能落地，同步更新标准文档。保留无关的未完成工作及现有草稿或原型。
  • 遵循Plan定义的高影响评审检查点。低影响任务可等到阶段末评审时处理。
  • 对于基于Plan的工作，仅在有证据支持时才核对任务和验收标准；仅应用所选阶段的文档变更（Doc Delta），并将非必要工作归入「发现的后续事项（Discovered Follow-ups）」。
  • 如果没有Plan，不要自行创建Plan相关的记录工作。将授权工作视为一个评审范围，仅保留其他工作人员或评审人员需要了解的状态信息。

Close the scope

关闭工作范围

  1. Self-check the entire authorized scope against its input, docs, tests, actual diff, and durable-artifact boundary.
  2. Run the relevant verification and read its output.
  3. 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.
  4. Repeat only the review coverage justified by the changed surface or residual risk.
  5. Update governing artifacts. For Plan-backed work, use phase-review-template.md, finish the selected Phase's Plan/doc updates, and only then mark it complete.
Do not recursively review the review. Add Milestone-level integration review only when cross-Phase acceptance or risk warrants it. Leave Plan or Roadmap cleanup to final review.
  1. 对照输入文件、文档、测试用例、实际代码差异及持久化工件边界，自行检查整个授权范围的完成情况。
  2. 运行相关验证流程并查看输出结果。
  3. 通过
    review-work
    将整个工作范围（而非仅最新补丁）提交给独立的新上下文评审人员；对照原始证据验证已确认的事项，修复已授权的阻塞性问题，并重新运行受影响的检查。
  4. 仅根据变更范围或剩余风险，重复必要的评审覆盖内容。
  5. 更新指导性工件。对于基于Plan的工作，使用phase-review-template.md，完成所选阶段的Plan/文档更新后，再标记该阶段为完成。
不要递归评审评审内容。仅当跨阶段验收或风险需要时，才添加里程碑级别的集成评审。将Plan或路线图的清理工作留到最终评审时处理。