Convert product requirements into traceable QA-ready Markdown test cases.
npx skills add https://github.com/tense-i/stock-market-simulator --skill test-cases-tense-i
Please help me install this Agent Skill. Skill: test-cases Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/test-cases Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill test-cases-tense-i
This skill translates product requirements or PRD documents into structured, test-case coverage, ensuring every requirement maps to tests and covering functional, edge-case, and error scenarios.
Run a test-case generation on your PRD or requirements document to produce a full suite of test cases.
High-intent search queries and answers about installing and using this skill.
Generating test cases from product requirements involves parsing PRDs or user stories to produce structured, traceable test suites. This skill converts written requirements into QA-ready Markdown files covering functional, edge-case, error-handling, and state-transition scenarios with full requirement traceability.
Requirements traceability in test case generation ensures every test case maps directly to a specific product requirement. This skill enforces requirement-driven coverage, guaranteeing that each functional, error-handling, or state-transition scenario aligns with a documented PRD or user story.
Yes, you can create state-transition test scenarios from a PRD. The skill processes written requirements to cover state-transition scenarios alongside functional and edge-case tests, producing Markdown documentation that captures system behavior changes and error-handling flows.
Yes, this test case generation skill handles edge-case and error-handling coverage. It analyzes requirements to identify boundary conditions and failure paths, producing comprehensive test documentation that includes error-handling and state-transition scenarios in a QA-ready Markdown format.
The best way to document QA-ready test cases from user stories is to convert them into structured Markdown files with traceability. This skill translates user stories into comprehensive test suites covering functional, edge-case, and state-transition scenarios aligned with QA workflows.
A limitation when converting requirements into test documentation is the dependency on well-written input. The skill processes PRDs, user stories, or written requirements, meaning incomplete or ambiguous source documents will directly impact the coverage and accuracy of the generated state-transition and error-handling test cases.
GACLoveGenerate structured PRDs with problem statements, user stories, and success metrics.
haomingzEstablish Google-standard QA workflows with test strategies, defect tracking, and reports.
ajianazOrchestrate QA testing workflows from strategy design to metrics reporting.
wukangcheng2944Transform PRDs and user requirements into structured Markdown test cases.
