relentless-data-skills

relentless-data-skills

Agent skills for data and analytics engineers, organised around the end-to-end data lifecycle. v1.5 completes the spine: Stage 0 — Requirements & Discovery — deeply, plus Stage 1 — Generation, Stage 2 — Ingestion, Stage 3 — Storage, Stage 4 — Transformation, and Stage 5 — Serving — built around the same discipline: interrogate every artefact before a pipeline is written, and refuse to produce a downstream artefact that does not chain back to the upstream one. Stage 5 closes the loop — a Serving Surface names both the model it reads and the decision it informs — so the lineage graph is now a closed cycle from the founding question back to it. Built for Claude Code; structured so each skill produces a durable, version-controlled artefact that downstream stages can consume.

Why this exists

Generic "data requirements templates" produce filled-in forms that look thorough but quietly accept asks that should have been killed — nothing in them forces the question "if the answer flipped, would anything actually change?" This repo encodes that question (and a few others) as agent skills, so pipelines and dashboards stop getting built for decisions nobody can later name.

Install

Skills are self-contained — install one, or install the set (ADR-0004). Each skill folder carries its own contract (references/<artefact>.md) and linter (scripts/lint-<artefact>.sh); the shared worldview (CONTEXT.md) and lifecycle reference are linked by absolute URL as optional deeper reading, so a lone skill folder works on its own.

skills.sh (third-party installer):

npx skills add sleeplessv/relentless-data-skills --skill <name>   # one skill
npx skills add sleeplessv/relentless-data-skills                  # the whole set

Claude Code plugin (the whole set as one selectable plugin):

/plugin marketplace add sleeplessv/relentless-data-skills
/plugin install relentless-data-skills@relentless-data-skills

Pick the single relentless-data-skills plugin and all skills install together; reload with /reload-plugins.

Local development. The plugin path works from a local clone too: /plugin marketplace add <path-to-clone> then /plugin install relentless-data-skills@relentless-data-skills, reloaded with /reload-plugins. The repo ships both .claude-plugin/plugin.json (the plugin) and .claude-plugin/marketplace.json (the single-plugin marketplace pointing at it).

v1.5 skills

Stage 0 — Requirements & Discovery:

• /gather-requirements — interrogates a stakeholder ask into one or more Decision-Grade Question (DGQ) documents under docs/requirements/; enforces the action-change kill-switch (if nothing would change when the answer flips, the ask is rejected, not built) and bundles its own contract (references/dgq.md) and linter (scripts/lint-dgq.sh) inside the skill folder for schema enforcement (ADR-0004 pilot).
• /write-adr — scaffolds a MADR-lite Architecture Decision Record under docs/adr/ for cross-cutting platform commitments; refuses single-option decisions and bundles its own contract (references/adr.md) and linter (scripts/lint-adr.sh) inside the skill folder for structural enforcement (ADR-0004).

Stage 1 — Generation:

• /profile-source — interrogates an upstream source (database table, SaaS endpoint, streaming topic, partner feed) into a Source Profile document under docs/sources-of-record/; enforces the Generation kill-switch (an accepted profile must name at least one consumer DGQ in consumed_by — no consumer, no profile) and bundles its own contract (references/source-profile.md) and linter (scripts/lint-source-profile.sh) inside the skill folder for schema enforcement (ADR-0004).

Stage 2 — Ingestion:

• /plan-ingestion — interrogates a planned (or undocumented) ingestion path into an Ingestion Plan document under docs/ingestion-plans/; enforces the Ingestion kill-switch (an accepted plan must name at least one upstream Source Profile in related_sources_of_record — no profiled upstream, no plan) and bundles its own contract (references/ingestion-plan.md) and linter (scripts/lint-ingestion-plan.sh) inside the skill folder for schema enforcement (ADR-0004).

Stage 3 — Storage: