agentsclimarketplace
Sign in

User stories

Skill phuryn/pm-skills/pm-execution/skills/user-stories

Create 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.From its SKILL.md

Install
npx -y skills add phuryn/pm-skills --skill user-stories

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.9 KB, 609 tokens by cl100k_base, as published. Nobody here has run it

User Stories

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.

Use when: Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.

Arguments:

  • $PRODUCT: The product or system name
  • $FEATURE: The new feature to break into stories
  • $DESIGN: Link to design files (Figma, Miro, etc.)
  • $ASSUMPTIONS: Key assumptions or context

Step-by-Step Process

  1. Analyze the feature based on provided design and context
  2. Identify user roles and distinct user journeys
  3. Apply 3 C's framework:
    • Card: Simple title and one-liner
    • Conversation: Detailed discussion of intent
    • Confirmation: Clear acceptance criteria
  4. Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
  5. Use plain language a primary school graduate can understand
  6. Link to design files for visual reference
  7. Output user stories in structured format

Story Template

Title: [Feature name]

Description: As a [user role], I want to [action], so that [benefit].

Design: [Link to design files]

Acceptance Criteria:

  1. [Clear, testable criterion]
  2. [Observable behavior]
  3. [System validates correctly]
  4. [Edge case handling]
  5. [Performance or accessibility consideration]
  6. [Integration point]

Example User Story

Title: Recently Viewed Section

Description: As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.

Design: [Figma link]

Acceptance Criteria:

  1. The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
  2. It is not displayed for users visiting the first product page of their session.
  3. The current product itself is excluded from the displayed items.
  4. The section showcases product cards or thumbnails with images, titles, and prices.
  5. Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
  6. Clicking on a product card leads the user to the corresponding product page.

Output Deliverables

  • Complete set of user stories for the feature
  • Each story includes title, description, design link, and 4-6 acceptance criteria
  • Stories are independent and can be developed in any order
  • Stories are sized for one sprint cycle
  • Stories reference related design documentation

Further Reading

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most product spec skills give in 609 tokens

Counted across 483 of the 502 authors here whose files we hold, read 2026-09-06

  • Write the PRD using the templatein 39 of 483, across 36 files
  • Ask one question at a timein 24 of 483
  • Write acceptance criteria in Given-When-Then formatin 24 of 483
  • Write user stories with acceptance criteriain 22 of 483, across 21 files
  • Respect ADRs in areas you touchin 21 of 483, across 17 files
  • Use the domain glossary vocabulary throughout the PRDin 20 of 483, across 16 files
  • Explore the repo to understand the current codebasein 19 of 483, across 15 files
  • Provide testable acceptance criteriain 19 of 483, across 17 files
  • Publish the PRD to the issue trackerin 18 of 483, across 14 files
  • Apply the ready-for-agent triage labelin 15 of 483, across 13 files
  • Prefer existing seams over new onesin 14 of 483, across 12 files
  • Save the PRD as a markdown filein 14 of 483, across 9 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.