What problem does it solve? Requirements often reference vague terms like "customer information" or "order details" without defining what fields they contain, causing developers to make conflicting assumptions and producing inconsistent data structures in production. ## Core Features & Use Cases - Formal Notation: Define primitives, composite structures, repeating groups, selections, and optional elements using standard data dictionary symbols (=, +, [a|b], {x}, (x)). - CRUD Matrix Analysis: Cross-reference data entities against system functions to detect missing Create, Read, Update, or Delete requirements before development starts. - Enumeration and Valid Value Specification: Eliminate ambiguous fields by explicitly defining allowed values, formats, ranges, and defaults for every primitive element. - Use Case: Your requirements mention a "chemical record" but nobody has defined its fields. Use this Skill to decompose it into primitives (CAS number, quantity, expiration date), specify valid values, and run a CRUD matrix that reveals a missing Alert History feature. ## Quick Start Ask the agent to build a data dictionary for your project by defining every data element referenced in your requirements and running a CRUD completeness analysis.
