# Edge Case Elicitor

> edge-case-elicitor

- Skill: `45ck/edge-case-elicitor` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 45ck/edge-case-elicitor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/45ck/edge-case-elicitor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: 45ck (https://skillmd.com/u/45ck)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/45ck/edge-case-elicitor

---

# edge-case-elicitor

## Purpose
Generate realistic boundary, invalid, exceptional, and rarely discussed cases from normal requirements.

## Trigger this skill when
- A feature looks simple and therefore risky to under-specify.
- Validation, permissions, workflow branching, or time/state logic exists.
- Acceptance criteria are too happy-path heavy.

## Expected inputs
- requirements
- acceptance criteria
- data rules
- workflow states

## Deliverables
- edge-case catalogue
- negative scenarios
- follow-up questions

## Operating procedure
1. Inspect actor, data, timing, ordering, concurrency, state, limits, and environment assumptions.
2. Generate invalid, missing, duplicated, stale, partial, unauthorized, boundary, and sequencing scenarios.
3. Mark which cases need requirement clarification vs direct acceptance criteria.

## Quality gates
- Cases are plausible, not random.
- Edge cases map back to a real workflow or data rule.
- Critical failure modes are represented.

## Handoff targets
- acceptance-criteria-writer
- verification/test packs later
- ambiguity-hunter

## Output style
- Be explicit about uncertainty.
- Prefer short, testable statements over long prose.
- Surface risk and ambiguity instead of guessing.
- Separate facts, assumptions, constraints, and open questions.

## Failure modes to avoid
- Do not invent stakeholder intent.
- Do not convert preferences into mandatory requirements without evidence.
- Do not hide unresolved ambiguity behind polished wording.
- Do not collapse functional, non-functional, and business rule concerns into one blob.

## Minimum output skeleton
```md
## Summary
## Findings
## Structured outputs
## Assumptions
## Constraints
## Open questions
## Recommended next skill
```