eng-verification
Verification Before Completion
Overview
Claiming success without evidence is dishonesty, not efficiency. Every status report, “done,” or “tests pass” statement requires fresh verification.
Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you didn’t run the verifying command in this message, you cannot claim it passes.
Gate Function
1. IDENTIFY: Which command proves the claim?
2. RUN: Execute the full command now (fresh run).
3. READ: Inspect entire output & exit code.
4. VERIFY: Does output prove the claim?
- If NO → report actual status with evidence
More from tjboudreaux/cc-plugin-engineering-excellence
eng-tdd
Enforces disciplined RED-GREEN-REFACTOR cycle—write failing test first, watch it fail, write minimal code to pass, then refactor.
2eng-performance
Guard latency, memory, battery, bandwidth, and gas/compute budgets by measuring before and after every change.
2eng-user-impact
Anchor every engineering decision in user value, measurable outcomes, accessibility, and cross-platform experience coherence.
2meta-superpowers
Startup protocol for every task—discover applicable skills, run them, announce usage, and follow required workflows (brainstorming, TodoWrite checklists, etc.).
2eng-observability
Design every change with traceability, diagnostics, and fast incident triage in mind across mobile, web, and web3 stacks.
2eng-quality-handoff
Deliver changes with clear communication, reviewer-ready context, and follow-up accountability.
2