review-requirements

<skill_overview> Ensure that the task or requirement definition is clear, complete, and actionable before or during implementation. User asks to review a task description or ticket. User provides a requirements document for a code review. Analyzing a PR description against the implemented code. </skill_overview>

<checklist_requirements_quality> Clarity: Is the goal of the task unambiguous? Can it be interpreted in multiple ways? Acceptance Criteria: Are there clear "Definition of Done" criteria? (Given/When/Then is preferred). Scope Boundaries: Is it clear what is IN scope and what is OUT of scope? Context: Is the "Why" (user value/business goal) explained? Technical Feasibility: Are there obvious technical blockers or missing dependencies mentioned? Edge Cases: Does the task consider error states, empty states, or boundary conditions? </checklist_requirements_quality>