This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.
93
92%
Does it follow best practices?
Impact
94%
1.51xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
QA project initialization
Init script used
93%
100%
tests/docs/ dir exists
0%
100%
tests/e2e/ dir exists
0%
0%
tests/fixtures/ dir exists
0%
0%
TEST-EXECUTION-TRACKING.csv
41%
100%
BUG-TRACKING-TEMPLATE.csv
41%
100%
BASELINE-METRICS.md
20%
100%
WEEKLY-PROGRESS-REPORT.md
20%
100%
Master QA Prompt file
30%
100%
README file
42%
100%
AAA pattern test cases with security coverage
TC-[CAT]-[NUM] format
100%
100%
Prerequisites section (Arrange)
100%
100%
Test Steps section (Act)
100%
100%
Expected Result section (Assert)
100%
100%
Priority assigned
25%
100%
Potential bugs section
0%
100%
Security test cases present
70%
100%
OWASP injection coverage
0%
100%
OWASP auth failure coverage
100%
100%
CSV is tracking-only
100%
100%
Pass/Fail criteria
50%
100%
Bug filing and quality metrics calculation
Sequential bug IDs
100%
100%
Three bugs filed
100%
100%
SQL injection is P0
70%
100%
P1 severity for TC-INV-005
62%
100%
Steps to Reproduce numbered
100%
100%
Environment field populated
80%
100%
Actual result documented
100%
100%
Bug IDs in tracking CSV
100%
100%
calculate_metrics.py used
100%
100%
All 6 quality gates listed
40%
100%
P0 bug handling noted
78%
100%
4f0eae8
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.