skills.rest
Luscii
LusciiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

feature-file-organization

Organize Gherkin feature files for Terraform modules into docs/features with kebab-case naming.

Updated Jan 20, 2026
Search Tags:#patterns#organize#terraform#docs#scenarios#gherkin#feature-files
One-click install
npx skills add https://github.com/Luscii/terraform-fluentbit-luscii-presets --skill feature-file-organization
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-file-organization
Source: https://github.com/Luscii/terraform-fluentbit-luscii-presets/tree/main/.github/skills/feature-file-organization
Command: npx skills add https://github.com/Luscii/terraform-fluentbit-luscii-presets --skill feature-file-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and structure Gherkin feature files for Terraform modules to improve maintainability and scalability, reducing navigation friction and duplication as projects grow.

Core Features & Use Cases

  • Establishes a consistent docs/features layout for Terraform module tests
  • Provides patterns for grouping scenarios, avoiding duplication, and creating reusable steps
  • Enables migration from monolithic to organized feature sets with clear README indexes

Quick Start

  • Create docs/features/ with kebab-case feature files describing domain concepts, ensure each file focuses on a single capability, use Background for shared setup, and add a README index.

Frequently Asked Questions about feature-file-organization

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

FAQPage Schema
How do I organize Gherkin feature files for Terraform modules?▼

To organize Gherkin feature files for Terraform modules, establish a consistent docs/features layout using kebab-case naming, group scenarios by domain concepts, and use Background for shared setup to prevent duplication.

What is the best way to prevent step duplication in feature files as projects grow?▼

Preventing step duplication in feature files requires applying patterns for grouping, splitting, and reusing steps, ensuring each file focuses on a single capability, and maintaining a clear README index.

How do I split monolithic feature files into scalable sets?▼

Splitting monolithic feature files into scalable sets involves migrating to a docs/features structure, creating kebab-case files describing domain concepts, and adding a README index for navigation.

When should I use Background in Gherkin feature files?▼

Use Background in Gherkin feature files for shared setup steps that repeat across scenarios within the same file, reducing duplication and maintaining readability as feature sets grow.

Does organizing Terraform feature files require a specific directory structure?▼

Organizing Terraform feature files requires a docs/features/ directory structure, kebab-case naming for files, and a README index to ensure scalable navigation and maintainability.

Related Skills

Explore More Content & Communication Skills→
kinncjkinncj
23

cucumber-automation

Extract Gherkin scenarios from story markdown into .feature files and generate step stubs.

Community
Advanced
MathiasPaulenkoMathiasPaulenko

behave-bdd

Integrate Gherkin feature files with Python step definitions using behave.

Community
Advanced
pantheon-orgpantheon-org
9

terraform-validator

Validate, lint, and security-scan Terraform configurations and HCL files.

Official
Advanced
PaulRBergPaulRBerg
69

ls-lint

Enforce file and directory naming conventions via .ls-lint.yml configuration.

Community
Intermediate