What problem does it solve? Requirements often hide unstated decisions, disguise simple status changes as domain behavior, or lock in implementations too early. This Skill reviews requirement text, tickets, or specs on explicit request and exposes those problems before implementation begins. ## Core Features & Use Cases - Problem vs Solution Check: Flags technical choices that obscure the real business need while ignoring settled constraints. - CRUD Detection: Identifies commands whose only effect is a database status change and probes for observable behavior like counters, quotas, and reversibility. - Hidden Decision Signal Map: Scans domain clusters such as money, retention, roles, integrations, status transitions, dates, and search to surface targeted questions. - Rigid Quantifier Probe: Tests words like always, never, only, and must against boundary scenarios. - Use Case: Paste a ticket like "users can always cancel orders" and receive quoted issues, discriminating questions, and a concrete rewrite into observable behavior. ## Quick Start Ask the assistant to critique the pasted requirement text or ticket and report hidden decisions with a suggested rewrite.