Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Don't claim "done" until you've checked against the criteria that define "done."
vibe-reflect-and-compound instead)Find the criteria — Look in:
Validate each criterion — For each one:
Report results:
| # | Criterion | Status | Evidence |
|---|---|---|---|
| 1 | [criterion text] | PASS/FAIL/PARTIAL | [evidence] |
Result: PASS / FAIL / PARTIAL Criteria Met: X/Y (Z%)
| # | Criterion | Status | Evidence |
|---|---|---|---|
| 1 | ... | ✓/✗/◐ | ... |
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.
中文简介正在准备中。当前显示原文说明。
Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.
中文简介正在准备中。当前显示原文说明。
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
中文简介正在准备中。当前显示原文说明。
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
中文简介正在准备中。当前显示原文说明。
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
中文简介正在准备中。当前显示原文说明。
Extracts and records architectural decisions from diffs, conversation context, and explicit choices. Supports automatic extraction from staged changes, deduplication against prior decisions, and persistent ADR-format logging with spec traceability. Use after a significant design or architecture choice, before committing a diff that embeds implicit decisions, or when the same question keeps resurfacing.
中文简介正在准备中。当前显示原文说明。