User Stories
Pawel HurynCommunityCreated by Pawel Huryn
- Skill
- Content generator
- Business and productivity
- MIT
- No issues found
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
Download the skill as a ZIP:
https://autogineer.com/agent-skills/phuryn/user-stories/downloadUnzip 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
Analyze the feature based on provided design and context
Identify user roles and distinct user journeys
Apply 3 C's framework:
Card: Simple title and one-liner
Conversation: Detailed discussion of intent
Confirmation: Clear acceptance criteria
Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
Use plain language a primary school graduate can understand
Link to design files for visual reference
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:
[Clear, testable criterion]
[Observable behavior]
[System validates correctly]
[Edge case handling]
[Performance or accessibility consideration]
[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:
The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
It is not displayed for users visiting the first product page of their session.
The current product itself is excluded from the displayed items.
The section showcases product cards or thumbnails with images, titles, and prices.
Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
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.mdAdded by AutoGineer856 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.9 KiB
SKILL.md
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
Analyze the feature based on provided design and context
Identify user roles and distinct user journeys
Apply 3 C's framework:
Card: Simple title and one-liner
Conversation: Detailed discussion of intent
Confirmation: Clear acceptance criteria
Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
Use plain language a primary school graduate can understand
Link to design files for visual reference
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:
[Clear, testable criterion]
[Observable behavior]
[System validates correctly]
[Edge case handling]
[Performance or accessibility consideration]
[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:
The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
It is not displayed for users visiting the first product page of their session.
The current product itself is excluded from the displayed items.
The section showcases product cards or thumbnails with images, titles, and prices.
Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
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
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.
Related skills
Marketing Plan
Corey Haines· Community
Generates a comprehensive, executable 12-month marketing plan structured by the AARRR framework for fractional CMOs and founders.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskGitHub stars of the source repository59k
Revops
Corey Haines· Community
Expert guidance for designing and optimizing revenue operations, lead lifecycle management, and marketing-to-sales handoff processes.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Ab Testing
Corey Haines· Community
A comprehensive framework for planning, executing, and analyzing statistically rigorous A/B tests and growth experimentation programs.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Pricing
Corey Haines· Community
Expert guidance on SaaS pricing strategy, packaging, monetization, and auditing pricing pages for human and AI-agent readability.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Community Marketing
Corey Haines· Community
A strategic framework for building and managing online communities to drive product growth, brand loyalty, and user engagement.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Paywalls
Corey Haines· Community
Expert guidance for designing and optimizing in-app upgrade flows, paywalls, and feature gates to maximize conversion.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download user-stories.zip