user-story

Generate user stories with structured Gherkin acceptance criteria.

3|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/whimzyLive/nightshift-ai --skill user-story-whimzylive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/whimzyLive/nightshift-ai/tree/main/plugins/sdlc/skills/user-story
Command: npx skills add https://github.com/whimzyLive/nightshift-ai --skill user-story-whimzylive

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Crafting user stories can be time-consuming and error-prone, especially when ensuring they're clear, concise, and aligned with the right acceptance criteria. This skill addresses the challenge by guiding you through the process with a structured format and examples.

Core Features & Use Cases

  • Structured User Story Format: Follows the Mike Cohn and Gherkin formats for user stories.
  • Guided Creation: Provides templates and instructions for writing user stories.
  • Acceptance Criteria: Offers guidance on creating testable acceptance criteria.
  • Use Case: Ideal for product managers, developers, and QA engineers looking to streamline the creation of user stories in agile development processes.

Quick Start

Use the 'user-story' skill to generate a user story for a new feature in your application.

Frequently Asked Questions about user-story

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

FAQPage Schema
How do I write agile user stories with Gherkin acceptance criteria?

Agile user stories with Gherkin acceptance criteria are generated by following the Mike Cohn format for the story and the Given/When/Then structure for testable conditions. This ensures clarity and testability for agile development environments.

What is the best format for structuring testable acceptance criteria?

The best format for structuring testable acceptance criteria is Gherkin. It uses a Given/When/Then syntax to define clear, testable conditions, ensuring that user stories are verifiable by QA engineers and aligned with agile development requirements.

How do I create a user story for a new application feature?

To create a user story for a new application feature, you provide the feature details to generate a structured story. It follows the Mike Cohn format and includes Gherkin acceptance criteria to ensure the feature requirements are clear and testable.

Does the Mike Cohn user story format work with Gherkin acceptance criteria?

Yes, the Mike Cohn user story format works seamlessly with Gherkin acceptance criteria. The skill combines the concise 'As a user, I want, so that' structure with Given/When/Then syntax to produce clear, testable agile development requirements.

When should I use Gherkin acceptance criteria in agile development?

You should use Gherkin acceptance criteria in agile development when you need clear, testable conditions for a user story. It is ideal for product managers, developers, and QA engineers looking to streamline feature creation and ensure alignment.