Edge Cases

An edge cases document systematically catalogs the unusual, boundary, and error scenarios for a feature. While happy-path flows are typically well-specified, edge cases often get discovered in production . causing bugs, poor user experience, and support burden. Documenting edge cases upfront ensures engineering handles them intentionally and QA knows what to test.

When to Use

• During feature specification before engineering begins
• When preparing QA test plans
• After discovering production bugs to prevent similar issues
• When reviewing PRDs or user stories for completeness
• Before launch to ensure error states have been designed

Instructions

When asked to document edge cases, follow these steps:

1. Define the Feature Scope Clearly describe what feature or flow you're analyzing. Edge cases are specific to context . the same input might be valid in one feature and invalid in another.