Menu
Run a pre-QA implementation self-check against task scope, acceptance criteria, validation evidence, and pending diff.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | implementation-check |
| description | Run a pre-QA implementation self-check against task scope, acceptance criteria, validation evidence, and pending diff. |
在 Engineer 完成实现后、进入 QA 验收前，对任务范围、实现 diff、验证结果和已知风险做自检；它是 QA 前门禁，不替代 QA 的独立验收结论。
/implementation-check <任务定义、PRD 或 pending diff>
/acceptance-check 的 QA 验收每次自检必须逐项记录状态、证据和结论：
depends_on、read_before_start、execution、evidence、handoff 是否存在；缺失时必须说明原因和影响。evidence 和 handoff 恢复任务状态。建议进入 QA 或 不建议进入 QA，并给出一句理由。/implementation-check tasks-p8.md 中 token-report skill 变更，核对 pending diff 是否只包含 SKILL.md 和任务勾选/implementation-check bugfix 提交涉及 unrelated README 改动，判断是否偏离任务范围[示例：实现符合任务]
[自检对象] ...
[范围一致性] 通过（证据：...）
[文件变更检查]
- path: 与任务输出的关系 / 是否在范围内
[任务字段完整性]
- 任务 ID / depends_on / read_before_start / execution / evidence / handoff: 完整 / 缺失原因
[验证证据]
- 命令或检查：结果 / 关键证据
[上下文恢复性]
- 可恢复 / 不可恢复（证据：任务文件、依赖产物、evidence、handoff）
[已知限制]
- ...
[风险项]
- 兼容性 / 数据 / 权限 / 性能 / 安全 / 发布
[结论] 建议进入 QA / 不建议进入 QA
[理由] ...
[退回项] （仅当不建议进入 QA 时）
[示例：实现偏离任务]
[范围一致性] 不通过（证据：...）
[文件变更检查]
- path: 与任务无关 / 需要移出本次提交
[验证证据]
- 缺失或失败：...
[任务字段完整性]
- 缺失字段或缺失原因：...
[上下文恢复性]
- 不可恢复（原因：缺少 read_before_start / evidence / handoff / 依赖产物）
[结论] 不建议进入 QA
[退回项]
- 移除无关变更或拆分任务
- 补齐失败/缺失的定向验证
建议进入 QA 或 不建议进入 QAProduce a QA acceptance report for a task or change set following the acceptance-document field standard in docs/claude/standards.md.
Generate or append a task entry into tasks-pX.md following the task-list field standard defined in docs/claude/standards.md.
Produce a read-only release readiness recommendation from implementation results, QA evidence, environment details, and rollback conditions.
Read pending diff, PRs, task results, or selected files and produce a structured review without modifying code.
Read OPC run artifacts and summarize token, API call, duration, and cost-related usage without invoking models or tools.
Convert a PRD, bug report, or task description into structured test points and targeted validation commands.