What problem does it solve? Teams often jump from vague requirements straight to implementation, producing designs with missing concepts, untested assumptions, and blurred interface boundaries. This Skill enforces a disciplined design workflow that separates problems from solutions and converts requirements into verifiable contracts before code is written. ## Core Features & Use Cases - Problem Framing: Separates observations, assumptions, problem statements, objectives, and measurable success criteria before any design work begins. - Domain Model Completeness Audits: Checklists for missing concepts, states, constraints, failure modes, and authority rules in a use case. - Design by Contract: Converts natural language requirements into preconditions, postconditions, invariants, failure guarantees, and executable contract tests. - Interface/Implementation Separation: Eliminates caller-side branching by designing boundaries around caller intent rather than technical details. - Use Case: Before building a payment retry feature, use the Skill to produce a Problem Framing Package, a PaymentAttempt domain model audit, retry contracts with test oracles, and a review-ready implementation spec. ## Quick Start Ask the agent to apply mino-problem-framing to your feature request, for example: help me frame this problem before designing, users complain the report is slow.