Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

agentic-quality-engineering

Use when orchestrating QE agents, understanding PACTS principles, configuring the AQE v3 fleet, or leveraging AI agents as force multipliers for quality work.

proffesor-for-testing · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add proffesor-for-testing/agentic-qe --skill agentic-quality-engineering

About this skill


name: agentic-quality-engineering description: "Use when orchestrating QE agents, understanding PACTS principles, configuring the AQE v3 fleet, or leveraging AI agents as force multipliers for quality work." category: qe-core priority: critical tokenEstimate: 1400 agents: [qe-test-architect, qe-parallel-executor, qe-coverage-specialist, qe-quality-gate, qe-performance-tester, qe-security-scanner, qe-requirements-validator, qe-fleet-commander, qe-deployment-advisor, qe-regression-analyzer, qe-contract-validator, qe-flaky-hunter, qe-visual-tester, qe-chaos-engineer, qe-code-complexity, qe-qx-partner, qe-devils-advocate] implementation_status: optimized optimization_version: 1.0 last_optimized: 2025-12-02 dependencies: [] quick_reference_card: true tags: [pacts, agents, fleet, coordination, autonomous, structured, foundational] trust_tier: 1 validation: schema_path: schemas/output.json

Agentic Quality Engineering

<default_to_action> When implementing agentic QE or coordinating agents:

  1. SPAWN appropriate agent(s) for the task using Task tool with agent type
  2. CONFIGURE agent coordination (hierarchical/mesh/sequential)
  3. EXECUTE with PACTS principles: Proactive analysis, Autonomous operation, Collaborative feedback, Targeted risk focus, Structured governance (observability and explainability of agent behavior)
  4. VALIDATE results through quality gates before deployment
  5. LEARN from outcomes - store patterns in aqe/learning/* namespace

Quick Agent Selection:

  • Test generation needed → qe-test-architect
  • Coverage gaps → qe-coverage-specialist
  • Quality decision → qe-quality-gate
  • Security scan → qe-security-scanner
  • Performance test → qe-performance-tester
  • Full pipeline → qe-fleet-commander

Critical Success Factors:

  • Agents amplify human expertise, not replace it
  • Human-in-the-loop for critical decisions
  • Measure: bugs caught, time saved, coverage improved, and how often agent claims survive verification
  • Done means committed, tested, and CI-validated with evidence attached, not "reported as complete" </default_to_action>

Quick Reference Card

When to Use

  • Designing autonomous testing systems
  • Scaling QE with intelligent agents
  • Implementing multi-agent coordination
  • Building CI/CD quality pipelines

PACTS Principles

PrincipleAgent BehaviorHuman Role
ProactiveAnalyze pre-merge, predict riskSet guardrails
AutonomousExecute tests, fix flaky testsReview critical
CollaborativeMulti-agent coordinationProvide context
TargetedRisk-based prioritizationDefine risk areas
StructuredGovernance, observability, explainable decisions (measure confidence, not trust)Audit behavior, set policy

Core Agents

The full fleet lives in .claude/agents/v3/qe-*.md; these are the agents most core jobs start with.

CategoryAgentsPrimary Use
Core Testingqe-test-architect, qe-parallel-executor, qe-coverage-specialist, qe-quality-gateDaily testing
Performance/Securityqe-performance-tester, qe-security-scannerNon-functional
Strategicqe-requirements-validator, qe-fleet-commanderPlanning, orchestration
Advancedqe-regression-analyzer, qe-contract-validator, qe-flaky-hunterSpecialized
Visual/Chaosqe-visual-tester, qe-chaos-engineerEdge cases
Deploymentqe-deployment-advisorRelease
Analysisqe-code-complexityMaintainability
Verificationqe-devils-advocateChallenge other agents' claims

Coordination Patterns

Hierarchical: fleet-commander → [generators] → [executors] → quality-gate
Mesh: test-gen ↔ coverage ↔ quality (peer decisions)
Sequential: risk-analyzer → test-gen → executor → coverage → gate

Success Criteria

✅ Deployment frequency rises without escaped defects rising (measured against your own baseline) ✅ Coverage gaps detected in real-time ✅ Bugs caught pre-production ✅ Agent claims checked against evidence before anyone relies on them ❌ Agents acting without human oversight on critical decisions ❌ Deploying the whole fleet at once (start with 1-2)


Core Concepts

QE Evolution

StageApproachLimitation
TraditionalManual everythingHuman bottleneck
AutomationScripts + fixed scenariosNeeds orchestration
AgenticAI agents + human judgmentRequires confidence-building: evidence that agent output holds up

Core Premise: Agents amplify human expertise. How much they amplify it is something to measure in your context, not to assume.

Confidence, not trust: trust is a feeling; confidence can be explained. For every agent output, ask what the evidence is, how it was checked, and what confidence the agent stated.

Key Capabilities

1. Intelligent Test Generation

// Agent analyzes code change, generates targeted tests
const tests = await Task("Generate tests", prDiff, "qe-test-architect");
// → Happy path, edge cases, error handling tests

2. Pattern Detection - Scan logs, find anomalies, correlate errors

3. Adaptive Strategy - Adjust test focus based on risk signals

4. Root Cause Analysis - Link failures to code changes, suggest fixes

Completion Theater (the central failure mode)

Agents optimize for appearing done rather than being done, and it gets harder to spot as their output gets more plausible. Patterns to check for:

  • Work reported complete that was never committed
  • Tests that assert a status code without checking the payload, or check that variables exist instead of behavior
  • Coverage inflated by tests that touch code without exercising it
  • Validation that checks counts or thresholds instead of behavior
  • Report volume standing in for working software
  • Stubs accepted as implementations
  • Agent claims that the visible evidence contradicts

An honest, low-

Read the complete source ↗