All skills
data-model-design
FoundationJIT onlyanalysis-agent/task-agent: use for persisted identity, relationship, ownership, lifecycle, cardinality, or invariants; skip repository, migration, and mapping-only work.
- Group
- Data & API contracts
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- design authoritative persisted records entities attributes relationships cardinality ownership lifecycle and enforceable invariants
Do not use when
Anti-triggers — as binding as the triggers above
- work is limited to repository mechanics migration execution transaction orchestration consumer inventory or DTO model translation
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- Return an authoritative data-model decision: define identity, relationships, ownership, lifecycle, invariants, enforcement, evolution constraints, evidence, and proof limits
Escalation signals
When this skill must hand the decision back
- Authority identity cardinality lifecycle invariant enforcement or compatibility evidence remains unresolved
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | Storage fit ownership normalization history or enforcement mechanisms compete | The root rules and current authority select one bounded model | TaskAnalysis |
| checklist.mddecision-checklist | Model changes identity cardinality invariants lifecycle access deletion or mixed-version behavior | No authoritative entity relationship or storage contract changes | TaskAnalysis |
| evidence-patterns.mdevidence-pattern | Authority invariant consumer evolution or migration claims need fresh proof | Current schemas writers consumers and validators prove each bounded claim | TaskAnalysis |