user-story
From the author
Create clear, concise user stories that combine Mike Cohn's user story format with Gherkin-style acceptance criteria. Use this to translate user needs into actionable development work that focuses on
Install
npx skills add aAAaqwq/AGI-Super-Team --skill user-story -a claude-code
Installs to .claude/skills/user-story/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- acceptance-criteriaChenxingJi-Innovate/Cheatcode_Write acceptance criteria for user stories or requirements as Gherkin scenarios (Given, When, Then) or EARS statements, including negative, boundary and permission cases, so that business users and testers agree on done before development starts. Use when a story or requirement needs acceptance criteria, when existing criteria are vague, or when preparing stories for refinement or UAT.Writing★ 81
- user-storiesphuryn/pm-skillsCreate user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.Design★ 27.6K
- requirements-specificationnicepkg/ai-workflowMaster requirements gathering, user story writing, acceptance criteria definition, and scope management. Transform insights into clear, actionable specifications.Planning★ 288
- deliver-user-storiesproduct-on-purpose/pm-skillsGenerates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.Writing★ 784
- scenario-generatorArabelaTso/Skills-4-SEGenerate comprehensive test scenarios, user stories, and acceptance criteria from requirements and specifications. Use this skill when planning testing efforts, writing user stories, creating test cases, documenting acceptance criteria, exploring edge cases, designing test coverage, or translating requirements into actionable scenarios. Supports BDD (Given-When-Then), Gherkin syntax, user story format, and test case documentation.Testing★ 260
- deliver-acceptance-criteriaproduct-on-purpose/pm-skillsGenerates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.Testing★ 784
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in