skills.rest
slabgorb
slabgorbCOMMUNITY
Explore all skills by this author →
GitHub

sq-playtest

Coordinate cross-workspace Sideplay tests, tracking bugs and fixes via ping-pong file.

2|Updated Mar 25, 2026
Search Tags:#qa#playwright#workflows#bug-tracking#playtest#cross-workspace
One-click install
npx skills add https://github.com/slabgorb/sidequest --skill sq-playtest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sq-playtest
Source: https://github.com/slabgorb/sidequest/tree/main/.claude/skills/sq-playtest
Command: npx skills add https://github.com/slabgorb/sidequest --skill sq-playtest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SideQuest Playtest Skill coordinates end-to-end playtests across two workspaces (OQ-2 and OQ-1), enabling coordinated bug discovery, task coordination, and restart workflows via a shared ping-pong file.

Core Features & Use Cases

  • Full-stack playtest mode (UI + Playwright + UX Designer + daemon)
  • Headless playtest mode (API-only + Python driver)
  • Cross-workspace ping-pong collaboration for bug tracking and verification
  • Health-check, sync, and restart orchestration across services
  • Screenshots capture and UX evaluation workflow

Quick Start

Launch the playtest by starting the OQ-2 driver and the three services, then monitor the ping-pong file for issues.

Frequently Asked Questions about sq-playtest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate cross-workspace playtests to find bugs across multiple repos?▼

Cross-workspace playtests coordinate bug discovery and task coordination across OQ-1 and OQ-2 workspaces using a shared ping-pong file for status tracking and restart workflows. You launch the driver and services, then monitor the ping-pong file for issues.

Can I run headless API testing separately from full-stack Playwright testing?▼

Headless API testing runs separately from full-stack testing. Headless mode uses API-only checks with a Python driver, while full-stack mode combines UI testing with Playwright, a UX designer, and a daemon for interactive sessions.

What is a ping-pong file and how does it track bugs during QA workflows?▼

A ping-pong file tracks bugs during QA workflows by serving as a shared status file across two workspaces. It coordinates bug discovery, verification, and restart workflows by synchronizing issue states between OQ-1 and OQ-2 environments.

Does cross-workspace playtest orchestration handle health checks and restarts across services?▼

Cross-workspace playtest orchestration handles health checks and restarts across services. It synchronizes multi-repo states and coordinates service restarts using the shared ping-pong file to maintain testing continuity.

What do I need to set up before starting full-stack playtest mode with Playwright?▼

Full-stack playtest mode requires starting the OQ-2 driver and three services. You need Playwright for UI automation, a UX designer component, and a daemon running to capture screenshots and evaluate UX workflows.

Are there limitations when synchronizing playtests across OQ-1 and OQ-2 workspaces?▼

Synchronizing playtests across OQ-1 and OQ-2 workspaces relies entirely on the ping-pong file for coordination. Limitations include dependency on file status accuracy for health checks and restart orchestration across both services.

Related Skills

Explore More Software Engineering Skills→
mauriciodelriomauriciodelrio
3

monorepo-and-tooling

Configure pnpm and Turborepo monorepos with shared configs and cacheable builds.

Community
Advanced
WindXRanWindXRan

playtest-report

Generate standardized playtest reports from raw tester feedback.

Community
Intermediate
Blake-JohnBlake-John

webapp-testing

Automate local web app testing with Playwright and server orchestration.

Community
Intermediate
SvtooSvtoo

ralph-wiggum

Automate ATK plugin development and testing through a developer-tester ping-pong loop.

Official
Advanced