| name | parallel-qa-orchestra |
| description | Replaces the serial playtester → gap-checker chain with 4 concurrent QA workers: static analysis (no browser), golden-path scenario runner, dynamic fuzzer, and physics debug validator. Merges all results into a single failure list for the refiner. Cuts QA time from ~2 min to ~30s. |
Parallel QA Orchestra — Concurrent Validation
Orchestrates 4 independent QA checks that run simultaneously, each on its own dev-server port. The refiner gets a single merged failure report with every issue in one pass, cutting the number of refine-iterate cycles needed.
When to use
Replace the sequential playtester → gap-checker calls in the main pipeline with a single call to this skill. Use after codesmith and the manifest-auditor + mobile-compat-checker linting passes.
The 4 workers
| Worker | Browser? | What it catches |
|---|
| static | No | BFS reachability, border holes, jump-arc gaps, spawn collision |
| golden-path | Yes (port A) | Boot, walk, jump, attack scenarios; win-condition reachability |
| fuzzer | Yes (port B) | Stuck state, spawn-trap, no-progress, out-of-bounds, NaN state |
| physics-debug | Yes (port C) | Hitbox misalignment, body offset bugs |
All 4 run concurrently. Total wall-clock time ≈ max(individual times) ≈ 30–45s.
Output contract
{
"ts": "<ISO>",
"ok"
...
...
...
