Run any Skill in Manus with one click

user-story-acceptance-criteria

Stars2

Forks0

UpdatedJanuary 2, 2026 at 18:58

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

michaellperry

michaellperry/aaad

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

More from this repository

same repository

design-system-patterns

michaellperry/aaad

Design system patterns for reusable UI via atomic design, Tailwind tokens/variants, and accessibility. Use when creating atoms/molecules, theming, or hardening a11y.

2026-01-112

ef-core-patterns

michaellperry/aaad

Entity Framework Core best practices for configuration, queries, concurrency, and multi-tenancy.

2026-01-112

frontend-architecture-patterns

michaellperry/aaad

Frontend architecture patterns for React apps (React Router 7, TanStack Query). Use when planning features, defining routes, data strategies, and component gaps.

2026-01-112

infrastructure-standards

michaellperry/aaad

Infrastructure standards for Docker, scripts, middleware, and authentication in multi-tenant deployments.

2026-01-112

integration-testing-performance

michaellperry/aaad

Integration testing performance optimization, test parallelization, cleanup strategies, and CI/CD categorization patterns. Use when optimizing test execution speed, managing test data, or structuring tests for automated pipelines.

2026-01-112

minimal-api-patterns

michaellperry/aaad

ASP.NET Core Minimal APIs patterns for endpoints, DTOs, validation, and service integration. Use when implementing API endpoints, defining request/response contracts, or structuring API projects with clean separation of concerns.

2026-01-112

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