data-plan

Derive a DATA_PLAN.md with entities, relationships, storage, and migrations from an approved Ur-Plan.

Updated Apr 19, 2026

Search Tags:#schema-design #data-model #design-doc #data-plan #backend-planning #ur-plan

Ready to run

npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill data-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-plan
Source: https://github.com/Tschonsen/spec-driven-claude-development/tree/main/plugin/sdcd/skills/data-plan
Command: npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill data-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It derives a concrete Data-Plan from an approved Ur-Plan to guide data modeling decisions and keep schema work aligned with project goals.

Core Features & Use Cases

Derives core entities, relationships, storage options, and migration outlines from design/UR_PLAN.md.
Outputs design/DATA_PLAN.md to serve as the canonical data-layer blueprint for backend planning.
Supports scoping and validation by dispatching challenger trio for security, performance, and maintainability feedback.

Quick Start

Use the data-plan skill after UR_PLAN approval to generate design/DATA_PLAN.md from design/UR_PLAN.md and prepare for the backend plan.

Frequently Asked Questions about data-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn an approved project plan into a concrete data model and schema design?▼

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.

When do I need to generate a data plan for backend planning?▼

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.

How do I derive entities and storage choices for my backend schema?▼

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.

Can I validate my data model for security and performance before backend implementation?▼

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.

What is the best way to outline database migrations from an initial project design?▼

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.

Do I need an approved Ur-Plan before defining core entities and relationships?▼

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.