Ds handoff
Packages a project so someone else can rerun it — pinned environment, model card, and a rerunnable artifact. Hard gate — refuses to proceed without exact pinned versions. Use when someone asks to make work reproducible, pin dependencies, or write a model card. Use when a project is being handed to another person or team.From its SKILL.md
npx -y skills add StamKavid/last-ds-mile --skill ds-handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.6 KB, as published. Nobody here has run it
ds-handoff — Reproducibility & Handoff
Overview
Packages the finished work so someone else can rerun it, trust it, and know its limits — the last mile the whole plugin is named for.
When to Use
- The model or analysis is ready to be shared, deployed, or handed to another team.
- After
/ds-reporthas produced the stakeholder narrative and limitations. - NOT for: further tuning or re-evaluation — if the model isn't finished, go back to
/ds-modelor/ds-evaluatefirst.
Core Process
- Gate check: confirm the environment is pinned — a lockfile, or a
requirements.txt/environment.ymlwith exact versions, not bare package names. If it isn't pinned, stop and pin it before continuing. - Write a model card: what it predicts, a training-data summary, the metric and its
baseline lift, known limitations (from
/ds-report), and intended vs. out-of-scope use. - Confirm the notebook or script reruns cleanly top-to-bottom in a fresh kernel/environment before considering the work done.
- Serialize the model artifact together with its version and the training-data hash/date, recorded alongside it.
- Write to
.last-ds-mile/stages/10-handoff.md: the model card, the environment pin location, the rerun confirmation, and the artifact location.
Common Rationalizations
See ds-method for the shared Rationalizations that apply to every stage, in particular
"it's just exploratory, I'll clean this up before shipping" — the notebook-nobody-could-
rerun failure mode this stage exists to prevent.
Red Flags
| Red Flag | What it usually means |
|---|---|
| The environment file lists packages with no version numbers | This is exactly the condition the Gate Check above exists to catch — unpinned environments are how "works on my machine" ships. |
See ds-method for the shared Red Flags that apply to every stage.
See lessons/the-notebook-nobody-could-rerun.md for a real example of a
handoff that looked done but wasn't reproducible.
Verification
- Gate check passed: the environment is pinned with exact versions.
- Model card written, including intended and out-of-scope use.
- Notebook or script reruns cleanly in a fresh environment.
-
.last-ds-mile/stages/10-handoff.mdwritten.