qa-lead

Plan and validate E2E, API, and UI tests with generated reports.

8|3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ydnikolaev/antigravity-factory --skill qa-lead
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-lead
Source: https://github.com/ydnikolaev/antigravity-factory/tree/main/src/skills/qa-lead
Command: npx skills add https://github.com/ydnikolaev/antigravity-factory --skill qa-lead

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a Gatekeeper for quality, coordinating E2E, API, and UI testing to prevent releases with defects.

Core Features & Use Cases

  • Establishes test strategy across backend and frontend implementations.
  • Generates and tracks test-cases, test-reports, and bug reports.
  • Acts as a gatekeeper to ensure QA coverage before handoff and release.

Quick Start

Run the qa-lead workflow after both backend and frontend implementations reach a stable state, then review generated test artifacts.

Frequently Asked Questions about qa-lead

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

FAQPage Schema
How do I automate end-to-end test strategy across API and UI layers?

End-to-end test strategy is orchestrated by coordinating with backend and frontend implementations to generate test cases, assess implementation readiness, and produce test reports across E2E, API, and UI layers.

When do I need to generate test cases and bug reports for release readiness?

You need to generate test cases and bug reports for release readiness when backend and frontend implementations reach a stable state, acting as a quality gatekeeper to prevent defect releases.

Can I use this QA workflow to enforce traceability and artifact creation in project docs?

Yes, you can use this QA workflow to enforce artifact creation and traceability by managing test cases, test reports, and bug reports directly within your project documentation.

What is the best way to assess implementation readiness before handoff?

The best way to assess implementation readiness before handoff is to run a QA workflow that validates E2E, API, and UI tests, ensuring complete coverage and generating required test artifacts.

Does this end-to-end quality assurance workflow coordinate with specific backend and frontend frameworks?

This end-to-end quality assurance workflow coordinates directly with backend-go-expert and frontend-nuxt to establish test strategy, generate test cases, and assess implementation readiness across the stack.