skills.rest
Alteriom
AlteriomOFFICIAL
Explore all skills by this author →
WebsiteGitHub

feature-specification

Define testable feature specifications with BDD templates and workflows.

Updated Apr 14, 2026
Search Tags:#tdd#specification#agile#bdd#gherkin#acceptance-criteria#example-mapping
One-click install
npx skills add https://github.com/Alteriom/ai-dev-skills --skill feature-specification-alteriom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-specification
Source: https://github.com/Alteriom/ai-dev-skills/tree/main/skills/feature-specification
Command: npx skills add https://github.com/Alteriom/ai-dev-skills --skill feature-specification-alteriom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams and developers translate abstract features into clear, testable specifications using BDD, acceptance criteria, and collaborative mapping.

Core Features & Use Cases

  • Templates for a structured spec: User Story + Acceptance Criteria, Gherkin (Given-When-Then), and Example Mapping to guide discussion and testing.
  • Workflow guidance: A repeatable process from feature inception to test-ready specs, including identifying happy paths and edge cases.
  • Quality assurance patterns: Verification checklists, pitfalls to avoid, and integration with other skills to support implementation and QA.

Quick Start

Draft a feature concept, write a user story with acceptance criteria, then convert it to Gherkin scenarios to drive test automation.

Frequently Asked Questions about feature-specification

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

FAQPage Schema
How do I write testable acceptance criteria for agile user stories?▼

Testable acceptance criteria are written using structured templates like User Story + Acceptance Criteria and Gherkin scenarios to define clear conditions. This approach translates abstract features into testable specifications using BDD principles.

What is the best way to convert feature concepts into Gherkin Given-When-Then scenarios?▼

Converting feature concepts into Gherkin scenarios involves drafting a user story with acceptance criteria, then mapping those criteria into Given-When-Then syntax. This creates test-ready specs to drive automation and identify edge cases.

How does example mapping help identify edge cases in BDD specifications?▼

Example mapping guides collaborative discussion by breaking rules into concrete examples, revealing happy paths and edge cases. It structures feature specifications and ensures teams uncover hidden requirements before implementation begins.

Can I use BDD specifications for TDD workflows in product development?▼

BDD specifications support TDD workflows by providing structured, test-ready scenarios derived from acceptance criteria. Teams apply these Gherkin scenarios across agile projects to drive test automation and verify feature behavior.

What are common pitfalls when writing feature specifications with Gherkin?▼

Common pitfalls when writing feature specifications include ambiguous acceptance criteria, missing edge cases, and poorly structured Gherkin scenarios. A verification checklist and workflow patterns help teams avoid these issues and ensure spec quality.

Related Skills

Explore More Product & Management Skills→
fhltafhlta

guildops-prd-discovery

Transforms GuildOps feature concepts into structured, Spec Kit-ready PRDs with ambiguity checklist and template.

Community
Intermediate
wtahwtah

e2e-testing

Plan and execute end-to-end tests with Playwright and MCP server.

Community
Advanced
laraxotlaraxot
26

bmad-dev-story

Automate development story implementation from story specification files.

Official
Advanced
anton-abyzovanton-abyzov
156

spec-kit-expert

Generate RFC 2119-compliant specifications with Gherkin scenarios and user stories.

Community
Basic