skills.rest
nroze22
nroze22COMMUNITY
Explore all skills by this author →
GitHub

acceptance-criteria

Generate Gherkin acceptance criteria for Talosix EDC user stories using Jira context.

1|1|Updated Feb 24, 2026
Search Tags:#testing#acceptance criteria#user stories#jira#regulatory compliance#edc
One-click install
npx skills add https://github.com/nroze22/TalosixSkills --skill acceptance-criteria-nroze22
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acceptance-criteria
Source: https://github.com/nroze22/TalosixSkills/tree/main/.claude/skills/acceptance-criteria
Command: npx skills add https://github.com/nroze22/TalosixSkills --skill acceptance-criteria-nroze22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of detailed acceptance criteria for user stories, ensuring comprehensive test coverage and adherence to regulatory standards in clinical trial systems.

Core Features & Use Cases

  • Automated Criteria Generation: Creates acceptance criteria covering happy paths, error handling, edge cases, permissions, audit trails, and regulatory compliance.
  • Gherkin Syntax: Utilizes Given-When-Then format for clarity and testability.
  • Use Case: When a new user story for a data entry module is created in Jira, this Skill can generate all necessary acceptance criteria, including specific audit trail and data integrity requirements.

Quick Start

Generate acceptance criteria for the Jira ticket with ID 'PROJ-123'.

Frequently Asked Questions about acceptance-criteria

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

FAQPage Schema
How do I generate acceptance criteria for Jira user stories?▼

To generate acceptance criteria for Jira user stories, provide a Jira ticket ID to automatically create comprehensive criteria covering happy paths, error handling, and edge cases in Gherkin syntax.

What is Gherkin syntax for user stories?▼

Gherkin syntax for user stories uses the Given-When-Then format to structure acceptance criteria, ensuring clear testability for functional requirements and error handling scenarios.

How do I write acceptance criteria for clinical trial EDC systems?▼

Writing acceptance criteria for clinical trial EDC systems requires covering functional requirements, permissions, audit trails, and regulatory compliance to ensure validated system test coverage.

What should acceptance criteria include for regulatory compliance?▼

Acceptance criteria for regulatory compliance must include specific conditions for data integrity, audit trails, permissions, and error handling to meet validated clinical trial system standards.

Can I automate test coverage for edge cases in Jira?▼

You can automate test coverage for edge cases in Jira by generating detailed acceptance criteria that explicitly define error handling and boundary conditions using Given-When-Then syntax.

Does acceptance criteria generation work without manual test case writing?▼

Acceptance criteria generation works without manual test case writing by automatically outputting structured Given-When-Then statements that cover happy paths, data integrity, and audit trail requirements.

Related Skills

Explore More Product & Management Skills→
foolpoet44foolpoet44
1

userstory-documentation

Translate PRDs into epics, user stories, and acceptance criteria.

Community
Advanced
hmctshmcts
3

generate-bdd-specs

Converts acceptance criteria into Cucumber/Gherkin feature files with backgrounds and tags.

Official
Intermediate
nroze22nroze22
1

product-prd

Generate structured PRDs for clinical trial EDC features using Jira and Confluence context.

Community
Advanced
dasheck0dasheck0
8

story-to-testcases

Transform Jira user stories with acceptance criteria into deterministic test case suites.

Community
Advanced