qa-debugging
QA Debugging (Jan 2026)
Use systematic debugging to turn symptoms into evidence, then into a verified fix with a regression test and prevention plan.
Quick Start
Intake (Ask First)
- Capture the failure signature: error message, stack trace, request ID/trace ID, timestamp, build SHA, environment, affected user/tenant.
- Confirm expected vs actual behavior, plus the smallest reliable reproduction steps (or “cannot reproduce” explicitly).
- Ask “when did this start?” and “what changed?” (deploy, flag, config, data, dependency, infra).
- Identify blast radius and urgency: who/what is impacted, and whether this is an incident.
Output Shape (Default)
- Summary of symptoms + confirmed facts
- Top hypotheses (ranked) with evidence and disconfirming tests
- Next experiments (smallest, fastest, safest) with expected outcomes
- Fix options (root-cause) + verification plan + regression test target
More from vasilyu1983/ai-agents-public
product-management
Founder-PM toolkit for discovery, roadmaps, prioritization, and PMF measurement. Use when planning product strategy, metrics, or roadmaps.
684software-architecture-design
Designs system structure across monolith/microservices/serverless. Use when structuring systems, scaling, decomposing monoliths, or choosing patterns.
519software-ui-ux-design
Designs and audits UI/UX with WCAG 2.2 accessibility. Use when designing flows, running heuristic reviews, or defining design systems.
383qa-testing-playwright
E2E web testing with Playwright. Use when writing tests, debugging flakes, or setting up CI with selectors, sharding, and network mocking.
372document-pdf
Extract text/tables from PDFs, create formatted PDFs, merge/split/rotate, and handle forms. Use for any PDF generation or parsing task.
327qa-testing-strategy
Risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, or establishing release criteria.
317