deliver-edge-cases SKILL.md skillA
deliver-edge-cases from product-on-purpose/pm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add product-on-purpose/pm-skills/deliver-edge-cases@v2.1.1Pins v2.1.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- product-on-purpose/pm-skills
- Path
skills/deliver-edge-cases/SKILL.md- Versions recorded
- 5
- Latest version
- v2.1.1, committed Jun 13, 2026
- First version recorded
- Apr 23, 2026
- Size
- 4,342 bytes
- Repository stars
- 790
- License
- Apache-2.0
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # 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 …
Read the whole file at its exact version.
How to install
mdr add product-on-purpose/pm-skills/deliver-edge-cases@sha256:36d1f89195972d49The line at the top of this page pins the label v2.1.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_v54rfd46vwflg4m7)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 23, 2026 and Jun 13, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.1.1 latest | 2026-06-13 | 01716da | 4,342 B | A | view · diff |
| v2.1.0 | 2026-06-10 | bf23914 | 4,048 B | A | view · diff |
| v2.0.1 | 2026-06-10 | b8ccff6 | 3,368 B | A | view · diff |
| v2.0.0 | 2026-05-20 | be1352b | 3,192 B | A | view · diff |
| v2.0.0 | 2026-04-23 | 8ab0f81 | 3,186 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4342 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
product-on-purpose/pm-skills · 790 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v54rfd46vwflg4m7 GET https://markdownregistry.com/api/v1/resolve?ref=product-on-purpose/pm-skills/deliver-edge-cases GET https://markdownregistry.com/api/v1/blob/36d1f89195972d49e334581c9080f7352f66f451a2507fe7b391c1c4b251962f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.