Mlops pipeline design
Skill planifest/planifest-framework/planifest-framework/external-skills/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.From its SKILL.md
npx -y skills add planifest/planifest-framework --skill mlops-pipeline-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
1.8 KB, 309 tokens by cl100k_base, as published. Nobody here has run it
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
- Define stage contracts in
assets/mlops-pipeline-stage-template.md. - Apply gate policy from
references/promotion-gate-rules.md. - Validate success/failure branches and rerun behavior.
- Confirm lineage traceability across stages.
- 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.
What ships with it: 1 file
11.3 KB alongside SKILL.md
- attribution.txt11.3 KB