Back to Details

user-stories

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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
遵循3C原则（Card、Conversation、Confirmation）和INVEST标准创建用户故事，生成包含描述、设计链接及验收标准的故事内容。
适用场景： 编写用户故事、将功能拆分为用户故事、创建待办事项或定义验收标准时使用。
参数：
  • $PRODUCT
    ：产品或系统名称
  • $FEATURE
    ：需拆分为故事的新功能
  • $DESIGN
    ：设计文件链接（Figma、Miro等）
  • $ASSUMPTIONS
    ：关键假设或上下文信息

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
  1. 分析功能：基于提供的设计和上下文信息进行分析
  2. 识别用户角色及不同的用户旅程
  3. 应用3C框架：
    • Card：简洁标题和一句话描述
    • Conversation：关于需求意图的详细讨论
    • Confirmation：清晰的验收标准
  4. 遵循INVEST标准：独立（Independent）、可协商（Negotiable）、有价值（Valuable）、可估算（Estimable）、小粒度（Small）、可测试（Testable）
  5. 使用通俗易懂的语言，确保小学毕业生也能理解
  6. 关联设计文件链接，提供视觉参考
  7. 输出结构化格式的用户故事

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]
标题： [功能名称]
描述： 作为[用户角色]，我想要[执行操作]，以便[获得收益]。
设计： [设计文件链接]
验收标准：
  1. [清晰、可测试的标准]
  2. [可观察的行为]
  3. [系统能正确验证]
  4. [边缘情况处理]
  5. [性能或可访问性考量]
  6. [集成点相关要求]

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.
标题： 最近浏览板块
描述： 作为一名在线购物者，我希望在商品页面看到“最近浏览”板块，以便轻松回访我之前关注过的商品。
设计： [Figma链接]
验收标准：
  1. 对于之前至少浏览过1件商品的所有用户，“最近浏览”板块会显示在商品页面底部。
  2. 对于会话中首次访问商品页面的用户，不显示该板块。
  3. 当前浏览的商品不会出现在展示列表中。
  4. 板块展示包含图片、标题和价格的商品卡片或缩略图。
  5. 每个商品卡片会标注浏览时间（例如：“5分钟前浏览”）。
  6. 点击商品卡片可跳转到对应的商品页面。

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
  • 该功能的完整用户故事集合
  • 每个故事包含标题、描述、设计链接及4-6条验收标准
  • 故事相互独立，可按任意顺序开发
  • 故事粒度适合一个迭代周期完成
  • 故事关联相关设计文档

Further Reading

拓展阅读