Menu
PM Airtable data model reference. Use when creating tables, querying structure, or understanding relationships between Domain, Subdomain, Capability, Entity, Requirement, and BacklogItem tables.
| name | airtable-model |
| description | PM Airtable data model reference. Use when creating tables, querying structure, or understanding relationships between Domain, Subdomain, Capability, Entity, Requirement, and BacklogItem tables. |
Reference for Airtable tables used by PM plugins.
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
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
| 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.
Architecture Decision Records (ADRs) for documenting technical decisions. Use when creating, updating, or reviewing architecture decisions. Triggers on discussions about technical choices, trade-offs, or "why did we choose X" questions.
Document domain knowledge including entities, attributes, relationships, processes, and ubiquitous language. Use when documenting domain models, entity relationships, business processes, or building a glossary of domain terms.
Interactive implementation planning from backlog items. Use when creating plans for features, fixes, or tasks. Guides 6-phase collaborative dialogue from discovery through documentation.
BDD requirements using Gherkin syntax. Activates when users describe features, requirements, user stories, acceptance criteria, or work with .feature files. Generates Given-When-Then scenarios, validates Gherkin structure, and creates complete feature files.