verification-before-completion

作成者: obra

作業完了、修正完了、またはテスト通過と主張する前に使用します。コミットやPR作成の前に、検証コマンドを実行し、その出力を確認してから成功を主張する必要があります。主張の前には常に証拠が必要です。

npx skills add https://github.com/obra/superpowers --skill verification-before-completion

Verification Before Completion

Overview

Core principle: Evidence before claims, always.

Violating the letter of this rule is violating the spirit of this rule.

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you haven't run the verification command in this message, you cannot claim it passes.

The Gate Function

BEFORE claiming any status or expressing satisfaction:

1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
   - If NO: State actual status with evidence
   - If YES: State claim WITH evidence
5. ONLY THEN: Make the claim

Skip any step = lying, not verifying

Common Failures

ClaimRequiresNot Sufficient
Tests passTest command output: 0 failuresPrevious run, "should pass"
Linter cleanLinter output: 0 errorsPartial check, extrapolation
Build succeedsBuild command: exit 0Linter passing, logs look good
Bug fixedTest original symptom: passesCode changed, assumed fixed
Regression test worksRed-green cycle verifiedTest passes once
Agent completedVCS diff shows changesAgent reports "success"
Requirements metLine-by-line checklistTests passing

Red Flags - STOP

  • Using "should", "probably", "seems to"
  • Expressing satisfaction before verification ("Great!", "Perfect!", "Done!", etc.)
  • About to commit/push/PR without verification
  • Trusting agent success reports
  • Relying on partial verification
  • Thinking "just this once"
  • Tired and wanting work over
  • ANY wording implying success without having run verification

Rationalization Prevention

ExcuseReality
"Should work now"RUN the verification
"I'm confident"Confidence ≠ evidence
"Just this once"No exceptions
"Linter passed"Linter ≠ compiler
"Agent said success"Verify independently
"I'm tired"Exhaustion ≠ excuse
"Partial check is enough"Partial proves nothing
"Different words so rule doesn't apply"Spirit over letter

Key Patterns

Tests:

✅ [Run test command] [See: 34/34 pass] "All tests pass"
❌ "Should pass now" / "Looks correct"

Regression tests (TDD Red-Green):

✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "I've written a regression test" (without red-green verification)

Build:

✅ [Run build] [See: exit 0] "Build passes"
❌ "Linter passed" (linter doesn't check compilation)

Requirements:

✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
❌ "Tests pass, phase complete"

Agent delegation:

✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
❌ Trust agent report

When To Apply

ALWAYS before:

  • ANY variation of success/completion claims
  • ANY expression of satisfaction
  • ANY positive statement about work state
  • Committing, PR creation, task completion
  • Moving to next task
  • Delegating to agents

Rule applies to:

  • Exact phrases
  • Paraphrases and synonyms
  • Implications of success
  • ANY communication suggesting completion/correctness

obraのその他のスキル

brainstorming
obra
あらゆる創造的作業(機能の作成、コンポーネントの構築、機能の追加、動作の変更)の前に必ず使用すること。実装前にユーザーの意図、要件、設計を探求します。
creativeresearchdesign
systematic-debugging
obra
バグ、テストの失敗、または予期しない動作に遭遇した際、修正を提案する前に使用してください
developmenttestingcode-review
writing-plans
obra
コードに触れる前に、複数ステップのタスクの仕様や要件がある場合に使用します。
developmentproject-management
using-superpowers
obra
会話を開始する際に使用します。スキルの検索方法と使用方法を確立し、明確化の質問を含むあらゆる応答の前に、必ずスキルツールの呼び出しを必要とします。
developmentdocumentproductivity
requesting-code-review
obra
タスク完了時、主要機能実装時、またはマージ前に、作業が要件を満たしているか確認するために使用します。
developmentcode-review
test-driven-development
obra
あらゆる機能やバグ修正を実装する際、実装コードを書く前に使用します。
developmenttestingcode-review
executing-plans
obra
別のセッションでレビューチェックポイントを設けて実行するための、書面による実装計画がある場合に使用します。
developmentproject-managementcode-review
subagent-driven-development
obra
現在のセッション内で独立したタスクを持つ実装計画を実行する際に使用する
developmentproject-management