Quality Engineering Quality Assurance Agent Skill
Write or review manual Zephyr test cases with 1-condition-per-TC granularity, Module_Action on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use for test-case authoring and review; defer Jira traceability, linking, and pushing cases to Zephyr.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill quality-engineering-quality-assuranceWhat comes with it
2 864 bytes besides the instructionThe instruction itself
9 sections, as written by the authorQuality Assurance Standards
Priority: P1 (HIGH)
1. Test Case Granularity
- 1 Test Case = 1 Condition on 1 Screen.
- Split Screens: "Order Details" & "Item Details" separate.
- Split Conditions: "Config " & "Config B" separate.
- No "OR" Logic: Each TC must test single, distinct path.
2. Naming Convention
- Pattern:
Platform_Module_Action on Screen when Condition(e.g.,Web_Order_Verify...orMobile_Order_Verify...) - Rule: Only include
Web_orMobile_prefix if requirement exclusive to one platform. Omit prefix if it supports Both. - Example:
Order_Verify payment term on Item Details when Toggle is OFF(Supports Both)
3. Priority Levels
Use priority rationale to justify each classification:
- High: Critical path, blocker bug.
- Normal: Standard validation, edge case.
- Low: Cosmetic, minor improvement.
4. References
- Detailed Examples
Anti-Patterns
- No Broad TCs:
"Verify order flow works"— too broad; every TC must cover exactly 1 condition on 1 screen - No Shared TCs (Divergent): Testing Web and Mobile behavior in single TC when behavior diverges — split into separate TCs per platform
- No Incomplete Naming:
Order_Verify page— name must follow full pattern:Module_Action on Screen when Condition - No Priority Inflation: Marking cosmetic spacing bug as High priority — reserve High for critical path blockers only
Review wording
- Call out naming violations explicitly when a test case breaks the naming convention, then split it into separate TCs with one condition on one screen.
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- naming violations
- 1 Test Case = 1 Condition
- High: Critical path
- Low: Cosmetic
- Module_Action on Screen when Condition
- No "OR" Logic
- Split into separate TCs
- priority rationale
Other skills for the same job
different authors, same section of the catalogue
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
Prepares and structurally reviews readiness evidence for ISO management-system and laboratory-competence standards - ISO 13485 medical device QMS, ISO 14971 device risk management, ISO/IEC 17025 testing and calibration laboratories, and ISO 15189 medical laboratories. Use when organizing declared scope, controlled documents, risk-management files, scope of accreditation, traceability, CAPA, external-provider controls, or bounded local evidence manifests, and when separating ISO certification from laboratory accreditation, FDA QMSR inspection, CLIA certification, MDSAP, and EU MDR/IVDR evidence boundaries. Not for legal applicability, compliance, certification, or accreditation decisions; contains no clause text.
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers closed-form power for t-tests, ANOVA, proportions, correlations, chi-square, and regression, plus simulation-based (Monte Carlo) power for designs with no formula — logistic/Poisson regression, mixed models, cluster-randomized trials, survival, and interactions. Use this skill even when the request only mentions an effect size, alpha, or "80% power" without saying "power analysis" explicitly. For laying out the study (randomization, blocking, factorial/DOE, crossover, sequential designs) use experimental-design; for analyzing data already collected and reporting it use statistical-analysis.
> reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge. Handles features, bugs, refactors, greenfield projects, planning breakdowns, and migrations. Triggers on "absolute work", "build this end-to-end", "plan and build", "break this into tasks", "grill me on this plan", "pick up this ticket", "run this migration".
Universal QA checklist for generated scientific plots: overlapping labels, clipped text, missing axes/legends, overcrowded data, and cross-journal resolution/format guidance.
Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation.
Run PinchBench benchmarks to evaluate OpenClaw agent performance across real-world tasks. Use when testing model capabilities, comparing models, submitting benchmark results to the leaderboard, or checking how well your OpenClaw setup handles calendar, email, research, coding, and multi-step workflows.
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
How to use it
Take hoangnguyen0403/quality-engineering-quality-assurance from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.