airtable-model

SmidigStorm's avatarfrom SmidigStorm

PM Airtable data model reference. Use when creating tables, querying structure, or understanding relationships between Domain, Subdomain, Capability, Entity, Requirement, and BacklogItem tables.

⭐1stars🔀0forks📁View on GitHub🕐Updated Dec 16, 2025

When & Why to Use This Skill

This Claude skill serves as a comprehensive technical reference for the PM Airtable data model, specifically designed to streamline product management workflows. It provides detailed documentation on entity relationships (ERD), hierarchical structures, and table specifications, enabling users to effectively manage complex data connections between Domains, Capabilities, Requirements, and Backlog Items within Airtable.

Use Cases

  • Case 1: Designing and setting up a new Airtable base for product requirements and backlog management with pre-defined relational structures.
  • Case 2: Querying complex data relationships to understand how high-level business domains map down to specific technical requirements and test cases.
  • Case 3: Standardizing product management data entry by referencing the 'Ubiquitous Language' in the Glossary and following the established table hierarchy.
  • Case 4: Troubleshooting or auditing existing Airtable structures to ensure data integrity across linked tables like Entities, Attributes, and Recommendations.
nameairtable-model
descriptionPM Airtable data model reference. Use when creating tables, querying structure, or understanding relationships between Domain, Subdomain, Capability, Entity, Requirement, and BacklogItem tables.

PM Airtable Data Model

Reference for Airtable tables used by PM plugins.

Entity Relationships

erDiagram
    Domain ||--o{ Subdomain : contains

    Subdomain ||--o{ Capability : contains
    Subdomain ||--o{ Entity : contains
    Subdomain ||--o{ Process : has
    Subdomain ||--o{ Glossary : has

    Entity ||--o{ Attribute : has
    Entity ||--o{ Relationship : from
    Entity ||--o{ Relationship : to

    Capability ||--o{ Requirement : has

    Requirement ||--o{ Rule : has
    Requirement ||--o{ OpenQuestion : has
    Requirement ||--o{ Test : inspires

    Rule ||--o{ Example : has

    TestSuite ||--o{ Test : contains
    TestSuite ||--o{ TestRun : executes

    Fact ||--o{ Insight : supports
    Insight ||--o{ Recommendation : leads-to
    Recommendation ||--o{ BacklogItem : becomes

    BacklogItem }o--o{ Requirement : links

Hierarchy

flowchart TD
    D[Domain] --> SD[Subdomain]
    SD --> C[Capability]
    SD --> E[Entity]
    SD --> P[Process]
    SD --> G[Glossary]

    E --> A[Attribute]
    E --> REL[Relationship]
    REL --> E

    C --> R[Requirement]
    R --> RU[Rule]
    R --> OQ[OpenQuestion]
    R -.-> T[Test]
    RU --> EX[Example]

    TS[TestSuite] --> T
    TS --> TR[TestRun]

    F[Fact] --> I[Insight]
    I --> REC[Recommendation]
    REC -.-> B[BacklogItem]

    B -.-> R

Tables Overview

Table Links To Purpose
Domain - Top-level areas
Subdomain Domain Sub-areas, has 3-letter prefix
Capability Subdomain Categorizes requirements, has 3-letter prefix
Entity Subdomain Domain objects
Attribute Entity Entity properties
Relationship Entity, Entity Entity-to-entity connections
Process Subdomain Business workflows
Glossary Subdomain Ubiquitous language
Requirement Capability BDD requirements (MoSCoW), ReqID: SUB-CAP-NNN
Rule Requirement Business rules
Example Rule Concrete examples
OpenQuestion Requirement Unresolved questions
TestSuite - Groups related tests
Test TestSuite, Requirement Individual test cases
TestRun TestSuite Execution record with results
Fact - Raw research observations
Insight Fact[] Patterns from facts
Recommendation Insight[] Actionable suggestions
BacklogItem Requirement[], Recommendation Prioritized work items

For detailed field specifications, see table-specs.md.