QA Orchestrator

Run the project's acceptance gate and existing required checks. Use its own tooling and the approved verification scope.

Discover before running

Before picking commands: find the project's runner (Makefile, Taskfile, package.json scripts -- see [[z-go-makefile]], [[z-go-taskfile]]), the test frameworks actually wired in (Go testing + testcontainers-go, vitest, playwright, pytest), and whether the project already has its own QA-cycle skill or command (a project-local /qa-run or <project>-regression skill). If one exists, use it -- most projects run tests directly through go test/vitest/pytest wired into CI with no dedicated QA layer at all; only build the phased flow yourself when nothing project-local covers it.

Phases

Run the requested phases in order. Stop between phases after the first failed phase unless the caller requests continuation. Within a phase, collect the intended failure census without fail-fast; see [[z-qa-debugger]].

Phase 1: Changed acceptance and critical smoke

• Record the selected scenarios and their public product boundaries before execution.
• Run changed acceptance scenarios and the project's required critical smoke journeys.
• Use browser, running-service, or CLI checks according to the product. Apply [[z-bdd]] for explicit assertions and evidence.
• Run build or setup prerequisites as needed. Preserve required static checks in their established order.