user-story-acceptance-criteria
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.
When & Why to Use This Skill
This Claude skill streamlines the software development lifecycle by automating the creation and review of Agile user stories and acceptance criteria. It ensures that product requirements are comprehensive, testable, and aligned with industry standards, covering critical aspects such as core functionality, security, and user experience to bridge the gap between stakeholders and engineering teams.
Use Cases
- Drafting detailed user stories for new product features to ensure all business requirements and user perspectives are captured.
- Generating standardized acceptance criteria for developers and QA teams to ensure objective verifiability and high-quality deliverables.
- Reviewing existing backlog items for completeness, identifying missing edge cases, and ensuring stories are independent and valuable.
- Translating complex business rules and validation logic into clear functional requirements without including restrictive technical implementation details.
- Auditing project documentation for the GloboTicket platform to maintain consistency across multi-tenant event ticketing features.
| 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
Recommended 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