data-plan

To turn an approved plan into a concrete data model, you derive a DATA_PLAN.md from the approved Ur-Plan. This process extracts core entities, relationships, and storage options to guide backend planning and schema work.

You need a data plan for backend planning when a project requires a structured data schema. It is generated after UR_PLAN approval to define entities, relationships, storage choices, and database migrations.

You derive entities and storage choices by processing an approved design/UR_PLAN.md file. The workflow extracts these schema components and outputs them into a design/DATA_PLAN.md file to serve as the canonical data-layer blueprint.

Yes, you can validate your data model by dispatching a challenger trio. This mechanism reviews the generated data plan to provide feedback on security, performance, and maintainability before backend implementation.

The best way to outline database migrations from an initial design is by deriving them from the approved UR_PLAN.md. This ensures the migration outlines align with project goals and are documented in the DATA_PLAN.md.

Yes, you need an approved Ur-Plan before defining core entities and relationships. The data planning process strictly derives the data schema and enforces project scope from the existing design/UR_PLAN.md document.