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
- 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.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9