What problem does it solve? Choosing the wrong modeling approach for a business feature leads to over-engineered CRUD screens or under-protected concurrent operations. This Skill analyzes a requirement, UI mockup, or feature description and assigns it to one of four modeling problem classes so implementation effort matches the actual risk. ## Core Features & Use Cases - Four-class classification: Sorts requirements into CRUD, Transformation & Presentation, Integration, or Resource Contention based on hard signals like side effects, cross-system sync, and concurrency. - Targeted clarifying questions: Asks discriminating questions when concurrency, integration, or state gating is ambiguous instead of guessing. - Structured output: Produces a primary class, optional secondary class, evidence-based rationale, open questions, and a recommended implementation direction. - Use Case: Given a feature request for a seat-booking flow, the classifier detects concurrent availability checks and classifies it as Resource Contention, recommending locking or reservation patterns rather than plain CRUD. ## Quick Start Ask the assistant to classify your feature description into a modeling problem class using the problem-classifier skill.