Back to Details

spec-loop-implementation-flow

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
This skill is mandatory only for approved task-file-path implementation under the 
spec-loop-plan-task
workflow. It is not used for short planning path work kept in chat.
Use this skill when implementation deviates from the approved task, when uncertainty must be clarified instead of guessed through, when new blocking questions arise, or before presenting the current task or subtask to the User.
Before work: read 
../spec-loop-plan-task/SKILL.md
, follow all files it requires, and apply the full 
spec-loop-plan-task
bundle as shared convention guidance. Then read implementation-flow-guidance.md.
Use the same active task file used for planning and approval. Do not create a second implementation artifact or a new task status. Do not edit that active task file except as explicitly authorized by 
implementation-flow-guidance.md
.
Use 
implementation-flow-guidance.md
as the authoritative source for implementation-phase authorized task-file updates, clarification routing, post-implementation approval handling for implemented deviations, 
Implementation notes
, completion checks, and the 
in-progress
-> 
review
transition.
Implementation notes
simplifies change review by capturing relevant implementation decisions and reasons above code level. It is not a live worklog. After implementation and verification, and before presenting work as ready, moving it to 
review
, or proposing a commit, perform the mandatory 
Implementation notes
check defined in 
implementation-flow-guidance.md
.
This skill may be applied in parallel with other implementation- related skills only when their instructions do not contradict this skill or the governing 
spec-loop-plan-task
bundle. If implementation-related skills conflict or set different priorities, stop and ask the User to clarify which priorities govern the work.
Follow 
implementation-flow-guidance.md
for the implementation-time routing and response rules.
If no approved active task file exists, if short-path planning is in use, or if the current increment is unclear, do not use this skill. Continue task work under the 
spec-loop-plan-task
bundle instead.
此技能仅在
spec-loop-plan-task
工作流下已批准的任务文件路径实施中强制使用。不适用于保存在聊天记录中的短规划路径工作。
当实施内容偏离已批准任务、必须澄清不确定性而非自行猜测、出现新的阻塞问题，或向用户展示当前任务或子任务前，需使用此技能。
开始工作前：阅读
../spec-loop-plan-task/SKILL.md
，遵循其要求的所有文件，并将完整的
spec-loop-plan-task
套件作为通用约定指南应用。然后阅读implementation-flow-guidance.md。
使用用于规划和审批的同一活跃任务文件。 请勿创建第二个实施工件或新的任务状态。 除非经
implementation-flow-guidance.md
明确授权，否则不得编辑该活跃任务文件。
将
implementation-flow-guidance.md
作为实施阶段授权任务文件更新、澄清流程、实施偏差的实施后审批处理、
Implementation notes
、完成检查以及
in-progress
-> 
review
阶段转换的权威依据。
Implementation notes
通过在代码层面之上记录相关实施决策及原因，简化变更评审流程。它不是实时工作日志。在实施和验证完成后，以及在提交工作成果、将其移入
review
阶段或提议提交代码前，需执行
implementation-flow-guidance.md
中定义的强制
Implementation notes
检查。
仅当其他实施相关技能的说明与本技能或管控的
spec-loop-plan-task
套件无冲突时，才可与本技能并行使用。若实施相关技能存在冲突或设定了不同优先级，请停止工作并询问用户以明确工作遵循的优先级。
实施阶段的流程和响应规则请遵循
implementation-flow-guidance.md
。
若不存在已批准的活跃任务文件、使用了短路径规划或当前增量不明确，则请勿使用此技能。请转而在
spec-loop-plan-task
套件下继续任务工作。