Generate user stories using Mike Cohn format and Gherkin acceptance criteria.
npx skills add https://github.com/phuhao00/bony-agent --skill user-story-phuhao00
Please help me install this Agent Skill. Skill: user-story Source: https://github.com/phuhao00/bony-agent/tree/main/.agent/skills/user-story Command: npx skills add https://github.com/phuhao00/bony-agent --skill user-story-phuhao00
This skill solves the common challenge of vague, unmeasurable requirements by providing a structured framework that ensures user stories are outcome-focused, testable, and clear to both product and engineering teams.
Use the user-story skill to generate a story template for a user logging in with Google to improve signup conversion.
High-intent search queries and answers about installing and using this skill.
User stories with Gherkin acceptance criteria are generated using the Mike Cohn format (As a, I want to, so that) and Given-When-Then logic. This translates user needs into actionable, testable sprint tickets for product management and engineering workflows.
The best way to structure agile user stories for testing is combining the Mike Cohn format for user-centric value with Gherkin-style acceptance criteria. Given-When-Then logic makes stories verifiable by QA and ensures clear alignment on success conditions before development begins.
Gherkin format works by enforcing Given-When-Then logic to define verifiable success conditions for development tasks. Paired with the As a-I want to-so that structure, it ensures user stories remain outcome-focused, testable, and clear to both product and engineering teams.
You need Gherkin acceptance criteria when translating high-level user needs into concrete sprint tickets. It solves the challenge of vague, unmeasurable requirements by ensuring stories are outcome-focused and verifiable by QA before development starts.
Yes, the Mike Cohn user story format standardizes the As a, I want to, so that structure for complex product management workflows. It ensures user-centric value across all backlog items, regardless of workflow complexity.
Agile backlogs often have untestable user stories because acceptance criteria lack structured Given-When-Then logic. Gherkin format enforces verifiable success conditions, ensuring stories are testable by QA and aligned with desired outcomes before development begins.
jasonmeansGenerate user personas and use case tables in markdown documents.
warpcodeTranslate epics into user stories and Gherkin acceptance criteria.
theandyalvarez7-rubyTurn epics into structured user stories with INVEST-aligned acceptance criteria.
Adelie-SquadGenerate Job Stories, User Stories, and Gherkin acceptance criteria from product briefs.
