azure-devops-work-item-creation

Create and link Azure DevOps work items from markdown files.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/onshoreoutsourcing/lighthouse-beacon --skill azure-devops-work-item-creation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-devops-work-item-creation
Source: https://github.com/onshoreoutsourcing/lighthouse-beacon/tree/main/.claude/skills/azure-devops-work-item-creation
Command: npx skills add https://github.com/onshoreoutsourcing/lighthouse-beacon --skill azure-devops-work-item-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the end-to-end creation and hierarchical linking of Azure DevOps work items (Epics, Features, User Stories) from structured markdown documentation, eliminating manual entry and ensuring consistency.

Core Features & Use Cases

  • Automated parsing: Read epic/feature/sprint markdown files to extract IDs, names, statuses, priorities, and tasks.
  • UCP integration: Compute Objective UCP via the ucp-calculator skill and inject it into work items.
  • Hierarchical linking: Automatically link Epics -> Features -> User Stories to preserve traceability.
  • Batch creation: Generate MCP-ready payloads for single or batched work item creation with proper field mappings.

Quick Start

  1. Write a markdown epic/feature/sprint file following the templates.
  2. Run the workflow to parse the markdown and calculate UCP, then format for Azure DevOps MCP.
  3. Execute the MCP tool calls to create items and establish parent links.

Frequently Asked Questions about azure-devops-work-item-creation

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

FAQPage Schema
How do I automate Azure DevOps work item creation from markdown files?

Automating Azure DevOps work item creation involves parsing structured markdown files to extract details and generating MCP-ready payloads for batch creation. This process reads epic and sprint documentation to automatically format and generate work items.

Can I automatically link Epics, Features, and User Stories in Azure DevOps?

Automatically linking Epics, Features, and User Stories preserves hierarchical relationships and traceability in Azure DevOps. The workflow parses markdown sources to establish parent-child links between generated work items during batch creation.

How do I calculate and inject Objective UCP into Azure DevOps work items?

Calculating Objective UCP for Azure DevOps work items requires integrating with the ucp-calculator to compute values from markdown sources. The computed UCP results are then injected directly into the generated MCP tooling payloads.

What is the best way to batch create Azure DevOps work items from markdown?

Batch creating Azure DevOps work items from markdown is best handled by parsing structured documentation to extract IDs and tasks, then formatting MCP-ready payloads. This ensures proper field mappings and hierarchical linking for single or batched entries.

Do I need specific markdown templates to generate Azure DevOps work items?

Specific markdown templates are required to generate Azure DevOps work items accurately. Writing epic, feature, or sprint markdown files following the predefined templates ensures the parser can correctly extract IDs, names, statuses, priorities, and tasks.

Why does markdown parsing fail to create Azure DevOps work items properly?

Markdown parsing fails to create Azure DevOps work items when the source files deviate from required templates, breaking the extraction of IDs, names, and tasks. Proper structure is essential to format MCP-ready payloads and establish parent links.