What problem does it solve? Gathered requirements are often ambiguous, conflicting, or incomplete, leading teams to design solutions on unvalidated assumptions. This Skill structures the analysis of elicited requirements so they are clear, consistent, feasible, and traceable before engineering work starts. ## Core Features & Use Cases - Requirement Quality Assessment: Evaluates clarity, completeness, consistency, testability, and traceability of each requirement. - Classification & Structuring: Organizes requirements into functional, non-functional, and constraint categories with dependencies, risks, and assumptions documented. - Conflict & Gap Detection: Identifies contradictory expectations, undefined ownership, and open questions, escalating uncertainty to clarification workflows. - Use Case: A product team finishing stakeholder interviews uses this Skill to turn raw notes into a structured requirements specification with a readiness assessment, so architects can begin design with confidence. ## Quick Start Analyze the requirements in my project brief and produce a structured requirements specification with classifications, risks, and a readiness assessment.