retail-onboard-tablelisted

Walk a NEW raw retail table across the FIRST readiness transition -- Source Ready (Stage 1) through Mapping Ready (Stage 2) -- and seed its per-table readiness-status, in the Seshat BI repo. Use when someone says "onboard <schema>.<table>", "take this new table from nothing to a reviewed map", or "start the readiness journey for a table". This is the stage-transition FRONT DOOR: it sequences profile -> map -> gate, writes the readiness-status record, and STOPS at Mapping Ready. It DELEGATES the five mapping artifacts to the `source-mapping` skill (it does not re-implement mapping); it NEVER writes `silver.*` SQL, NEVER self-grants the gate approval, and NEVER answers a Principle-V judgment call (grain, PII, business rollup, product identity).
Kemetra/Seshat-BI · ★ 2 · AI & Automation · score 68

Install: claude install-skill Kemetra/Seshat-BI

# retail-onboard-table The onboarding front door for ONE table's first two readiness stages. The kit already ships the verb that authors the mapping artifacts (`source-mapping`) and the conductor that sequences every verb end-to-end (`retail-orchestrate`). This skill is the stage-scoped composition between them: "I have a new raw table -- walk me from nothing to a reviewed map." It advances **Source Ready -> Mapping Ready**, seeds the per-table `readiness-status.yaml`, and STOPS. It is a procedure the agent performs (agent-first, Principle I); `seshat check` and the read-only profile are gates it CALLS, not a CLI subcommand. ## Scope boundary (read first) - **Agent-first, no CLI.** This is a SKILL the agent runs; it adds no `retail` subcommand and no Python. - **ENTERS at Source Ready, EXITS at Mapping Ready.** The terminal state is Mapping Ready -- the three gate artifacts committed and either `mapping_ready: blocked` (review pending, the common case) or `mapping_ready: pass` (only after a HUMAN has recorded approval). Both are successful wizard runs. - **NEVER crosses into Silver Ready** (Principle IV, roadmap rule #2). It writes no `silver.*` SQL, no migration, and never calls `retail-build-warehouse`. Its last action is to seed/update the readiness-status, state the next allowed action, and STOP. - **NEVER self-grants approval or invents a judgment call** (Principle V). The four reserved seams -- grain, PII publish-safety, business rollup/segment, produ