verification-before-completion
Verification Before Completion
Overview
Claiming work is complete without verification is dishonesty, not efficiency.
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
More from pcvelz/superpowers
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
40using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
40writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
37requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
37executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
36subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
35