Back to Details

parallel

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
One agent per independent problem domain, all dispatched in a single response so they run concurrently.
Each agent's prompt carries:
  • Scope: one file, one subsystem, one problem. "Fix all the tests" loses the agent.
  • Context, pasted in: error messages, test names, relevant paths. Agents inherit nothing from the session.
  • Constraints: what must not change ("tests only", "do not touch production code").
  • Expected return: a summary of root cause and changes, so integration is reviewable.
Integrate when they return: read each summary, check the diffs for conflicts, run the full suite, then the 
verify
skill before claiming the batch done.
Do not use when failures are related (fixing one may fix the rest: investigate together first), when the problem is still exploratory, or when agents would touch the same files.
每个独立问题领域对应一个Agent，所有Agent在单次响应中被分派，以便并发运行。
每个Agent的提示信息需包含：
  • 范围：单个文件、单个子系统、单个问题。类似“修复所有测试”这样的指令会让Agent迷失方向。
  • 上下文：粘贴相关内容，如错误信息、测试名称、相关路径。Agent不会继承会话中的任何内容。
  • 约束条件：明确哪些内容不能修改（例如“仅修改测试代码”、“请勿改动生产代码”）。
  • 预期返回结果：根因分析和修改内容的摘要，以便集成时可审核。
当Agent返回结果后进行集成：阅读每个摘要，检查差异是否存在冲突，运行完整测试套件，然后在宣告批量任务完成前执行
verify
skill。
请勿在以下场景使用：故障之间存在关联（修复一个可能解决其余问题：需先共同排查）、问题仍处于探索阶段、或多个Agent会操作同一文件时。