skills.rest
nroze22
nroze22COMMUNITY
Explore all skills by this author →
GitHub

technical-debt-tracking

Identify, prioritize, and track technical debt with Jira stories.

1|1|Updated Feb 24, 2026
Search Tags:#code quality#compliance#technical debt#risk management#jira integration#edc systems
One-click install
npx skills add https://github.com/nroze22/TalosixSkills --skill technical-debt-tracking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-debt-tracking
Source: https://github.com/nroze22/TalosixSkills/tree/main/.claude/skills/technical-debt-tracking
Command: npx skills add https://github.com/nroze22/TalosixSkills --skill technical-debt-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams systematically identify, document, prioritize, and track technical debt, especially within regulated environments like clinical trial EDC systems, mitigating associated risks.

Core Features & Use Cases

  • Automated Detection: Scans code for common debt indicators like TODOs, warnings, and complexity issues.
  • Manual Identification: Provides categories for architectural, code, test, documentation, infrastructure, security, compliance, and data debt.
  • Prioritization Framework: Uses a Risk-Effort-Impact matrix to score and prioritize debt items.
  • Jira Integration: Generates structured Jira stories for tracking and management.
  • Metric Tracking: Defines key metrics and reporting for quarterly debt reviews.
  • Use Case: A development team can use this skill to identify and create Jira tickets for all instances of duplicated code and missing audit trails in their EDC system, prioritizing compliance-related debt for immediate remediation.

Quick Start

Use the technical-debt-tracking skill to identify and document all instances of compliance debt within the codebase.

Frequently Asked Questions about technical-debt-tracking

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

FAQPage Schema
How do I track technical debt in clinical trial EDC systems?▼

To track technical debt in clinical trial EDC systems, you can scan code for common debt indicators like TODOs and missing audit trails, categorize compliance risks, and generate structured Jira stories for remediation.

What is the best way to prioritize technical debt for remediation?▼

The best way to prioritize technical debt is using a Risk-Effort-Impact matrix to score items, ensuring compliance and security debt in regulated software systems are addressed based on their potential impact.

Can I generate Jira stories directly from identified code quality issues?▼

Yes, you can generate Jira stories directly from identified code quality issues. The process automates detection of code complexity and warnings, then formats them into structured tickets for management.

How do you categorize technical debt in a regulated software environment?▼

You categorize technical debt in a regulated environment by grouping issues into architectural, code, test, documentation, infrastructure, security, compliance, and data debt categories for manual identification.

Does this approach to technical debt tracking work without external dependencies?▼

Yes, this approach to technical debt tracking works without external dependencies. It uses internal scripts and references to identify debt, implement prioritization frameworks, and define metrics for quarterly reviews.

Related Skills

Explore More Software Engineering Skills→
ConsiliencyConsiliency
8

security-audit

Scan codebases for OWASP vulnerabilities and generate prioritized remediation reports.

Official
Intermediate
paimlpaiml
161

Code Quality Analysis with PMAT

Analyze code quality and technical debt with PMAT metrics.

Official
Advanced
dgethingsdgethings

atlassian-itsm

Automate Jira and Confluence ITSM workflows with human-in-the-loop governance.

Community
Advanced
GDSDNGDSDN
3

qa-review-story

Scan code with CodeRabbit and fix critical, high, and medium severity issues.

Community
Advanced