write-user-story

Name: write-user-story
Availability: InStock
Author: EnigmaWu

Develop BDD-style user stories with Given/When/Then scenarios.

1|Updated Apr 6, 2026

Search Tags:#acceptance criteria #product development #BDD #user story #requirement specification

Ready to run

npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill write-user-story-enigmawu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-user-story
Source: https://github.com/EnigmaWU/MyCodeAgentSkills/tree/main/write-user-story
Command: npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill write-user-story-enigmawu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill tackles the challenge of formulating User Stories in a clear, business-focused, and executable manner, using Behavior-Driven Development (BDD) techniques to ensure unambiguous specifications.

Core Features & Use Cases

BDD Formatting: Prompts the user to frame User Stories in BDD-style acceptance criteria.
Role & Business Value: Assists in defining the user role and business value associated with the feature.
Testable Scenarios: Generates Given/When/Then scenarios to ensure the User Story is testable.
Use Case: For a new feature such as "User profile creation," it will help define the role, business value, and executable acceptance criteria.

Quick Start

Write a user story for the feature 'User profile creation' with BDD-style criteria.

Frequently Asked Questions about write-user-story

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

FAQPage Schema

How do I write a BDD-style user story with testable acceptance criteria?▼

To write a BDD-style user story, define the user role, business value, and executable acceptance criteria using Given/When/Then scenarios. This structured approach ensures your requirement specification remains unambiguous and testable throughout product development.

What is BDD formatting for requirement specification in product development?▼

BDD formatting for requirement specification is a technique that frames user stories using Behavior-Driven Development scenarios. It aligns explicit business intent with technical implementation by generating structured Given/When/Then scenarios to ensure clarity and consistency.

How do I create Given/When/Then scenarios for a new feature like user profile creation?▼

You create Given/When/Then scenarios for user profile creation by defining the specific user role, stating the associated business value, and outlining the executable acceptance criteria. This process ensures the user story is structured and explicitly testable.

Can I use BDD user stories to align business intent and technical implementation?▼

Yes, you can use BDD user stories to align business intent and technical implementation. They are specifically designed for product development and specification workshops where explicit business goals must translate directly into structured, testable technical scenarios.

What is the best way to structure a user story for product specification workshops?▼

The best way to structure a user story for specification workshops is using BDD-style formatting. This method clarifies the user role and business value while generating structured, testable Given/When/Then scenarios to ensure unambiguous requirement specification across the team.