qa-verify
Verification Before Completion
Announce: "I'm using enggenie:qa-verify to verify before claiming completion."
Hard Rule: Don't say "done" until you've seen the proof.
No "should work." No "probably passes." No "looks good." Run the command. Read the output. State the evidence.
Current-turn binding: If you haven't run the verification command in THIS response, you cannot claim it passes. Previous turns don't count - state may have changed.
The Verification Gate
Before claiming ANYTHING is complete, follow this exact sequence:
1. IDENTIFY - What command proves this claim?
2. RUN - Execute the FULL command. Fresh. Complete. Not partial.
3. READ - Full output. Exit code. Failure count. Warnings.
4. VERIFY - Does output actually confirm your claim?
More from badrusiddique/enggenie-skill
dev-implement
Use when executing an implementation plan task-by-task - dispatches subagents for implementation, manages git worktrees, handles phased multi-service deployment
10review-design
Use when reviewing frontend implementation against design specs - design system compliance, responsive behavior, accessibility audit
10dev-tdd
Use when writing any code - enforces test-driven development discipline with RED-GREEN-REFACTOR cycle, fires during any coding task
9architect-plan
Use when creating implementation plans from specs or requirements - phased task breakdown with deployment readiness gates before any coding begins
9review-code
Use when requesting or receiving code review - dispatches reviewer subagent or processes human PR feedback with technical evaluation
9memory-recall
Use when asking about previous sessions - cross-session context search via claude-mem with token-efficient 3-layer retrieval
9