qa-engineer

Create repeatable QA plans and test case templates for software releases.

12|4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/TurnaboutHero/oh-my-antigravity --skill qa-engineer-turnabouthero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/TurnaboutHero/oh-my-antigravity/tree/main/skills/qa-engineer
Command: npx skills add https://github.com/TurnaboutHero/oh-my-antigravity --skill qa-engineer-turnabouthero

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams spend excessive time on manual testing and documenting test plans, leading to bottlenecks and inconsistent quality outcomes.

Core Features & Use Cases

  • Manual Testing: Create repeatable, structured test cases that validate software behavior across features.
  • Test Planning: Develop comprehensive test plans, track execution, and log results for releases.
  • Use Case: When releasing a new feature, generate a complete QA plan with test cases, expected results, and defect logging templates.

Quick Start

Use the qa-engineer to generate a comprehensive test plan for the signup flow.

Frequently Asked Questions about qa-engineer

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

FAQPage Schema
How do I create a test plan for manual testing?

A test plan for manual testing is a structured document that outlines test cases, expected results, and execution steps for validating software features. Use this Skill to generate comprehensive test plans with repeatable checklists and templates that ensure consistent QA coverage across your release cycle.

What's the best way to organize test cases and bug reports?

Organize test cases and bug reports using standardized templates that capture test objectives, steps, expected outcomes, and defect details. This Skill enforces structured formats for both test cases and bug reports, reducing inconsistency and improving traceability across sprints.

How do I track manual testing execution and results?

Manual testing execution tracking records which test cases have been run, their results, and any defects discovered. This Skill provides templates and checklists to log test execution systematically, enabling you to monitor progress and identify gaps before release.

Can I use exploratory testing sessions with structured documentation?

Yes. Exploratory testing sessions can be documented using structured templates that capture findings and defects in a consistent format. This Skill supports both planned test cases and exploratory testing sessions with enforced documentation standards.

What should a QA checklist include for feature releases?

A QA checklist for feature releases should include test cases covering functionality, edge cases, and acceptance criteria, plus templates for logging results and defects. This Skill generates release-ready checklists that ensure no testing areas are missed.

How does structured testing reduce manual QA bottlenecks?

Structured testing reduces bottlenecks by replacing ad-hoc test execution with repeatable test plans and checklists, eliminating redundant documentation effort. This Skill applies templated formats for test cases and bug reports, allowing QA teams to execute faster and more consistently.