Create user stories with As a/I want/so that and Gherkin acceptance criteria.
npx skills add https://github.com/MiDouTech/myTapd --skill user-story-midoutech
Please help me install this Agent Skill. Skill: user-story Source: https://github.com/MiDouTech/myTapd/tree/main/.claude/skills/user-story Command: npx skills add https://github.com/MiDouTech/myTapd --skill user-story-midoutech
Product and engineering teams often receive vague requirements that lack clear user value, measurable outcomes, and testable acceptance criteria, which leads to misaligned implementation and unclear definitions of done. This Skill helps convert user needs and product requirements into concise, outcome-focused user stories that are ready for development and QA.
Write a user story for a trial user who wants to log in with Google so that they can access the app without creating a new password and include Gherkin acceptance criteria.
High-intent search queries and answers about installing and using this skill.
Write user stories using Mike Cohn's 'As a / I want / so that' structure to focus on user value, then add Gherkin Given/When/Then acceptance criteria so QA and engineering can validate the outcome. This produces testable, development-ready backlog items.
Convert a PRD requirement into a single backlog item by generating a concise persona use case and pairing it with Gherkin Given/When/Then acceptance criteria. This translates vague product requirements into measurable, testable conditions for development.
Split large user stories during sprint planning by applying included guidance on decomposition for QA and engineering. This ensures each backlog item remains outcome-focused, testable, and small enough to fit within a single sprint cycle.
Gherkin Given/When/Then defines the definition of done by specifying a clear context, action, and expected outcome for each user story. This format provides QA and engineering with unambiguous, testable validation steps directly from the requirements.
No prior product management experience is strictly required to use structured user story templates. The format applies to product managers and teams preparing backlog items, providing practical examples and quality checks to refine stories during grooming.
Vague requirements lack clear user value and testable acceptance criteria, causing misaligned implementation. User stories fix this by combining outcome-focused 'As a/I want/so that' structures with Gherkin validation to ensure a clear definition of done.
C0ntr0lledCha0sAutomate sprint planning and backlog refinement with prioritization frameworks.
zhengxuyuGenerate user stories and Gherkin acceptance criteria for product management.
kevinlinEstimate time, effort, cost, and complexity for software backlog items with P50/P80 confidence intervals.
mlbrightGuide structured interviews to create feature specifications with Gherkin scenarios.
