hve-resiliency-workitem-import

Bulk-creates Azure DevOps work items from a resiliency export CSV via the ADO REST API.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/christopherromero/HVE-Resiliency --skill hve-resiliency-workitem-import-christopherromero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hve-resiliency-workitem-import
Source: https://github.com/christopherromero/HVE-Resiliency/tree/main/.github/skills/hve-resiliency-workitem-import
Command: npx skills add https://github.com/christopherromero/HVE-Resiliency --skill hve-resiliency-workitem-import-christopherromero

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually recreating dozens of resiliency assessment findings as Azure DevOps work items is slow and error-prone. This Skill automates the bulk creation of work items from an export CSV, including parent hierarchy, priority grouping, field mapping, and assessment attachments. ## Core Features & Use Cases - Bulk ADO Import: Posts each CSV row to Azure DevOps as a work item using the REST API, with per-row success/failure logging. - Process Template Mapping: Maps types, severity, acceptance criteria, and state fields correctly for Basic, Agile, and Scrum process templates. - Hierarchy and Grouping: Creates a parent Epic summarizing the assessment, optionally inserts P0–P3 priority group work items, and links all findings as children. - Use Case: After running a resiliency assessment, import 40 findings into an Agile ADO project with one command, producing an Epic parent with the assessment markdown attached, four User Story priority groups, and one Bug per finding. ## Quick Start Run /hve-resiliency-workitem-import in Copilot Chat and provide your ADO organization URL, project name, process template, and the path to the export CSV when prompted.

Frequently Asked Questions about hve-resiliency-workitem-import

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

FAQPage Schema
How do I bulk import work items into Azure DevOps from a CSV?

Run the import-ado.ps1 script with the CSV path, organization URL, project name, and process template. It posts each row to the ADO REST API, creates a parent Epic, links children hierarchically, and writes a per-row import log CSV.

How do I group imported work items by priority in Azure DevOps?

Pass the -GroupByPriority switch to the import script. It creates one grouping work item per P0-P3 bucket present in the CSV and links each finding to its matching priority group under the parent.

Does the ADO import support Basic, Agile, and Scrum process templates?

Yes, the -Process parameter accepts Basic, Agile, or Scrum. Bug rows become Issues on Basic, severity and acceptance criteria fields are only set on Agile and Scrum, and group types default to Issue, User Story, or Product Backlog Item respectively.

Why does the ADO import fail with VS402625 work item type does not exist?

This error means the -Process parameter does not match the project's actual process template. Verify the template with az devops project show or the process settings page in ADO, then rerun with the correct value.

Can I test the ADO work item import without creating anything?

Yes, use the -DryRun switch. The script parses and validates the CSV, prints the planned parent, priority groups, and each row's target type, but makes no changes in Azure DevOps.