Verified:GitHub

planning-data-architecture

Produce story-scoped data architecture with schema, indexes, and migration considerations.

Updated Aug 27, 2026

Search Tags:#schema design #database migration #indexes #data architecture #system planning #contract alignment #access patterns

Ready to run

npx skills add https://github.com/gleeb/ai-registry --skill planning-data-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning-data-architecture
Source: https://github.com/gleeb/ai-registry/tree/main/systems/sdlc/skills/planning-data-architecture
Command: npx skills add https://github.com/gleeb/ai-registry --skill planning-data-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents data model drift by producing a story-scoped data architecture that is validated against the story requirements and any consumed shared contracts.

Core Features & Use Cases

Per-story data discovery: Reads story scope and supporting architecture docs to identify entities, relationships, and implied access patterns.
Contract-aligned schema design: Uses consumed contracts as authoritative for shared entities and ensures schema supports required contract terms.
Index- and lifecycle-aware output: Maps read/write patterns to indexes, defines integrity and migration considerations, and writes the final architecture to the story’s data document.

Quick Start

Use planning-data-architecture for a specific user story by asking it to produce data architecture for US-NNN-name and write the result to plan/user-stories/US-NNN-name/data.md.

Frequently Asked Questions about planning-data-architecture

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

FAQPage Schema

How do I design database schemas aligned with user story requirements?▼

To design database schemas for user stories, read the story scope and supporting architecture docs to identify entities and relationships, ensuring schema design aligns with consumed shared contracts. This prevents data model drift by validating architecture against story requirements.

What is story-scoped data architecture and when do I need it?▼

Story-scoped data architecture is a data model validated against a specific user story's requirements and consumed contracts. You need it during Phase 3 planning when dispatching data architecture work for a single user story that includes data candidate domains.

How do I map database indexes to query access patterns?▼

Map database indexes to query access patterns by discovering implied read and write patterns from story planning documents, then explicitly defining index mappings that support those operations alongside integrity and migration considerations in the final data document.

Can I use existing shared contracts when planning data architecture?▼

Yes, you can use existing shared contracts when planning data architecture by treating them as authoritative sources for shared entities. This ensures the story-scoped schema design supports all required contract terms and prevents model drift.

What's the best way to document database migration and integrity considerations?▼

The best way to document database migration and integrity considerations is to write them into a dedicated data architecture file. Define lifecycle-aware rules by mapping read/write patterns to indexes and outputting the final architecture to the story's data document.

Does planning data architecture work for multiple user stories at once?▼

No, planning data architecture is scoped for a single user story. It produces a story-specific data document by discovering entities and access patterns from that individual story's requirements and related planning documents.