Data Model Evolution Planning

D

Daniel Okoye

@daniel-okoye

·

Plan data model evolution by reasoning through schema changes.

5 copies0 forks
Plan data model evolution step by step.

Current model:
{{current_schema}}

New requirements:
{{new_requirements}}

Constraints: {{constraints}}

Think through systematically:

1. REQUIREMENT ANALYSIS: What data needs do the new requirements introduce?

2. GAP ANALYSIS: What is missing in the current model?

3. NORMALIZATION: Should new data be normalized or denormalized?

4. RELATIONSHIPS: What new relationships are needed?

5. BACKWARD COMPATIBILITY: How do we maintain compatibility with existing code?

6. MIGRATION PATH: How do we get from current to target state?

7. DATA POPULATION: How will new fields be populated for existing records?

8. INDEX STRATEGY: What new indexes are needed?

9. QUERY IMPACT: How will this affect existing queries?

10. ROLLOUT PLAN: What is the phased approach?

Details

Category

Coding

Use Cases

Data model evolution planningSchema design reviewFeature data requirements

Works Best With

claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared

Create your own prompt vault and start sharing