data-governance-policy

Included with Lifetime

$97 forever

Design data governance policy — stewardship, quality standards, access control, lifecycle, lineage + metadata catalog, change + issue management. Aligns with GDPR / CCPA / sector regulations.

Design

What this skill does


# Data Governance Policy

You design data governance for an organization. Covers stewardship, quality, access, lifecycle, metadata, and change management.

## Core rules

- **Per-domain stewardship** — someone owns each data domain
- **Classification drives access** — from `data-dictionary-definition` + `security-requirements-classification`
- **Lineage traceable** — where data came from + who transformed it
- **Lifecycle explicit** — retention + archival + destruction
- **Metadata discoverable** — catalog exists
- **Issue management** — data issues trackable

## Governance components

### Stewardship

| Role | Responsibility |
|---|---|
| **Data owner** | Accountable for a data domain (CFO for financials, CPO for customer data) |
| **Data steward** | Day-to-day quality + access decisions |
| **Data custodian** | Operational (DBA / platform engineer) |
| **Data consumer** | Uses data; responsible for correct use |

Per data domain (from `data-dictionary-definition`) — assign roles.

### Quality standards

Per data asset:

| Dimension | Measurable as |
|---|---|
| **Accuracy** | % records matching source of truth |
| **Completeness** | % required fields populated |
| **Timeliness** | Lag between event and available data |
| **Consistency** | Agreement across systems |
| **Validity** | % conforming to format / schema |
| **Uniqueness** | Duplicate rate |

SLAs per data asset; monitoring + alerting.

### Access control

- Classification from `data-dictionary-definition` → access policy
- Role-based (finance sees payroll; support sees tickets not payroll)
- Purpose-based (GDPR — data used only for declared purpose)
- Audit every sensitive access

### Lifecycle

1. **Creation / ingestion**
2. **Active use**
3. **Archive** (reduced access, cheaper storage)
4. **Destruction** (per retention + legal hold exceptions)

Retention rules per data class (legal / regulatory / business minimums).

### Lineage

Per data element: source → transformations → destinations. Tools: dbt / DataHub / Amundsen / OpenLineage / Collibra.

### Metadata catalog

Discoverable source of:
- What data exists
- Where it lives
- Who owns it
- What it means
- Quality metrics
- Access policy

Tools: DataHub / Amundsen / Collibra / Alation.

### Change management

- Schema change approval process
- Impact analysis before change (link to `impact-analysis`)
- Deprecation notice for data contract changes
- Communication to consumers

### Issue management

- Data quality incidents logged
- Root-cause analysis
- Preventive measures

## Regulatory alignment

- **GDPR** — lawful basis + purpose limitation + data-subject rights
- **CCPA / CPRA** — consumer rights + privacy notice
- **HIPAA** — PHI-specific controls
- **SOX** — financial data integrity + audit
- **Industry** — sector-specific (banking, healthcare)

## Report

```markdown
# Data Governance Policy: [Org]

## Scope
[Data domains + regulatory context]

## Stewardship
[Roles per domain]

## Quality Standards
[SLAs per data asset]

## Access Control
[Policies by classification + role + purpose]

## Lifecycle
[Retention + archive + destruction per class]

## Lineage
[Tracking approach + tooling]

## Metadata Catalog
[Chosen tool + coverage]

## Change Management
[Process + approvers]

## Issue Management
[Logging + RCA process]

## Regulatory Alignment
[Per regime]

## Rollout Plan
[Phased adoption]
```

## Failure behavior
- No data owners → require assignment before rest
- No classification → prerequisite from `data-dictionary-definition`
- No lineage tooling → recommend adoption
- mmdc failure → see mixin

Files: 1

Size: 3.8 KB

Complexity: 12/100

Category: Design

Source: https://github.com/ssiertsema/claude-code-plugins/tree/main/data-governance-policy/skills/data-governance-policy

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts