user-story

Organize requirements into verb-noun capability cards with Gherkin scenarios.

2|1|Updated Oct 8, 2009

Search Tags:#requirements #gherkin #acceptance-criteria #user-story #capability-card

Ready to run

npx skills add https://github.com/riethmayer/dotfiles --skill user-story-riethmayer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/user-story
Command: npx skills add https://github.com/riethmayer/dotfiles --skill user-story-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing and communicating requirements can be ambiguous; this Skill helps convert requirements into structured, reusable capability cards that map to verb-noun packages.

Core Features & Use Cases

Card-based storytelling: create clear, traceable capability cards named <verb>-<noun> that map 1:1 to package directories.
Conversation-then-Confirmation: define a Conversation (live) and Confirmation (Gherkin scenarios) that prove the capability works.
Co-located specs: store a co-located .feature file within the corresponding package directory to serve as living documentation.

Quick Start

Create a new user-story card by selecting a verb-noun capability and describing it with a concise domain, modalities, and acceptance criteria.

Frequently Asked Questions about user-story

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

FAQPage Schema

How do I write user stories with clear acceptance criteria?▼

User stories become structured capability cards by mapping requirements to a verb-noun naming pattern and defining 3-5 Gherkin scenarios as acceptance criteria for confirmation. This ensures each capability is traceable and testable.

What is the best way to organize requirements into capability cards?▼

Organizing requirements into capability cards involves mapping each capability 1:1 to a package directory using a verb-noun pattern, then co-locating a .feature file inside to serve as living documentation for the domain.

How do I structure Gherkin scenarios for a capability?▼

Structuring Gherkin scenarios for a capability requires writing 3-5 confirmation scenarios per capability card. These scenarios are stored in a co-located .feature file within the corresponding package directory to prove the capability works.

When do I need to use a capability card for capturing requirements?▼

You need capability cards when capturing requirements, onboarding agents to a domain, or writing user stories. They convert ambiguous requirements into structured, reusable cards that map directly to package directories.

Does this approach to requirements management require co-located .feature files?▼

Yes, this approach requires co-locating a .feature file in each package directory. This file holds the 3-5 Gherkin scenarios that act as living documentation and confirmation for the verb-noun capability card.

Why use a verb-noun naming pattern for user stories?▼

A verb-noun naming pattern structures user stories into clear, reusable capability cards that map 1:1 to package directories. This reduces ambiguity and creates traceable conversation and confirmation definitions for each capability.