ticket-enrich

Enrich Jira tickets with metadata, priority, estimates, and acceptance criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill ticket-enrich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-enrich
Source: https://github.com/afoxnyc3/chelsea-piers-itops/tree/main/plugins/jira-pm/skills/ticket-enrich
Command: npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill ticket-enrich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Poorly written or incomplete Jira tickets slow down triage and planning by missing the metadata, structure, and context teams need to execute quickly.

Core Features & Use Cases

  • Ticket enrichment from a single source: Analyzes and proposes improvements across category tagging, priority inference, story point estimation, acceptance criteria, description expansion, related issue links, and epic assignment.
  • Actionable before/after review: Presents one consolidated before/after diff for all proposed changes and writes only after confirmation.
  • Best-fit for backlog hygiene: Ideal when tickets are created quickly with minimal detail, acceptance criteria are missing for stories, or backlog grooming requires consistent structure and routing.

Quick Start

Ask to enrich a specific issue key by saying: "enrich this ticket CPOPS-123".

Frequently Asked Questions about ticket-enrich

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

FAQPage Schema
How do I add missing acceptance criteria and story points to thin Jira tickets?

Enriching thin Jira tickets involves analyzing existing issue fields to propose missing acceptance criteria, infer priority, and estimate story points. This process transforms under-specified descriptions into structured, actionable work items for backlog grooming.

What is the best way to automate backlog grooming for under-specified Jira stories?

The best way to automate backlog grooming for under-specified Jira stories is to enrich tickets across multiple dimensions like category tagging and epic assignment. This approach generates a consolidated before/after diff for approval before writing updates.

Can I infer priority and estimate story points for Jira tickets automatically?

Yes, you can infer priority and estimate story points for Jira tickets automatically by reading issue fields through the Atlassian MCP server. The system proposes these values alongside expanded descriptions and gates the writes behind a single user confirmation.

Does Jira ticket enrichment work with the Atlassian MCP server?

Yes, Jira ticket enrichment works with the Atlassian MCP server to read issue fields and coordinate up to seven enrichment dimensions. It requires this connection to analyze ticket data and propose metadata improvements like related issue links.

How do I review proposed changes before updating enriched Jira tickets?

You review proposed changes before updating enriched Jira tickets by examining a consolidated before/after diff covering all dimensions. The system gates all writes behind a single user confirmation to ensure accurate backlog updates.

When should I avoid automated ticket enrichment for IT operations planning?

You should avoid automated ticket enrichment when a Jira ticket already contains comprehensive metadata, clear priority, and defined acceptance criteria. It is designed specifically for under-specified descriptions and missing metadata during JSM intake and backlog grooming.