菜单
Governs how Azure DevOps epics are interpreted and translated into medallion architecture diagrams. Use when reading epic details and deciding which data sources, transformations, and serving outputs belong in the diagram.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | Azure DevOps Epic Mapping |
| description | Governs how Azure DevOps epics are interpreted and translated into medallion architecture diagrams. Use when reading epic details and deciding which data sources, transformations, and serving outputs belong in the diagram. |
An Azure DevOps epic describes a business outcome, not a technical architecture. The agent must extract architectural signals from the epic's title, description, acceptance criteria, and tags — and resist the temptation to over-engineer or under-specify. One epic produces exactly one diagram. Epics with no data-engineering scope are skipped with a written explanation.
get_epic_details and before calling generate_diagramSignals in epic text that indicate a data source:
Signals that indicate transformation work:
Signals that indicate a serving layer:
semantic_model + report nodespipeline node in Serving zone labelled "Export Pipeline"An epic warrants a diagram if it contains at least one of:
Skip the epic (with explanation) if it is purely about:
title, description, acceptance_criteria, and tags from get_epic_detailsdata_sources nodes with type: sourceserving_nodesget_fabric_context) map to each layeredges list to connect every node in the flowgenerate_diagram with the complete spec.drawio file per epic; never merge two epics into one diagram{epic_id}-{slugified_title}.drawio| Situation | Action |
|---|---|
| Epic has no data source | Add a generic "Source System" node; note ambiguity in run summary |
| Epic mentions a source but no ingestion tool | Default to "Dataflows Gen2" in Bronze; note assumption |
| Epic has no serving output | Add a placeholder "TBD Report" node; note ambiguity |
| Epic is ambiguous about Silver vs Gold | Default to including both layers |
| Epic explicitly says "no reporting needed" | Omit Serving layer; note deviation |
Always:
Ask First:
Never:
data_sources node name maps to a system or file format mentioned in the epicserving_nodes node maps to an output or consumer mentioned in the epicPrefer the simplest solution that satisfies the current epic; never add complexity for hypothetical future needs
Ensures the agent only references data assets that verifiably exist in Microsoft Purview's Data Map. Use before generating any diagram node that represents a catalogued asset (Lakehouse, Pipeline, Notebook, Warehouse, Table).
Governs how the agent chooses between single-workspace and cross-workspace design modes. Use when deciding which Purview collections to query for a given epic, and when placing nodes from different workspaces into the same diagram.
Enforces formatting, layout, and label rules for all generated .drawio files. Use whenever calling generate_diagram or reviewing diagram output to ensure files open and render correctly in draw.io Desktop and diagrams.net.
Enforces Bronze/Silver/Gold layer discipline when designing Microsoft Fabric data architectures. Use when generating or reviewing any medallion architecture diagram for a Fabric workspace.