Agent skill · magnus919
qa-methodology
Design and apply QA methodology for software teams: test strategy, regression testing, CI failure triage, test automation, quality gates and metrics, risk-based testing, exploratory testing, test design techniques, AI code quality gates (independent verification, acceptance-criteria testability review for agentic Spec-Driven Development), mutation-guided test hardening and review evidence (surviving mutants, weak assertions, diff-aware mutation testing), agentic eval design (dataset test design, judge-as-system-under-test, flaky-eval discipline), QA career levels (Senior/Staff/Principal), and SDET engineering (test infrastructure, gTAA, CI/CD integration). Do not use for root-cause debugging of production incidents, security implementation or threat modeling, or evaluation framework governance and statistical analysis — route those to systematic-debugging, secure-software-engineering, and agent-evals-and-observability respectively.
What it needs
About 6k tokens when loaded.
What this skill does
QA Methodology Senior-to-principal QA and SDET methodology: test strategy, automation, regression, risk-based prioritization, exploratory testing, quality gates, AI code quality gates for agentic Spec-Driven Development, agentic eval design, career leveling, and SDET engineering. Ownership You own You don't own --------- -------------- Test strategy — what to test, at what level, with what priority Root-cause debugging — route to systematic-debugging Test automation — framework selection, parallelism, flaky management Security implementation and threat modeling — route to secure-software-engineering E2E automation strategy and coverage decisions Operating a browser test tool (Playwright) — authoring/running specs, selectors, network mocking, scraping — route to playwright Regression suites — selection, impact analysis, suite evolution Spec pipeline mechanics and gate verdicts — route to spec-driven-development Quality gates — blocking vs advisory, metrics, DORA Eval framework governance and statistics — route to agent-evals-and-observability Risk-based testing — P×I scoring, prioritization, registers Verification verdicts against explicit criteria — route to verification-methodology Exploratory testing — SBTM charters, heuristics, tours Feature implementation — that's the developer AI code quality gates — independent verification, AC testability Production monitoring and incident response — that's SRE Mutation-guided test hardening — bounded mutation review evidence and survivor triage Verification verdicts against explicit criteria — route to verification-methodology Agentic eval design — dataset design, judge bias, flaky-eval discipline QA career levels — Senior/Staff/Principal scope progression SDET engineering — test infrastructure, gTAA, CI/CD integration Core Principles If it isn't tested, it's broken. Untested code is code whose failure mode hasn't been discovered yet. Quality is a property of the process, not the artifact. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/qa-methodology