quality-gates

Parallel quality assurance workflow orchestration runs validator and tester agents concurrently, eliminating sequential code review bottlenecks and reducing feedback loops by up to 40%. This ensures code quality and UX standards are met before deployment.

To run parallel validation and E2E testing, invoke the quality gates skill in your current worktree. It executes validator and tester agents simultaneously to verify TypeScript types, unit tests, and Playwright E2E tests before finalizing your pull request.

Yes, you need Playwright and standard TypeScript/Node.js testing tools to enforce automated code quality checks. The workflow requires these integrations to execute E2E testing and performance benchmarking within its mandatory decision matrix.

If validation or testing fails during parallel code quality checks, a strict decision matrix prevents code from proceeding to the scribe. Both quality gates must be satisfied before the workflow allows progression to the next stage.

The best way to automate performance benchmarking alongside unit tests is using a parallel quality assurance workflow. This approach executes validator and tester agents simultaneously, enforcing a mandatory pass/fail routing system before deployment.

You should not use parallel processing for automated code quality checks if your project lacks standard TypeScript/Node.js testing tools or Playwright integration. The workflow depends on these specific environments to orchestrate its validator and tester agents concurrently.