qa-testlisted

# 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. --- ## Jira Ticket Entry When the user references a Jira ticket (e.g., "Test PROJ-1234", "QA PROJ-1234"): 1. Read the Jira ticket using MCP tools 2. Find the "For QA" section in the ticket description - it contains the spec path, key edge cases, and Playwright scenarios written by the PM 3. Find the "Dev Handoff" comment - it contains the PR link, what was built, known limitations, and focus areas written by the Dev 4. Open the linked spec file. Extract the acceptance criteria, QA test plan table, and Playwright automation scenarios 5. Open the PR to understand what code changed This gives you the full chain: what PM specified → what Dev built → what QA should verify. If any piece is missing, ask the user for clarification. If Jira MCP is not available, ask: "I can't read PROJ-1234 directly. Can you share the spec path and PR link?" --- ## A