Data platform documentation updates
Unified skill: .cursor/skills/data-platform-doc/SKILL.md (modes: kickoff, update, backfill, audit). Aliases: data-platform-doc-kickoff, data-platform-doc-update, data-platform-doc-backfill (each pins a mode; audit is always the parent skill in audit mode).
Which mode should I use?
| Situation | Mode | How to invoke |
|---|---|---|
| No client Data Platform Documentation sheet yet, or you need a new copy from the canonical template with standard tabs | kickoff | data-platform-doc kickoff, or alias data-platform-doc-kickoff |
| Sheet exists and is actively maintained (e.g. updated within the last ~14 days—see auto-detect in the skill) | update | data-platform-doc update, or alias data-platform-doc-update |
| Sheet exists but is stale (no meaningful update for more than ~14 days, or the user asked to catch up) | backfill | data-platform-doc backfill, or alias data-platform-doc-backfill |
| Read-only check: list gaps, wrong headers, TBD—no writes to the sheet | audit | data-platform-doc in audit mode (no thin alias) |
Important: Update and backfill fill from discovery and may create missing standard tabs 1–11 (per skill U3), including Production Mart Catalog when absent. They do not auto-create optional / client-specific tabs (see data-platform-documentation-standard-tabs-sheets.md). If the workbook is far from template shape, prefer kickoff (fresh copy) or audit first.
Rules (Cursor): .cursor/rules/data-platform-doc-kickoff.mdc, data-platform-doc-update.mdc, data-platform-doc-backfill.mdc — use when the user’s wording matches kickoff vs update vs backfill.
Playbook / standards: Google Workspace CLI first, MCP second (google-workspace-cli-setup.md and links from data-platform-doc-common.md).
Quick reference (legacy table)
| Scenario | Skill |
|---|---|
| New client, no sheet yet | data-platform-doc kickoff (alias: data-platform-doc-kickoff) |
| Sheet exists and is actively maintained | data-platform-doc update (alias: data-platform-doc-update) |
| Sheet exists but is stale | data-platform-doc backfill (alias: data-platform-doc-backfill) |
Production Mart Catalog: Required standard tab #11 for every client sheet with a mart layer. Canonical 18-column (A–R) schema and aliases: knowledge/standards/02-writing/data-platform-documentation-standard-tabs-sheets.md. Implementation-agnostic fill rules: knowledge/standards/02-writing/data-platform-doc-common.md → Production Mart Catalog tab and Mart catalog automation — behavior contract. Confirm Snowflake vs BigQuery vs Redshift before querying metadata.
Last updated: 2026-04-22