phase-1-schema

Define glossary terms, entities, relationships, and data schema for projects.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/joshua3403/giit-template --skill phase-1-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-1-schema
Source: https://github.com/joshua3403/giit-template/tree/main/.agent/skills/phase-1-schema
Command: npx skills add https://github.com/joshua3403/giit-template --skill phase-1-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define the terminology and data structures used across a project, unifying language and ensuring consistent communication across teams by establishing glossary terms, entities, relationships, and schema design.

Core Features & Use Cases

  • Establish a common glossary for business terms and global standards.
  • Identify core entities and relationships, and draft the data schema or domain model.
  • Provide deliverables and references to support onboarding, design reviews, and future phase transitions (phase 2 conventions).

Quick Start

Step-by-step example: create a glossary.md, domain-model.md, and schema.md for a new project, and reference existing templates to maintain consistency.

Frequently Asked Questions about phase-1-schema

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

FAQPage Schema
How do I define project terminology and data structures for a new initiative?

Creating a data schema for new project initiatives involves establishing a common glossary for business terms, identifying core entities and relationships, and drafting a domain model to unify language and ensure consistent communication across teams.

What is the purpose of a glossary and domain model in schema design?

The purpose of a glossary and domain model in schema design is to establish common global standards and business terms, ensuring consistent communication by unifying language before drafting the final data structures.

How do I create a glossary and data schema for a new project?

You create a glossary and data schema by generating deliverables like glossary.md, domain-model.md, and schema.md, referencing existing templates to maintain consistency across the project's design review and onboarding processes.

When do I need to establish a data schema and glossary in the PDCA cycle?

You need to establish a data schema and glossary during Phase 1 of the PDCA cycle, which specifically focuses on defining terminology, identifying entities, and setting up automation references for future phase transitions.

Can I use this approach to unify terminology across different teams?

Yes, you can unify terminology across different teams by establishing a shared glossary of business terms and global standards, which ensures consistent communication and provides common references for design reviews.