yonglun/dama-skill / skills/modeling-data
modeling-data
VerifiedUse when business requirements must be represented as conceptual, logical, or physical data models; when defining entities, relationships, grain, keys, attributes, naming, lineage, model reviews, or controlled model changes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.3 KB |
| agents/openai.yaml | config | 280 B |
| references/playbook.md | markdown | 13.2 KB |
| templates/delivery-pack.en.md | markdown | 3.1 KB |
| templates/delivery-pack.zh.md | markdown | 2.8 KB |
| templates/register.en.xlsx | binary | 8.6 KB |
| templates/register.zh.xlsx | binary | 9.1 KB |
| templates/report.en.docx | binary | 37.5 KB |
| templates/report.zh.docx | binary | 38.0 KB |
templates/delivery-pack.en.md
View on GitHub# Data Modeling Delivery Pack
Skill: `modeling-data`
[Word report](report.en.docx) · [Excel register](register.en.xlsx)
## Record details
| ID | Field | Project value |
| --- | --- | --- |
| `artifact_id` | Artifact ID | |
| `project` | Project | |
| `skill` | Skill | |
| `version` | Version | |
| `date` | Date | |
| `status` | Status | |
| `author` | Author | |
| `owner` | Owner | |
| `approver` | Approver | |
| `purpose` | Purpose | |
| `business_outcome` | Business outcome | |
| `scope` | Scope and exclusions | |
| `source_inputs` | Inputs and sources | |
| `assumptions` | Assumptions and constraints | |
| `decisions` | Decisions | |
| `rationale` | Rationale | |
| `risks` | Risks | |
| `exceptions` | Exceptions | |
| `open_items` | Open items | |
| `due_date` | Due date | |
| `acceptance_criteria` | Acceptance criteria | |
| `evidence_location` | Evidence location | |
| `reviewer_decision` | Reviewer decision | |
| `next_gate` | Next stage gate | |
## Domain analysis and decisions
### Business use cases and scope (`use_cases`)
State the business processes, decisions, and consumers supported by the model.
> Enter project evidence, conclusion, and owner.
### Model level and approach (`model_level`)
Choose conceptual, logical, or physical level and the appropriate relational, dimensional, or other pattern.
> Enter project evidence, conclusion, and owner.
### Requirements and terms (`requirements`)
List governed definitions, disputed terms, and approval status of business rules.
> Enter project evidence, conclusion, and owner.
### Grain keys and relationships (`grain_keys`)
Fix entity or fact grain, keys, cardinality, optionality, and temporal rules.
> Enter project evidence, conclusion, and owner.
### Model and source traceability (`traceability`)
Trace conceptual to logical to physical design and source-to-target mappings and deviations.
> Enter project evidence, conclusion, and owner.
### Review and approval (`review`)
Record findings and decisions from requirements, design, and physical feasibility reviews.
> Enter project evidence, conclusion, and owner.
### Version and change control (`change_control`)
For breaking changes, record impact, migration, compatibility, and rollback.
> Enter project evidence, conclusion, and owner.
### Quality and acceptance evidence (`acceptance_evidence`)
Use scenarios, profiling, and reverse comparison with implementation to verify the model.
> Enter project evidence, conclusion, and owner.
## Working registers
### Data Dictionary (`dictionary`)
Maintain entities, attributes, keys, and precise definitions.
| Entity or fact (`entity`) | Attribute (`attribute`) | Definition (`definition`) | Key (`key`) | Source (`source`) | Owner (`owner`) | Version (`version`) |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
### Model Mappings (`mappings`)
Trace source fields to target fields and transformation rules.
| Source field (`source_field`) | Target field (`target_field`) | Transformation (`transformation`) | Rule (`rule`) | Owner (`owner`) | Test (`test`) | Evidence (`evidence`) |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |