ears
Defines the Easy Approach to Requirements Syntax (EARS) — five natural-language patterns (Ubiquitous, State-driven, Event-driven, Optional Feature, Unwanted Behaviour) plus a Complex composite — and the rules that make a requirement statement clear, concise, unambiguous, testable, and written in active voice with a specific system name. Use this skill whenever an agent must author, review, classify, or rewrite a requirement, validate that an L2 Requirement node (per the input-hierarchization skill) conforms to convention, distinguish a real requirement from a stakeholder goal, or decide whether EARS even applies to a given statement.