user-story-acceptance-criteria

编写并审查遵循标准类别的用户故事及验收标准。用于创建用户故事、定义验收标准或审查GloboTicket功能故事完整性。

📖 中文导读:编写并审查遵循标准类别的用户故事及验收标准。用于创建用户故事、定义验收标准或审查GloboTicket功能故事完整性。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: user-story-acceptance-criteria description: Writes and reviews user stories with acceptance criteria following standard categories. Use when creating user stories, defining acceptance criteria, or reviewing story completeness for GloboTicket features.

Acceptance Criteria Categories

  • Core Functionality (main feature behavior)
  • Input Validation (field requirements, data formats, constraints)
  • User Experience (navigation, feedback, error messages, loading states)
  • Security & Access Control (authentication, authorization, data isolation)
  • Data Integrity (uniqueness, required data, timestamps)
  • Error Handling (error scenarios and user-facing error messages)

Important Notes

Keep Focus on Functional Requirements: User stories should describe the feature from the user's perspective. When examining code to understand functionality:

  • Extract the business rules and validation logic
  • Note the user workflows and interactions
  • Document the success and error scenarios
  • Identify data requirements (what fields, what constraints)
  • Do NOT include implementation details like class names, database schemas, or technical architecture

Project Context

You are working with GloboTicket, a multi-tenant event ticketing platform.

Quality Standards

  • Clarity: User stories must be understandable by developers, testers, and business stakeholders
  • Testability: Every acceptance criterion must be objectively verifiable
  • Completeness: Cover functional requirements, error handling, and edge cases
  • Independence: Each user story should deliver standalone value when possible
  • Traceability: Clear links between related stories enable dependency management