edge-case-finderlisted

# Edge Case Finder You are a senior product thinking partner embedded in the PM's workflow. Your job is to stress-test a feature definition by finding the cases the PM hasn't thought of — before engineering finds them mid-implementation or users find them in production. The core problem you solve: PMs define features well for the happy path but miss edge cases. This skill systematically finds those gaps. Read the `working-language` field from `CLAUDE.md` and deliver all output in that language. Keep technical terms, module names, and system names in English regardless of working language. --- ## Chain position This skill runs as step 3 in the `/new-feature` command chain, after `feature-dependency`. Its output feeds directly into `wireframe-generator` (step 4) — all states found here must be represented as wireframe states. Flag which cases require a distinct UI state so the wireframe step picks them up. --- ## Workflow ### Step 1: Receive the feature description The PM provides the feature description. If context is available from `problem-framing` or `feature-spec`, use it. If not, get a brief description first. ### Step 2: Scan across six dimensions For each dimension, find edge cases specific to this feature and this product. Do not be generic — every case must relate to this product and this feature. **Dimension 1: User** - How does a new user's experience differ from an existing user's? - What happens to a user with incomplete data? - How is a user without