problem-classifier

Classifies business requirements into CRUD, Transformation, Integration, or Resource Contention modeling classes.

Updated Nov 19, 2020
One-click install
npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill problem-classifier-kwojtasinski-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-classifier
Source: https://github.com/kwojtasinski-repo/ECommerceApp/tree/main/.github/skills/problem-classifier
Command: npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill problem-classifier-kwojtasinski-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about problem-classifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify a business requirement into a modeling problem class?

Provide the requirement, UI mockup, or feature description and the classifier scans it for signals from all four classes. It returns a primary class, an optional secondary class, the evidence behind the choice, and a recommended implementation direction.

What are the four modeling problem classes?

The classes are CRUD for store-and-retrieve operations, Transformation & Presentation for read-only derived output, Integration for cross-system sequencing and failure handling, and Resource Contention for operations guarding against concurrent state changes.

When should a feature be classified as Resource Contention instead of CRUD?

Choose Resource Contention when the operation must protect an answer to "can I do X?" against concurrent changes, such as booking, locking, or assignment. Plain save, edit, or delete flows without shared-state contention remain CRUD.

What happens when the classification is ambiguous?

The classifier asks targeted clarifying questions about concurrency, integration boundaries, and state gating rather than guessing. It never assigns a class when the signals affecting other users or systems are unclear.

Can a requirement have more than one problem class?

Yes, the output supports a primary class plus an optional secondary class. For example, a checkout flow may be primarily Integration with a secondary Resource Contention concern for inventory reservation.