holistic-testing-pact

The holistic-testing-pact skill provides a structured framework for evolving quality engineering from a reactive, phase-based activity into a proactive, whole-team practice. It is designed for software teams, Quality Engineers (QE), and DevOps professionals who are building, maintaining, or scaling classical, AI-assisted, and Agent-based systems. By leveraging the PACT methodology, the skill helps teams move away from manual gatekeeping and toward autonomous, high-confidence delivery pipelines.

• Implements the PACT framework: Proactive (testability design and risk analysis), Autonomous (local developer execution and CI-driven quality), Collaborative (Three Amigos, pair testing, shared ownership), and Targeted (risk-based prioritization to eliminate valueless tests).

• Facilitates mapping testing activities to specific quadrants: Technology-facing (unit/integration) and Business-facing (BDD/exploratory/usability) to ensure comprehensive coverage.

• Coordinates specialized agents including qe-fleet-commander for orchestration, qe-test-generator for automated test suites, qe-quality-analyzer for metrics, and qe-requirements-validator for design-time validation.

• Enables the shift from activity-based metrics (test counts) to outcome-based metrics (bug escape rates, release confidence, and cycle time).

• Integrates with modern CI/CD pipelines to ensure feedback loops are measured in minutes rather than days, promoting faster feature deployment.

• Use this skill during architecture refinement to identify potential risks before coding begins.

• Apply the quadrant assessment to ensure your test suite balances fast feedback (support) with deep exploration (critique).

• Use the fleet orchestration capability to run parallel quality assessments, such as simultaneous security scanning, integration testing, and performance benchmarking.

• Inputs typically include user stories, technical specifications, or codebase paths; outputs consist of strategic test plans, risk-weighting reports, and coordination signals for sub-agents.

• Practical constraints: Requires team buy-in for 'whole-team quality' shifts and assumes an environment where developers are empowered to write and own their test code rather than relying solely on a centralized QA department.