user-story-writer

Convert feature ideas into INVEST-aligned user stories with Gherkin acceptance criteria.

3|2|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JayRHa/AgentSkills --skill user-story-writer-jayrha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story-writer
Source: https://github.com/JayRHa/AgentSkills/tree/main/user-story-writer
Command: npx skills add https://github.com/JayRHa/AgentSkills --skill user-story-writer-jayrha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing clear, testable user stories from vague ideas and scattered notes is time-consuming and error-prone. This skill provides a repeatable, structured approach to transform features into INVEST-compliant stories with explicit role/goal/benefit phrasing and ready-made Gherkin acceptance criteria.

Core Features & Use Cases

  • Convert feature ideas or epic concepts into well-formed user stories with the canonical "As a <role>, I want <capability>, so that <benefit>" format.
  • Generate testable acceptance criteria in Gherkin, including happy and edge cases, using templates and references to INVEST checklists.
  • Split epics into thin vertical slices for incremental delivery and maintainable backlog items.

Quick Start

Provide a feature idea or epic and the skill will generate ready-to-estimate user stories with acceptance criteria.

Frequently Asked Questions about user-story-writer

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

FAQPage Schema
How do I write INVEST-aligned user stories from feature ideas?

To write INVEST-aligned user stories from feature ideas, structure them using the "As a <role>, I want <capability>, so that <benefit>" format and validate them against INVEST checklists to ensure they are independent, negotiable, and testable for sprint planning.

How do I generate Gherkin acceptance criteria for a backlog item?

Generate Gherkin acceptance criteria for a backlog item by defining explicit Given-When-Then scenarios that cover both happy paths and edge cases, ensuring the user story is testable and ready for development.

What is the best way to split epics into thin vertical slices for agile delivery?

Splitting epics into thin vertical slices for agile delivery involves breaking down broad feature concepts into smaller, independently deliverable user stories using established story-splitting patterns, maintaining a manageable and incremental backlog.

Do I need a Definition of Done to create ready-to-sprint user stories?

A Definition of Done is necessary to create ready-to-sprint user stories, as applying DoD guidance alongside INVEST compliance ensures the backlog items meet quality standards and are fully prepared for sprint planning.

Can I use Gherkin and INVEST checklists for backlog grooming?

Yes, you can use Gherkin and INVEST checklists for backlog grooming to refine requirements, verify story quality, and ensure each backlog item has clear, testable acceptance criteria before estimation.