work-item-management-expert

Generates work item creation and update commands for GitHub Issues, Projects v2, and Azure DevOps Boards.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/psmfd/pi-config --skill work-item-management-expert-psmfd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-item-management-expert
Source: https://github.com/psmfd/pi-config/tree/main/agent/skills/work-item-management-expert
Command: npx skills add https://github.com/psmfd/pi-config --skill work-item-management-expert-psmfd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams working across GitHub and Azure DevOps struggle to apply consistent work item taxonomy — types, labels, fields, hierarchy, and state models differ sharply between platforms, and CLI/REST syntax is error-prone. This Skill provides a read-only reference that discovers live taxonomy and outputs correct, runnable commands without executing mutations itself. ## Core Features & Use Cases - Cross-platform taxonomy reference: Covers GitHub Issues, Projects v2 fields, and Azure DevOps Boards process models (Basic, Agile, Scrum, CMMI) with field reference names, link types, and WIQL. - Read-only command generation: Discovers live state with read commands and emits gh, az boards, or REST JSON Patch commands for the user to run, never mutating directly. - Frozen-script routing: When a project contains scripts/wim/, routes all work item creation through its manifest-driven scripts instead of raw CLI commands. - Use Case: A user asks to file a bug in Azure DevOps with severity and repro steps; the Skill outputs the exact az boards work-item create command with correct Microsoft.VSTS.* field reference names and cites first-party documentation. ## Quick Start Ask the assistant to draft the commands for creating a user story in Azure DevOps or a labeled GitHub issue, and it will return runnable commands with the correct fields and labels.

Frequently Asked Questions about work-item-management-expert

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

FAQPage Schema
How do I create a work item in Azure DevOps from the command line?▼

Use az boards work-item create with --title, --type, and --fields for values like StoryPoints or Priority. Always use field reference names such as Microsoft.VSTS.Scheduling.StoryPoints, and note that --area and --iteration take the short form without the project prefix.

How do GitHub Issues map to Azure DevOps work item types?▼

GitHub has no enforced type system, so labels approximate ADO types: the bug label maps to Bug in Agile, Scrum, and CMMI, while enhancement maps to User Story, PBI, or Requirement. Tasklists and the Projects v2 parent field correspond to ADO parent-child hierarchy links.

Why does the GitHub sub-issues API return HTTP 422?▼

The sub-issues endpoint requires sub_issue_id as a JSON integer. Using gh api -f sends it as a string and fails with 422; use gh api -F sub_issue_id=N instead, which sends the typed value.

Does this skill execute gh or az commands directly?▼

No, it is read-only by default. It runs read commands like gh issue list and az boards query to discover live state, then outputs create, update, and delete commands for the user to execute themselves.

What happens when a project has a scripts/wim directory?▼

All work item creation must route through the frozen scripts in scripts/wim/ by authoring a manifest.json and invoking apply-manifest.sh. The scripts must never be edited; unsupported needs are surfaced to the orchestrator as blocking gaps.