qa-test
enggenie:qa-test
Announcement
When this skill is invoked, announce:
I'm using enggenie:qa-test for [automation/manual] QA testing.
Replace [automation/manual] with the appropriate mode based on user request or context.
Key Distinction
- enggenie:qa-verify asks: "Does my code work?"
- enggenie:qa-test asks: "Does the product work for users?"
qa-verify is developer-facing - unit tests, integration tests, type checks, lint passes. qa-test is user-facing - can a real person accomplish their goal using this product? The difference matters. A feature can pass every unit test and still be broken for users.
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