yonglun/dama-skill / skills/designing-data-architecture
designing-data-architecture
VerifiedUse when an enterprise, domain, platform, program, or project needs current, target, or transition data architecture; capability and data-flow alignment; architecture principles, standards, decisions, conformance, or an evolution roadmap.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.8 KB |
| agents/openai.yaml | config | 282 B |
| references/playbook.md | markdown | 12.0 KB |
| templates/delivery-pack.en.md | markdown | 3.0 KB |
| templates/delivery-pack.zh.md | markdown | 2.7 KB |
| templates/register.en.xlsx | binary | 8.5 KB |
| templates/register.zh.xlsx | binary | 8.9 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 Architecture Delivery Pack
Skill: `designing-data-architecture`
[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 outcome and scope (`business_outcome`)
State the business capabilities, decisions, and boundaries the architecture must support.
> Enter project evidence, conclusion, and owner.
### Current-state evidence (`current_state`)
Describe systems, flows, ownership, and known problems with evidence dates.
> Enter project evidence, conclusion, and owner.
### Principles and requirements (`principles`)
Distinguish mandatory constraints from negotiable design preferences.
> Enter project evidence, conclusion, and owner.
### Target architecture (`target_state`)
Describe target capabilities, data boundaries, interfaces, governance, and operations ownership.
> Enter project evidence, conclusion, and owner.
### Transition architecture (`transition`)
Define deliverable interim states, migration order, and compatibility measures.
> Enter project evidence, conclusion, and owner.
### Key decisions and trade-offs (`tradeoffs`)
Record alternatives, trade-offs, approval roles, and triggers for revisiting decisions.
> Enter project evidence, conclusion, and owner.
### Conformance and acceptance (`conformance`)
List standards, exceptions, tests, and view-review evidence.
> Enter project evidence, conclusion, and owner.
### Dependency roadmap (`roadmap`)
Map capability and data dependencies to gates and verifiable exits.
> Enter project evidence, conclusion, and owner.
## Working registers
### Capabilities (`capabilities`)
Compare current and target capabilities with dependencies.
| Capability (`capability`) | Current state (`current`) | Target state (`target`) | Dependency (`dependency`) | Owner (`owner`) | Evidence (`evidence`) |
| --- | --- | --- | --- | --- | --- |
| | | | | | |
### Architecture Decisions (`decisions`)
Record architectural choices, trade-offs, and approval evidence.
| Decision (`decision`) | Rationale (`rationale`) | Impact (`impact`) | Owner (`owner`) | Approver (`approver`) | Evidence (`evidence`) | Review date (`review_date`) |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |