Menu
Trigger only after an implementation exists and must be validated against an explicit plan, acceptance criteria, or expected behavior by running relevant checks and reporting evidence-backed pass/fail results.
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 | verification |
| description | Trigger only after an implementation exists and must be validated against an explicit plan, acceptance criteria, or expected behavior by running relevant checks and reporting evidence-backed pass/fail results. |
| requires | [] |
Use this skill only after implementation exists and must be checked against:
Do not use this skill to implement fixes, perform root-cause debugging, review style, or create a plan.
verified: true is valid only when all required criteria pass.Identify plan, implementation summary, expected behavior, and acceptance criteria. If criteria are absent, derive minimal criteria from the user request and label them as derived.
Choose the smallest sufficient check set:
Run checks and capture exact results. If a command cannot run, mark the corresponding criterion blocked or skipped, not passed.
Return verified: true only when every required criterion passes and no required command failed.
verified: true after failed tests.status: verified | failed | blocked
verified: boolean
criteria:
- id: string
description: string
result: passed | failed | skipped | blocked
evidence: string
commands:
- command: string
result: passed | failed | skipped
summary: string
passed: string[]
failed: string[]
skipped: string[]
blockedReason: string | null
nextAction: none | fix | debug | provide-environment | accept-risk
Trigger only when an already-approved PLAN.md or equivalent structured plan must be executed through wave-ordered tasks, isolated git worktrees, wave-level verification, final integration, and controlled merge handling; never create the plan or execute unapproved work.
Trigger only to inspect an existing diff, commit, branch, or PR for correctness, regression, security, performance, and maintainability issues; do not use to implement changes or run acceptance verification.
Trigger only when an observed failure, reproducible bug, regression, stack trace, failing test, or merge conflict requires evidence-based root-cause diagnosis before applying or recommending a fix.
Trigger only when the user explicitly requests test-driven implementation or when an assigned task requires adding behavior by first writing a failing test, then minimal code, then refactoring without behavior change.
Trigger only when a coding task requires a written implementation plan before execution, especially multi-file or multi-step work needing dependency analysis, wave classification, and file-isolation-safe task partitioning; dispatches Planner to write a timestamped plan under ~/.yi-workflow/docs/plans/ and performs no implementation.