onus:work-item-handler

Fetches and manages work items from GitHub, JIRA, and Azure DevOps.

1|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/flexion/claude-domestique --skill onus-work-item-handler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onus:work-item-handler
Source: https://github.com/flexion/claude-domestique/tree/main/onus/skills/work-item-handler
Command: npx skills add https://github.com/flexion/claude-domestique --skill onus-work-item-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of fetching and managing work items from various issue trackers, reducing the manual overhead of project management tasks.

Core Features & Use Cases

  • Issue Fetching: Retrieve details for specific work items using issue numbers.
  • Tracker Integration: Supports GitHub Issues, JIRA, and Azure DevOps.
  • Use Case: When you reference an issue number like #42 or PROJ-123 in your conversation, this skill can fetch the title, description, and status of that issue to provide context.

Quick Start

Use the onus skill to fetch issue number 42.

Frequently Asked Questions about onus:work-item-handler

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

FAQPage Schema
How do I fetch GitHub issue details using an issue number in my conversation?

To fetch GitHub issue details, reference an issue number like #42 in your conversation. The skill retrieves the title, body, state, and labels to provide context and automates the work item management process.

Can I retrieve JIRA work items by referencing an issue key directly?

Yes, you can retrieve JIRA work items by referencing an issue key like PROJ-123. The skill fetches the title, description, and status from integrated issue trackers including JIRA and Azure DevOps.

Does this work with Azure DevOps issue tracking or just GitHub Issues?

This works with Azure DevOps issue tracking, GitHub Issues, and JIRA. It fetches work item details including number, title, body, state, and labels across all supported trackers with caching for efficiency.

What is the best way to clarify task scope using issue tracker integration?

To clarify task scope, reference your work item number or key. The skill fetches the issue title, description, state, and labels from your integrated tracker to provide immediate context for requirement inquiries.

Do I need to manually copy issue descriptions when inquiring about requirements?

No, you do not need to manually copy issue descriptions. The skill automates retrieval of issue details including title, body, state, and labels when you reference an issue number or key in conversation.

Why does this skill cache work item details from integrated issue trackers?

This skill caches work item details from integrated issue trackers to improve efficiency during repeated retrieval. Caching automates fetching details like title, body, state, and labels when referencing issue numbers.