skills.rest
jasonmichaelbell78-creator
jasonmichaelbell78-creatorCOMMUNITY
Explore all skills by this author →
GitHub

verify-technical-debt

Verify technical debt items and triage VERIFIED ones into ROADMAP sprints.

Updated Feb 24, 2026
Search Tags:#automation#roadmap#verify#triage#code-review#technical-debt
One-click install
npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill verify-technical-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-technical-debt
Source: https://github.com/jasonmichaelbell78-creator/framework/tree/main/.claude/skills/verify-technical-debt
Command: npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill verify-technical-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of growing queues of technical-debt items by providing a structured two-phase workflow to verify items in NEW status and triage VERIFIED items into ROADMAP sprints for approval.

Core Features & Use Cases

  • Phase 1 (Verify): Check each NEW item exists in the codebase and classify as VERIFIED/FALSE_POSITIVE/DUPLICATE/RESOLVED.
  • Phase 2 (Triage): Group VERIFIED items by category and severity, map them to existing ROADMAP.md sprints/milestones, and present placement proposals for approval.
  • Input/Output: Input: docs/technical-debt/views/verification-queue.md; Output: Updated docs/technical-debt/MASTER_DEBT.jsonl and ROADMAP.md.

Quick Start

Invoke the verify-technical-debt skill to verify NEW debt items and triage them into the appropriate ROADMAP sprints.

Frequently Asked Questions about verify-technical-debt

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

FAQPage Schema
How do I automate technical debt triage into roadmap milestones?▼

Automating technical debt triage involves verifying NEW items against the codebase and mapping VERIFIED items into ROADMAP.md sprints. This skill reads verification queues and MASTER_DEBT.jsonl to classify, timestamp, and place items into appropriate milestones.

What is the process for verifying technical debt items in a backlog?▼

Verifying technical debt items requires checking each NEW item against the codebase to classify it as VERIFIED, FALSE_POSITIVE, DUPLICATE, or RESOLVED. The process updates MASTER_DEBT.jsonl with verified_by timestamps and regenerates views.

How do I map verified technical debt to existing sprints?▼

Mapping verified technical debt to sprints involves grouping VERIFIED items by category and severity, then proposing placements into existing ROADMAP.md milestones. The skill presents these mapping proposals for final approval before updating the roadmap.

What file formats do I need for technical debt verification and triage?▼

Technical debt verification and triage requires a markdown verification queue as input and uses JSONL and markdown formats for output. Specifically, it reads verification-queue.md and updates MASTER_DEBT.jsonl alongside ROADMAP.md.

When should I run a technical debt verification workflow?▼

A technical debt verification workflow should be run when NEW debt items exist in the backlog or when verification is overdue. It is specifically designed for routine maintenance, backlog spikes, and audits requiring structured triage.

Related Skills

Explore More Software Engineering Skills→
jtvarisjtvaris

tech-debt

Scan codebases for TODO/FIXME indicators and update a debt register.

Community
Advanced
sidunrealdesidunrealde

plan-milestone-gaps

Create project phases from milestone audit results and update ROADMAP.md and REQUIREMENTS.md.

Community
Advanced
JesusFilmJesusFilm
25

file-todos

Create and manage Markdown todos with YAML frontmatter for code review feedback.

Official
Advanced
oalansilvaoalansilva

tech-debt-portfolio

Catalog tech debt items, impacts, and dependencies to generate a prioritized roadmap.

Community
Intermediate