mlops-pipeline-design

Designs reproducible ML training pipelines with data versioning, staged caching, and gated model promotion.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill mlops-pipeline-design-snoodleboot-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mlops-pipeline-design
Source: https://github.com/snoodleboot-io/discrecontinual_equations/tree/main/.claude/skills/mlops-pipeline-design
Command: npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill mlops-pipeline-design-snoodleboot-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? ML pipelines that version only code produce irreproducible models: the same git sha trained on different data snapshots yields different models, monolithic training scripts make every experiment pay full compute cost, and ungated promotion lets bad runs reach production. ## Core Features & Use Cases - Run Fingerprinting: Records git sha, dataset URI, dataset manifest hash, params hash, and environment hash so any past model can be rebuilt from its fingerprint alone. - Stage Decomposition and Caching: Splits pipelines into ingest, validate, build_features, train, evaluate, and register stages with content-hash cache keys so unchanged stages are skipped. - Blocking Data Validation: Raises on row-count, category-cardinality, and label-base-rate failures instead of logging warnings, stopping bad data before compute is spent. - Champion Comparison and Gated Promotion: Evaluates candidates against the live champion on the same deterministic holdout, including per-segment regression checks, and separates registration from promotion. - Use Case: A team retraining a churn model uses this guidance to snapshot source tables immutably, split holdouts by deterministic hash buckets, and block automatic promotion when a segment-level AUC regression is detected. ## Quick Start Ask the AI to review your ML training pipeline design against reproducibility, validation, and promotion-gating best practices.

Frequently Asked Questions about mlops-pipeline-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make ML training runs reproducible?

Record a run fingerprint combining git sha, dataset URI, dataset manifest hash, resolved params hash, and environment hash for every run. Snapshot mutable data sources into immutable date-partitioned tables as the first pipeline stage so old runs stay rebuildable.

How should I structure an ML training pipeline for caching?

Decompose the pipeline into ingest, validate, build_features, train, evaluate, and register stages, each with declared inputs and outputs. The orchestrator can then skip any stage whose content-hash cache key is unchanged, so hyperparameter sweeps only re-run training.

Should data validation fail the pipeline or log a warning?

Data validation should raise and fail the run before compute is spent. Checks like row count, unseen category rates, and label base rate shifts catch partial loads and upstream schema changes that would otherwise train cleanly and degrade in production.

How do I avoid training and serving skew in feature pipelines?

Define features once in a shared feature library or feature store with two materializations. The offline path must use point-in-time-correct as-of joins so historical labels are joined to feature values as they existed at the label timestamp.

When should a model be promoted to production?

Training should only register the model to staging; promotion is a separate gated decision. Compare the candidate against the live champion on the identical holdout, overall and per segment, and block promotion on any regression beyond tolerance.

Is a random train test split safe for time series data?

No, random splits let the model see the future for the same entity when the target is temporally ordered. Split by time instead, and use a deterministic hash-bucket rule for non-temporal data so holdouts stay stable and comparable across runs.