qa-engineer

Translate BRD/PRD criteria and API contracts into QA plans and executable tests.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Exia-thd/Digital-Nervous --skill qa-engineer-exia-thd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/Exia-thd/Digital-Nervous/tree/main/skills/qa-engineer
Command: npx skills add https://github.com/Exia-thd/Digital-Nervous --skill qa-engineer-exia-thd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end software quality assurance by translating BRD/PRD criteria and API contracts into structured test plans and executable tests across unit, integration, contract, and e2e levels.

Core Features & Use Cases

  • Automates generation of test plans across unit, integration, contract, and end-to-end tests
  • Produces executable test suites and artifacts compatible with common CI pipelines
  • Ensures traceability from BRD/PRD criteria to test cases and coverage metrics
  • Integrates with API specs, OpenAPI contracts, and service schemas to enforce contract quality

Quick Start

Provide BRD/PRD criteria and API contracts to generate a full QA plan and test suite.

Frequently Asked Questions about qa-engineer

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

FAQPage Schema
How do I automate test plan generation from BRD and API contracts?▼

Automate test plan generation by providing BRD/PRD criteria and API contracts to translate requirements into structured test plans. This ensures traceable coverage from business requirements to executable unit, integration, contract, and end-to-end tests.

Can I integrate generated test suites into existing CI pipelines?▼

Yes, generated test suites integrate with common CI pipelines. The automation produces executable test artifacts and quality gates that align with deployment pipelines to enforce consistent testing across backend and frontend codebases.

What is contract testing and how does it validate API specs?▼

Contract testing validates API interactions by enforcing contract quality against OpenAPI contracts and service schemas. It translates these specifications into executable tests to ensure backend and frontend integrations adhere to defined agreements.

How do I ensure traceable test coverage from PRD criteria?▼

Ensure traceable coverage by translating PRD criteria directly into executable test cases. This maps business requirements to unit, integration, and e2e tests, providing consistent quality gates and measurable coverage metrics throughout the pipeline.

Does this test automation support testcontainers for realistic environments?▼

Yes, the test automation supports testcontainers to provision realistic environments. This allows integration and end-to-end tests to execute against accurate service instances within your deployment pipelines.

What's the best way to structure end-to-end tests from business requirements?▼

The best way to structure e2e tests from business requirements is translating BRD/PRD criteria into a structured QA plan. This generates repeatable executable tests across frontend and backend codebases, ensuring traceable coverage and quality gates.