/setup-relentless-data-skills — scaffold a consumer project for the data lifecycle

This skill prepares a consumer project (not this upstream repo) to use the data-lifecycle skills: it writes a thin ## Data skills index block into the project's CLAUDE.md/AGENTS.md and creates the docs/<stage-area>/ directories where each stage's artefact will land. It is a setup ritual the user runs once — a sibling to the advisor (meta) skills under skills/meta/ (ADR-0002): it has no lifecycle position, writes no durable lifecycle artefact, and has no linter, so it lives outside the numbered 00-…05- spine. It is prompt-driven, not a script — explore, present what you found, confirm with the user, then write.

This skill is self-contained: the vocabulary it leans on is inlined just below, and it ships with no references/ contract and no scripts/ linter — there is nothing to read or run beside it. It writes into the consumer's repo at runtime, which is the point.

Vocabulary this skill assumes (the minimum it needs; the full worldview is optional deeper reading, linked at the end):

• Lifecycle spine. The ordered chain of stages each skill serves: Requirements (Stage 0) → Generation (1) → Ingestion (2) → Storage (3) → Transformation (4) → Serving (5), closing back to Requirements. Each stage produces one durable, version-controlled markdown artefact under a stable docs/<stage-area>/ directory.
• Stage-area directory. The plural-noun directory a stage's artefacts live in, in the consumer project: docs/requirements/, docs/adr/, docs/sources-of-record/, docs/ingestion-plans/, docs/storage-plans/, docs/model-plans/, docs/serving-surfaces/ (ADR-0001). This skill creates them; the stage skills fill them.
• Kill-switch. The named condition under which a stage refuses to produce its artefact — no consumer DGQ → no Source Profile; no upstream Source Profile → no Ingestion Plan; and so on down the chain. The ## Data skills block this skill writes names each one, so the consumer internalises the chain rather than treating the skills as form-fillers.

Optional deeper reading — not required to run this skill: the full repo worldview in CONTEXT.md and the lifecycle reference in docs/data-engineering-101.md.

What this skill is — and is not

• It is a one-time, idempotent scaffolding pass. It explores, confirms three decisions, then writes an index block and creates directories. Re-running it updates the block in place and adds any newly-chosen stage dirs — it never duplicates the block and never overwrites an existing directory or its contents.
• It authors no lifecycle artefact and has no linter. Like the advisor skills under skills/meta/, it is exempt from ADR-0001's one-skill/one-artefact/one-lint pattern. The durable, lint-gated artefacts are produced downstream by the stage skills it scaffolds for.
• It stays in its lane. It configures only the data-lifecycle skills. If the project also uses the engineering skills (to-issues, triage, to-prd, …), their setup is a separate concern — leave any ## Agent skills block from /setup-matt-pocock-skills untouched; the two blocks coexist.