deliver-edge-cases

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Edge Cases
3 
4An 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.
5 
6## When to Use
7 
8- When you need to enumerate failure modes, race conditions, timeouts, and boundary or limit scenarios - everything that can go wrong - and define a recovery path for each
9- During feature specification before engineering begins
10- When preparing QA test plans
11- After discovering production bugs to prevent similar issues
12- When reviewing PRDs or user stories for completeness
13- Before launch to ensure error states have been designed
14 
15## When NOT to Use
16 
17- You need story-scoped Given/When/Then checks for handoff -> use `deliver-acceptance-criteria`; this skill catalogs the whole feature's failure surface
18- The feature is not specified enough to enumerate inputs, states, and limits -> use `deliver-prd` first
19- A production incident already happened and you want the learning banked -> use `iterate-lessons-log`, then update this catalog with the new case
20- You need readiness coordination for a launch, not failure analysis -> use `deliver-launch-checklist`
21 
22## Instructions
23…