retail-scaffold
Skill2 starsChanged 4 months agoApache-2.0View on GitHub
Scaffold the per-table artifact skeletons a retail table needs in the Seshat BI repo. Use when someone asks to create the mapping or readiness files for a new table. It writes empty templates only and answers no judgment call.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- approval-consoleSkill
- approval-evidence-packSkill
- business-knowledge-interviewSkill
- capabilitiesSkill
- consumer-data-dictionarySkill
- cross-table-lineageSkill
- dagster-orchestration-adapterSkill
- dashboard-designSkill
- dashboard-intelligenceSkill
- dbt-transformation-adapterSkill
- evidence-pack-generatorSkill
- first-hour-compassSkill
- friendly-pr-reviewerSkill
- grain-confidence-reviewerSkill
- kpi-contract-builderSkill
- pbi-mcp-write-adapterSkill
- pbip-workflowSkill
- pbip-xraySkill
- pbir-authoring-adapterSkill
- portfolio-watchSkill
- powerbi-dashboard-designSkill
- pr-readiness-reviewerSkill
- readiness-viewerSkill
- release-notes-generatorSkill
- report-intent-interviewSkill
- retail-build-warehouseSkill
- retail-control-roomSkill
- retail-discover-portfolioSkill
- retail-governSkill
- retail-initSkill
- retail-onboard-tableSkill
- retail-orchestrateSkill
- retail-semantic-checkSkill
- retail-validateSkill
- run-next-readinessSkill
- seshat-studioSkill
- showcase-buildSkill
- source-mappingSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- bi-analyst-knowledgeSkill
- bi-bigdata-knowledgeSkill
- bi-dax-knowledgeSkill
- bi-python-knowledgeSkill
- bi-sql-knowledgeSkill
- retail-kpi-knowledgeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Use retail-govern when a check FAILED and you need the fix.
- Very specific: line 82
If a freshly authored (or edited) rule then trips seshat check, switch to the retail-govern skill to map the finding id to its fix -- that …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
retail-scaffold
The authoring front door for a NEW seshat check rule. Adding a rule means wiring the
same five places every time; doing it by hand silently under-governs a rule when a
place is missed (a shipped rule once had no glossary row). This skill runs the
retail scaffold CLI verb, which automates the mechanical part with a strict
write/print split, and interprets its output.
Boundary vs retail-govern (read first)
Both wrap a governance CLI verb; they do opposite jobs:
retail-govern-- INTERPRET existingseshat checkfindings: map a reported rule id (D8,C2,S2,G1, …) to its meaning and fix. It reasons about rules that already exist.retail-scaffold(this skill) -- AUTHOR a NEW rule + verify its wiring. It creates a rule that does not yet exist, or doctors an existing rule's five-place wiring for drift.
Use retail-govern when a check FAILED and you need the fix; use retail-scaffold
when you are ADDING a rule or checking whether one is fully wired.
Scope + non-negotiables
- Invoke-and-interpret only. This skill runs
retail scaffoldand reads its output; it does not hand-edit the five places itself. - The CLI (not this skill) is the source of the five wiring places. They are
declared in
src/seshat/scaffold.py(FIVE_PLACES); this skill points at that authority and never re-enumerates a competing list (anti-fork). - Never invents rule intent (DEC-1). The author supplies the id, the title, and the real check logic. The generated stub yields no findings until the author fills it in; its test stub fails on purpose (honest red).
- Never self-grants a wiring pass (Principle I). Whether a rule is correctly wired is disposed of by the test suite + the gate exit code, not by this skill or the helper.
- Prose + golden records are PRINT-only (Principle V). The helper writes exactly
three targets and PRINTS the rest (golden-regen commands, a suggested glossary row,
the import/
__all__edit) for a human to apply by hand. It never writes the glossary or a golden record.
Author mode -- add a new rule
retail scaffold --id <RULE_ID> --title "<one-line title>"WRITES exactly three targets:
- a generic stub rule module under
src/seshat/rules/(registered no-op body); - a matching failing test stub under
tests/unit/(honest red); - the insertion of
<RULE_ID>intoEXPECTED_RULE_IDSin the wiring test.
PRINTS (for the human to run / apply -- never written by the helper):
- the golden-record regen commands (
retail manifest,retail severity-posture); - a suggested glossary row to paste into
docs/glossary.md; - the import +
__all__edit forsrc/seshat/rules/__init__.py.
Then: fill the stub with real logic, replace the failing test with a real one, run the
printed regen commands, apply the printed edits, and let seshat check + the suite
decide it is wired. Refuses (no writes) on an invalid id, an already-registered id, or
an existing stub module.
Doctor mode -- verify wiring drift (read-only)
retail scaffold --doctor # sweep every registered rule id
retail scaffold --doctor --id <RULE_ID> # verify one idReports, per id, which of the five places it is present in / missing from, and exits non-zero on any drift. The sweep is the value driver: a rule missing from just the glossary is only discoverable by sweeping. Read-only -- it reports drift, never repairs it.
After a scaffold -- the fix loop
If a freshly authored (or edited) rule then trips seshat check, switch to the
retail-govern skill to map the finding id to its fix -- that is govern's job, not
this skill's.
See also
- The CLI verb + write/print helper:
src/seshat/scaffold.py(FIVE_PLACESis the authoritative wiring-place list); the spec:specs/062-scaffold-rule-generator/. - The interpret sibling:
.claude/skills/retail-govern/SKILL.md(map a rule id → fix). - Rule families + ids:
docs/glossary.md; the gate: theseshat checkstatic surface.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

