Write Mike Cohn user stories with Gherkin Given/When/Then acceptance criteria.
npx skills add https://github.com/ch-m-n/dotfile --skill user-story-ch-m-n
Please help me install this Agent Skill. Skill: user-story Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/user-story Command: npx skills add https://github.com/ch-m-n/dotfile --skill user-story-ch-m-n
Helps product teams avoid vague, untestable backlog entries by codifying the Mike Cohn user story structure with Gherkin acceptance criteria, so every story clarifies who benefits, what changes, and how success is validated.
Ask the Skill to write a Mike Cohn user story with Gherkin acceptance criteria for the new notification workflow.
High-intent search queries and answers about installing and using this skill.
To write user stories with Gherkin acceptance criteria, use the Mike Cohn format (As a / I want / so that) combined with Given/When/Then scenarios to clarify who benefits, what changes, and how success is validated during backlog grooming.
The best way to translate user needs into testable acceptance criteria is structuring them as Gherkin scenarios with Given/When/Then steps, ensuring every story focuses on value, measurable triggers, and verifiable results for the target persona.
Persona-driven user story structure works for B2B SaaS by capturing the specific persona, problem understanding, desired outcome, and constraints before writing the story, ensuring the resulting backlog entry directly addresses that user's context.
Yes, you can use Given/When/Then scenarios during sprint planning to define outcomes. This Gherkin acceptance criteria structure ensures stories remain user-centric, testable, and focused on verifiable results before development begins.
Vague backlog entries fail because they lack clear validation paths. Codifying the Mike Cohn user story structure with Gherkin acceptance criteria fixes this by explicitly defining who benefits, what changes, and how success is verified.
You do not need extensive product management experience to use Gherkin acceptance criteria, as utilizing context checklists and structured templates guides you through capturing personas, desired outcomes, and constraints to write verifiable stories.
officebeatsGenerate user-centered problem statements using an empathy-driven framework.
omeragaakbasTranslate user needs into user stories with Gherkin acceptance criteria.
AbsolutelySkilledGenerate user stories and acceptance criteria using INVEST and Given/When/Then templates.
AsiaOstrichGuide teams through ATDD workflows with Given-When-Then acceptance criteria.
