qa-engineer

Generate risk-based test plans and cases using EP/BVA and decision tables.

7|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/pranav8494/team-of-agents --skill qa-engineer-pranav8494
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/pranav8494/team-of-agents/tree/main/skills/qa-engineer
Command: npx skills add https://github.com/pranav8494/team-of-agents --skill qa-engineer-pranav8494

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you prevent bugs and regressions by designing thorough, risk-based tests that you can trust before and after release.

Core Features & Use Cases

  • Risk-based test planning: Define scope, entry/exit criteria, and a test strategy aligned to the Test Pyramid.
  • High-signal test design: Generate test plans and cases using equivalence partitioning, boundary value analysis, decision tables, and state transition coverage.
  • Quality-focused execution support: Recommend automation decisions, quarantine flaky tests, and perform exploratory testing with structured charters and findings logs.
  • Defect reporting & review: Produce complete bug reports and review code specifically for testability and flakiness risk.

Quick Start

Write a risk-based test plan for the “checkout” flow, including entry/exit criteria, key edge cases, and a proposed automation strategy for the most critical regressions.

Frequently Asked Questions about qa-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a risk-based test plan for a critical feature flow?

High-signal test design uses equivalence partitioning, boundary value analysis, decision tables, and state transition coverage. These techniques generate structured test cases that target edge cases and maximize defect detection across complex state logic.

What is the best way to format bug reports to ensure quick resolution?

A structured bug report format enforces severity and priority rules while specifying reproduction steps and expected results. This standardization accelerates developer triage and ensures flakiness risks are clearly communicated for quarantine decisions.

How do I run structured exploratory testing sessions without losing coverage?

Code review for testability assesses architectural coupling and state dependencies that cause flaky tests. It identifies quarantine candidates and recommends automation decisions to stabilize unit, integration, and E2E layers against non-deterministic behavior.

Can I use equivalence partitioning and boundary value analysis for complex business logic?

Equivalence partitioning and boundary value analysis generate structured test cases for complex business logic. Combined with decision tables and state transition coverage, these techniques maximize defect detection across variable input ranges and system states.