new-feature

Generate ATDD Gherkin feature files with a review gate before implementation.

18|4|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bdfinst/vsm-workshop --skill new-feature-bdfinst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-feature
Source: https://github.com/bdfinst/vsm-workshop/tree/main/.claude/skills/new-feature
Command: npx skills add https://github.com/bdfinst/vsm-workshop --skill new-feature-bdfinst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to define ATDD feature files before implementation to prevent ambiguity in acceptance criteria.

Core Features & Use Cases

  • Standardized ATDD feature-file template to guide feature development.
  • Pre-implementation review gate to ensure alignment with user stories and acceptance criteria.
  • VSM workshop-specific scenario guidance to integrate with existing processes.

Quick Start

Run /new-feature <FeatureName> to generate the template feature file and pause for review.

Frequently Asked Questions about new-feature

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

FAQPage Schema
How do I create ATDD feature files before implementation?

To create ATDD feature files before implementation, run the new-feature command with your feature name to generate a standardized Gherkin template and pause for a team review gate prior to coding.

What is a pre-implementation review gate for Gherkin feature files?

A pre-implementation review gate for Gherkin feature files is a workflow checkpoint that pauses development to ensure the ATDD acceptance criteria align with user stories before any coding begins.

How do I standardize Gherkin feature file templates for Value Stream Mapping?

You standardize Gherkin feature file templates for Value Stream Mapping workflows by applying a consistent structure that provides VSM workshop-specific scenario guidance and prevents ambiguity in acceptance criteria.

When do I need to define acceptance criteria using a feature file template?

You need to define acceptance criteria using a feature file template when teams are defining new features, ensuring a clear Gherkin structure and a review-driven workflow to prevent ambiguity before development starts.

Can I integrate ATDD feature file creation with existing Value Stream Mapping processes?

Yes, you can integrate ATDD feature file creation with existing Value Stream Mapping processes through VSM workshop-specific scenario guidance that ensures alignment with your current workflows.

What is the best way to prevent ambiguity in acceptance criteria before coding?

The best way to prevent ambiguity in acceptance criteria before coding is to automate the creation of ATDD feature files using a standard Gherkin template and enforce a review gate prior to implementation.