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 grnfromdark/autodevskill
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
22auto-dev
>
21systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
21requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
21subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
21brainstorming
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.
20