skills.rest
mec07
mec07COMMUNITY
Explore all skills by this author →
GitHub

TechDebt

Create Jira tech debt tickets from brief notes with duplicate checks.

1|Updated Apr 2, 2026
Search Tags:#automation#workflow#jira#tech-debt#duplicate-detection#ticket-creation#epic-link
One-click install
npx skills add https://github.com/mec07/claude_skills --skill techdebt-mec07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: TechDebt
Source: https://github.com/mec07/claude_skills/tree/main/stow/TechDebt
Command: npx skills add https://github.com/mec07/claude_skills --skill techdebt-mec07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts brief notes about technical debt into consistent, well-structured Jira tickets, reducing drafting time and errors while keeping debt work organized in the project workflow.

Core Features & Use Cases

  • Duplicate detection against open issues to prevent creating redundant tickets.
  • AI-assisted expansion of a brief note into a full ticket description with clear problem, impact, and steps.
  • Automated ticket creation with project, issue type, priority, assignee, and epic linkage; supports opening and reviewing the ticket instantly.
  • Related-tickets workflow: link related debts or epics to keep remediation tracked.

Quick Start

Describe the tech debt briefly and run the ticket creation workflow.

Frequently Asked Questions about TechDebt

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

FAQPage Schema
How do I create Jira tickets for technical debt from quick notes?▼

To create Jira tech debt tickets from quick notes, this Skill automates the conversion of brief descriptions into structured issues with standard metadata, duplicate detection, and epic linkage for organized remediation.

Can I prevent duplicate Jira issues when logging technical debt?▼

Yes, you can prevent duplicate Jira issues because this Skill performs duplicate checks against open issues before creating new tickets, ensuring redundant debt entries are avoided.

How does AI expansion work for Jira ticket descriptions?▼

AI expansion for Jira ticket descriptions works by taking a brief note and automatically generating a full ticket description with clear problem, impact, and steps for structured remediation.

What is the best way to link technical debt tickets to related epics in Jira?▼

The best way to link technical debt tickets to related epics in Jira is through automated epic linkage, which organizes debt work within the project workflow during ticket creation.

Does this tech debt ticket creation workflow support assigning priority and assignee?▼

Yes, this tech debt ticket creation workflow supports assigning project, issue type, priority, and assignee automatically when creating the Jira ticket from your note.

What are the limitations of automating tech debt ticket creation from notes?▼

A key limitation is that automating tech debt ticket creation relies on the quality of the brief note input; while AI expands the description, unclear notes may result in less accurate ticket metadata.

Related Skills

Explore More Software Engineering Skills→
rchandnaWUSTLrchandnaWUSTL
14

Map Customer Asks to Existing Jira Issues

Match customer asks to existing open Jira issues from a JSON snapshot.

Community
Intermediate
cuongtl1992cuongtl1992
10

project-management

Automate Jira and Confluence workflows for project management tasks.

Community
Advanced
openshift-engopenshift-eng
7

edge-ic:sprint-status

Query Jira sprint tickets and group them by workflow status.

Official
Intermediate
hirokimryhirokimry
1

release-epic

Create a GitHub release pull request after verifying all child issues are closed.

Community
Advanced