yonglun/dama-skill / skills/managing-reference-and-master-data
managing-reference-and-master-data
VerifiedUse when shared business entities or controlled code sets must be made authoritative across systems; when resolving customer, product, supplier, location, employee, account, hierarchy, or reference-code conflicts; or when defining identity resolution, golden-record, match/merge/split, survivorship, stewardship, publication, reconciliation, and system-of-record controls.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.6 KB |
| agents/openai.yaml | config | 310 B |
| references/playbook.md | markdown | 16.0 KB |
| templates/delivery-pack.en.md | markdown | 3.1 KB |
| templates/delivery-pack.zh.md | markdown | 2.9 KB |
| templates/register.en.xlsx | binary | 8.6 KB |
| templates/register.zh.xlsx | binary | 9.0 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# Master and Reference Data Pack
Skill: `managing-reference-and-master-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
### Domain charter (`domain_charter`)
Define the shared entity or code set, business use, owner, and consumers.
> Enter project evidence, conclusion, and owner.
### Sources and authority (`authority`)
Assign authoritative sources, adjudication rights, and distribution by attribute or event.
> Enter project evidence, conclusion, and owner.
### Global identity and crosswalk (`global_identity`)
Define global IDs, local-ID crosswalks, creation, and retirement rules.
> Enter project evidence, conclusion, and owner.
### Golden record and survivorship (`survivorship`)
Specify source precedence, recency, conflicts, human adjudication, and traceability.
> Enter project evidence, conclusion, and owner.
### Match merge and split (`merge_split`)
Cover false-merge safeguards, reversible splits, versions, and independent tests.
> Enter project evidence, conclusion, and owner.
### Hierarchies and reference codes (`hierarchies`)
Set hierarchy changes, code-set versions, effective dates, and backward compatibility.
> Enter project evidence, conclusion, and owner.
### Distribution and acknowledgment (`distribution`)
Define publication contracts, consumer acknowledgments, reconciliation, and correction.
> Enter project evidence, conclusion, and owner.
### Quality and operating acceptance (`acceptance_evidence`)
List stewardship workflow, quality measures, exceptions, and gate evidence.
> Enter project evidence, conclusion, and owner.
## Working registers
### Identity Crosswalk (`crosswalk`)
Record local identities against governed global identities.
| Source (`source`) | Source ID (`source_id`) | Global ID (`global_id`) | Match rule (`match_rule`) | Owner (`owner`) | Status (`status`) | Evidence (`evidence`) |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
### Match Decisions (`decisions`)
Track merge/split decisions and false-match recovery evidence.
| Source ID (`source_id`) | Global ID (`global_id`) | Decision (`decision`) | Rationale (`rationale`) | Approver (`approver`) | 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 |