user-stories
phuryn/pm-skills
Create well-structured user stories following 3 C's and INVEST criteria with acceptance criteria and design links.
What is user-stories?
This skill generates user stories that follow the 3 C's framework (Card, Conversation, Confirmation) and INVEST criteria. Use it when breaking down features into backlog items, writing user stories, or defining acceptance criteria for development teams.
- Analyzes features and identifies distinct user roles and journeys
- Applies the 3 C's framework to structure stories (Card, Conversation, Confirmation)
- Generates acceptance criteria that are clear, testable, and observable
- Links stories to design files (Figma, Miro, etc.) for visual reference
- Ensures stories follow INVEST principles (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- Sizes stories appropriately for single sprint cycles
How to install user-stories
npx skills add https://github.com/phuryn/pm-skills --skill user-storiesHow to use user-stories
- 1.Provide the product/system name, feature description, design file link (Figma, Miro, etc.), and key assumptions or context
- 2.The skill analyzes the feature and identifies distinct user roles and journeys
- 3.Review the generated user stories, each with title, description, design link, and 4-6 acceptance criteria
- 4.Refine stories as needed through team conversation before adding to sprint backlog
- 5.Use the acceptance criteria as the definition of done for development
Use cases
- Breaking down a new product feature into independent, developable user stories
- Creating backlog items with clear acceptance criteria for a development team
- Defining acceptance criteria for a feature based on design mockups and requirements
- Writing stories for an e-commerce feature like product recommendations or checkout flow
- Documenting user journeys and acceptance criteria for a mobile app feature
- Product managers writing and refining backlog items
- Scrum masters facilitating story creation and refinement
- Development teams needing clear, testable acceptance criteria
- Product owners breaking down features into sprint-ready stories
user-stories FAQ
Card (simple title and one-liner), Conversation (detailed discussion of intent and context), and Confirmation (clear acceptance criteria that define when the story is complete).
Independent (stories don't depend on each other), Negotiable (details can be discussed), Valuable (delivers user value), Estimable (team can estimate effort), Small (completable in one sprint), and Testable (acceptance criteria are clear and verifiable).
Each story should include 4-6 acceptance criteria that are clear, testable, and observable behaviors or system validations.
Yes, the skill generates independent stories that can be developed in any order, though some may have logical dependencies worth discussing during refinement.
Yes, linking to design files (Figma, Miro, etc.) provides visual reference and reduces ambiguity during development and acceptance testing.
Full instructions (SKILL.md)
Source of truth, from phuryn/pm-skills.
name: user-stories description: "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."
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
Related skills
More from phuryn/pm-skills and the wider catalog.
value-prop-statements
Generate targeted value proposition statements for marketing, sales, and onboarding messaging.
value-proposition
Design compelling value propositions using a 6-part JTBD template for clarity and market fit.
wwas
Create structured product backlog items in Why-What-Acceptance format with strategic context and testable outcomes.
ab-test-analysis
Analyze A/B test results with statistical significance, confidence intervals, and ship/extend/stop recommendations.
app-sizzle
>
app-store-screens
>