ogt-docs-define

# OGT Docs - Define

Guide for creating definition documents that establish WHAT things ARE in your system.

## Philosophy

**Definitions are the foundation of shared understanding.**

Before anyone can implement, market, or discuss something, there must be a clear, agreed-upon definition of what it IS.

```
┌─────────────────────────────────────────────────────────────────┐
│                    THE DEFINITION PRINCIPLE                     │
├─────────────────────────────────────────────────────────────────┤
│  A definition answers:                                          │
│    • WHAT is this thing?                                        │
│    • WHY does it exist?                                         │
│    • WHAT are its boundaries? (what it is NOT)                  │
│    • HOW does it relate to other things?                        │
│                                                                 │
│  A definition does NOT specify:                                 │
│    • HOW to implement it (that's rules/)                        │
│    • WHAT to do with it (that's todo/)                          │
└─────────────────────────────────────────────────────────────────┘
```

## When to Use This Skill

Use `ogt-docs-define` when you need to:

- Understand the definitions folder structure
- Choose the right definition sub-skill
- Create a definition that doesn't fit specialized categories

**For specific definition types, use:**

| Type                   | Sub-Skill                   | Use When                               |
| ---------------------- | --------------------------- | -------------------------------------- |
| Business concepts      | `ogt-docs-define-business`  | Pricing, users, revenue, market        |
| Product features       | `ogt-docs-define-feature`   | New capabilities, user-facing features |
| Technical architecture | `ogt-docs-define-code`      | Services, data models, APIs            |
| Marketing concepts     | `ogt-docs-define-marketing...