dag-generation

Generate two-stage DAGs from task catalog fragments and plan artifacts.

35|8|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/microsoft/github-copilot-modernization --skill dag-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dag-generation
Source: https://github.com/microsoft/github-copilot-modernization/tree/main/plugins/github-copilot-modernization/skills/dag-generation
Command: npx skills add https://github.com/microsoft/github-copilot-modernization --skill dag-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

DAG generation for modernization projects automates the planning and execution orchestration by deriving task graphs from a catalog and plan artifacts, reducing manual planning effort and ensuring traceable dependencies across modules and stages.

Core Features & Use Cases

  • Generate stage-1 initial DAG by selecting fragments from the task catalog and forming a plan skeleton.
  • Generate stage-2 execute+validate DAG from plan artifacts to support execution and verification.
  • Read reference files such as references/task-catalog.md and references/dag-rules.md to enforce rules and dependencies.

Quick Start

Provide a project profile and your migration goal to generate the initial DAGs and orchestration plan.

Frequently Asked Questions about dag-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a DAG for a code modernization project?

You generate a DAG for a modernization project by providing a project profile and a migration goal, which produces a plan DAG and an execute+validate DAG from task catalog fragments.

What is a two-stage DAG for cross-module rewrites and upgrades?

A two-stage DAG is an orchestration graph that separates planning from execution, producing a plan skeleton in stage one and an execution and validation DAG from plan artifacts in stage two.

Can I automate task orchestration for module extraction without manual planning?

Yes, you can automate task orchestration for module extraction by deriving dependency graphs and phase labels from a task catalog and project profile, eliminating manual planning effort.

Does DAG generation work for coordinated execution across multiple groups?

DAG generation supports coordinated execution across multiple groups by deriving traceable dependencies and task structures for cross-module rewrites, upgrades, and extractions.

How do task catalog fragments and dag rules enforce dependencies during planning?

Task catalog fragments and dag rules enforce dependencies by providing reference files that the generation process reads to derive phase labels, task structures, and orchestration rules.

What inputs do I need to provide for automated DAG generation?

You need to provide a project profile and a user migration ask to generate the initial DAGs, alongside access to task catalog and dag rules reference files for dependency derivation.