Skip to content
SkillModel-led609 tokens in use

user-stories

Break a feature into user stories that follow the 3 C's and INVEST criteria, each with a design link and acceptance criteria.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-execution/skills/user-stories
claude plugin install pm-execution@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing user-stories costs

52tokens idle
609tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples3/15
  • Output5/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

user-stories takes a product, a feature, a link to designs and key assumptions, and produces a set of user stories. Each has a title, a description in the form “As a [role], I want to [action], so that [benefit]”, a design link and four to six acceptance criteria.

It applies the 3 C’s (Card, Conversation, Confirmation) and checks every story against INVEST: Independent, Negotiable, Valuable, Estimable, Small and Testable.

What You Get

  • A complete set of stories for the feature
  • A title, description and design link for each story
  • Four to six testable acceptance criteria per story
  • Stories independent enough to build in any order
  • Stories sized for one sprint

Common Use Cases

  • Breaking a feature into backlog items
  • Writing acceptance criteria for a design
  • Preparing stories for sprint planning

What Makes It Unique

It builds on two named frameworks, the 3 C’s and INVEST, and keeps the wording accessible to a wide audience. Acceptance criteria cover behavior, edge cases, performance or accessibility and integration points.

Under The Hood

The skill is one SKILL.md of instructions with no scripts. It takes the product, feature, design link and assumptions as arguments and writes the stories in its reply. The design link is carried into the story text and is not fetched.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers