Data Requirements and Dictionary for a Feature
Specify the data a feature needs.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Define data requirements. Feature: [FEATURE]. Users and workflows: [USERS_AND_WORKFLOWS]. Systems involved: [SYSTEMS]. Privacy context: [PRIVACY_CONTEXT]. Produce a data dictionary table: Field | Description | Type | Required | Allowed values or format | Source | Owner | Retention | Sensitivity (public, internal, personal, sensitive) | Notes. Include audit fields (created, updated, by whom), identifiers, and status fields. Add business rules (uniqueness, relationships, calculations with formulas), data quality checks, and migration needs. Add privacy questions to resolve: lawful basis and purpose, minimization (can we avoid collecting this?), deletion and export, access control, and cross-border transfer [VERIFY with a privacy specialist in [JURISDICTION]]. Include examples of valid and invalid values for the three most complex fields and a list of open questions. Mark which fields are needed at launch and which can wait, note any field that duplicates data held elsewhere (and which source is authoritative), and list the retention period for each personal-data field.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.