Translate user needs into user stories with Gherkin acceptance criteria.
npx skills add https://github.com/omeragaakbas/zoyare --skill user-story-omeragaakbas
Please help me install this Agent Skill. Skill: user-story Source: https://github.com/omeragaakbas/zoyare/tree/main/.claude/skills/user-story Command: npx skills add https://github.com/omeragaakbas/zoyare --skill user-story-omeragaakbas
This Skill helps product teams consistently transform user needs into concise, testable stories that pair Mike Cohn's Use Case format with Gherkin-style acceptance criteria. It ensures stories are outcome-focused, actionable, and ready for discussion between product, design, and engineering.
Provide a persona, action, and outcome to generate a ready-to-use user story skeleton.
High-intent search queries and answers about installing and using this skill.
Testable user stories combine Mike Cohn's Use Case format (As a..., I want to..., so that...) with Gherkin-style acceptance criteria (Given, When, Then) to ensure outcomes are measurable and verifiable across product, design, and engineering teams.
The best way to format a user story for sprint planning is using a Use Case structure that defines a specific persona, action, and outcome, paired with clear Gherkin scenarios to guide development and testing discussions.
You can split large user stories by applying story-splitting guidance to break down broad outcomes into smaller, testable units, ensuring each divided story retains clear persona, problem, and verifiable acceptance criteria.
Yes, generating a user story requires clear inputs for persona, action, and outcome. Providing these three elements produces a ready-to-use user story skeleton complete with testable Gherkin acceptance criteria.
Gherkin syntax structures acceptance criteria into Given, When, Then scenarios, ensuring that user story requirements are measurable and verifiable while providing clear conversation starters for engineering and design teams.
You need the user-story format during backlog grooming to transform ambiguous user needs into concise, outcome-focused, and actionable items that are ready for discussion between product, design, and engineering stakeholders.
deanpetersGenerate user stories with Gherkin acceptance criteria and YAML frontmatter templates.
getcrew44Split large user stories into independently deliverable stories using eight splitting patterns.
zhengxuyuGenerate user stories and Gherkin acceptance criteria for product management.
yuyuxinliTranslate user needs into structured stories with Gherkin acceptance criteria.
