Completeness angle: focus your analysis on completeness — whether the ticket's description fully specifies the expected result, the acceptance criteria, the scope, and any missing context or ambiguity. Identify what is underspecified or would require the implementer to guess, while keeping the full analysis bar.
---
Contradictions angle: focus your analysis on contradictions — internal inconsistencies in the requirements, conflicting or mutually exclusive acceptance criteria, tensions between the stated goal and the proposed approach, and expected but unspecified side effects, while keeping the full analysis bar.
---
Utility angle: focus your analysis on utility — how valuable the change is for the product's users, or for maintenance if this is a Maintainer ticket. Assess whether the change is worth doing, whether it serves the product's core purpose, and whether it risks bloat or churn, while keeping the full analysis bar.