skills.rest
Pact-Community-Organization
Pact-Community-OrganizationOFFICIAL
Explore all skills by this author →
Website𝕏@PactCommOrgGitHub

test-case-generation

Generate structured test cases from ADRs, PROC, ACs, user stories with Source, Precondition, Action, Expected fields.

1|1|Updated Jun 9, 2026
Search Tags:#qa#specifications#adr#traceability#generate#acceptance-criteria#test-cases
One-click install
npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill test-case-generation-pact-community-organization
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-case-generation
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/test-case-generation
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill test-case-generation-pact-community-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates test cases directly from specifications, acceptance criteria, and ADRs to ensure implementations meet intended behavior without relying on code introspection.

Core Features & Use Cases

  • Extracts testable assertions from ADRs, PROC, ACs, and user stories.
  • Maps each assertion to a structured test-case template with Source, Precondition, Action, and Expected fields.
  • Flags ambiguous specifications with [UNCERTAIN] markers for clarification and traceability.

Quick Start

Provide the specification source (ADR/PROC/AC/user story) and have the skill generate test cases.

Frequently Asked Questions about test-case-generation

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

FAQPage Schema
How do I generate test cases from acceptance criteria and user stories?▼

Generating test cases from ADRs and acceptance criteria involves extracting testable assertions and mapping each to a template with Source, Precondition, Action, and Expected fields. It ensures implementations meet intended behavior without relying on code introspection.

What is the best way to ensure test coverage from ADRs and specifications?▼

Ensuring test coverage from specifications means extracting testable assertions from ADRs and user stories, then mapping them to structured test cases. Ambiguous requirements are flagged with [UNCERTAIN] markers to drive clarification and maintain traceability.

Can I use ADRs and user stories to generate test cases without looking at the code?▼

Yes, you can generate test cases directly from ADRs and user stories without code introspection. The skill derives test cases solely from specifications, ensuring the implementation meets intended behavior defined in the documentation.

How does the test case generation process handle ambiguous specifications?▼

The test case generation process handles ambiguous specifications by flagging them with [UNCERTAIN] markers. This highlights unclear areas in the ADR or acceptance criteria, ensuring traceability and prompting necessary clarifications before testing.

Related Skills

Explore More Software Engineering Skills→
thrawn01thrawn01
11

stories-create

Extract user workflows from PRDs into testable stories with traceability.

Community
Advanced
TravisLeeeeeeTravisLeeeeee
110

QA Tester

Design QA test plans and executable test cases for features and APIs.

Community
Advanced
imMamdouhaboammarimMamdouhaboammar

qa-test-planner

Generate structured QA documentation including test plans, test cases, and bug reports.

Community
Intermediate
eykdeykd

quality-review

Review GitHub pull requests for correctness, style, test coverage, and standards.

Community
Advanced