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 lgbarn/devops-skills
terraform-plan-review
Use when analyzing terraform/tofu plan output for risks, security issues, and potential service disruptions. Required before any apply operation.
11using-devops-skills
Use when starting any conversation - establishes mandatory skill invocation for both Development AND Operations workflows
10writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
9brainstorming
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.
9writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
9executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
9