maister:problem-classifier

To classify business requirements into the correct domain modeling problem class, describe your feature to the Skill. It scans text or UI mockups, asks targeted clarifying questions, and maps inputs to CRUD, Transformation, Integration, or Resource Contention classes.

The four domain modeling problem classes are CRUD, Transformation and Presentation, Integration, and Resource Contention. Identifying the correct class prevents architectural misalignment by guiding the selection of appropriate building blocks and implementation patterns.

You need to identify a Resource Contention problem class when features involve booking limited slots or managing constrained assets. The Skill recommends aggregate design with atomic concurrency checks and optimistic locking to prevent critical underengineering.

Yes, you can use this problem classifier with UI mockups and Polish language inputs. The Skill supports signal scanning of text and mockup inputs, and conducts targeted clarifying questions in both English and Polish to resolve classification ambiguity.

The best way to prevent architectural misalignment when modeling new features is to classify the requirement early. The Skill identifies the correct problem class and delivers implementation recommendations with rationale to avoid costly rework from overengineering or underengineering.

Your software architecture suffers from overengineering and unnecessary service layers when business requirements are misclassified into incorrect modeling problem classes. Accurate classification prevents adding unneeded aggregates and ensures appropriate implementation patterns are applied.