Orchestrate end-to-end Agile metric onboarding to the Unified Data Model.
npx skills add https://github.com/huangcd/gcusage --skill agile-to-udm
Please help me install this Agent Skill. Skill: agile-to-udm Source: https://github.com/huangcd/gcusage/tree/main/.github/skills/agile-to-udm Command: npx skills add https://github.com/huangcd/gcusage --skill agile-to-udm
END-TO-END orchestrator that combines multiple skills into a single workflow: traces Agile metric dependencies, documents ESA, analyzes dimensions, creates ADO work items, and invokes dimension creation. This is the FULL PIPELINE skill — NOT just tracing (use agile-metric-dependency-tracing for tracing only). USE WHEN user says: 'convert Agile metric to UDM', 'make Agile metric adhere to unified data model', 'full UDM onboarding for metric', 'end-to-end metric onboarding', or wants the COMPLETE workflow from Agile metric analysis through dimension creation. Make sure to use this skill whenever the user wants the full workflow, not just one step.
Convert CopilotActiveUsers to UDM using the full Agile-to-UDM workflow.
High-intent search queries and answers about installing and using this skill.
To onboard an Agile metric to the Unified Data Model, you orchestrate dependency tracing across multiple repos, document ESA fields, analyze dimensions, and create ADO work item drafts. This full pipeline coordinates every step from metric analysis to optional dimension creation.
Full Agile metric onboarding orchestrates the complete workflow including ESA documentation, dimension analysis, and ADO work item creation, whereas dependency tracing only maps metric dependencies across repos without generating documentation or work items.
You generate ADO work items by analyzing which external fields should become UDM dimensions, then creating draft CSV mappings for those dimensions within the end-to-end onboarding workflow to populate Azure DevOps.
Yes, Agile metric onboarding traces dependencies across four specific repos: IDEASRapidIQ, DORA, NitroUMDP, and IDEAsComSchema, documenting external fields in ESA to satisfy unified data model architecture requirements.
Yes, documenting external ESA fields is a core step in the onboarding workflow. The pipeline identifies external fields during dependency tracing and generates the necessary ESA documentation alongside dimension analysis.
End-to-end Agile metric onboarding requires local workflow prerequisites and telemetry setup to orchestrate tracing, ESA updates, dimension analysis, and ADO CSV draft creation across the four target repositories.
huangcdTrace Agile metric field dependencies across repos and generate an SVG diagram.
huangcdTransforms CSV mapping into UDM dimension definition with generated CSVs, ScopeConnectors, DefaultSNDConfigResources.
huangcdUpdate ESA Markdown and JSON schema files from constraint files.
haxlysInstrument Python applications with structured logging, metrics, and distributed tracing.
