Identify and document edge cases using the BOUNDARY framework.
npx skills add https://github.com/tarunccet/pm-skills --skill edge-cases-tarunccet
Please help me install this Agent Skill. Skill: edge-cases Source: https://github.com/tarunccet/pm-skills/tree/main/pm-execution/skills/edge-cases Command: npx skills add https://github.com/tarunccet/pm-skills --skill edge-cases-tarunccet
This Skill helps product teams systematically discover error states, boundary conditions, and recovery paths that specs and happy-path designs often miss, reducing post-launch defects and rework.
Run an edge case analysis on the provided PRD or user story and return an Edge Case Matrix with categorized cases, severity levels, recommended handling, and acceptance criteria.
High-intent search queries and answers about installing and using this skill.
To identify edge cases in a PRD, apply the BOUNDARY framework to systematically surface boundary conditions, outages, and recovery paths. This produces an Edge Case Matrix with severity levels and acceptance criteria ready for issue tracker import during sprint preparation.
The BOUNDARY framework is a structured method for QA test design covering Boundaries, Outages, Unusual inputs, Network, Data, Access, Race conditions, and Yesterday's assumptions. It ensures comprehensive failure mode coverage by systematically categorizing potential error states missed by happy-path designs.
Document failure modes and recovery paths by generating an Edge Case Matrix that categorizes each scenario with its severity, expected behavior, handling recommendation, and acceptance criteria. This structured risk assessment output helps reduce post-launch defects and rework.
Yes, boundary analysis supports post-incident analysis and bug prevention by applying the BOUNDARY framework to review what went wrong. It surfaces hidden failure modes and documents recovery paths to prevent similar error states in future feature releases.
Yes, edge case analysis outputs an Edge Case Matrix containing categorized cases, severity levels, expected behavior, handling recommendations, and acceptance criteria specifically structured for direct import into standard issue tracking tools.
Run edge case analysis after writing a PRD, before sprint planning, during QA test design, or when reviewing acceptance criteria. Applying it at these stages catches failure modes early, reducing post-launch defects and rework.
lalaABCGenerate a PRODUCT.md specification for a Warp feature.
tarunccetGenerate step-by-step test scenarios with objectives and expected outcomes from user stories and acceptance criteria.
VirtoCommerceGenerate structured end-to-end test plans from scenario catalogs and feature requirements.
product-on-purposeCatalog edge cases for features, APIs, and user workflows using a structured template.
