test-spec

Generates Gherkin BDD test specifications from structured use case artifacts using Clark's transformation algorithm.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/geekatron/jerry-claude-plugin --skill test-spec-geekatron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-spec
Source: https://github.com/geekatron/jerry-claude-plugin/tree/main/skills/test-spec
Command: npx skills add https://github.com/geekatron/jerry-claude-plugin --skill test-spec-geekatron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing acceptance tests from use case specifications is manual and error-prone, often leaving error paths untested. This Skill deterministically transforms structured use case artifacts (basic flow, alternative flows, extensions) into Gherkin Feature files with Given-When-Then scenarios, then verifies coverage completeness against the source use case. ## Core Features & Use Cases - Deterministic UC-to-Gherkin Transformation: Maps every use case flow element to exactly one scenario using Clark's (2018) UC2.0-to-Gherkin algorithm, with full traceability via Source annotations and a Traceability Matrix. - Coverage Analysis: Computes quantitative C1 Coverage metrics (mapped flows / total mappable flows) against the source use case, applies a 7 Cs quality framework, and produces prioritized gap remediation recommendations (P0-P3). - Slice-Scoped Generation: Generates Feature files scoped to specific implementation slices, with aggregate cross-slice coverage analysis and cross-slice gap detection. - Use Case: After authoring UC-AUTH-001 (Validate Credentials) with the /use-case skill, invoke this Skill to produce a Feature file with a happy path scenario plus negative test scenarios for each extension, then run coverage analysis to confirm 100% flow mapping before implementation begins. ## Quick Start Ask the agent to generate BDD scenarios from use case UC-AUTH-001 and then analyze test coverage of the resulting Feature file against the source use case.

Frequently Asked Questions about test-spec

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

FAQPage Schema
How do I generate Gherkin scenarios from a use case specification?

Invoke the test-spec skill with a use case artifact at ESSENTIAL_OUTLINE detail level or higher. The tspec-generator agent applies Clark's UC2.0-to-Gherkin mapping to produce a Feature file with one happy path scenario, one scenario per alternative flow, and one per extension.

How do I analyze BDD test coverage against a use case?

Use the tspec-analyst agent with both the Feature file and the source use case artifact. It computes coverage as mapped scenarios divided by total mappable flows, applies the 7 Cs quality framework, and reports prioritized gaps with effort estimates.

What use case format is required for Gherkin test generation?

The use case artifact must have detail_level of ESSENTIAL_OUTLINE or FULLY_DESCRIBED, a basic_flow of 3-9 steps with typed steps (actor_action, system_response, validation), and at least one extension. Artifacts below this threshold are rejected with guidance to elaborate first.

Does this skill generate executable test code like pytest?

No. It produces human-readable Gherkin BDD specifications in .feature.md files, not executable test code. For unit tests or pytest implementation, write tests directly or use a separate engineering skill; the Feature files serve as acceptance criteria.

What happens when a use case changes after the Feature file was generated?

The coverage analyst performs staleness detection by comparing the Feature file's recorded flow count against the live use case. On divergence it emits a staleness warning and recommends regenerating the Feature file to synchronize.