senior-qa

Design QA strategies and evaluate release readiness with risk-based test plans.

5|Updated Jul 6, 2025
One-click install
npx skills add https://github.com/GuicedEE/ai-rules --skill senior-qa-guicedee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-qa
Source: https://github.com/GuicedEE/ai-rules/tree/main/skills/.curated/senior-qa
Command: npx skills add https://github.com/GuicedEE/ai-rules --skill senior-qa-guicedee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

QA workflow design to strengthen testing coverage and ensure dependable releases across projects.

Core Features & Use Cases

  • Risk-based testing: prioritize tests by risk, critical paths, and data loss scenarios.
  • Test pyramid decisions: guide layering decisions (unit, integration, E2E) for efficient coverage.
  • Regression planning and release criteria alignment for sign-off.
  • Triaging flaky tests: root-cause and stabilize flaky tests to improve release confidence.

Quick Start

Create a risk-based test plan for a new release and map coverage to the test pyramid.

Frequently Asked Questions about senior-qa

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

FAQPage Schema
How do I create a risk-based test plan for a software release?

A risk-based test plan prioritizes testing by critical paths and data loss scenarios. You can map test coverage to the test pyramid and generate sign-off criteria using reusable templates to ensure dependable releases.

What is the best way to structure test pyramid layers for CI/CD pipelines?

Structuring the test pyramid involves guiding layering decisions across unit, integration, and E2E tests. This approach ensures efficient coverage and streamlines regression planning within your CI/CD pipelines.

How do I triage flaky tests to improve release confidence?

To triage flaky tests, you root-cause and stabilize the inconsistent test behaviors. This process directly improves release confidence by ensuring dependable regression results across your automation suite.

How do I define release criteria and sign-off templates for regression planning?

Defining release criteria involves aligning regression planning with sign-off requirements. You can generate standardized templates and reusable references to evaluate release readiness and fortify quality.

Can I apply risk-based testing to coordinate QA workflows across software teams?

Yes, risk-based testing supports software teams coordinating QA strategy design. It prioritizes tests by risk and critical paths, streamlining evaluation across projects and CI/CD pipelines.

When should I not use risk-based testing for my QA strategy?

Risk-based testing may not suit projects without identifiable critical paths or data loss scenarios. Without clear risk prioritization, standard regression planning provides more uniform coverage for your releases.