菜单
Verify work is actually done before claiming completion. Run verification commands, see passing output, confirm behavior. Evidence before assertions. Use before committing, creating PRs, or claiming a fix works.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Post-implementation business assessment by Prometeo (PM). Verifies success metrics achievement, scope compliance, acceptance criteria business interpretation, risk materialization, and product decision closure. Outputs structured report with verdict and confidence score.
Analyzes checklist effectiveness by tracking hit rates, identifying stale items, and finding coverage gaps. Generates evolution suggestions following Boorman's principles. Use periodically to keep checklists field-tested and relevant.
Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Use periodically or before releases to maintain code hygiene.
Creates a complete product feature specification. Use when defining new features, writing user stories, or planning product work. Generates structured specs in docs/specs/.
Generates test cases for a module or function following FIRST principles and Arrange-Act-Assert pattern. Detects test framework from project config. Use to bootstrap test coverage for existing code or as the Red phase of TDD.
Create and manage git worktrees for isolated feature work. Use when starting implementation that should not touch the main workspace, or for parallel development. Handles creation, baseline verification, and cleanup.
| name | verification-before-completion |
| description | Verify work is actually done before claiming completion. Run verification commands, see passing output, confirm behavior. Evidence before assertions. Use before committing, creating PRs, or claiming a fix works. |
Verify: $ARGUMENTS
You MUST see evidence before claiming success. "It should work" is not evidence. A passing test run is evidence. A working command output is evidence.
Before ANY completion claim, run through these:
Run the tests — see them pass with your own eyes
Run: {project test command}
Expected: ALL tests pass
Actual: {paste actual output}
Verify the specific change — does it do what was requested?
Test: {specific verification for this change}
Expected: {expected behavior}
Actual: {paste actual output}
Check for regressions — did you break anything else?
Run: {full test suite or broader test}
Expected: No new failures
Actual: {paste actual output}
Verify the claim you're about to make — is it actually true?
"It should work because..." Not evidence. Run it.
"I made the change so it will pass now" Not evidence. Run the tests.
"The logic is correct" Not evidence. See it work.
"I fixed the same kind of bug before" Not evidence for this bug. Verify this fix.
"Tests were passing before my change" They might not be now. Run them again.
When reporting completion, include actual evidence:
Verification:
- Tests: {N} passing, {0} failing (command: {what you ran})
- Specific: {what you verified and what you saw}
- Regressions: none (full suite passing)
This skill reinforces the SIGN OUT checklist item "Stated build/test results (all passing, or documented what's failing and why)." The difference: this skill requires you to ACTUALLY RUN the verification and SHOW the output, not just state a claim.