plan

Name: plan
Availability: InStock
Author: LangWatch

Create a feature file with acceptance criteria before implementation.

3.5k|340|Updated Sep 9, 2023

Search Tags:#workflow #plan #bdd #specs #acceptance-criteria #issue-tracker #feature-file

Ready to run

npx skills add https://github.com/langwatch/langwatch --skill plan-langwatch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/langwatch/langwatch/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/langwatch/langwatch --skill plan-langwatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a feature file workflow to ensure acceptance criteria precede implementation, preventing scope creep and misaligned expectations.

Core Features & Use Cases

Automatically generate specs/features/<feature-name>.feature when missing.
Enforce references to issue descriptions and acceptance criteria from the issue tracker.
Quick-start guidance for immediate feature-file creation.

Quick Start

Write the new feature file to specs/features/<feature-name>.feature

Frequently Asked Questions about plan

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

FAQPage Schema

How do I generate a feature file with acceptance criteria before coding?▼

Generating a feature file with acceptance criteria requires defining behavior before coding to prevent scope creep. This workflow outputs a structured specs/features/<feature-name>.feature file that enforces alignment with issue tracker descriptions and testing guidelines.

Why define behavior in a feature file before starting implementation?▼

Defining behavior in a feature file before implementation prevents scope creep and misaligned expectations. Establishing acceptance criteria early ensures the development process aligns directly with issue tracker descriptions and testing philosophy.

What is the best way to link issue tracker descriptions to BDD specs?▼

The best way to link issue tracker descriptions to BDD specs is to enforce references to acceptance criteria during feature file creation. This ensures the generated specs/features/<feature-name>.feature file accurately reflects the defined issue requirements.

Can I automatically create a feature file when missing specs are detected?▼

Yes, you can automatically create a feature file when missing specs are detected. This workflow triggers when no specs/features/*.feature files exist for the work, automatically generating the necessary file to guide teams in defining behavior.

Does generating acceptance criteria require an existing issue tracker entry?▼

Generating acceptance criteria requires referencing issue descriptions and criteria from the issue tracker. This ensures the created feature file accurately captures the expected behavior and aligns with the predefined scope before development starts.