# Mlops Pipeline Design

> MLOps pipeline design workflow for orchestrating training, validation, packaging, and promotion with explicit gates. Use when ML lifecycle stages must be automated end-to-end with traceable promotion criteria; do not use for model-architecture research decisions. Use when this capability is needed.

- Skill: `tomevault-io/mlops-pipeline-design` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/mlops-pipeline-design`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/mlops-pipeline-design/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/mlops-pipeline-design

---


# Mlops Pipeline Design

## Overview
Use this skill to design ML pipelines that are reproducible, governable, and promotion-safe.

## Scope Boundaries
- Use this skill when the task matches the trigger condition described in `description`.
- Do not use this skill when the primary task falls outside this skill's domain.

## Shared References
- Promotion gate rules:
  - `references/promotion-gate-rules.md`

## Templates And Assets
- Pipeline stage template:
  - `assets/mlops-pipeline-stage-template.md`

## Inputs To Gather
- Required lifecycle stages and ownership model.
- Artifact lineage and reproducibility requirements.
- Promotion/rollback policy constraints.
- Failure handling and rerun expectations.

## Deliverables
- Pipeline stage contracts with inputs/outputs/gates.
- Promotion criteria and rollback strategy.
- Audit-ready lineage and execution policy.

## Workflow
1. Define stage contracts in `assets/mlops-pipeline-stage-template.md`.
2. Apply gate policy from `references/promotion-gate-rules.md`.
3. Validate success/failure branches and rerun behavior.
4. Confirm lineage traceability across stages.
5. Publish pipeline governance and operational ownership.

## Quality Standard
- Every stage has explicit pass/fail gates.
- Promotion path is auditable and reversible.
- Artifact lineage remains intact end-to-end.

## Failure Conditions
- Stop when stages are not reproducible or traceable.
- Stop when promotion criteria are ambiguous.
- Escalate when manual overrides lack governance controls.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/kentoshimizu) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-15 -->