qa-tc

Generate Given-When-Then test cases from tech specs and user stories.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/gridi-ai/gridi-skills --skill qa-tc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-tc
Source: https://github.com/gridi-ai/gridi-skills/tree/main/skills/qa-tc
Command: npx skills add https://github.com/gridi-ai/gridi-skills --skill qa-tc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the creation of comprehensive test cases from tech specs and user stories, reducing manual drafting time and improving QA repeatability.

Core Features & Use Cases

  • Analyze tech specs and user stories to extract user scenarios, acceptance criteria, and API endpoints.
  • Generate test cases in Given-When-Then format, including positive, negative, boundary, and security-oriented scenarios.
  • Provide ready-to-use documentation templates and test-case outputs for integration into QA pipelines and reporting.

Quick Start

Provide a tech spec and a user story document to generate test cases.

Frequently Asked Questions about qa-tc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate test cases from user stories and tech specs?

You can generate test cases from user stories by analyzing the documents to extract scenarios and acceptance criteria, automatically producing functional, negative, and boundary test cases in Given-When-Then format.

Can I automate BDD test case creation for API and UI flows?

Yes, automating BDD test case creation for API and UI flows involves parsing technical specifications to output Given-When-Then formatted scenarios, including positive, negative, and security-oriented cases with test-data templates.

What is the best way to write boundary and negative test scenarios from specifications?

Writing boundary and negative test scenarios from specifications requires analyzing user stories to extract edge cases, enforcing Given-When-Then formatting, and outputting ready-to-run documentation with test-data templates.

Does this test case generation approach work without external dependencies?

Yes, this test case generation approach works without external dependencies, directly analyzing your provided tech specs and user stories to output ready-to-run test cases and documentation templates.

How do I create ready-to-run test data templates for QA pipelines?

Creating ready-to-run test data templates for QA pipelines involves extracting API endpoints and acceptance criteria from specs, generating structured outputs that integrate directly into your reporting and automation workflows.