qa-team

Generate agentic outside-in tests from YAML scenarios for CLI, TUI, Web, and Electron apps.

8|4|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/rysweet/amplihack-rs --skill qa-team-rysweet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-team
Source: https://github.com/rysweet/amplihack-rs/tree/main/amplifier-bundle/skills/qa-team
Command: npx skills add https://github.com/rysweet/amplihack-rs --skill qa-team-rysweet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External-facing validation is hard when you must avoid internal knowledge; QA Team enables outside-in testing by letting you author declarative YAML scenarios that drive agentic validation, parity checks, and shadow-mode comparisons across multiple implementations.

Core Features & Use Cases

  • Declarative YAML-based test scenarios that describe external behavior for CLI, TUI, Web, and Electron apps.
  • Parity and shadow-mode workflows to compare legacy vs replacement or rollout divergences without blocking execution.
  • Cross-environment execution with observable tmux sessions, SSH targets, and multi-agent orchestration.
  • Evidence collection and reporting (screenshots, logs, traces) for auditability and debugging.
  • Agent-driven validation that can surface insights beyond exact text matches and adapt to dynamic outputs.

Quick Start

Create a YAML scenario that captures a user-facing workflow and run it with the QA Team test harness to execute automated behavior-driven validation.

Frequently Asked Questions about qa-team

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

FAQPage Schema
What is outside-in testing and how does it validate application behavior?

Outside-in testing verifies application behavior from an external user's perspective without relying on internal implementation details. It uses agentic validation to drive cross-platform scenarios, comparing outputs dynamically across CLI, TUI, Web, and Electron environments.

How do I write test scenarios for cross-platform parity checks?

You write declarative YAML-based test scenarios to define cross-platform parity checks. These scenarios specify steps, prerequisites, and evidence collection, which agents execute across different environments to compare behavior and log rollout divergences.

Does this testing framework support shadow-mode comparisons for legacy system rollouts?

Yes, the framework supports shadow-mode workflows to compare legacy versus replacement implementations. It performs side-by-side comparisons and logs rollout divergences without blocking execution, ensuring observable behavior parity during system migrations.

Can I use agentic validation for testing dynamic CLI and TUI outputs?

Yes, agentic validation can test dynamic CLI and TUI outputs. Agents surface insights beyond exact text matches by adapting to dynamic outputs, validating behavior within observable tmux sessions and across SSH targets.

How does evidence collection work for behavior validation audits?

Evidence collection captures screenshots, logs, and traces during scenario execution for auditability and debugging. Agents gather this evidence automatically as they validate application behavior across the specified cross-platform environments.