create-user-story

Translate natural language descriptions into structured YAML e2e user stories.

Updated Aug 23, 2026

Search Tags:#testing #e2e #QA #yaml #generate #stories

Ready to run

npx skills add https://github.com/brian-wijaya/dotfiles --skill create-user-story

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-user-story
Source: https://github.com/brian-wijaya/dotfiles/tree/main/.claude/skills/create-user-story
Command: npx skills add https://github.com/brian-wijaya/dotfiles --skill create-user-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates conversational user needs into formal, machine-readable e2e user stories that can be executed by QA or testing loops.

Core Features & Use Cases

Intent extraction: Derives feature, behavior, and acceptance criteria from natural language descriptions.
Story generation: Produces structured YAML stories compatible with /e2e-test-debug-loop.
Workspace integration: Saves stories to ~/.claude/e2e-stories/ and supports an optional target story file path.

Quick Start

Use the skill to convert a user description like "I want Emacs to auto-save my session every 5 minutes" into an e2e story and write it to ~/.claude/e2e-stories/.

Frequently Asked Questions about create-user-story

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

FAQPage Schema

How do I generate e2e test stories from natural language descriptions?▼

To generate e2e test stories from natural language, this skill extracts feature intents, behaviors, and acceptance criteria from conversational descriptions and translates them into structured YAML files stored under ~/.claude/e2e-stories/.

What is the best way to convert user feature requests into structured YAML for QA testing?▼

Converting user feature requests into structured YAML for QA testing is done by parsing natural language inputs to derive acceptance criteria and outputting validated e2e stories compatible with testing loops like /e2e-test-debug-loop.

Can I specify a custom file path when generating e2e stories?▼

Yes, you can specify an optional target story file path when generating e2e stories. By default, the skill validates the YAML structure and writes the output to the ~/.claude/e2e-stories/ directory.

Does the generated YAML work directly with the e2e-test-debug-loop?▼

Yes, the generated YAML is specifically designed to be compatible with the e2e-test-debug-loop. The skill validates the story structure before writing to ensure seamless execution by QA testing workflows.

What types of conversational descriptions can be turned into e2e stories?▼

Conversational descriptions detailing software features, behaviors, or test scenarios can be turned into e2e stories. The skill derives intent and acceptance criteria from these natural language inputs to produce structured YAML outputs.