Build and maintain Page Object Models by live element discovery — never by guessing selectors. Build mode pairs with the user: derives the element inventory from test cases, proves every locator against the running app, and confirms with highlighted screenshots before anything enters the POM. Heal mode runs…
Set up Playwright e2e automation tailored to this team and app. Probes the running app (auth mechanism, API surface, spec availability), interviews with recommendations instead of open questions, scaffolds the playwright/ folder, and records every decision in playwright/AUTOMATION.md for the other e2e skills to read.…
Write the e2e test suite from test cases: API client for preconditions, fixtures, and intent-only specs on top of a proven POM. Never invents locators — if a page has no POM, it invokes /qa-e2e-pom first. Done only when the suite passes three gates: green, green again (cleanup proof), and green under --repeat-each=3…
Run eval fixtures against a skill to verify it produces correct output. Two modes per fixture: simulate (read SKILL.md, simulate the scenario, check assertions) and execute (run the skill's generated artifacts against the local fixture app and grade via exit codes and file checks). Use after /qa-improve to verify…
Generate and guide exploratory testing sessions. Produces a session charter, executes time-boxed unscripted testing using heuristic techniques, captures findings as new test scenarios, UX improvements, and missing coverage. Feeds discoveries back into the knowledge base and test cases. Use when: "exploratory test"…
Meta-skill that improves other skills based on real usage failures. When an SDT reports a skill produced incorrect or unexpected output, this skill analyzes the root cause, generates a structured improvement proposal, applies the fix following CONTRIBUTING.md guidelines, and offers to create a PR or apply locally.…
SDT test execution skill. Executes test cases from the knowledge base, verifies acceptance criteria in the browser, files bugs in Jira for failures, and updates the KB with results. Works within sprint context: knows the ticket, the ACs, the test cases, and what needs to pass before the ticket moves forward. Optional…
Review a Jira ticket during backlog grooming or refinement. Audits the ticket for testability, AC completeness, missing edge cases, and potential blockers. Outputs a structured review the SDT can bring to the grooming session. Use when: "review this ticket", "check ACs", "testability review", "grooming". Do NOT use…
First-run configuration wizard for QABuddy. Sets up context source (Jira, spec docs, chat, custom), team mode (solo vs PR-based), and project preferences. Writes .qabuddy.json to the project root. Re-run to reconfigure. Use when: "setup", "configure", "first time setup", "change settings". Do NOT use when: asking…
Guided end-to-end QA workflow. Chains test planning, ticket reviews, and test case generation in sequence, pausing after each phase for SDT review. Resumes from where it left off if interrupted. The main entry point for new epics. Use when: "start", "begin workflow", "qa workflow", "guided qa", "new epic". Do NOT use…
Generate test cases from a Jira ticket's acceptance criteria. Produces Playwright e2e test scenarios and a unit test checklist for developers. Test cases map back to requirements for traceability. Use when: "write test cases", "generate tests", "e2e tests for PROJ-789", "test cases for this ticket". Do NOT use when…
Build a test plan when a new Epic is created. Pulls epic details and linked stories from Jira, analyzes scope, and produces a test plan covering strategy, automation gap analysis, success criteria, environment needs, and risks. Output goes to Confluence and local test knowledge base. Use when: "test plan", "plan tests…
Re-test a bug fix after a developer resolves it. Pulls the original bug from Jira, re-executes the repro steps in the browser, checks for regressions, and updates the bug status. The final step in the SDT workflow before a ticket moves to Done. Use when: "verify fix", "retest", "is this fixed?", "check BUG-123"…