Deliver Edge Cases

This walks you through documenting edge cases during specification or QA planning. It covers input validation, boundary conditions, error states, concurrency issues, and recovery paths. The real value is the systematic approach: instead of discovering problems in production, you think through what happens when inputs are empty or too long, when networks fail, when users double-click, or when data changes mid-save. Each edge case gets a priority and a defined recovery path. It's basically a checklist to force completeness before code ships. Works best when you have a feature spec that covers the happy path but feels underspecified on the what-ifs.

skills.sh installs: 934
GitHub stars: 794
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add product-on-purpose/pm-skills --skill deliver-edge-cases --agent claude-code

Installs into .claude/skills of the current project.

Files

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

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
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