qa

Launch a real browser to execute user interactions and verify web flows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mferris77/SpringBoard --skill qa-mferris77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/mferris77/SpringBoard/tree/main/vscode-citadel-harness/skills/qa
Command: npx skills add https://github.com/mferris77/SpringBoard --skill qa-mferris77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies user-facing web application flows by exercising the app exactly like a user would, reducing regression risk from untested interactions and catching visual or behavioral regressions before release.

Core Features & Use Cases

  • End-to-end Interaction Testing: Launches a real browser to navigate pages, click buttons, fill forms, and assert outcomes for user flows such as onboarding, CRUD operations, and authentication.
  • Evidence Capture: Takes screenshots for every tested flow and writes structured QA reports to support reproducibility and handoff.
  • Dependency Awareness & Fallbacks: Detects whether Playwright is available, offers an installation path, and falls back to visual-only verification if the user declines installation.
  • Campaign & CI Integration: Can run as a phase end condition in campaign files or as an explicit, user-invoked QA step for feature verification.

Quick Start

Run the qa skill to perform browser-based user-flow verification with Playwright, capture screenshots, and produce a QA report.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate e2e-testing for user flows like form submissions and authentication?

End-to-end browser testing is automated by launching a real browser to execute interactions like navigation and form submissions, then asserting outcomes to catch behavioral regressions before release.

Do I need Playwright installed to run browser-testing and capture screenshots?

Playwright is required for scripted interaction tests, but the system detects its availability and falls back to screenshot-only visual verification if you decline the installation path.

Can I use automated QA verification for local development servers?

Automated QA verification supports local development servers by navigating pages and testing CRUD operations, provided the server is reachable for browser interaction during the test phase.

What's the best way to capture evidence for user flow test automation?

Evidence capture for test automation is handled by taking screenshots for every tested flow and writing structured QA reports that support reproducibility and handoff for campaign phase verification.

Why does browser-based e2e-testing fall back to screenshot-only verification?

Screenshot-only verification is a fallback used when Playwright is unavailable for scripted interaction tests, ensuring visual regressions are still checked without full interaction testing dependencies.

How do I integrate test-automation as a phase end condition in CI workflows?

Test-automation integrates into CI workflows by running as a phase end condition in campaign files or as an explicit user-invoked QA step to verify feature readiness before release.