verification-before-completion

por obra

Úsalo cuando estés a punto de afirmar que el trabajo está completo, corregido o pasando, antes de hacer commits o crear PRs; requiere ejecutar comandos de verificación y confirmar la salida antes de hacer cualquier afirmación de éxito; siempre evidencia antes de aseveraciones.

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

Más skills de obra

brainstorming
obra
Debes usar esto antes de cualquier trabajo creativo: crear funciones, construir componentes, agregar funcionalidad o modificar comportamiento. Explora la intención del usuario, los requisitos y el diseño antes de la implementación.
creativeresearchdesign
systematic-debugging
obra
Úsalo al encontrar cualquier error, fallo en pruebas o comportamiento inesperado, antes de proponer correcciones.
developmenttestingcode-review
writing-plans
obra
Úsalo cuando tengas una especificación o requisitos para una tarea de varios pasos, antes de tocar el código.
developmentproject-management
using-superpowers
obra
Úsalo al iniciar cualquier conversación: establece cómo encontrar y usar habilidades, requiriendo la invocación de la herramienta Skill antes de CUALQUIER respuesta, incluyendo preguntas aclaratorias.
developmentdocumentproductivity
requesting-code-review
obra
Úsalo al completar tareas, implementar funciones importantes o antes de fusionar para verificar que el trabajo cumple con los requisitos.
developmentcode-review
test-driven-development
obra
Úsalo al implementar cualquier funcionalidad o corrección de errores, antes de escribir el código de implementación.
developmenttestingcode-review
executing-plans
obra
Úsalo cuando tengas un plan de implementación escrito para ejecutar en una sesión separada con puntos de control de revisión.
developmentproject-managementcode-review
subagent-driven-development
obra
Úsese al ejecutar planes de implementación con tareas independientes en la sesión actual.
developmentproject-management