qa-architect

Define a risk-based testing plan and generate a Markdown Test Design Document.

8|2|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/u1pns/skills-entrepeneur --skill qa-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-architect
Source: https://github.com/u1pns/skills-entrepeneur/tree/main/qa-architect
Command: npx skills add https://github.com/u1pns/skills-entrepeneur --skill qa-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA Architect reduces production outages by defining a rigorous testing strategy before code is written, acting as a gatekeeper of quality using TEA methodology.

Core Features & Use Cases

  • Risk-based Testing: Prioritizes tests by impact and likelihood to catch critical failures early.
  • Test Pyramid & Strategy: Defines unit, integration, and E2E balance and tooling recommendations.
  • Quality Gates: Establishes Definition of Done criteria and gating rules for releases.
  • Test Data & Debugging: Plans data seeds and systematic debugging approaches to reproduce issues.
  • Output: Generates a comprehensive Test Design Document for stakeholder alignment.

Quick Start

Provide a complete Test Design Document for the given project, detailing risk assessment, coverage plan, automation strategy, and quality gates.

Frequently Asked Questions about qa-architect

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

FAQPage Schema
How do I create a risk-based testing plan to prevent production defects?

A risk-based testing plan prioritizes tests by impact and likelihood to catch critical failures early. It reduces production outages by defining a rigorous testing strategy before code is written, acting as a gatekeeper of quality.

What is the best way to balance unit, integration, and E2E tests in an automation strategy?

Balance unit, integration, and E2E tests by defining a test pyramid strategy. This ensures optimal coverage and tooling recommendations while maintaining a rigorous automation approach to prevent defects from reaching production.

How do you establish quality gates and Definition of Done criteria for releases?

Establish quality gates by defining specific Definition of Done criteria and gating rules for releases. This ensures that a rigorous testing strategy is enforced, acting as a gatekeeper to prevent defects from reaching production.

Can I generate a single Test Design Document for stakeholder alignment?

Yes, you can generate a comprehensive Markdown Test Design Document for stakeholder alignment. This output details risk assessment, coverage planning, automation strategy, and quality gates ready for review.

How do I plan test data seeds and systematic debugging approaches to reproduce issues?

Plan test data seeds and systematic debugging approaches by defining data preparation strategies within your testing plan. This ensures issues are reproducible and traceable before the code reaches production environments.

Do I need a risk assessment before defining test coverage and automation strategy?

Yes, a risk assessment is required before defining test coverage and automation strategy. Prioritizing tests by impact and likelihood ensures the coverage plan effectively prevents critical defects from reaching production.