AgentAlley
Submit

User stories skill

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

by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗

Use now

Files of User stories

phuryn/main1 file shown
SKILL.md
Show the full text75 lines
user-stories/SKILL.md75 lines · 2.9 KB
Outline
RawView on GitHub

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
1---
2name: user-stories
3description: "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."
4---
5# User Stories
6 
7Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.
8 
9**Use when:** Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.
10 
11**Arguments:**
12- `$PRODUCT`: The product or system name
13- `$FEATURE`: The new feature to break into stories
14- `$DESIGN`: Link to design files (Figma, Miro, etc.)
15- `$ASSUMPTIONS`: Key assumptions or context
16 
17## Step-by-Step Process
18 
191. **Analyze the feature** based on provided design and context
202. **Identify user roles** and distinct user journeys
213. **Apply 3 C's framework:**
22 - Card: Simple title and one-liner
23 - Conversation: Detailed discussion of intent
24 - Confirmation: Clear acceptance criteria
254. **Respect INVEST criteria:** Independent, Negotiable, Valuable, Estimable, Small, Testable
265. **Use plain language** a primary school graduate can understand
276. **Link to design files** for visual reference
287. **Output user stories** in structured format
29 
30## Story Template
31 
32**Title:** [Feature name]
33 
34**Description:** As a [user role], I want to [action], so that [benefit].
35 
36**Design:** [Link to design files]
37 
38**Acceptance Criteria:**
391. [Clear, testable criterion]
402. [Observable behavior]
413. [System validates correctly]
424. [Edge case handling]
435. [Performance or accessibility consideration]
446. [Integration point]
45 
46## Example User Story
47 
48**Title:** Recently Viewed Section
49 
50**Description:** As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.
51 
52**Design:** [Figma link]
53 
54**Acceptance Criteria:**
551. The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
562. It is not displayed for users visiting the first product page of their session.
573. The current product itself is excluded from the displayed items.
584. The section showcases product cards or thumbnails with images, titles, and prices.
595. Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
606. Clicking on a product card leads the user to the corresponding product page.
61 
62## Output Deliverables
63 
64- Complete set of user stories for the feature
65- Each story includes title, description, design link, and 4-6 acceptance criteria
66- Stories are independent and can be developed in any order
67- Stories are sized for one sprint cycle
68- Stories reference related design documentation
69 
70---
71 
72### Further Reading
73 
74- [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)
75 

Discussion

Alternatives

Academy guideStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Business & ops · Apache-2.0Analyze feature requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions. · MITAdvocacy program designerUse when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规Business & ops · Apache-2.0Act as a product managerGuides the AI to act as a product manager, assisting in writing product requirement documents and addressing product-related queries.Business & ops · CC0-1.0

Browse more free Claude skills or everything in Product.