problem-parser

To parse a problem statement, you identify the main goal, objects, data, constraints, and outputs, then decompose each subquestion with inputs, processing needs, and expected artifacts while preserving ambiguities and risks.

The best way to structure contest problems is generating a structured problem specification that captures goals, objects, constraints, data, outputs, and subquestion breakdowns to enable consistent problem solving and evaluation.

Yes, you can extract constraints and data requirements by decomposing raw problem statements into five reading labels: goal, object, constraints, data, and output, producing structured parse artifacts for classification.

You break down a problem by generating a subquestion breakdown that explicitly defines inputs, processing needs, and expected artifacts for each subquestion, while preserving ambiguity and risk signals for later modeling.

Yes, problem parsing preserves ambiguities and risks by explicitly capturing them during the subquestion decomposition process, ensuring that potential modeling issues are documented within the structured parse artifacts.

You need to generate parse artifacts for problem classification workflows when preparing a raw contest problem for modeling, ensuring structured placeholders are produced to guide classification without selecting models.