feature

Convert user requests into Gherkin feature files with job stories.

1|2|Updated Nov 29, 2024
One-click install
npx skills add https://github.com/JohnStrunk/66-laps --skill feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/JohnStrunk/66-laps/tree/main/.gemini/skills/feature
Command: npx skills add https://github.com/JohnStrunk/66-laps --skill feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineers translate vague requirements into precise, executable feature specifications.

Core Features & Use Cases

  • Dialog-driven job story creation to capture situation, action, and outcome.
  • Generate Gherkin-based feature files under features/NNNN-name.feature with a clear structure.
  • Use best practices like Background, Rules, and Data Tables to organize scenarios.
  • Scaffold initial step definitions and provide guidance for validation.

Quick Start

Ask the Skill to draft a feature spec (e.g., 'Create a feature spec for a user login flow'). The Skill will prompt for the job story, confirm the feature file name, and output a ready-to-use .feature skeleton plus a plan for scaffolding steps.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I turn vague product requirements into executable BDD feature specs?

To create executable BDD feature specs, this Skill uses a dialog-driven approach to capture job stories and translates them into structured Gherkin feature files. It guides you through defining the situation, action, and outcome to ensure precise acceptance criteria.

What is the best way to write Gherkin feature files with Background, Rules, and Data Tables?

The best way to write Gherkin feature files is by applying built-in best-practice templates that organize scenarios using Background, Rules, and Data Tables. This Skill scaffolds these structures automatically under features/NNNN-name.feature for clear testable behavior.

Do I need any external testing tools to generate job stories and Gherkin scenarios?

You do not need external testing tools to generate job stories and Gherkin scenarios. This Skill relies entirely on structured prompts and best-practice templates to drive the spec creation dialog, requiring no additional dependencies.

How to scaffold step definitions after creating a feature spec?

To scaffold step definitions after creating a feature spec, this Skill outputs a ready-to-use .feature skeleton along with a foundational plan for step validation. It provides structural guidance to connect your Gherkin scenarios to executable test code.

Can I use job stories instead of user stories for feature scoping and acceptance criteria?

You can use job stories for feature scoping and acceptance criteria by capturing the specific situation, action, and outcome through a guided dialog. This approach focuses on the contextual motivation of the user to define testable behavior.