execute
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseExecute
执行
Use this skill when the work is understood and the job is to build it.
This is the canonical execution workflow. , , ,
, , , and route here.
autopilotralphultraworkultragoalultrapilotpipelineswarm当任务需求已明确,需要开展开发工作时,使用本skill。
这是标准的执行工作流。、、、、、和均会路由至此。
autopilotralphultraworkultragoalultrapilotpipelineswarmGoal
目标
Take a task from agreed intent to working code, with evidence that it works.
将任务从已达成共识的需求转化为可运行的代码,并提供代码可正常工作的验证依据。
Workflow
工作流
- Confirm the task is clear enough to build. If it is not, plan first.
- Break the work into independent units; run genuinely independent units in parallel.
- Implement the smallest correct change per unit, reusing existing utilities and patterns.
- Verify as you go, not only at the end.
- Report what changed, what was verified, and what remains.
- 确认任务需求足够清晰以便开展开发。若需求不清晰,应先进行规划。
- 将工作拆分为独立单元;真正独立的单元可并行推进。
- 针对每个单元实现最小的正确变更,复用现有工具和模式。
- 边开发边验证,而非仅在最后阶段验证。
- 汇报已完成的变更、已验证的内容以及剩余待办事项。
Scale
规模适配
Match the machinery to the task:
- Single unit — implement directly, verify, done.
- Several independent units — delegate to agents in parallel.
executor - Long-running or unbounded — keep a durable task list and continue until the list is empty.
- Needs coordinated parallel workers — use .
team
Do not spin up coordination for work that one focused pass would finish.
根据任务规模匹配相应机制:
- 单个单元 — 直接实现、验证,完成任务。
- 多个独立单元 — 并行委托给agents处理。
executor - 长期运行或无边界任务 — 维护一个持久化任务列表,直至列表为空。
- 需要协作并行处理的任务 — 使用。
team
对于单次专注即可完成的工作,无需启动协作机制。
Rules
规则
- Prefer deletion over addition when behavior is preserved.
- Do not add dependencies without an explicit request.
- Keep diffs small and reversible.
- Placeholder TODOs, , and stub tests are blockers, not progress.
test.skip - Authoring and approval are separate passes — do not self-approve; hand off to or
review.verify
- 在保持原有功能的前提下,优先选择删除代码而非新增代码。
- 若无明确要求,不得添加依赖。
- 保持代码变更(diff)小且可回滚。
- 占位符TODO、和存根测试属于阻塞项,不代表进度。
test.skip - 代码编写与审批为独立环节 — 不得自行审批;需移交至或
review环节。verify
Completion
完成标准
Before claiming done:
- No pending tasks
- Tests pass, or failures are reported plainly
- Verification evidence collected
在宣称任务完成前,需满足:
- 无待办任务
- 测试通过,或明确报告测试失败情况
- 已收集验证依据
Output
输出内容
- Files changed
- What was implemented
- Evidence it works
- What is still open
- 已修改的文件
- 已实现的功能
- 代码可正常运行的验证依据
- 仍未完成的事项