Deliver Edge Cases
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.
Install
/plugin marketplace add product-on-purpose/pm-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add product-on-purpose/pm-skills --skill deliver-edge-casesgit clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/deliver-edge-cases ~/.claude/skills/deliver-edge-casesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 ## When NOT to Use - You need story-scoped Given/When/Then checks for handoff -> use `deliver-acceptance-criteria`; this skill catalogs the whole feature's failure surface - The feature is not specified enough to enumerate inputs, states, and limits -> use `deliver-prd` first - A production incident already happened and you want the learning banked -> use `iterate-lessons-log`, then update this catalog with the new case - You need readiness coordination for a launch, not failure analysis -> use `deliver-launch-checklist` ## Instructions When asked to document edge cases, follow these steps: 1. **Define the Feature Scope**
Details
- Skill name
deliver-edge-cases- Repository
- product-on-purpose/pm-skills
- Path
skills/deliver-edge-cases/SKILL.md- License
- Apache-2.0
- Repo updated
- 17 November 2026
FAQ
What does the Deliver Edge Cases skill do?
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.
How do I install the Deliver Edge Cases skill?
Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Deliver Edge Cases popular?
It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.
Related skills
<phase or Classification Skill Name>
819product-on-purpose/pm-skills
<single-line 20-100 word description; include trigger keywords and do not use folded YAML>
Define Hypothesis
819product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
Define Jtbd Canvas
819product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
Measure Experiment Design
819product-on-purpose/pm-skills
Designs an A/B test or experiment with variants, success metrics, sample size, and duration for an existing hypothesis. Use when planning an experiment to validate a product change or test an assumption you have already framed. To articulate the hypothesis itself first, use define-hypothesis.
Sanger Chromatogram QA
2.1kaipoch/medical-research-skills
Use sanger chromatogram qa for data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries.
Measure Experiment Results
819product-on-purpose/pm-skills
Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations. Use after experiments conclude to communicate findings, inform decisions, and build organizational knowledge.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.