user-story

Draft user stories with Gherkin acceptance criteria for bounded contexts.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/I-Synergy/AI --skill user-story-i-synergy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/I-Synergy/AI/tree/main/.claude/skills/user-story
Command: npx skills add https://github.com/I-Synergy/AI --skill user-story-i-synergy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts informal feature discussions into well-structured, INVEST-aligned user stories with clear Gherkin acceptance criteria for bounded contexts, reducing ambiguity and rework.

Core Features & Use Cases

  • Drafts and finalizes user stories from design discussions or existing documentation.
  • Generates Gherkin-style acceptance criteria and associates them with the relevant bounded context.
  • Validates stories against INVEST criteria and exports them to docs/bounded-contexts/{BC}/user-stories.md.

Quick Start

Provide feature details with phrases like 'user story' or 'as a user' and I will draft and finalize the story with Gherkin 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 Gherkin acceptance criteria?

To write user stories with Gherkin acceptance criteria, provide informal feature details with phrases like 'user story' or 'as a user'. The system drafts the stories, converting discussions into structured documents validated against INVEST criteria.

How do I convert informal feature discussions into structured user stories?

Converting informal feature discussions into structured user stories involves extracting details during design sessions or from existing documents. The process applies bounded context rules and INVEST validation to produce ready-to-use stories in a markdown file.

Does this user story drafting process support bounded contexts?

Yes, the user story drafting process supports bounded contexts by associating Gherkin acceptance criteria with the relevant context. It exports the finalized stories directly to the docs/bounded-contexts/{BC}/user-stories.md directory path.

What is the best way to validate user stories against INVEST criteria?

The best way to validate user stories against INVEST criteria is to use an automated drafting tool that checks the structured output. The system ensures the generated stories with Gherkin criteria meet INVEST standards before finalizing them into documentation.

Can I extract user stories from existing documentation?

Yes, you can extract user stories from existing documentation. The system processes defined bounded contexts within your documents and converts them into structured user stories with Gherkin acceptance criteria, ready for immediate use.