Does this skill support automated testing?

Yes, it generates Gherkin scenarios that serve as the direct foundation for Cucumber feature files and RSpec acceptance tests.

How does it handle non-functional requirements?

It provides structured templates for performance, security, and scalability requirements, ensuring they are measured by specific, verifiable metrics.

Can I use this for non-Rails projects?

While the repository focuses on Rails, the requirement patterns, Gherkin formats, and INVEST principles are portable to any software development environment.

What is the INVEST criteria used by this skill?

INVEST is a checklist (Independent, Negotiable, Valuable, Estimable, Small, Testable) used to ensure high-quality user stories that are ready for development.

Enterprise Requirements Writing & Gherkin

Name: Enterprise Requirements Writing & Gherkin
Author: Kaakati

byKaakati

•

Security & Testing

Standardizes the software development lifecycle by generating testable User Stories and Gherkin scenarios for enterprise Rails applications.

About

This skill empowers developers and product owners to bridge the gap between business logic and technical implementation through high-quality documentation. It provides a structured framework for crafting User Stories using the INVEST criteria and defining detailed acceptance criteria via Gherkin scenarios. Specifically optimized for enterprise Rails environments, it emphasizes domain-driven language, traceability, and the distinction between functional and non-functional requirements to ensure features are ready for BDD (Behavior-Driven Development).

Key Features

Traceability mapping from user needs to executable test scenarios
Example Mapping discovery techniques for complex business logic
User Story generation following the INVEST quality framework
Functional and non-functional requirement categorization and templates
2 GitHub stars
Gherkin scenario authoring with Given-When-Then structure

Use Cases

Defining new feature sets for a SaaS platform with clear, unambiguous acceptance criteria
Documenting complex logistical business rules such as zone bundling or payment reconciliation
Generating the documentation layer for BDD workflows using RSpec or Cucumber

About

Key Features

Traceability mapping from user needs to executable test scenarios
Example Mapping discovery techniques for complex business logic
User Story generation following the INVEST quality framework
Functional and non-functional requirement categorization and templates
2 GitHub stars
Gherkin scenario authoring with Given-When-Then structure

Use Cases

Defining new feature sets for a SaaS platform with clear, unambiguous acceptance criteria
Documenting complex logistical business rules such as zone bundling or payment reconciliation
Generating the documentation layer for BDD workflows using RSpec or Cucumber