About this skill

Problem It Solves

When a PRD, requirement note, or API spec already exists, testcase-generator turns functional modules, interface constraints, and edge conditions into structured test cases. It is not a test runner; it produces a reviewable and savable test case draft for engineers.

How It Works

Input understanding: detects business requirements, API definitions, or performance metrics, then extracts endpoints, methods, parameters, error codes, required fields, and state transitions.
Default design strategy: generates cases using happy path, negative, boundary, equivalence, state, and scenario approaches, and labels type and priority.
Standards on demand: loads the matching references standard for API, performance, functional, or automation candidates; follows a Word/Excel template in assets when one is specified.

Boundaries and Notes

The skill relies on plain-text documentation; screenshots should be converted to text first. It does not invent missing business rules and does not call test tools automatically. Output is shown in chat by default, and files are written only when explicitly requested.

Screenshots

Use Cases

After receiving a payment PRD, break order, refund, and permission rules into reviewable positive and negative cases.
While reviewing an API spec, organize endpoint, parameter, and error-code cases with priorities.
When performance targets are in the requirements, add timeout, concurrency, and SLA performance cases.
When the team provides an Excel template, map document analysis into the required columns and save the file.