qa-team

Coordinate parallel QA testing across specialist roles for web, Electron, iOS, and macOS apps.

1|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/laststance/skills --skill qa-team-laststance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-team
Source: https://github.com/laststance/skills/tree/main/skills/qa-team
Command: npx skills add https://github.com/laststance/skills --skill qa-team-laststance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Comprehensive QA for applications requires coordinating multiple specialist perspectives to ensure quality across user flows, platforms, and edge cases.

Core Features & Use Cases

  • Team composition: qa-lead, visual-tester, functional-tester, hig-tester, edge-case-tester, ux-tester, with a defined activation flow and output artifacts.
  • Activation & orchestration: parallel task spawning, platform detection, and cross-perspective reports with aggregated scoring.
  • Output artifacts: structured reports, screenshots, and a centralized QA documentation directory (claudedocs/qa/).

Quick Start

Assign the qa-team to the project and initiate the multi-perspective QA workflow.

Frequently Asked Questions about qa-team

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

FAQPage Schema
How do I coordinate QA testing across multiple specialist perspectives?

Multi-perspective QA coordination uses a defined activation flow to spawn parallel verification tasks across roles like visual, functional, and edge-case testers, aggregating their findings into structured reports. This detects defects early by evaluating user flows simultaneously.

Can I run automated QA workflows on both web and iOS applications?

Automated QA workflows support web, electron, iOS, and macOS applications. The orchestration process detects the target platform automatically and applies the relevant testing perspectives to collect evidence and generate centralized QA documentation.

What's the best way to aggregate evidence and generate structured QA reports?

Aggregating QA reports requires collecting screenshots and outputs from parallel testing tasks into a centralized directory. The workflow scores results against defined rubrics and compiles them into a final structured report for comprehensive quality tracking.

Does comprehensive QA orchestration work for edge-case and UX testing scenarios?

QA orchestration explicitly includes edge-case and UX testing perspectives. Activation assigns dedicated testers to these scenarios, running them in parallel with functional checks to ensure broad coverage and early defect detection.

How do I start a multi-perspective QA workflow for my project?

Starting the workflow requires assigning the QA orchestration to your project and initiating the activation flow. It spawns parallel tasks for each specialist perspective, creating artifact directories for evidence collection and final report generation.