AI Agent Hub
Back to skills
QA Team AI Workbench icon

QA Team AI Workbench

AI Agent Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Follow https://skillhub.cn/install/skillhub.md and install @user_8e8e447f/qa-team-skills.

About this skill

A command-driven workflow for QA teams

QA work is often fragmented across PRD review, test design, agent testing, bug analysis, reporting, and team management. Instead of treating this as one generic generate-test-cases prompt, this skill models the workflow as explicit commands: /qa is the unified entry point for intent parsing, routing, memory management, and planning; subcommands cover /qa-prd, /qa-case, /qa-agent, /qa-bug, /qa-report, /qa-team, and /qa-explore.

Progressive loading with validation

The skill avoids injecting every prompt into context at once. It first reads the entry point and intent rules, then loads the relevant references/ prompt file. For example: review this PRD → /qa routes to PRD → load prd/prompt.md → run validation-rules.md before output. Important constraints include verb-first, independently verifiable test steps; missing data marked as {{待确认}} or -; report statistics must come from user-provided data; high-severity PRD issues, low/medium-confidence root-cause findings, memory writes, and version cleanup all require confirmation.

Boundaries

It is best for structured QA tasks with clear inputs: PRD review, test case design, AI/Agent testing, bug root-cause analysis, report drafting, and team dashboards. It does not invent compliance standards, accounts, amounts, paths, or test data, and it will not continue generation when required inputs are missing. If intent is ambiguous, it should present candidate commands for confirmation.

Use Cases

  • Review a new PRD against fixed risk dimensions and generate open questions.
  • Plan AI Agent tests around hallucination, prompt injection, and tool permissions.
  • Analyze a reported bug, identify root cause, and record confidence for review.
  • Prepare release readiness by aggregating progress, risks, trends, and outputs.

Best For

  • QA engineers doing PRD review: break requirements into risks and open questions.
  • Engineers testing AI agents: plan tests for hallucination, injection, permissions.
  • QA managers preparing releases: aggregate progress, risks, trends, and outputs.
  • Test or dev engineers reviewing bugs: trace root cause and mark confidence.