AutoGineer
Generated banner for User Stories
Generated logo for User Stories

User Stories

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill assists in the creation of user stories by applying the 3 C's (Card, Conversation, Confirmation) and INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable) frameworks. It transforms feature requests into actionable backlog items complete with descriptions, design references, and detailed acceptance criteria, ensuring that each story is ready for development cycles.

What it does

  • Analyzes features based on provided context and design links.
  • Identifies user roles and distinct user journeys.
  • Drafts user stories using the standard 'As a, I want to, so that' format.
  • Generates 4-6 clear, testable acceptance criteria per story.
  • Ensures stories are sized appropriately for a single sprint cycle.
  • Integrates links to design documentation for visual reference.

When to use it

  • When breaking down large features into smaller, manageable backlog items.
  • When defining clear acceptance criteria for development tasks.
  • When preparing requirements for a new sprint.
  • When standardizing the format of user stories across a project.

Advantages

  • Promotes consistency in backlog documentation.
  • Ensures stories meet the INVEST criteria for better project planning.
  • Provides clear, testable requirements for developers and testers.
  • Connects development tasks directly to design documentation.

Usage examples

“Create user stories for a checkout feature in an e-commerce app using the provided Figma link.”
The agent generates a set of independent user stories for the checkout process, each including a role-based description, the design link, and specific acceptance criteria for validation and edge cases.
“Break down the 'User Profile' feature into small, estimable stories.”
The agent produces a list of granular user stories for profile management, ensuring each is small enough for a single sprint and follows the 3 C's framework.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/user-stories/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip user-stories.zip -d .agents/skills

Documentation by Pawel Huryn

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

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "user-stories", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-execution/skills/user-stories · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download user-stories.zip