Acceptance Criteria Edge Case Identifier

Pro v1.0.0 1 view

Systematically analyzes feature descriptions and existing acceptance criteria to identify missing edge cases across six categories. Generates specific, testable acceptance criteria for each missing edge case with priority ratings.

What You Get

Catches the 50% of defects that stem from inadequate acceptance criteria before development begins, reducing 1-2 sprints of rework.

The Problem

Product managers and QA engineers often write acceptance criteria that only cover the happy path, leading to 50% of software defects stemming from incomplete requirements. Edge cases around empty states, boundary conditions, error scenarios, concurrent users, invalid inputs, and network failures are frequently missed until they become bugs in production.

The Solution

This skill applies a systematic framework to analyze features across six edge case categories: empty/null states, boundary conditions, error scenarios, concurrent/conflict scenarios, input validation, and network/performance. For each identified gap, it generates specific, testable acceptance criteria with priority ratings (Critical/High/Medium/Low) based on likelihood and user impact. The output includes coverage assessment, detailed edge case analysis, priority summary, and estimated bugs prevented.

How It Works

  1. 1 Analyze current acceptance criteria to assess coverage percentage and identify what's already covered
  2. 2 Apply systematic edge case framework across six categories: empty states, boundary conditions, errors, concurrency, validation, network
  3. 3 Identify missing edge cases with clear descriptions and user impact assessment
  4. 4 Prioritize edge cases by likelihood and severity (Critical/High/Medium/Low)
  5. 5 Generate specific, testable acceptance criteria for each identified edge case
  6. 6 Provide coverage summary with estimated bugs prevented and recommended next steps

What You'll Need

  • Feature description explaining what the feature does
  • Current acceptance criteria (even if minimal or happy-path only)

Get This Skill

Requires Pro subscription ($9/month)

Have Feedback?

Help us improve this skill by sharing your ideas and suggestions.

Request Improvements

Examples

API Rate Limiting Technical Edge Cases

Analyzes an API rate limiting feature to identify missing boundary conditions, race conditions, and distributed systems edge cases. Demonstrates technical infrastructure-level analysis including off-by-one errors, concurrent request handling, and failure mode decisions.

View example

Password Reset Feature Security Analysis

Analyzes a basic password reset flow to identify missing security, validation, and error handling edge cases. Demonstrates comprehensive coverage of authentication-related features including email enumeration prevention, rate limiting, and token expiration.

View example

Subscription Checkout Payment Edge Cases

Analyzes a subscription checkout flow to identify missing payment failures, validation, and concurrent user edge cases. Demonstrates handling of e-commerce scenarios including card declines, gateway failures, and duplicate submission prevention.

View example
View all examples