Menu
Walk branching paths and boundary conditions in content, reporting only unhandled edge cases.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Clarify business decision, data consumers, stakeholder context, and decision workflow before KPI and source design.
Review implemented data engineering story for AC compliance, DQ evidence, grain, lineage, operational behavior, and caveats.
Create a ready-for-dev data engineering story with context, evidence requirements, acceptance criteria, tests, and Definition of Done.
Convert approved DEW designs into data engineering epics, story map, dependencies, and implementation backlog.
Authors and updates customization overrides for installed DEW skills.
Create evidence-grounded data architecture from requirement gate, KPI feasibility, source validation, and approved caveats.
| name | dew-review-edge-case-hunter |
| description | Walk branching paths and boundary conditions in content, reporting only unhandled edge cases. |
Goal: Find unhandled edge cases by systematically walking branches and boundaries.
Do not comment on whether the content is generally good or bad. Report only missing handling.
content — diff, full file, function, spec, story, or data artifact.also_consider optional — specific risk areas to include.Walk:
For DEW/data engineering artifacts, also walk:
Revisit each edge class and keep only unhandled conditions.
Return a JSON array of objects:
[
{
"location": "artifact or file section",
"trigger_condition": "short edge condition",
"guard_snippet": "minimal guard or mitigation",
"potential_consequence": "what could go wrong"
}
]
An empty array is valid only after exhaustive review.