skills.rest
sub-22
sub-22COMMUNITY
Explore all skills by this author →
GitHub

QA Agent

Generate and execute test cases from specs with requirement traceability.

1|Updated May 14, 2026
Search Tags:#qa#reporting#test-generation#traceability#test-execution#spec-reading
One-click install
npx skills add https://github.com/sub-22/subkontrol --skill qa-agent-sub-22
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: QA Agent
Source: https://github.com/sub-22/subkontrol/tree/main/skills/qa
Command: npx skills add https://github.com/sub-22/subkontrol --skill qa-agent-sub-22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams spend significant effort reading specs, deriving exhaustive test cases, executing tests, and reporting results. This skill automates end-to-end QA workflows, ensuring consistency and traceability from requirements to validation.

Core Features & Use Cases

  • Spec-loading & interpretation: reads specs to extract requirements and acceptance criteria.
  • Test-case generation: creates comprehensive test cases covering happy paths, edge cases, and negative scenarios.
  • Test execution coordination: orchestrates test runs and collects results.
  • Reporting & traceability: reports outcomes with mappings back to requirements and tickets.
  • Use Case: Given a feature ticket, generate 50-100 test cases from specs, run them, and produce a summary report.

Quick Start

Run a full QA cycle by loading specs/<ticket-id>.md, generating test cases, executing them, and returning a summary report.

Frequently Asked Questions about QA Agent

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

FAQPage Schema
How do I automate test generation from feature specs and tickets?▼

Automating test generation from feature specs involves loading requirement files like specs/<ticket-id>.md, extracting acceptance criteria, and mapping them to comprehensive test cases covering happy paths, edge cases, and negative scenarios.

How does traceability work when mapping test cases to requirements?▼

Traceability in test execution works by linking generated test cases directly back to original spec requirements and feature tickets, ensuring structured results summarize outcomes with clear mappings for validation coverage.

Can I use this QA workflow for large scale test case generation?▼

Yes, you can use this QA workflow for large scale test case generation, typically producing 50 to 100 test cases from a single feature ticket spec, executing them, and returning a comprehensive summary report.

What happens if a spec file is not available for the feature ticket?▼

If a spec file is not available for the feature ticket, the QA workflow enforces gating by halting test generation and execution, ensuring tests are only derived from validated requirement documents.

What is the best way to coordinate test execution and reporting end-to-end?▼

The best way to coordinate test execution end-to-end is to orchestrate test runs immediately after generation, collect execution results, and produce a structured summary report mapping outcomes back to initial requirements.

Related Skills

Explore More Software Engineering Skills→
ilandahanilandahan
9

aid-qa-ship

Validate implementations against acceptance criteria and certify software releases.

Community
Basic
satanyakivsatanyakiv
11

kover-analyze

Analyze Kover XML coverage reports to prioritize Kotlin test improvements.

Community
Advanced
ongspxmongspxm
1

meagent-update-blog

Trigger and monitor GitLab CI/CD pipelines for blog content rendering.

Community
Intermediate
xlelibertyxleliberty

testrail

Synchronize Playwright test results and case definitions with TestRail.

Community
Advanced