phatnguyen975

scenario-test-design

Apply this skill whenever a user needs to design test scenarios based on real-world business workflows before writing test data or test scripts. Triggers on: "design test scenarios", "scenario testing", "create test scenarios", "scenario-based testing", "test scenario design", "identify test scenarios", "write test cases from requirements", or any request to analyze requirements, BRs, FRs, or User Stories and produce scenario flows. This skill covers TEST DESIGN (analysis + scenario flow), NOT automation code or test scripts. Invoke even if the user only pastes requirements and says "help me test this".

functional-test-design

Apply this skill whenever you need to design test cases for functional testing of any feature, requirement, or system behavior. This is the parent skill that routes to the correct black-box or experience-based test design technique based on the nature of the requirement. Triggers include: "design test cases", "write test cases", "how do I test this", "test this feature", "test this requirement", "test this API", "test this flow", "test this business rule", or any request to systematically design a test suite for a functional requirement — regardless of the specific technique needed. If you know which sub-skill to use, invoke that sub-skill directly instead.

decision-table-testing

Apply this skill whenever you need to design test cases using Decision Table Testing techniques. Use when given requirements involving multiple conditions (inputs/states) that combine to produce different outcomes (actions/results) — especially when business rules contain "if-then-else", "and/or" logic, overlapping conditions, or multi-variable combinations. Triggers include: "design test cases", "write test cases for business rules", "test combinations", "decision table", "condition coverage", or any requirement with 2+ interdependent conditions controlling system behavior (discount rules, access control, eligibility logic, pricing engines, validation rules with multiple flags).

domain-testing

Apply this skill whenever you need to design test cases using Domain Testing techniques (Equivalence Partitioning and Boundary Value Analysis). Use when given any input/output specification, business rule, field constraint, API parameter, or functional requirement that involves ranges, sets, formats, or conditions. Triggers include: "design test cases", "write test cases", "identify test data", "EP", "BVA", "equivalence class", "boundary value", "partition", or any request to test a field/function with defined input constraints.

Web & Frontend Listed

error-guessing

Apply this skill whenever you need to design supplementary test cases using Error Guessing — an experience-based test design technique. Use after applying black-box techniques (Domain Testing, Decision Table, State Transition, Use Case Testing) to identify additional high-value test cases targeting defect-prone areas that systematic techniques may miss. Triggers include: "error guessing", "what else should we test", "edge cases", "what could go wrong", "attack the system", "fault attack", "experience-based testing", or any request to supplement an existing test suite with additional risk-based cases. Also use when the tester has domain knowledge, historical defect data, or heuristic intuition about where defects are likely to hide.

state-transition-testing

Apply this skill whenever you need to design test cases using State Transition Testing. Use when given requirements describing a system whose behavior depends on its current state AND its history of events — not just the current input alone. Triggers include: "design test cases", "test state machine", "test workflow", "test lifecycle", "state transition", "FSM", or any requirement describing: user authentication flows, account lifecycles, order/transaction workflows, session management, multi-step wizards, embedded system controllers, or any feature where the same event produces different outcomes depending on what happened previously.

use-case-testing

Apply this skill whenever you need to design test cases using Use Case Testing — a black-box test design technique that derives test cases from use case specifications. Use when given a use case specification (or equivalent: user story with acceptance criteria, feature with defined actor-system interactions), and the goal is to ensure the system correctly handles all flows: the main success scenario, alternate flows, and exception flows. Triggers include: "design test cases from use case", "test this user story", "test this feature end-to-end", "use case testing", "UC", "actor interaction", "flow testing", or any request to test a feature where behavior is described as a sequence of actor-system interactions leading to a defined goal.

AI & Automation Listed

ai-audit-log

Audit and log AI interactions into a structured monthly log file. Trigger this skill whenever the user invokes /ai-audit-log or /ai-audit-log --last=N (N: 1–5). The skill reads conversation context to extract prompts and outputs, then asks the user to evaluate each interaction via a structured form. Use this skill to track AI usage quality, model performance, and revision patterns over time.