菜单
Use when the user wants a structured learning path across DES phases, wants to study Data Engineering through DES artifacts, or wants a personalized plan based on completed artifacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | des-learning-path |
| description | Use when the user wants a structured learning path across DES phases, wants to study Data Engineering through DES artifacts, or wants a personalized plan based on completed artifacts. |
Use this learning skill to create a structured Data Engineering learning path based on the 22 DES lifecycle phases and available project artifacts.
This skill helps the user learn Data Engineering through project-based artifacts rather than isolated theory.
The learning path should connect DES phases to Data Engineering lifecycle concepts, undercurrents, practical outputs, exercises, quizzes, and recommended next actions.
Use this skill when:
des-learning-path;Use this skill after:
knowledge/FUNDAMENTALS-MAP.md exists;Do not use this skill to replace the 22 main DES lifecycle skills.
The agent should read:
SOUL.md
knowledge/FUNDAMENTALS-MAP.md
Optional inputs:
_des-output/planning-artifacts/
_des-output/learning-artifacts/
_des-output/implementation-artifacts/des-workflow-status.md
If no project artifacts exist, create a generic DES learning path.
If project artifacts exist, create a personalized learning path based on completed, draft, missing, or weak phases.
Create or update:
_des-output/learning-artifacts/des-learning-path.md
The learning path must include:
Use this default module structure:
Module 1 — Foundation and Business Context
Module 2 — Data Engineering Lifecycle Core
Module 3 — Modeling, Contracts, and Quality
Module 4 — Operations, Governance, and Reliability
Module 5 — Delivery, Review, and Portfolio Readiness
SKILL.md completely.customize.toml.SOUL.md.knowledge/FUNDAMENTALS-MAP.md.steps/step-01-learning-context.md.HALT point.This skill will:
Do not execute this overview directly. Follow the step files.
The agent must not:
Stop when:
SOUL.md is missing;knowledge/FUNDAMENTALS-MAP.md is missing;Recommend one of:
des-explain-artifact;des-artifact-quiz;des-workflow-status-update if learning status tracking is enabled.Use when designing the global data architecture, including storage, compute, integration patterns, layer strategy, environment promotion, security posture, observability, governance, cost, operational burden, and decision reversibility.
Use when creating the Bronze Layer Specification for raw/near-raw storage, source fidelity, ingestion metadata, schema drift, replay, quarantine, retention, access control, and lineage before Silver design.
Use when designing CI/CD, testing strategy, release gates, deployment promotion, rollback, release evidence, and environment validation for data products.
Use when designing cost, performance, scalability, storage, compute, query, serving, monitoring, and FinOps optimization strategies for data products.
Use when creating the Data Contract Specification for source feeds, Silver datasets, Gold datasets, serving outputs, dashboards, semantic models, APIs, ML/AI datasets, external exports, or downstream systems that need stable structure, meaning, freshness, quality, access, ownership, lineage, and change behavior.
Use when defining or designing data quality dimensions, rules, thresholds, severity, gates, failure handling, ownership, and validation expectations across Bronze, Silver, Gold, contracts, transformations, and serving outputs.