Skip to content
TrustedSkillsbeta
Back to all skills

User Story

Checked
deanpeters·vlatest·productivity

Generates user stories from a single prompt, helping teams quickly capture requirements and prioritize features for development.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add deanpeters/product-manager-skills --skill user-story -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

deanpeters

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned deanpeters/product-manager-skills at cfcb697f14.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
cfcb697f14
Manifest
skills/user-story/SKILL.md
Scanned
5 files, 593 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The user-story skill allows an AI agent to generate and refine user stories, a common practice in agile software development. It can take high-level requirements or ideas and translate them into actionable user story formats including "As a [user type], I want [goal] so that [benefit]". The skill also helps break down larger features into smaller, more manageable user stories.

When to use it

  • Product Backlog Creation: Generate initial user stories for a new product or feature based on high-level requirements.
  • Feature Breakdown: Decompose complex features into smaller, testable user stories.
  • Requirement Clarification: Translate vague requests from stakeholders into well-defined user story format.
  • Agile Sprint Planning: Quickly create user stories for tasks to be completed during a sprint.

Key capabilities

  • Generates user stories in the "As a...I want...so that..." format.
  • Breaks down larger features into smaller user stories.
  • Translates high-level requirements into actionable user stories.

Example prompts

  • "Create a user story for a mobile app feature allowing users to share photos."
  • "Break down the 'customer onboarding' feature into smaller user stories."
  • "Turn this requirement: 'Users need to be able to reset their passwords' into a user story."

Tips & gotchas

The quality of the generated user stories depends heavily on the clarity and detail provided in the initial prompt. Providing context about the user type and desired benefit will yield more relevant and useful results.