quality-expert

Assess and shape holistic quality strategies for software teams.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/felixgeelhaar/skills --skill quality-expert-felixgeelhaar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-expert
Source: https://github.com/felixgeelhaar/skills/tree/main/quality-expert
Command: npx skills add https://github.com/felixgeelhaar/skills --skill quality-expert-felixgeelhaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design comprehensive quality strategies that balance testing and exploration, ensuring risk-aware quality across the software lifecycle.

Core Features & Use Cases

  • Socratic evaluation and testing strategy design for product development.
  • Whole-team quality culture guidance to shift quality left and distribute ownership.
  • Four-quadrant quality planning and hermetic testing principles applied to modern CI/CD contexts.

Quick Start

Schedule a 60-minute workshop with product, engineering, and QA to align on quality goals and assign owners for exploratory testing and risk-based plans.

Frequently Asked Questions about quality-expert

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

FAQPage Schema
How do I design a risk-based testing strategy for my software team?▼

Design a risk-based testing strategy by assessing project risks and prioritizing test architectures around critical areas. This approach ensures risk-aware coverage and balances automated checking with exploratory testing across the software lifecycle.

What is the difference between testing and checking in a quality strategy?▼

Testing is an exploratory process evaluating product quality, while checking verifies specific expected outcomes using automation. A whole-team quality strategy differentiates the two to balance human exploration with repeatable verification.

How do I apply four-quadrant quality planning to modern CI/CD pipelines?▼

Apply four-quadrant quality planning by mapping tests across technology-facing and business-facing dimensions, combining automated checks with exploratory testing. This ensures comprehensive coverage within hermetic CI/CD environments.

Can I use hermetic testing principles for distributed engineering and QA teams?▼

Yes, hermetic testing principles suit distributed teams by ensuring tests run in isolated environments without external dependencies. This enables reliable execution and supports a whole-team quality culture across engineering and QA.

What is the best way to shift quality left and build a QA culture?▼

Shift quality left by distributing ownership across product, engineering, and operations through a whole-team strategy. Socratic evaluation and collaborative workshops align quality goals and establish shared responsibility.

When should I prioritize exploratory testing over automated test checks?▼

Prioritize exploratory testing when assessing complex risk areas requiring human intuition and rapid learning. Use automated checks for stable, repeatable verifications to maintain a balanced and risk-focused testing strategy.